[Feisty] hangs on "Starting Network Interfaces" w/ ipw3945

[Louis]

Hi
The first time I boot Feisty beta after install it boots fast, but after I've install the updates Feisty boot very slowly. It's stops with Booting network interface and after a long time it contrinue booting.
My Laptop is an HP Pavilion dv9271 with a ipw3945 wireless card.
I've tryed to delete all in my /etc/network/interfaces except this lines:

auto lo
iface lo inet loopback

And now Feisty booting fast and the network still working.

[Louis (louisdk)]

I've attachment my orginal /etc/network/interfaces-file.

[Juan Pablo Salazar Bertín (snifer)]

I can confirm this in Feisty using ipw3945 (Dell Inspiron 9400 laptop).

$ tail /var/log/dmesg
[ 17.056000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[ 17.240000] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xfa0b1, caps: 0xa04713/0x200000
[ 17.280000] input: SynPS/2 Synaptics TouchPad as /class/input/input4
[ 17.776000] fuse init (API version 7.8)
[ 17.824000] lp: driver loaded but no devices found
[ 17.864000] Adding 2329384k swap on /dev/disk/by-uuid/df543dd1-a41b-470b-82a8-9d5923f0df18. Priority:-1 extents:1 across:2329384k
[ 17.992000] EXT3 FS on sda2, internal journal
[ 18.844000] ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
[ 19.448000] NET: Registered protocol family 17
[ 65.280000] ADDRCONF(NETDEV_UP): eth1: link is not ready

So it looks like the problem is eth1 (my wireless interface, using ipw3945). I commented the following lines in /etc/network/interfaces:

#auto eth1
#iface eth1 inet dhcp

After reboot, and a faster boot process:

$ tail /var/log/dmesg
[ 16.936000] intel_rng: FWH not detected
[ 17.000000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 20
[ 17.000000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[ 18.140000] hda_intel: azx_get_response timeout, switching to polling mode...
[ 18.560000] fuse init (API version 7.8)
[ 18.568000] ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
[ 18.648000] lp: driver loaded but no devices found
[ 18.704000] Adding 2329384k swap on /dev/disk/by-uuid/df543dd1-a41b-470b-82a8-9d5923f0df18. Priority:-1 extents:1 across:2329384k
[ 18.860000] EXT3 FS on sda2, internal journal
[ 20.320000] NET: Registered protocol family 17

This bug is probably related to Bug #102675.

[David Fokkema (dfokkema)]

Related, who can say? This might be udev rules as well. But, Bug #102675 is fixed, this one is not. The symptoms are somewhat different, too, in that this seems to be hardware or driver related.

[VincentRC (vreneco1)]

Your talking about Feisty beta ?... Have you updated your system to the final release ? The bug you are describing has already been fixed.

[VincentRC (vreneco1)]

You're talking about Feisty beta ?... Have you updated your system to the final release ? The bug you are describing has already been fixed.

[Louis (louisdk)]

Yes I've updated my system to final. I try to create at new partition
where I install 7.04 final and see how fast it start up after install.

--
Mvh. Louis
Hjemmeside: www.louis.dk
Mail: <email address hidden>
MSN: <email address hidden>
Jabber: <email address hidden> (ikke en mailadresse)
Registreret Linuxbruger nr.: 405248

[Philipp Schlesinger (philipp-sadleder)]

I'd suggest that this problem (which I see on a laptop with an ipw3945, too) is due to the missing information which wireless network should be joined.
On a wired NIC, you can simply run dhcp commands and get an IP (or not). On a wireless NIC, one normally has to specify the SSID of the network.

[Deema (brushless)]

Yes! I have the same problem with a Toshiba M115, ipw3945, Feisty Beta that is updated. Hangs on boot on Configuring Network Devices.

[Paulo J. S. Silva (pjssilva)]

Same problem here. Initially fesity booted, now it hangs on boot. Commeting the eth1 lines in
the interfaces file also solve the problem.

This is a U205 laptop with ipw3945.

[wjbarbon (wjbarbon)]

I have fresh Feisty install in my laptop Dell Latitude C840 and it takes about 2 minutes just to boot. I am not suing wireless only wired connection with DHCP. I really don't know what is happening because by default, usplash does not show text but only the ubuntu logo.

I installed boot chart and I have attached the latest log of bootchart.

[Siegfried (siegzeit)]

Same problem with final version of Feisty on Toshiba M400, ipw3945.

[linuxguy123 (linuxguy123)]

I've got the same problem with Feisty completely updated.

During boot:
=====================================================================================
...
Configuring network interfaces...
udev-event[4084]: rename-netif: error changing netif name wlan0 to eth1: Device or resource busy.
...
=========================================================================================

This really holds up the boot process.

[iamtherealwoody (mgudwin)]

I have the exact same problem. Boot up takes over one minute. Broadcom 4306 with ndiswrapper. Will try to comment out eth1.

[chili555 (wrweston)]

Exact same problem on Lenovo T60 with ipw3945. Feisty with 2.6.20-15-generic. Network Manager uninstalled and interfaces file manually edited. Logs, etc. provided on request. sudo ifdown eth1 && ifup eth1 starts wireless easily.

[Mathijs Vogelzang (mathijs)]

I can confirm as well on a Toshiba A100-803 laptop.
The boot seems to not wait at the interfaces stage when I boot with a wired connection hooked up.

[chili555 (wrweston)]

I found a workaround on this bug report: https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/102675
"Move networking further down in the boot process. I moved networking from rcs.d to rc2.d/rc3.d/... and gave it a priority one lower than GDM."

Here's the command I used: sudo mv /etc/rcS.d/S40networking /etc/rc2.d/S14networking It works for me.

[Manuel López-Ibáñez (manuellopezibanez)]

Add another case. With Feisty up-to-date. Deleting everything in interfaces (except lo) seems to work. Sony Vaio VGN-FE31B with ipw3945 wireless card.

[Sander van der Veeke (sanderveeke-deactivatedaccount)]

Slow boot on my Dell inspiron 1501

editing the /etc/network/interfaces file worked great. only i added the wlan bit: my /etc/network/interfaces looks like this:

---
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
----

[Sander van der Veeke (sanderveeke-deactivatedaccount)]

A couple of weeks ago the slow boot turned back, it looks like it's searching for the network.

sometimes it takes 30 seconds to boot from power to desktop
sometimes up to 3 minutes

Bug not fixed!

[Nanley Chery (nanoman)]

It's been a while since this was reported. Is this still a problem for anyone?

[KevinK (kukevin)]

Yes I am running Feisty (Kubuntu) on a Dell Inspiron 1420. I did not notice this problem immediately, but I'm pretty sure it began once I set up my wireless connection.

There was a distinct 60+ second pause during boot while it configured network interfaces. I've implemented the workaround referenced by chili55 above, and now there is no pause.

After checking out the contents of my runlevel directories, I also used the same command as chili55:

 sudo mv /etc/rcS.d/S40networking /etc/rc2.d/S14networking

[KevinK (kukevin)]

I've found an alternative solution to this problem. It seems the crux of the problem lay in the fact that ubuntu needed to connect to my wireless network before I had the chance to log in and open the connection with my password. The 60 seconds or so was the time it took for this operation to time out.

I've "undone" the above change and put the networking script link back where it was in the boot order. Using this very instructive HOWTO http://ubuntuforums.org/showthread.php?t=202834 I modified my /etc/network/interfaces file so that my laptop can connect to my WPA network immediately, rather than waiting for my Kwallet key after I've logged in. Now I am not only free of the 60 second pause, I ALSO now do not have to enter a kwallet password to connect to the internet.

As a related change, I've uninstalled network-manager and replaced it with Wicd (see http://wicd.sourceforge.net/ for installation details). Network-manager seemed to give up once I modified the interfaces file, calling my connection a "manually configured" one and refusing to allow me to manipulate or change it from the system tray (such as when I would like to connect to another network or see what else is available) Wicd seems to handle my change much better, allowing me to still select other networks when traveling.

[Leann Ogasawara (leannogasawara)]

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result, we are closing the linux-source-2.6.20 kernel task. However, the Intrepid Ibex 8.10 release is set to come out at the end of the month. It contains a newer 2.6.27 kernel. It would be good to confirm if this is still an issue with Intrepid - http://www.ubuntu.com/testing . If the issue still exists, please add the linux kernel task to this bug report. This can by done by going to:

https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/126653/+distrotask

Then change the Source Package Name to be "linux" instead of "linux-source-2.6.20" and click Continue. Thanks.