Arch Linux Forums

Zom · 2009-04-14 15:39:08

Since I updated my system about a day ago, NetworkManager seems unable to configure my wireless card for some unknown reason. Only thing that got updated that I can imagine affects NetworkManager would be HAL. Looking through the logs, I spotted this in /var/log/daemon.log

Code:

Multivac NetworkManager: <info>  Wireless now disabled by radio killswitch
Multivac NetworkManager: <info>  (ath0): supplicant manager state:  down -> idle
....
Multivac NetworkManager: <info>  (eth0): device state change: 1 -> 2
Multivac NetworkManager: <info>  (eth0): bringing up device.
Multivac NetworkManager: <info>  (eth0): preparing device.
Multivac NetworkManager: <info>  (eth0): deactivating device (reason: 2).
Multivac NetworkManager: <info>  (eth0): carrier now ON (device state 2)
Multivac NetworkManager: <info>  (eth0): device state change: 2 -> 3
Multivac NetworkManager: <info>  (eth0): carrier now OFF (device state 3)
Multivac NetworkManager: <info>  (eth0): device state change: 3 -> 2
Multivac NetworkManager: <info>  (eth0): deactivating device (reason: 40).
Multivac NetworkManager: <info>  (ath0): device state change: 1 -> 2
Multivac NetworkManager: <info>  (ath0): bringing up device.
Multivac NetworkManager: <info>  (ath0): preparing device.
Multivac NetworkManager: <info>  (ath0): deactivating device (reason: 2).

So yeah, seems NetworkManager thinks the killswitch is on. This is on a Acer Aspire One, which doesn't have a "real" killswitch, so to speak. To enable it, I'm using this in rc.local

Code:

/usr/bin/setkeycodes e055 159
/usr/bin/setkeycodes e056 158

However, I can flick the killswitch how many times I want, it doesn't make a difference to NetworkManager, it still thinks it's enabled. I can still connect with the wireless card manually through iwconfig or through wicd, so why this is specific to NetworkManager is quite the mystery. Still, I'd like to fix it if I'm able to.

Oh, and I've tried using both ath5k and madwifi-hal (from AUR), and that makes zero difference.

Anybody have any ideas or similar issues?

Last edited by Zom (2009-04-14 15:40:29)

hellblazer · 2009-04-14 17:43:58

I am having exactly the same problem in the stock kernel since updating the system today, in my acer aspire one. I'm using the kernel compiled from the kernel-one aur package build and network manager works fine.

Any ideas?

Small progress: by disabling the kill switch module (rfkill) in rc.conf i was able to use network manager in the stock kernel again, but this is no solution, i would like to actually use the switch...

Last edited by hellblazer (2009-04-14 17:58:34)

azolotko · 2009-04-15 14:18:57

I have this problem too. hellblazer, thank you for workaround.

luciferin · 2009-04-15 14:33:08

It's definately an upstream bug. I'm not sure if it's specifically with HAL or with the 2.6.29 Kernel, but I believe it's the. I've had the issue with Fedora on my AAO.

hellblazer · 2009-04-15 15:12:04

Must be the new HAL, i have a 3G USB Modem and yesterday, after updating the system, i had no wireless connection and had to use usb_modswitch to use my modem, witch i haven't had to use in years, since HAL did all the work. Archlinux is always full of surprises in the updates.

Last edited by hellblazer (2009-04-15 15:13:03)

Arch Linux Forums

#1 2009-04-14 15:39:08

The killswitch, and how NetworkManager thinks it's always on.

Code:

Code:

#2 2009-04-14 17:43:58

Re: The killswitch, and how NetworkManager thinks it's always on.

#3 2009-04-15 14:18:57

Re: The killswitch, and how NetworkManager thinks it's always on.

#4 2009-04-15 14:33:08

Re: The killswitch, and how NetworkManager thinks it's always on.

#5 2009-04-15 15:12:04

Re: The killswitch, and how NetworkManager thinks it's always on.

Board footer