Public bug reported:

I recently successfully upgraded from Edgy to Feisty. My wifi (Netgear
WG311v3  pci card) was working fine. I the tried to enter settings to
allow the card to access a wpa network rather than wep. In doing so I
found that I could no longer configure the card correctly at all.

The card operates with the ndiswrapper driver

Removing the "gnome network manager" and "network manager" made no
difference. I also tried a number of alternative drivers for the card,
without success. In fact I even completely reinstalled feisty.

The card was accepting the wep key, key mode (eg open), nickname etc BUT
I could not set the essid. Looking at dmesg showed an error wlan0:
device not ready. Interestingly looking at iwevent while trying to add
the essid showed that iwevent was reporting that the essid had been
correctly set...... it had not.

I recall that on upgrading from ubuntu I saw a message that the card
configuration had been changed (I didn't pay much attention as
everything was working at the time). I think the message was generated
on modprobing ndiswrapper the first time). I also noticed that the
windows disk included a setup program as well as the drivers. I wondered
if the problem was due to some settings on the card having been reset in
the attempt to use wpa ...... and iwconfig/ndiswrapper/network manager
were all unable to reset these parameters?

I desperation I reinstalled windows XP on a spare corner of the machine
(!!!! I know, I know) and used the netgear utilities to connect the card
to my wifi router. This worked fine and the card remembered the setting
after a complete shutdown and reboot into Ubuntu.

Looking at various support websites I know that this problem (or
something remarkably similar) has affected a large number of people. It
also seems to have been around  for some time before Feisty. This is
important because failure to get wifi running would be a showstopper fro
many people.

I am happy to provide more specific evidence if required but, meanwhile,
I hope that the nature of the work-around above should help the
ndiswrapper/iwconfig maintainers to understand what is going on.

** Affects: Ubuntu
     Importance: Undecided
         Status: Unconfirmed

-- 
wlan0 device not ready - can't set essid -workaround
https://bugs.launchpad.net/bugs/113816
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to