Linksys USB NIC prevents boot-up or locks system after plugging in after boot on Fiesty Fawn

Thanks for taking the time to report this bug and helping to make Ubuntu better. How quickly does the system lock up? One way to get more information may be to log into a virtual terminal (Ctrl+Alt+F2) execute 'tail -f /var/log/messages' and then plug in the adapter. If you can capture what is causing the crash a picture of the crash may be helpful. Thanks in advance.

Hello Brian:
Although the system won't boot with the device plugged
in, the system doesn't initially lock up when I just
plug the USB NIC into the system. It seems I have to
perform an action (e.g. launching a web browser) that
will ask the system to access the network.

It usually takes about 30 seconds to a minute for the
system to lock up in full GUI mode (i.e. run level 5)
after I plug in the USB NIC if I attempt to access the
network (by launching a web browser, attempting to
access the update manager, etc).

In the virtual terminal, I captured this log file
immediately after plugging in the USB device, but the
last two entries only displayed on the console vs.
getting captured in the txt file. Here's what I
captured:

Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a
read-only configuration source at position 0
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address "xml:readwrite:/home/tdorris/.gconf"
to a writable configuration source at position 1
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a
read-only configuration source at position 2
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/var/lib/gconf/debian.defaults" to a
read-only configuration source at position 3
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/var/lib/gconf/defaults" to a read-only
configuration source at position 4
Apr 27 17:02:48 localhost kernel: [ 86.216000] NET:
Registered protocol family 10
Apr 27 17:02:48 localhost kernel: [ 86.216000] lo:
Disabled Privacy Extensions
Apr 27 17:02:48 localhost kernel: [ 86.216000]
ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 27 17:02:56 localhost kernel: [ 93.628000]
ondemand governor failed to load due to too long
transition latency
Apr 27 17:03:01 localhost gconfd (tdorris-5192):
Resolved address "xml:readwrite:/home/tdorris/.gconf"
to a writable configuration source at position 0
Apr 27 17:04:44 localhost kernel: [ 199.360000] usb
1-1: new full speed USB device using uhci_hcd and
address 2
Apr 27 17:04:44 localhost kernel: [ 199.512000] usb
1-1: configuration #1 chosen from 1 choice
Apr 27 17:04:45 localhost kernel: [ 200.264000]
ubuntu/wireless/at76/at76c503.c: Atmel at76c50x USB
Wireless LAN Driver 0.14beta1 loading
Apr 27 17:04:45 localhost kernel: [ 200.344000]
usbcore: registered new interface driver at76_usb
Apr 27 17:04:48 localhost kernel: [ 202.624000] usb
1-1: reset full speed USB device using uhci_hcd and
address 2
Apr 27 17:04:48 localhost kernel: [ 202.772000] usb
1-1: device firmware changed
Apr 27 17:04:48 localhost kernel: [ 202.772000] usb
1-1: USB disconnect, address 2
Apr 27 17:04:48 localhost kernel: [ 202.772000]
ubuntu/wireless/at76/at76c503.c: wlan0 disconnecting
Apr 27 17:04:48 localhost kernel: [ 202.772000]
ubuntu/wireless/at76/at76c503.c: at76_usb disconnected
Apr 27 17:04:48 localhost kernel: [ 202.884000] usb
1-1: new full speed USB device using uhci_hcd and
address 3
Apr 27 17:04:48 localhost kernel: [ 203.036000] usb
1-1: configuration #1 chosen from 1 choice
A...

I'm having a similar problem - my linksys card is alternately causing the system to lock up and working. When I enable nvidia drivers, I routinely get the same string of errors including 1784: assertion dev -> curr_bss == null failed (and) ... dev -> istate = init failed

Not an expert, but I was Googling around to fix this and came upon this thread.

Similar problem also for me. I have a SMC2662W USB wifi adapter, with atmel chipset. When I plug-in it, the keyboard apparently hangs (but really when I unplug the device all keystrokes appear on yhe terminal windows) . I have 2 boxes: one is a Dapper Drake LTS, 2.6.15-28-k7 #1 SMP PREEMPT, the other is Feisty Fawn 2.6.20-16-generic. This behaviour was initially the same on both, even after installing the proper packages by Synaptic. After that, I tried to compile the at76c50x driver from berlios.de in the Dapper box; and after installing the driver and the firmware from the same site, all was OK. But I didn't succeed in doing the same thing on the Feisty box. First, I had compiling problems because the sources were looking for linux/config.h - but I found that this header is no more used in the latest kernels, so I commented all the concerned "include" lines
Anyway, no luck with Feisty. Apparently, the drivers in the repositories have problems, and the available sources do not compile against 2.6.20.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.

On Tue, 28 Aug 2007 16:53:40 -0000
Brian Murray <email address hidden> wrote:

> However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon.

I am sorry, but this item cannot be tested in live environment, because
the working driver for the Atmel chipset in Dapper is the one that I
downloaded from berlios.de and compiled against 2.6.15 kernel in
Dapper. The same driver could not be compiled straightforwardly in
Feisty; I however compiled it after some hacking, but it didn't work and
had the same keyboard freezing as the precompiled package.
Of course I can't compile it from the live cd !!!

What I can do is just to try if the Gutsy live CD has a working
pre-compiled driver for Atmel USB WiFI NIC.
I will try to download Gutsy asap.

Best regards
Giorgio

 --
   | La Legge di Murphy applicata al software stabilisce che |
   | qualsiasi routine, procedura o funzione presenta sempre |
   | una o piu' condizioni di uscita totalmente imprev
$ segmentation fault - core dumped

I have good news! !!
As suggested by Brian, I tried the Gutsy Gibbon live.
After activating all the repositories, I installed by Synaptic the drivers for Atmel wifi devices provided by the Gutsy distribution.
I didn't yet test all thoroughly, but there was no more keyboard freezing, and iwconfig was reporting correctly the ESSID of the wlan without need for any manual configuration. So it seems that the bug is solved in Gutsy.
I noted also that the driver is reported as working for kernels => 2.6.20.
If this is true, the driver supplied with Gutsy should work also for Feisty. I am not so clever to transport the package into Feisty, but if somebody tells me how to, I am willing to try and maybe we can close this bug.

Greetings
Giorgio