mark gross wrote: > On Sun, Jun 30, 2013 at 04:34:24PM +0800, Chen Qi wrote: >> 于 2013年06月29日 22:17, Aleksandar Kuktin 写道: >>>> On Sat, 29 Jun 2013 12:51:03 +0800 >>>> Chen Qi <chen_...@163.com> wrote: >>>> >>>> Hi all, >>>> >>>> I've followed all instructions in the LFS stable 7.3 book, and made a >>>> USB containing my LFS system. >>>> >>>> As I don't know exactly which drivers and modules should be compiled >>>> into my LFS kernel to make it work on my DELL laptop, I made a >>>> 'allyesconfig' and compiled the kernel. >>>> >>>> I thought 'make allyesconfig' would make the kernel work. >>>> However, when it started up, the kernel was loaded but hung at 'TCP >>>> established hash table entries'. >>>> >>>> A previous message that might appear to be an error was 'ACPI png >>>> driver unregistered'. >>>> >>>> Can somebody give me a hand? >>>> >>>> Thanks in advance. >>>> >>>> //Chen Qi >>>> >>> I think that the best option would be to assume you will have to spend >>> a few days on this and then manually assemble the kernel options that >>> work on your system. >>> >>> One possible option to speed up this process is to first find which >>> options are necessary for booting the kernel (AKA the PCI driver, the >>> USB driver, at least one partition system and the filesystem) and then >>> make everything else a module. Assuming you have checked "automatic >>> module loading", when the system boots, you can use `lsmod' to find >>> which modules were loaded and, therefore, which things you need to >>> enable and which you don't have to. >>> >>> >> Hi Aleksandar, >> >> Thank you for your suggestions. >> The problem is how to find out which options are necessary for booting >> the kernel? >> Are there some useful resources or documents out there? >> >> I made the whole LFS system on a USB and I met the following error when >> the kernel started up. >> ''' >> VFS: Cannot open root device "sdb1" or unknown-block(0,0) >> ''' >> >> Maybe you have read the email which I replied to the list. There's more >> information in the email regarding this problem. >> >> I have 'CONFIG_USB=y' in my config file, is it not enough for booting >> from a USB device? >> >> Best Regards, >> Chen Qi >> > If you are trying to boot off of a USB flash disk file system you need to be > sure all the drivers needed to talk to a file system on the usb key are loaded > into memory before the kernel try's to run the init program. > > For a USB key this means either you set your bootloader to load an initial > ramdisk holding the driver modules and logic for loading the modules and any > pivot root business needed to get things going. > > or... > You need ot be sure the following are compiled into the kernel: > USB, SCSI, ext3 or ext4 FS. > > Also, you need to check your kernel command line to make sure root= is set to > the USB key's /dev/sd?? or the GUID of the file system on the USB key.
LFS, by default does not use a initramdisk. That is required ot use a USB key or GUID value. -- Bruce > If you are booting off a system that likely has a real HD then you will likely > want to use the GUID option. > > The more I think about it I think your issues are just as likely a boot loader > / kernel command line issue as it is a kernel config issue. > > Good luck. > > --mark > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
