I just swapped in a newer ASUS, Conroe CPU, G33 chipset, MoBo. It has several SATA, and one PATA connector. I figured I could use the old PATA HDD. Put that in, BIOS saw it, GRUB came up. My LFS systems kernel-panicked, even the latest one "POD-3" using libata, but there was an old Ubuntu "Ibex" partition that did boot. Puzzle #1 is what's different with that PATA connector that causes the kernel panic. It was all fine with a PATA Pentium-3 MoBo.
Well, I wasn't planning on doing that for long--planned on putting in a SATA drive and copying the partitions over. So next I installed a SATA drive. BIOS reports both drives, GRUB on the SATA drive comes up and the POD-3 system boots. Now I get Puzzle #2. So I go looking in dmesg for the PATA drive so I know what device to mount, and there's nothing about it! The BIOS is configured for a P-n-P OS. It does report the drive on PATA port, but I realize those PATA ports weren't intended to be full system drives. Something strange in the way chipsets/BIOS' handle them? I'd expect the Linux kernel to find it. Is there something unusual (that "Ibex" has), I need to configure in the kernel? -- Paul Rogers [email protected] http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.fm - Access all of your messages and folders wherever you are -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
