Re: Search for patched yaboot testers ...
On Nov 13, 2004, at 8:44 AM, Sven Luther wrote: On Fri, Nov 12, 2004 at 04:54:46PM -0500, Rick Thomas wrote: I got a chance to do an install from your mini.iso on a test machine. It's a G4 350 MHz (AGP graphics). I'm not clear as to whether this will install your test yaboot or not, but here's what happened: This will use my test yaboot for booting from the CD. I booted off the CD and chose the default (i.e. non-expert) install at the boot: prompt. I answered all the i18n questions with the default (US-English) and configured the network manually (no DHCP on this net). I chose the debain.rutgers.edu mirror because it's located in the next building over on the same campus and I have a 100-Mbit connection via campus LAN to it from the test machine. (I'm used to doing installs over a fairly fast cable-modem that gets about 4 Mbit/sec on a good day. This was *much* faster. -8) When it came time to partition the disk, I chose a guided partitioning, and it set me up with a 1 MB boot partition, a 4 GB root partition, and a 260 MB swap partition. Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. This is definitively a bug, could you fill a bug report about this ? i guess quil-installer or debian-installer are the packages to report a bug against. As I understand the discussion so far, this is just a bug in the mini.iso, and will not affect the netinst or businesscard .iso images. And nobody is interested in fixing the mini.iso problem, so there's no point in filing a bug report at this time. When the first phase was over, and it came time for the reboot, everything went completely as expected, and I finished the installation after an uneventful reboot. If this was using your new yaboot, then I'd say the test was successful. Well, to test booting from the disk, you need to install my yaboot .deb, run ybin, and try rebooting. If this sequence does *not* exercise your new yaboot, please give me instructions for what to do next. I'll be in Atlanta for the USENIX/LISA conference all next week, so my next opportunity for testing will be a week from now. Ok. So what I need now is a pointer to your patched yaboot .deb file. Can you give me a URL or whatever it is I need? Thanks, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Mon, Nov 22, 2004 at 03:23:09PM -0500, Rick Thomas wrote: So what I need now is a pointer to your patched yaboot .deb file. Can you give me a URL or whatever it is I need? http://people.debian.org/~luther/yaboot the -1 one is just patched, while the -2 has full debug on too. Notice that both Warren and Ethan seems to be ok, and there will be an upload to unstable of this patched version soon. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Mon, Nov 15, 2004 at 11:43:02PM -0500, Rick Thomas wrote: On Nov 15, 2004, at 12:41 PM, Sven Luther wrote: On Mon, Nov 15, 2004 at 12:29:09PM -0500, Rick Thomas wrote: I was going to wait until I could try it with a normal image. I assume that this means I would not have encountered this problem then. So should I submit a bug report against monolithic, or is it a known problem -- bug report would be redundant? monolithic is mostly there only for testing and development, so it should not be important. Ethan just said he had only very few success reports, and would like more testing, despite the tests i already got, and Leigh Brown haven tested it successfully on his 7043-140 or whatever it was. Both HD and CD, since NET is broken anyway on this one ? Colin, could i ask you to test the patch and write a it works report to the bug report, and Rick, did you ever fill a followup to the bug report, could you please do so, and any others that have tested it provide feedback too ? I believe I did file a followup to the bug report. If I didn't, I will as soon as I get a chance to try installing your patched yaboot .deb and run ybin -- next week when I have access to the hardware again (I'll be in Atlanta until Sunday evening. Monday will be my first day at work -- where the test machine is located.) Sorry I can't be quicker about this. Life keeps getting in the way! Ok, no problem. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Sat, Nov 13, 2004 at 02:44:59PM +0100, Sven Luther wrote: On Fri, Nov 12, 2004 at 04:54:46PM -0500, Rick Thomas wrote: Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. This is definitively a bug, could you fill a bug report about this ? i guess quil-installer or debian-installer are the packages to report a bug against. monolithic is like that; it includes both quik-installer and yaboot-installer, bypassing the XB-Subarchitecture: control field checks. It's not a problem for normal images. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
I was going to wait until I could try it with a normal image. I assume that this means I would not have encountered this problem then. So should I submit a bug report against monolithic, or is it a known problem -- bug report would be redundant? Rick On Nov 15, 2004, at 11:17 AM, Colin Watson wrote: On Sat, Nov 13, 2004 at 02:44:59PM +0100, Sven Luther wrote: On Fri, Nov 12, 2004 at 04:54:46PM -0500, Rick Thomas wrote: Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. This is definitively a bug, could you fill a bug report about this ? i guess quil-installer or debian-installer are the packages to report a bug against. monolithic is like that; it includes both quik-installer and yaboot-installer, bypassing the XB-Subarchitecture: control field checks. It's not a problem for normal images. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Mon, Nov 15, 2004 at 12:29:09PM -0500, Rick Thomas wrote: I was going to wait until I could try it with a normal image. I assume that this means I would not have encountered this problem then. Indeed. So should I submit a bug report against monolithic, or is it a known problem -- bug report would be redundant? You could file a bug report against quik-installer,yaboot-installer asking them to duplicate the subarchitecture checks in .isinstallable control files, I guess. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Mon, Nov 15, 2004 at 12:29:09PM -0500, Rick Thomas wrote: I was going to wait until I could try it with a normal image. I assume that this means I would not have encountered this problem then. So should I submit a bug report against monolithic, or is it a known problem -- bug report would be redundant? monolithic is mostly there only for testing and development, so it should not be important. Ethan just said he had only very few success reports, and would like more testing, despite the tests i already got, and Leigh Brown haven tested it successfully on his 7043-140 or whatever it was. Both HD and CD, since NET is broken anyway on this one ? Colin, could i ask you to test the patch and write a it works report to the bug report, and Rick, did you ever fill a followup to the bug report, could you please do so, and any others that have tested it provide feedback too ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Nov 15, 2004, at 12:41 PM, Sven Luther wrote: On Mon, Nov 15, 2004 at 12:29:09PM -0500, Rick Thomas wrote: I was going to wait until I could try it with a normal image. I assume that this means I would not have encountered this problem then. So should I submit a bug report against monolithic, or is it a known problem -- bug report would be redundant? monolithic is mostly there only for testing and development, so it should not be important. Ethan just said he had only very few success reports, and would like more testing, despite the tests i already got, and Leigh Brown haven tested it successfully on his 7043-140 or whatever it was. Both HD and CD, since NET is broken anyway on this one ? Colin, could i ask you to test the patch and write a it works report to the bug report, and Rick, did you ever fill a followup to the bug report, could you please do so, and any others that have tested it provide feedback too ? I believe I did file a followup to the bug report. If I didn't, I will as soon as I get a chance to try installing your patched yaboot .deb and run ybin -- next week when I have access to the hardware again (I'll be in Atlanta until Sunday evening. Monday will be my first day at work -- where the test machine is located.) Sorry I can't be quicker about this. Life keeps getting in the way! Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Fri, Nov 12, 2004 at 04:54:46PM -0500, Rick Thomas wrote: On Nov 10, 2004, at 6:01 AM, Sven Luther wrote: On Wed, Nov 10, 2004 at 03:46:58AM -0500, Rick Thomas wrote: The new yaboot seems to work at least on one of my machines. I'll try some others later. Specifically, I tried it on my BlueWhite G3. I booted holding down the C key (ADB keyboard) and got the yaboot messages. At the boot: prompt, I typed expert video=ofonly and it did the expected things. In fact everything proceeded as expected til I Ok, thanks, can you forward info about this to the bug report ? It is : [EMAIL PROTECTED] got to the partitioner, which hung up trying to look at the partitions on the disk on my SIIG Ultra ATA 133/100 Pro IDE controller PCI card. The dmesg command on the F2 console showed a bunch of messages hdg: dma_timeout_expiry: dma status == 0x24 AEC62XX timeout 4hdg: lost interrupt I've seen this before with 2.6 kernels. I've reported it to the list in installation reports, but nobody seems to care. Can you fill a bug report about this against the powerpc kernel-image-2.6.8-powerpc ? It seems to be a powerpc kernel problem. So I was unable to proceed any further on that machine. ... later ... I also tried it on my grey G4 minitower 733MHz. Worked fine up to partitioning disks. This is a production machine with no free disk partitions, so I couldn't proceed any further than that. I've got a G4 450MHz at work with some free partitions, so I'll try a full install there tomorrow. You tried only CD booting method, not net or disk, right ? What was the bug number of the bug report you wanted me to reply to for the new yaboot? See above. I got a chance to do an install from your mini.iso on a test machine. It's a G4 350 MHz (AGP graphics). I'm not clear as to whether this will install your test yaboot or not, but here's what happened: This will use my test yaboot for booting from the CD. I booted off the CD and chose the default (i.e. non-expert) install at the boot: prompt. I answered all the i18n questions with the default (US-English) and configured the network manually (no DHCP on this net). I chose the debain.rutgers.edu mirror because it's located in the next building over on the same campus and I have a 100-Mbit connection via campus LAN to it from the test machine. (I'm used to doing installs over a fairly fast cable-modem that gets about 4 Mbit/sec on a good day. This was *much* faster. -8) When it came time to partition the disk, I chose a guided partitioning, and it set me up with a 1 MB boot partition, a 4 GB root partition, and a 260 MB swap partition. Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. This is definitively a bug, could you fill a bug report about this ? i guess quil-installer or debian-installer are the packages to report a bug against. When the first phase was over, and it came time for the reboot, everything went completely as expected, and I finished the installation after an uneventful reboot. If this was using your new yaboot, then I'd say the test was successful. Well, to test booting from the disk, you need to install my yaboot .deb, run ybin, and try rebooting. If this sequence does *not* exercise your new yaboot, please give me instructions for what to do next. I'll be in Atlanta for the USENIX/LISA conference all next week, so my next opportunity for testing will be a week from now. Ok. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Search for patched yaboot testers ...
On Nov 10, 2004, at 6:01 AM, Sven Luther wrote: On Wed, Nov 10, 2004 at 03:46:58AM -0500, Rick Thomas wrote: The new yaboot seems to work at least on one of my machines. I'll try some others later. Specifically, I tried it on my BlueWhite G3. I booted holding down the C key (ADB keyboard) and got the yaboot messages. At the boot: prompt, I typed expert video=ofonly and it did the expected things. In fact everything proceeded as expected til I Ok, thanks, can you forward info about this to the bug report ? It is : [EMAIL PROTECTED] got to the partitioner, which hung up trying to look at the partitions on the disk on my SIIG Ultra ATA 133/100 Pro IDE controller PCI card. The dmesg command on the F2 console showed a bunch of messages hdg: dma_timeout_expiry: dma status == 0x24 AEC62XX timeout 4hdg: lost interrupt I've seen this before with 2.6 kernels. I've reported it to the list in installation reports, but nobody seems to care. Can you fill a bug report about this against the powerpc kernel-image-2.6.8-powerpc ? It seems to be a powerpc kernel problem. So I was unable to proceed any further on that machine. ... later ... I also tried it on my grey G4 minitower 733MHz. Worked fine up to partitioning disks. This is a production machine with no free disk partitions, so I couldn't proceed any further than that. I've got a G4 450MHz at work with some free partitions, so I'll try a full install there tomorrow. You tried only CD booting method, not net or disk, right ? What was the bug number of the bug report you wanted me to reply to for the new yaboot? See above. I got a chance to do an install from your mini.iso on a test machine. It's a G4 350 MHz (AGP graphics). I'm not clear as to whether this will install your test yaboot or not, but here's what happened: I booted off the CD and chose the default (i.e. non-expert) install at the boot: prompt. I answered all the i18n questions with the default (US-English) and configured the network manually (no DHCP on this net). I chose the debain.rutgers.edu mirror because it's located in the next building over on the same campus and I have a 100-Mbit connection via campus LAN to it from the test machine. (I'm used to doing installs over a fairly fast cable-modem that gets about 4 Mbit/sec on a good day. This was *much* faster. -8) When it came time to partition the disk, I chose a guided partitioning, and it set me up with a 1 MB boot partition, a 4 GB root partition, and a 260 MB swap partition. Then, for some reason I don't understand, it tried to install the quik bootloader. This is definitely a NewWorld machine, so it should have known better -- I would think! In any case, that got an error, and it offered to let me install yaboot instead, which I did. When the first phase was over, and it came time for the reboot, everything went completely as expected, and I finished the installation after an uneventful reboot. If this was using your new yaboot, then I'd say the test was successful. If this sequence does *not* exercise your new yaboot, please give me instructions for what to do next. I'll be in Atlanta for the USENIX/LISA conference all next week, so my next opportunity for testing will be a week from now. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
