Network stopped working after upgrade to Lucid from Jaunty

Bug #573432 reported by Mannex
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Upgrading from Jaunty. I booted from the Lucid CD, and the WiFi sees the network, but it won't connect to it. I am attaching a screen shot of the connection information when it works, as well as the iwevent for when it works and when it doesn't. Any help will be greatly appreciated, as this is preventing me upgrading. Thanks.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/yelp
Package: yelp 2.25.1-0ubuntu5
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: yelp
Uname: Linux 2.6.28-18-generic i686

Revision history for this message
Mannex (russ-mannex) wrote :
Revision history for this message
Mannex (russ-mannex) wrote :
Revision history for this message
Mannex (russ-mannex) wrote :
Revision history for this message
Mannex (russ-mannex) wrote :

This might be helpful. After screwing around with the network settings all day between the two setups, I noticed that the frequency setting is different on the network card on the different boots. "iwconfig" shows this on the Jaunty boot (which works):

eth1 IEEE 802.11b ESSID:"Goesh" Nickname:"HERMES I"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:60:B3:CD:DA:EE
          Bit Rate:2 Mb/s Sensitivity:1/3
          Retry limit:4 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=23/92 Signal level=-74 dBm Noise level=-97 dBm
          Rx invalid nwid:0 Rx invalid crypt:154 Rx invalid frag:419
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

The "iwconfig" for when it doesn't work looks like this:

eth1 IEEE 802.11b ESSID:""
          Mode:Managed Frequency:2.422 GHz Access Point: None
          Bit Rate:11 Mb/s Sensitivity:1/0
          Retry limit:8 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=0/70 Signal level=-122 dBm Noise level=-122 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:1
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I attempted to change the freq or channel, but was told the device was busy. The network was not connected to anything. I tried shutting it down (ifconfig eth1 down), but was still unable to change the frequency. Any ideas? Might this be the problem? Any help will be greatly appreciated. Thanks!

Revision history for this message
Mannex (russ-mannex) wrote :

It was suggested that I do the following to provide more information:

lspci -nn
lsusb
iwconfig (iwconfig will show what the wireless is detected as......wlan0, ath0, etc.)
lshw -C network
lsmod
ndiswrapper -l
cat /etc/modprobe.d/blacklist.conf
lspci|grep -i net

Attached is the terminal session from 10.04, logged in as ubuntu (booted from install CD). Please let me know if any of this helps. The most glaring thing to me was the fact that the frequency is incorrect on the card. It should be on 2.412 GHz, not 2.422. Thanks!

-Mannex

Revision history for this message
Mannex (russ-mannex) wrote :

Gentlemen, I am not sure what you want to do with this bug. I now have new hardware (i.e. 21st century - no tubes!) with a new network controller, and there is no problem with this hardware. Thus, if a solution were provided, I would have no way of verifying it. If someone else is still having this problem, perhaps they should chime in. Otherwise, I guess I would triage this as no longer an issue (if there is such a status).

priya (priyamtk)
affects: ubuntu → update-manager (Ubuntu)
Revision history for this message
Mannex (russ-mannex) wrote :

This can be closed. It was old hardware (since replaced), and I am now running 11.04 with a functioning network.

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.