[EMAIL PROTECTED] wrote: > I'd like to point out that further down, it still says "PCI: System > does not support PCI", which is why I initially ignored the "Fatal" > error. I looked at similar messages with dmesg while running 6.2-5 > from CD, and it too says "PCI: System does not support PCI". > However, the dmesg output does lack the "Fatal" error, and earlier > on mentions something about allocating PCI resources. >
Does your system have PCI at all? Please describe the system as thoroughly as you can. E.g., the CPU, the devices, (PCI ones can be determined from the output of the "lspci" command"), how the hard disk is connected, the year of manufacture. A full dmesg from the 6.2-5 CD would be useful, too. A working config for linux-2.6.22.X would be the best help, but I don't demand this. If this is really a 10-year-old computer, you may want to add the "nohlt" troubleshooting parameter (although I doubt that it will help, because the 6.2-5 CD works). Also beware: since the 6.3 CD doesn't work for you, it is also very likely that LFS-6.3 (built from any other fost) will suffer from the same problem. > Aside from that, dmesg says that isolinux on the 6.2-5 CD passes > "initrd=initramfs_data.cpio.gz BOOT_IMAGE=linux" as a kernel > parameter. What is the function of "BOOT_IMAGE=linux", and why > shouldn't I need that in my menu.lst? > The "BOOT_IMAGE=linux" is not needed in menu.lst because it has no useful function. It is always passed by isolinux, but unused on LFS LiveCD. Other distributions use this variable, though, to see which kernel image (of several available) has been booted. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/livecd FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
