Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Distributions > Linux From Scratch
User Name
Linux From Scratch This Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.


  Search this Thread
Old 05-20-2012, 09:48 AM   #1
Registered: May 2011
Distribution: Slackware
Posts: 121

Rep: Reputation: 0
delay on kernel boot

kernel 3.3.6 delays about 10 seconds may be for having trouble with hardware
[ 5.915609] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 6.416219] firewire_core: created device fw0: GUID 00023f648140d9af, S400 ### <- boot log stops here for 10 sec then continue
udevd[1196]: worker[1206] timeout, kill it
udev[1196]: seq 1490 '/devices/pci0000:00/0000:00:1e.0/0000:06:02.0' killed
[ 37.291680] ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
[ 37.294259] ipw2200: Unable to load firmware: -2
[ 37.297037] ipw2200: failed to register network device
[ 37.302853] ipw2200: probe of 0000:06:02.0 failed with error -5
udevd[1196]: worker[1206] terminated by signal 9 (killed)
and here is my kernel .config part of ipw2200

# CONFIG_IPW2100 is not set
# CONFIG_IPW2200_MONITOR is not set
# CONFIG_IPW2200_QOS is not set
# CONFIG_IPW2200_DEBUG is not set
Old 05-21-2012, 01:47 PM   #2
Registered: May 2007
Distribution: LFS
Posts: 628

Rep: Reputation: 185Reputation: 185
I don't know specifically what you need to do. But to me, the kernel may be discovering a firewire device and the driver for it is not available at that moment. For that, I would try looking at the various firewire settings in the kernel config. You might try recompiling the kernel with CONFIG_FIREWIRE and CONFIG_FIREWIRE_OHCI both built as modules.

For the wireless thing, it may be discovering the wireless adapter and loading the driver at a time when the firmware is not available. If you chose to build-in that device's driver, then you may also need to configure the kernel for the firmware to be built-in, too. Or, a probably easier thing to try (and my preference for a similar situation with video card firmware) is to recompile the kernel and choose to build the device driver as a module. Then the firmware (in the filesystem) should be available when the driver module is loaded.

No promises for anything above this sentence. But recompiling a new kernel is a simple, quick, and reversible thing to do. And that exact ipw2200 wireless thing has happened here before (and was fixed by compiling the driver as a module).

Last edited by stoat; 05-21-2012 at 03:58 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Boot delay Hugh Jass MEPIS 1 12-18-2006 06:39 PM
Boot delay Hugh Jass Linux - Newbie 2 12-18-2006 07:42 AM
Boot Delay DHCPCD Kelman Linux - Wireless Networking 5 10-13-2005 05:23 PM
Delay due to DHCP in boot pymehta Linux - Networking 2 09-15-2005 09:08 AM
Dual Boot Delay Time = 0 Raggit Linux - General 3 01-26-2005 10:25 AM > Forums > Linux Forums > Linux - Distributions > Linux From Scratch

All times are GMT -5. The time now is 11:13 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration