Hello, I’m having a slight issue with NetworkManager. It started up fine the first time I rebooted into my new Opensuse 12.1 and picked up my wireless right away. However I went afk for a while and closed the lid on my laptop, putting it into standby and when I came back I couldn’t connect. Since then it won’t work when I boot into OpenSUSE. I’ve found that if I open terminal and kill NetworkManager then restart it my wireless gets detected and I’m able to use the internet. I was hoping some one can help me fix it so that I don’t have to kill and restart NetworkManager everytime I log in.
Just some suggestions to start with.
- Next time this happens, grab the state reported from
cat /var/lib/NetworkManager/NetworkManager.state
and post here.
2.If you don’t have rfkill installed, do so
zypper in rfkill
You can check on the state of the interfaces with
/usr/sbin/rfkill list
This will show you if your wireless interface is available.
However I went afk for a while and closed the lid on my laptop, putting it into standby and when I came back I couldn’t connect.
I have read of this behaviour with certain wireless drivers in the past, but not reported recently. It might be helpful if you tell us a little bit about your wireless chipset
/usr/sbin/hwinfo --wlan
With a bit of luck, someone else will chime in with a possible solution…
linux-7xpx:/home/faror # cat /var/lib/NetworkManager/NetworkManager.state
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
linux-7xpx:/home/faror # /usr/sbin/rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
Okay, and as far as my wireless goes, here’s the output from this.
linux-7xpx:/home/faror # /usr/sbin/hwinfo --wlan
16: PCI 800.0: 0282 WLAN controller
[Created at pci.319]
Unique ID: y9sn.ME9ySuipOaE
Parent ID: z8Q3.gOf7LKOgBf5
SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:08:00.0
SysFS BusID: 0000:08:00.0
Hardware Class: network
Model: "Intel PRO/Wireless 3945ABG [Golan] Network Connection"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x4222 "PRO/Wireless 3945ABG [Golan] Network Connection"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x135b
Revision: 0x02
Driver: "iwl3945"
Driver Modules: "iwl3945"
Device File: wlan0
Features: WLAN
Memory Range: 0xe8000000-0xe8000fff (rw,non-prefetchable)
IRQ: 44 (no events)
HW Address: 00:13:02:af:83:5f
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: "pci:v00008086d00004222sv0000103Csd0000135Bbc02sc80i00"
Driver Info #0:
Driver Status: iwl3945 is active
Driver Activation Cmd: "modprobe iwl3945"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #5 (PCI bridge)
Hopefully, that’s enough information for some one to pick up on what could be going on. I’m not sure why it’s not detecting my wireless the first time. It did on the first boot but, after that I just have to kill and restart it once and it’ll be fine.
The information given was a great starting point. All looks well to me.
Are you using KDE 4 or Gnome 3? If KDE, are you using kwallet with your encrypted passphrase?
I’m using KDE 4. I’m not using Kwallet as far as I know. It remembers my passphrase when I restart it. If I try to mess with it before killing NetworkManager and restart it, it won’t even show my network as being available. It actually tells me that wireless isn’t enabled or something. Would, using kwallet fix that?
The underlying problem may well be revealed by /var/log/NetworkManager. If you want to share it, view it (as root) in a terminal
sudo cat /var/log/NetworkManager
Upload it to SUSE Paste (and change ‘Delete After’ to something sensible. Post the link to it here.
FWIW, I’ve found numerous threads online across different distros (and versions). This is typical:
wireless does not resume after suspend
BTW, I also found this old thread, which explains how to create a small hook as a workaround to a wireless driver which does not unload or reload properly during suspend/resume. This approach may work for you too. You’ll need to use ‘modprobe -r iwl3945’ and ‘modprobe iwl3945’ in the appropriate places, instead of the r8169 driver mentioned there.
Again sorry for the very long delay. I noticed that there were updates addressing the wireless not resuming on suspend. So, I updated and installed these patches. The only thing is… my system no longer was having issues with suspend, just at start up. So, after the installation of said updates, I now lose it on suspend… haha. Wonderful :D. Hopefully this reinstall fixes 90% of what ever happened and I’ll have a fresh start at this.
Hi everyone,
I’ve got the same problem.
Here the complete story:
I had a problem with suspend on 11.4:
I solved it like said in the thread above and everything was fine (wireless connection automatically re-established after resuming).
Now I’m using 12.1 with GNOME3, after installation I had the same problem and followed the same procedure that worked for 11.4.
This solved the issue partially because now, after resuming, network manager can’t find any connection until I restart it.
Can I adapt the solution for 11.4 to 12.1?
linux-g8jj:~ # /usr/sbin/hwinfo --wlan
16: PCI 200.0: 0282 WLAN controller
[Created at pci.319]
Unique ID: y9sn.apYiokQ9666
Parent ID: qTvu.YrkEO+J3T2A
SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: network
Model: "Atheros AR9285 Wireless Network Adapter (PCI-Express)"
Vendor: pci 0x168c "Atheros Communications Inc."
Device: pci 0x002b "AR9285 Wireless Network Adapter (PCI-Express)"
SubVendor: pci 0x1a3b
SubDevice: pci 0x1089
Revision: 0x01
Driver: "ath9k"
Driver Modules: "ath9k"
Device File: wlan0
Features: WLAN
Memory Range: 0xd2c00000-0xd2c0ffff (rw,non-prefetchable)
IRQ: 17 (no events)
HW Address: 74:f0:6d:7b:b9:a8
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: "pci:v0000168Cd0000002Bsv00001A3Bsd00001089bc02sc80i00"
Driver Info #0:
Driver Status: ath9k is active
Driver Activation Cmd: "modprobe ath9k"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #7 (PCI bridge)