Re: Installation report: FAILED on i386
Martin Michlmayr wrote: Apparently beta3 has better SATA support. Can you try? I did. :-P Here's the lowdown: the installer basically works and installs the system. Unfortunately I can't get either grub or lilo to work, so I can't boot it. This may have something to do with device mapping in the BIOS -- I may not be feeding the right information to lilo and/or grub. Or it may have something to do with the fact that my system doesn't appear to have a 'compatibility mode' for SATA -- lilo and grub may simply not support SATA natively. If you can help, please do. :-( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
Apparently beta3 has better SATA support. Can you try? This may have something to do with device mapping in the BIOS -- I may not be feeding the right information to lilo and/or grub. Or it may have something to do with the fact that my system doesn't appear to have a 'compatibility mode' for SATA -- lilo and grub may simply not support SATA natively. my dell gx270 doesn't have compat mode for SATA either [in fact the bios is pretty brain-dead] but grub doesn't seem to have a problem with it. what kind of board do you have? i think i missed that detail. elijah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
elijah wright wrote: Apparently beta3 has better SATA support. Can you try? This may have something to do with device mapping in the BIOS -- I may not be feeding the right information to lilo and/or grub. Or it may have something to do with the fact that my system doesn't appear to have a 'compatibility mode' for SATA -- lilo and grub may simply not support SATA natively. my dell gx270 doesn't have compat mode for SATA either [in fact the bios is pretty brain-dead] but grub doesn't seem to have a problem with it. what kind of board do you have? i think i missed that detail. The machine is a Dell Dimension XPS Gen 2. It appears to have an Intel ICH5 SATA controller. I really haven't been able to extract much more detail than that. Intel's software RAID driver has to be disabled entirely from the system BIOS (not just RAID turned off in the RAID driver BIOS) for Linux to recognize the disks' existence. Every installation I've attempted with this BIOS setting leads to grub saying GRUB GRUB GRUB GRUB GRUB forever on startup. (lilo gives L 99 99 99 99 99 ...) Perhaps there are sekrit configuration choices I need to make when installing grub? (And if so, how do I make them ?!?) (Oddly enough, if Intel's RAID driver is reenabled and turned off, lilo will load, but since Linux can't find the hard drive, it dies while booting...) The machine also has a PATA IDE drive (but can't boot from it at all), and two IDE CD drives. So it could be a device mapping issue, but I tried several configurations without luck. :-P -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installation report: FAILED on i386
About Message-id: [EMAIL PROTECTED] I have similar setup as follows: CPU: P4 1.6 GHz Make:Myself Chipset: i875/ICH5R M/B: Gigabyte GA-8i875 PATA Primary: Maxtor 160 GBSlave: None 2ndary: LG GSA-4081B Slave Ymaha CRW-F1 SATA0: Seagate 160GB SATA1: None I installed using daily-build of sid March 4th. Cuurrent image failed due to faulty partman, I believe. It does not let me use partitions solely on /dev/hde). Through my experience with ICH5 SATA, I know you really understand what you are doing. I did the same. I disabled chipset RAID function (before I had 2 SATA disk). I attached 3 files of my successful installation for you to examine: /etc/fstab, /boot/grub/menu.lst, and /var/log/dmesg. Apparently it still produces some errors, but d-i team has really come a long way. And I truelly appreciate their effort. Toshikazu Aiyama __ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com fstab Description: fstab menu.lst Description: menu.lst dmesg Description: dmesg
Re: Installation report: FAILED on i386
Herbert Xu wrote: Nathanael Nerode [EMAIL PROTECTED] wrote: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. * DHCP configuration is slow and flaky but eventually works. * Proceeding with the other drive, debootstrap fails -- wget fails to download the Release file for sarge with a Hostname not found failure. This pretty much scotches any install attempt, no workaround. Since you have a workaround for the hang, please get the system installed so that you can test the kernel-image packages. Once you're there, please test 2.4.24-1-386 as well 2.4.18 to see if either one works. Well, my primary computer died, but now I'm on a third machine for email, so I can work on this again. Unfortunately, I can't install Debian on any bootable modifiable drive on the new machine, and I can't boot from any modifiable drive I can install Debian on. So I tried booting from a number of different CDs. * the beta2 installation disks hit the hang if RAID is disabled in the BIOS, and can't find the disks at all if it's enabled. * The current Knoppix (kernel 2.4.22) does the same thing, except that the hang there hangs the whole machine, and can't be avoided during the boot process. * So I tried Scott Kveton's modified boot-floppies disk (http://oregonstate.edu/~kveton/debian/) based on kernel 2.4.23. Again, hangs while booting, preventing anything from working -- unless RAID is enabled in the BIOS, in which case it can't find the disks at all. FYI, the SATA chipset is Intel, presumably either ICH5 or ICH6 (I haven't actually been able to tell which). The machine is a Dell Dimension XPS. Hope this helps in tracking down the problem. And if you have any suggestions for how to break this Catch-22 situation between the BIOS and Linux, please tell me. :-) Maybe there's some scheme I haven't figured out yet with SYSLINUX or something to boot in Windows or a floppy or CD, but then load the kernel from a modifiable drive, so that I could try out different kernels and kernel modules (in an attempt to find one which recognizes the SATA disks), without burning a new CD each time? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Installation report: FAILED on i386
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-20 12:03]: So it turns out, having installed Linux to the one drive which is visible to Linux, that the BIOS won't boot from that drive. And I can't Boot from floppy or CD and use root=/dev/... or boot from the net via PXE. Or can you add a normal (parallel) IDE hard drive as a boot device? -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Installation report: FAILED on i386
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-18 18:44]: Perhaps you didn't notice that I'm completely stuck on another matter (the wget failure). Happy to try once I can work around that. Put the drive in another PC and use debootstrap to create a base system. Or install another distro, make a base with debootstrap another PC, copy it over and untar it, etc. So it turns out, having installed Linux to the one drive which is visible to Linux, that the BIOS won't boot from that drive. And I can't use lilo to install a boot block on the bootable SATA drive, because Linux can't see that drive And I can't put the SATA drives in another machine, because this is the only machine with a SATA connection. Got a suggestion for a workaround? Or perhaps a installer kernel which will recognize the drives? :-/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Installation report: FAILED on i386
Martin Michlmayr wrote: Boot from floppy or CD and use root=/dev/... I don't think that works, you get the d-i initrd, which is not very good at booting a regular debian system. -- see shy jo signature.asc Description: Digital signature
Re: Re: Installation report: FAILED on i386
* Joey Hess [EMAIL PROTECTED] [2004-01-20 12:43]: Boot from floppy or CD and use root=/dev/... I don't think that works, you get the d-i initrd, which is not very good at booting a regular debian system. Yeah, you'll need a special CD. However, this used to work with woody - I really hope we can make a rescue option which allows this. It has been useful many times. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Installation report: FAILED on i386
Martin Michlmayr wrote: Yeah, you'll need a special CD. However, this used to work with woody - I really hope we can make a rescue option which allows this. It has been useful many times. If we had a good and reasonably small rescue initrd, we could include it on the CD easily. -- see shy jo signature.asc Description: Digital signature
Re: Re: Installation report: FAILED on i386
* Joey Hess [EMAIL PROTECTED] [2004-01-20 13:12]: If we had a good and reasonably small rescue initrd, we could include it on the CD easily. Yeah, but even booting without an initrd (from an existing installation) should be possible. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Installation report: FAILED on i386
Martin Michlmayr wrote: * Joey Hess [EMAIL PROTECTED] [2004-01-20 13:12]: If we had a good and reasonably small rescue initrd, we could include it on the CD easily. Yeah, but even booting without an initrd (from an existing installation) should be possible. The standard debian install will not boot w/o an initrd, and I know of no way to make syslinux/isolinux load the initrd from the hard drive and the kernel from cdrom. -- see shy jo signature.asc Description: Digital signature
Re: Installation report: FAILED on i386
Martin Michlmayr wrote: * Nathanael Nerode [EMAIL PROTECTED] [2004-01-20 12:03]: So it turns out, having installed Linux to the one drive which is visible to Linux, that the BIOS won't boot from that drive. And I can't Boot from floppy or CD and use root=/dev/... or boot from the net via PXE. Or can you add a normal (parallel) IDE hard drive as a boot device? Nope. I have one but the BIOS won't boot from it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
Nathanael Nerode [EMAIL PROTECTED] wrote: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. * DHCP configuration is slow and flaky but eventually works. * Proceeding with the other drive, debootstrap fails -- wget fails to download the Release file for sarge with a Hostname not found failure. This pretty much scotches any install attempt, no workaround. Since you have a workaround for the hang, please get the system installed so that you can test the kernel-image packages. Once you're there, please test 2.4.24-1-386 as well 2.4.18 to see if either one works. -- Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED] Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
Herbert Xu wrote: Nathanael Nerode [EMAIL PROTECTED] wrote: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. * DHCP configuration is slow and flaky but eventually works. * Proceeding with the other drive, debootstrap fails -- wget fails to download the Release file for sarge with a Hostname not found failure. This pretty much scotches any install attempt, no workaround. Since you have a workaround for the hang, please get the system installed so that you can test the kernel-image packages. Once you're there, please test 2.4.24-1-386 as well 2.4.18 to see if either one works. Perhaps you didn't notice that I'm completely stuck on another matter (the wget failure). Happy to try once I can work around that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-18 18:44]: Perhaps you didn't notice that I'm completely stuck on another matter (the wget failure). Happy to try once I can work around that. Put the drive in another PC and use debootstrap to create a base system. Or install another distro, make a base with debootstrap another PC, copy it over and untar it, etc. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installation report: FAILED on i386
2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * It hangs on loading module ide-detect if RAID is disabled in the BIOS. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. * DHCP configuration is slow and flaky but eventually works. * Proceeding with the other drive, debootstrap fails -- wget fails to download the Release file for sarge with a Hostname not found failure. This pretty much scotches any install attempt, no workaround. -- Nathanael Nerode neroden at gcc.gnu.org http://home.twcny.rr.com/nerode/neroden/fdl.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-17 19:15]: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. Does a standard 2.4 kernel normally work? Or do you have patches or 2.6? -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
* Nathanael Nerode [EMAIL PROTECTED] [2004-01-17 20:26]: the mysterious hang was much more disturbing. I know. :/ Other people have experienced it as well (e.g. 224494), but I don't think our kernel maintainer has looked at it yet. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation report: FAILED on i386
Martin Michlmayr wrote: * Nathanael Nerode [EMAIL PROTECTED] [2004-01-17 19:15]: 2 Serial ATA drives, 1 IDE drive, e1000 Ethernet card. * If RAID is enabled in the BIOS, it gets past that, but it never detects either Serial ATA drive. Does a standard 2.4 kernel normally work? Or do you have patches or 2.6? Never tried putting Linux on the machine before, as it's new. I have no real complaints about not detecting the drives, actually; the mysterious hang was much more disturbing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]