Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote:On Thursday 21 December 2006 03:03, Dan Oglesby wrote: Could you file one new installation report for the issue that you need to press enter 4 times to get the root floppy loaded so we can keep track of that? I think that is now the only issue remaining. Let's investigate the issue below a bit further in this report, but I'd still appreciate a new report for the issue above so we can reassign it properly and don't have to wade through all the history in this one. Done. I sent an email regarding the installation floppy switch issues a few minutes ago. The install completes on the SS5-70, but will not successfully boot after install. It doesn't appear to load the esp module from the initfs, and cannot locate the root filesystem. OK. Let's start with the basic questions: - what are the last messages (10-15) on the console? - do you get dropped into a debug shell on the failure? - if so, please check: - if the module is present in the initrd (ls /lib/modules/) - if the module is loaded (lsmod) - if the module is listed in /etc/modules or in /etc/initramfs-tools/modules or similar - if the device is recognized at all (dmesg) I'm confident the installation process is correct with regards to the module. I verified that the disk I had in the SS5-70 would in fact boot with no modifications in an SS5-170 and the SS20 systems I have at my disposal. All I did was move the drive between the systems, and power up. All systems booted to a prompt. So, the SS5-70 system is not loading the esp module during boot from the initfs for some reason. It does load and configure the esp module automatically during the installation process. I have the console up with a failed boot on the SS5-70. On the systems that boot successfully (SS20 and SS5-170), I do see where the esp module is loaded and the output it generates when the drives and SCSI devices are detected. I do not see this output when I boot the SS5-70 system. The only lines that appear to be error messages are the last four, which are: VFS: Cannot open root device sda2 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing; VFS: Unable to mount root fs on unknown-block(0,0) 0Press Stop-A (L1-A) to return to the boot prom Pressing L1-A does nothing, and I am not dropped to a debug shell, or see an option at any time for a debug shell. The only way to reset the system is to power cycle it at this point. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: Hi, Sorry for delay. I had to concentrate on other work for a bit. Not a problem at all. I know how that goes. :-) On Thursday 21 December 2006 03:03, Dan Oglesby wrote: Could you file one new installation report for the issue that you need to press enter 4 times to get the root floppy loaded so we can keep track of that? I think that is now the only issue remaining. Let's investigate the issue below a bit further in this report, but I'd still appreciate a new report for the issue above so we can reassign it properly and don't have to wade through all the history in this one. I'll open a new bug report for the SS5 machines when I return from vacation (after Jan 3rd). The install completes on the SS5-70, but will not successfully boot after install. It doesn't appear to load the esp module from the initfs, and cannot locate the root filesystem. OK. Let's start with the basic questions: - what are the last messages (10-15) on the console? - do you get dropped into a debug shell on the failure? - if so, please check: - if the module is present in the initrd (ls /lib/modules/) - if the module is loaded (lsmod) - if the module is listed in /etc/modules or in /etc/initramfs-tools/modules or similar - if the device is recognized at all (dmesg) I poked around right before leaving vacation, so I can answer some of the questions right now. The last thing that appears on the console is an error message stating the root filesystem could not be located when the system tries to switch from the initfs image to the / partition on the disk. The esp module is present in the initfs image, but does not appear to load. It is listed in /etc/modules in the initfs image as well. I cannot drop to a debug shell, or even do a Stop-A to get to PROM at the point the system locks up. It is totally unresponsive to keyboard input at the point where the root filesystem fails to mount. This is with a Sun5c keyboard and a CG6 framebuffer for a console. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Hi, Sorry for delay. I had to concentrate on other work for a bit. On Thursday 21 December 2006 03:03, Dan Oglesby wrote: Could you file one new installation report for the issue that you need to press enter 4 times to get the root floppy loaded so we can keep track of that? I think that is now the only issue remaining. Let's investigate the issue below a bit further in this report, but I'd still appreciate a new report for the issue above so we can reassign it properly and don't have to wade through all the history in this one. The install completes on the SS5-70, but will not successfully boot after install. It doesn't appear to load the esp module from the initfs, and cannot locate the root filesystem. OK. Let's start with the basic questions: - what are the last messages (10-15) on the console? - do you get dropped into a debug shell on the failure? - if so, please check: - if the module is present in the initrd (ls /lib/modules/) - if the module is loaded (lsmod) - if the module is listed in /etc/modules or in /etc/initramfs-tools/modules or similar - if the device is recognized at all (dmesg) Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: On Wednesday 20 December 2006 05:18, Dan Oglesby wrote: Just completed a flawless install of Debian off of the 2006-12-19 floppy images on the SS20 system. All hardware detected automatically, no errors during the install, and the system rebooted to a login prompt. Great! Thanks for following up. As this report has now become a bit long and difficult to follow, I'm closing it. Could you file one new installation report for the issue that you need to press enter 4 times to get the root floppy loaded so we can keep track of that? I think that is now the only issue remaining. Cheers, FJP If possible, could you wait until I verify the same process works on the SparcStation 5? The install is almost finished, I think all that will be left by the time I get home is to reboot the system. If that works, then I'm sure we're out of the woods on this one. I'll submit a new bug report for the 4 x ENTER issue booting off the floppy when I get home tonight. Thanks! --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: On Wednesday 20 December 2006 05:18, Dan Oglesby wrote: Just completed a flawless install of Debian off of the 2006-12-19 floppy images on the SS20 system. All hardware detected automatically, no errors during the install, and the system rebooted to a login prompt. Great! Thanks for following up. As this report has now become a bit long and difficult to follow, I'm closing it. Could you file one new installation report for the issue that you need to press enter 4 times to get the root floppy loaded so we can keep track of that? I think that is now the only issue remaining. Cheers, FJP The install completes on the SS5-70, but will not successfully boot after install. It doesn't appear to load the esp module from the initfs, and cannot locate the root filesystem. So, the install process is fine on the SS20, but still does not install properly on an SS5 system. There were no errors that I saw during the installation process. Onboard ethernet and SCSI were detected automatically during the install. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Dan Oglesby [EMAIL PROTECTED] wrote: Frans Pop [EMAIL PROTECTED] wrote: On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: All of my hardware in the SS5-70 is detected automatically by the 2006-12-16 floppy images. The older floppies would not automatically detect the onboard ethernet chipset (sunlance), so I had to choose the module manually during the install after it failed to detect any networking hardware. When I was doing the installs on the SS20, I had to manually choose an ethernet chipset module and the SCSI module. This was with floppies older than the 2006-12-16 images. I will retest the SS20 with the latest floppy images tonight. --Dan Just completed a flawless install of Debian off of the 2006-12-19 floppy images on the SS20 system. All hardware detected automatically, no errors during the install, and the system rebooted to a login prompt. Started the install to the SS5-70 just now. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Sunday 17 December 2006 06:03, Dan Oglesby wrote: The installation went perfect, all hardware detected (network, SCSI controller, and hard drive), drive partitioned just fine. After rebooting, it looks like the SCSI controller module is missing from the initial ramdisk again. System boots from the hard drive, then can't find the root filesystem (can't open root device). Is this the esp module again or a different one? This is strange because the installer should add the esp module in /etc/initramfs-tools/modules, which in turn should ensure that the initrd contains and loads it. Could you check if esp is listed in /etc/initramfs-tools/modules? Could you check if the initrd actually contains the module or not (should be under /lib/modules/...; you can check when dropped into the debug shell)? Does this need to go into a seperate bug report since it is a different system (but same architecture as the SS20 I've been using)? No, as there are no different issues I don't think a separate report adds anything. Thanks very much for your tests! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: Both boots I had to manually tell it to load the lance module for my onboard NIC. I can't find a lance module, so I guess you mean sunlance. What exactly do you mean by both boots? Does the NIC get detected automatically by the installer or not? If it does get detected by the installer, it should automatically add the module to /etc/modules for the installed system. Could you check if it is listed in that file? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: On Sunday 17 December 2006 06:03, Dan Oglesby wrote: The installation went perfect, all hardware detected (network, SCSI controller, and hard drive), drive partitioned just fine. After rebooting, it looks like the SCSI controller module is missing from the initial ramdisk again. System boots from the hard drive, then can't find the root filesystem (can't open root device). Is this the esp module again or a different one? It's esp again. This is strange because the installer should add the esp module in /etc/initramfs-tools/modules, which in turn should ensure that the initrd contains and loads it. I'm pretty sure it's in the initramfs image. I booted from the floppies, switched to the 2nd and 3rd virtual console and started poking around last night. Could you check if esp is listed in /etc/initramfs-tools/modules? Could you check if the initrd actually contains the module or not (should be under /lib/modules/...; you can check when dropped into the debug shell)? It is listed there, and I did see the esp module where I thought it was supposed to be (with the kernel modules). I will verify this again tonight, as I am away from the machine right now (work). I did not get dropped to a debug shell. The system hung, and I couldn't even do a Stop-A on the keyboard to drop to PROM. I had to cycle the power, boot like I'm doing an install (rescue and expert doesn't work from SILO, fails to locate the root filesystem after booting the kernel). I booted like I was doing an install, let it detect all the hardware, then switched to the 2nd and 3rd virtual consoles to do the troubleshooting. Does this need to go into a seperate bug report since it is a different system (but same architecture as the SS20 I've been using)? No, as there are no different issues I don't think a separate report adds anything. Thanks very much for your tests! No problem! :-) --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: Both boots I had to manually tell it to load the lance module for my onboard NIC. I can't find a lance module, so I guess you mean sunlance. Sorry, I meant sunlance. What exactly do you mean by both boots? Does the NIC get detected automatically by the installer or not? If it does get detected by the installer, it should automatically add the module to /etc/modules for the installed system. Could you check if it is listed in that file? All of my hardware in the SS5-70 is detected automatically by the 2006-12-16 floppy images. The older floppies would not automatically detect the onboard ethernet chipset (sunlance), so I had to choose the module manually during the install after it failed to detect any networking hardware. When I was doing the installs on the SS20, I had to manually choose an ethernet chipset module and the SCSI module. This was with floppies older than the 2006-12-16 images. I will retest the SS20 with the latest floppy images tonight. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: I first tried to boot my SS20 that contained a CG6 framebuffer and a Sun Wide-SCSI + 100Mbit NIC SBUS card, but it froze the system hard while loading the esp module. So, I pulled the SBUS board with the SCSI and NIC, and tried again. This time it detected all hardware, and did a successful installation. The sparc kernel maintainer for Debian is going to look into this Both boots I had to manually tell it to load the lance module for my onboard NIC. Could you provide the output of 'lspci -nn' and 'prtconf' (from the sparc-utils package) for your box? kernel: program parted_server is using a deprecated SCSI ioctl, please convert it to SG_IO Known issue, but thanks for mentioning it. Cheers, FJP pgpt3GEndSb97.pgp Description: PGP signature
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: Both boots I had to manually tell it to load the lance module for my onboard NIC. Could you provide the output of 'lspci -nn' and 'prtconf' (from the sparc-utils package) for your box? lspci doesn't exist on the system (no PCI slots anyway). prtconf returns the following: System Configuration: Sun Microsystems sun4m Memory size: 256 Megabytes System Peripherals (Software Nodes): SUNW,SPARCstation-20 packages (driver probably installed) disk-label (driver probably installed) deblocker (driver probably installed) obp-tftp (driver probably installed) options (driver probably installed) aliases (driver probably installed) openprom (driver probably installed) iommu (driver probably installed) sbus (driver probably installed) espdma (driver probably installed) esp (driver probably installed) sd (driver probably installed) st (driver probably installed) ledma (driver probably installed) le (driver probably installed) SUNW,bpp (driver probably installed) SUNW,DBRIe (driver probably installed) cgsix (driver probably installed) obio (driver probably installed) zs (driver probably installed) zs (driver probably installed) eeprom (driver probably installed) counter (driver probably installed) interrupt (driver probably installed) SUNW,fdtwo (driver probably installed) auxio (driver probably installed) power (driver probably installed) memory (driver probably installed) virtual-memory (driver probably installed) eccmemctl (driver probably installed) SUNW,sx (driver probably installed) TI,TMS390Z55 (driver probably installed) TI,TMS390Z55 (driver probably installed) I'm trying to get a SS5-70 to install via floppy, but it's not working as well as the SS20 did. The installation went fine, but when it boots it can't find the disk again. I'm going to try the latest disk images on the SS5 tonight and see if it's fixed already. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote:Could you provide the output of 'lspci -nn' and 'prtconf' (from the sparc-utils package) for your box? Just to make sure I wasn't incorrect in my assumptions that lspci wouldn't work, I installed the pciutils package and ran the utility as you asked. It returned with no output. debian:~# lspci -nn debian:~# --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
I just did an install tonight using the floppies created on 2006-12-16 on a SparcStation 5, 70Mhz system w/80MB of RAM, a 4.3GB SCSI drive, and a CG6 framebuffer. The installation went perfect, all hardware detected (network, SCSI controller, and hard drive), drive partitioned just fine. After rebooting, it looks like the SCSI controller module is missing from the initial ramdisk again. System boots from the hard drive, then can't find the root filesystem (can't open root device). Does this need to go into a seperate bug report since it is a different system (but same architecture as the SS20 I've been using)? --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
(Please always reply to the bug report rather than individual persons.) On Monday 11 December 2006 21:14, you wrote: Frans Pop [EMAIL PROTECTED] wrote: Just tried today's testing boot floppies along with a CG6 framebuffer, Sun monitor, and Sun Type5 keyboard. It still looks like it needs more than one ENTER key press at the root disk prompt, but it did continue the boot process. So the problem is not the enter key versus the keypad enter key, but rather that it needs to be pressed more than once? Were you able to complete the installation after loading the other floppies? P.S. Please type your replies below the text you quote (and delete any irrelevant text). That makes things much easier to read... It appears to work after pressing the Enter key on the number pad, then pressing the Enter key on the keyboard. I was able to duplicate this on the serial console as well. I get a ^M when I'm on the serial console after pressing the number pad Enter key. OK. I doubt we'll have time to look into this before the release of Etch. Nice to hear that floppies actually work. We've not had an installation report for those in ages :-) I was able to complete an install once the root image loaded, but the esp module doesn't get loaded in the initial ramdisk image, so the system won't boot properly after install. This should be fixed with current images. Would be nice if you could verify. I have a small pile of sun4m machines (three SparcStation 5 systems, one SparcStation 20 w/dual SM71 processors), with floppies and CD-ROMs. I'd love to be able to run Debian on these, so anything I can do to help test stuff, please let me know. I also have a handful of SBus cards (various framebuffers, 100Mbit + Wide SCSI, and narrow SCSI). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: (Please always reply to the bug report rather than individual persons.) It looks like the message I replied to was not CC'd to the mailing list. I'll make sure to CC the list from now on. On Monday 11 December 2006 21:14, you wrote: Frans Pop wrote: Just tried today's testing boot floppies along with a CG6 framebuffer, Sun monitor, and Sun Type5 keyboard. It still looks like it needs more than one ENTER key press at the root disk prompt, but it did continue the boot process. So the problem is not the enter key versus the keypad enter key, but rather that it needs to be pressed more than once? Were you able to complete the installation after loading the other floppies? P.S. Please type your replies below the text you quote (and delete any irrelevant text). That makes things much easier to read... It appears to work after pressing the Enter key on the number pad, then pressing the Enter key on the keyboard. I was able to duplicate this on the serial console as well. I get a ^M when I'm on the serial console after pressing the number pad Enter key. OK. I doubt we'll have time to look into this before the release of Etch. Nice to hear that floppies actually work. We've not had an installation report for those in ages :-) I was able to complete an install once the root image loaded, but the esp module doesn't get loaded in the initial ramdisk image, so the system won't boot properly after install. This should be fixed with current images. Would be nice if you could verify. I'll download the newest images tonight and see how things go. I'm new to the whole Debian community, so I apologize if my postings are in the wrong mailing lists and such. I'll probably switch to a different mail account with a real mail client tonight, so it'll be easier to format replies and keep things organized. --Dan - Want to start your own business? Learn how on Yahoo! Small Business.
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop [EMAIL PROTECTED] wrote: It appears to work after pressing the Enter key on the number pad, then pressing the Enter key on the keyboard. I was able to duplicate this on the serial console as well. I get a ^M when I'm on the serial console after pressing the number pad Enter key. OK. I doubt we'll have time to look into this before the release of Etch. Nice to hear that floppies actually work. We've not had an installation report for those in ages :-) OK, played with this again tonight, and it takes four ENTERs to get the root floppy to mount. Doesn't matter about timing the ENTERs, (four quick taps of ENTER will get it going). This was with the ENTER key on a Sun5c keyboard, not touching the one on the number pad. I was able to complete an install once the root image loaded, but the esp module doesn't get loaded in the initial ramdisk image, so the system won't boot properly after install. This should be fixed with current images. Would be nice if you could verify. It has been verified. :-) I first tried to boot my SS20 that contained a CG6 framebuffer and a Sun Wide-SCSI + 100Mbit NIC SBUS card, but it froze the system hard while loading the esp module. So, I pulled the SBUS board with the SCSI and NIC, and tried again. This time it detected all hardware, and did a successful installation. Both boots I had to manually tell it to load the lance module for my onboard NIC. The 18GB SCSI drive was detected properly, and parted was able to use the entire drive. I did see the following message on the fourth virtual terminal repeating while parted was doing its thing: kernel: program parted_server is using a deprecated SCSI ioctl, please convert it to SG_IO After the install, the system booted properly, and went straight to a login prompt without anything that looked like an error. I'm going to see if this works on some of my SS5 systems now. :-) Thanks!!! --Dan - Everyone is raving about the all-new Yahoo! Mail beta.
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Friday 08 December 2006 05:21, Dan Oglesby wrote: Just tried today's testing boot floppies along with a CG6 framebuffer, Sun monitor, and Sun Type5 keyboard. It still looks like it needs more than one ENTER key press at the root disk prompt, but it did continue the boot process. So the problem is not the enter key versus the keypad enter key, but rather that it needs to be pressed more than once? Were you able to complete the installation after loading the other floppies? P.S. Please type your replies below the text you quote (and delete any irrelevant text). That makes things much easier to read... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Just tried today's testing boot floppies along with a CG6 framebuffer, Sun monitor, and Sun Type5 keyboard. It still looks like it needs more than one ENTER key press at the root disk prompt, but it did continue the boot process. --Dan Frans Pop [EMAIL PROTECTED] wrote: On Sunday 03 December 2006 07:01, Dan Oglesby wrote: Comments/Problems: After booting from the boot.img on floppy, the system prompted for the root.img floppy to be inserted into the floppy drive. After manually ejecting the boot.img floppy and inserting the root.img floppy, the system would not proceed after pressing the ENTER key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? - Everyone is raving about the all-new Yahoo! Mail beta.
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Sunday 03 December 2006 07:01, Dan Oglesby wrote: Comments/Problems: After booting from the boot.img on floppy, the system prompted for the root.img floppy to be inserted into the floppy drive. After manually ejecting the boot.img floppy and inserting the root.img floppy, the system would not proceed after pressing the ENTER key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Serial console at 9600,8,n,1. Connected to a Linux machine with minicom in vt102 emulation mode. When I hit ENTER, the console drops down a line, so it's getting the command (no other issues using the console so far either). --Dan Frans Pop [EMAIL PROTECTED] wrote: On Sunday 03 December 2006 07:01, Dan Oglesby wrote: Comments/Problems: After booting from the boot.img on floppy, the system prompted for the root.img floppy to be inserted into the floppy drive. After manually ejecting the boot.img floppy and inserting the root.img floppy, the system would not proceed after pressing the ENTER key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? - Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.
Bug#401396: 20061202 - daily build for sparc32 floppy install
I just tried to boot from floppy again, and this time used the ENTER key on the numeric key pad. It appears to work using that ENTER key. Still did not work using the ENTER key on the qwerty area of the keyboard. --Dan Frans Pop [EMAIL PROTECTED] wrote: On Sunday 03 December 2006 07:01, Dan Oglesby wrote: Comments/Problems: After booting from the boot.img on floppy, the system prompted for the root.img floppy to be inserted into the floppy drive. After manually ejecting the boot.img floppy and inserting the root.img floppy, the system would not proceed after pressing the ENTER key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? - Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.
Bug#401396: 20061202 - daily build for sparc32 floppy install
Package: installation-reports Boot method: How did you boot the installer? CD? floppy? network? floppy Image version: Full URL to image you downloaded is best http://people.debian.org/~stappers/d-i/images/daily/sparc32/floppy/2.6/ Date: Date and time of the install 2006-12-02 23:30 Machine: Description of machine (eg, IBM Thinkpad R32) Sun SparcStation 5 Processor: microSPARC II 70Mhz Memory: 80 MB Partitions: df -Tl will do; the raw partition table is preferred none Output of lspci -nn and lspci -vnn: none Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: After booting from the boot.img on floppy, the system prompted for the root.img floppy to be inserted into the floppy drive. After manually ejecting the boot.img floppy and inserting the root.img floppy, the system would not proceed after pressing the ENTER key. Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. - Everyone is raving about the all-new Yahoo! Mail beta.
