|
NM worked OK on wireless for about a week after installing a new
version of Ubuntu, 10.10.1. After that, it has never worked again on
wireless. After recent messages in this list I thought I'd try
again. PLEASE note: I'm not a programmer or a network guru or a
software debugger or a boot-message reader, I'm just trying to use
NM on Ubuntu to get work done, but this issue SERIOUSLY interferes
with work. I've been trying to resolve NM issues for over a month
now, with several helpful responses but no fixes. Is this not the
correct place to try to get help for NM issues? Please advise. Attachment details my tries based on today's e-mails to this list. What's wrong with NM, or its setup, or its config, and how do the issues get resolved? Thanks! -- Alan White awhite0006 gmail com |
Timothy Murphy wrote in response to James J Catchpole:
I'm no expert, but the 3 things I try when NM doesn't work
(not an infrequent occurrence):
1. Run "sudo iwlist scan".
If that sees something then the problem is certainly with the NM setup.
RESULT:
awhite author:~$ sudo iwlist scan
[sudo] password for awhite:
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wlan0 Interface doesn't support scanning : Network is down
wlan1 Interface doesn't support scanning : Network is down
2. Try the network service instead of NM;
sudo service NetworkManager stop
RESULT:
awhite author:~$ sudo service NetworkManager stop
NetworkManager: unrecognized service
So I thought I'd try this also:
awhite author:~$ sudo service NetworkManager restart
NetworkManager: unrecognized service
sudo service network restart
RESULT:
awhite author:~$ sudo service network restart
network: unrecognized service
3. Check that the entry in /etc/sysconfig/network-scripts/ifcfg-wlan0
is reasonably accurate.
RESULT:
vi /etc/sysconfig/network-scripts/ifcfg-wlan0
"/etc/sysconfig/network-scripts/ifcfg-wlan0" [New DIRECTORY]
4. Check /var/log/messages (I pulled out a few but there are MANY messages)
RESULT:
Dec 26 21:56:14 author kernel: [ 14.984775] ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23
Dec 26 21:56:14 author kernel: [ 14.984866] ath5k 0000:07:00.0: registered as 'phy0'
Dec 26 21:56:14 author kernel: [ 15.495926] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Dec 26 21:56:14 author kernel: [ 15.519317] usbcore: registered new interface driver rt2500usb
Dec 26 21:56:14 author kernel: [ 16.877108] usbcore: registered new interface driver rt73usb
Dec 26 21:56:14 author kernel: [ 17.017750] eth0: no link during initialization.
Dec 26 21:56:14 author kernel: [ 17.018424] ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 26 21:56:15 author kernel: [ 17.611781] ppdev: user-space parallel port driver
Dec 26 21:56:19 author kernel: [ 21.990031] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold
Dec 26 21:57:22 author kernel: [ 84.991868] eth0: link up.
Dec 26 21:57:22 author kernel: [ 84.992560] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
ADDITIONALLY:
$ ifconfig wlan0 (nm-applet reports this as Atheros AR5001 Wireless Network Adapter, "device not ready")
wlan0 Link encap:Ethernet HWaddr 00:24:2c:6e:54:a2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
$ ifconfig wlan1 (nm-applet reports this as Ralink 802.11 bg WLAN, "device not ready")
wlan1 Link encap:Ethernet HWaddr 00:0e:2e:86:80:68
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)