Long boot delay with Intel Pro/wireless

Bug #95892 reported by Mikko Ohtamaa
2
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Ben Collins

Bug Description

Binary package hint: linux-generic

I just installed Feisty Fawn to my HP nx9420 laptop. The laptop has PRO/Wireless 3945ABG Network WLAN.

For some reason, there is very long delay (> 30s) when setting up kernel network during boot when WLAN is enabled (hardware led is lit). This happens for both during set-up and booting the real system.

Otherwise card seems to work fine. If I recall correctly, the first version of Edgy didn't boot at all when WLAN was enabled on this hardware.

Looks like Feisty kernel is 2.6.20.12.8 kernel.

Revision history for this message
Ben Collins (ben-collins) wrote :

You are missing a considerable amount of needed information. Please attach the output of these commands (do not paste into comment). Use the web interface:

dmesg
lspci -vv
lspci -vvn

Changed in linux-meta:
assignee: nobody → ben-collins
status: Unconfirmed → Needs Info
Revision history for this message
Mikko Ohtamaa (mikko-red-innovation) wrote :

Thanks for attentation Ben. Here is the information you wish.

The relevant part from dmesg where you see the delay:

[ 19.264000] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
[ 59.880000] NET: Registered protocol family 10

Revision history for this message
Mikko Ohtamaa (mikko-red-innovation) wrote :

lscpi -vv output

Revision history for this message
Mikko Ohtamaa (mikko-red-innovation) wrote : lspci -vvn output
Revision history for this message
Mikko Ohtamaa (mikko-red-innovation) wrote :
Revision history for this message
Mikko Ohtamaa (mikko-red-innovation) wrote :

Also, I just confirmed that turning off WLAN kill switch will make the laptop boot faster. Just turn on WLAN when you have logged in and you save 30 second of boot time.

Revision history for this message
Ben Collins (ben-collins) wrote :

This looks more like a boot script issue. First, do you have linux-restricted-modules-generic installed (so that you have ipw3945d user space daemon), and also is the device configured correctly in /etc/network/interfaces?

If the latter is not true, then I suggest commenting out the entry for it in /etc/network/interfaces so that the startup scripts do not attempt to start the device (and hence, wait for it to come up, which is the cause of the delay). Then just use NetworkManager to configure the interface. Either that, or configure it correctly in /etc/network/interfaces.

Changed in linux-source-2.6.20:
status: Needs Info → Rejected
Revision history for this message
Mikko Ohtamaa (mikko-red-innovation) wrote :

This bug does not appear in Gutsy anymore - it can be closed.

Revision history for this message
Herve Rousseau (herve-rousseau) wrote :

This bug does not appear in Gutsy anymore - it can be closed.

Changed in linux-meta (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.