upgraded from gutsy to hardy, network manager no longer recognizes wireless device

Bug #206951 reported by Brian Boz
2
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

HP nc8000 laptop with Intel IPW2100 wireless. I upgraded from gutsy to hardy when the beta release occurred. Ever since, if I double click the network icon for my wireless network and then click configure I get the error dialog "The interface does not exist. Check that it is correctly supported by your system" (after being prompted for the password).

Odd thing is that wireless network is otherwise working fine, I just can't seem to open network manager. I was hoping several days of updates might fix the problem but suspect something went wrong with the upgrade and my configuration is now slightly wrong.

/etc/network/interfaces file attached (with the ESSID & password X'd out). I'm not sure what else to provide to help solve the problem.

Only other information of note is that when I upgraded from feisty to gutsy the naming of my ethernet adapters was swapped (so wireless which had been eth1 became eth0 and wired which had been eth0 became eth1).

Revision history for this message
Brian Boz (brian-boz) wrote :
Revision history for this message
Brian Boz (brian-boz) wrote :

Did a little more debugging. Found the problem is with network-admin, not network-manager. From the command line if I do:

gksu network-admin --configure eth0

I get the same error message when I double click the network icon in the task bar. I also noticed that if I run network-admin with no options it displays the list of connections but they are all grayed out and there is nothing in the Location: drop down list. This was working fine in gutsy before I upgraded.

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 184711, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.