ath5k?
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
ath5k?
by list-34
::
Rate this Message:
Hello,
I have an AR5212 WLAN adapter that runs with the ath5k driver from linux 2.6.31. I've tried NM 0.7.1 and 0.7.1_p20090824, and both fail to operate that card correctly. It works flawlessly with wicd or wpa_supplicant, but in nm-applet it says "device not ready". In syslog I see: Oct 26 00:42:47 wiese NetworkManager: <info> starting... Oct 26 00:42:47 wiese NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_168c_1014_rfkill_phy0_wlan Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01). Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'ath5k') Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_05_4e_47_24_10 Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the supplicant... Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the system settings daemon... Oct 26 00:42:52 wiese [25148.952901] ADDRCONF(NETDEV_UP): eth0: link is not ready Oct 26 00:42:52 wiese [25148.953399] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): device state change: 1 -> 2 (reason 2) Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): bringing up device. Oct 26 00:42:52 wiese [25148.986093] ADDRCONF(NETDEV_UP): wlan0: link is not ready Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): preparing device. Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): deactivating device (reason: 2). Oct 26 00:42:52 wiese NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed BTW, this happens now after I changed the system from Ubuntu 9.04 to Gentoo for performance reasons. In Ubuntu it used to work (also with ath5k). I have no idea if they patched nm or ath5k what else they might do differently. thanks for any hints... _______________________________________________ NetworkManager-list mailing list NetworkManager-list@... http://mail.gnome.org/mailman/listinfo/networkmanager-list |
|
|
Re: ath5k?
by Dan Williams
::
Rate this Message:
On Mon, 2009-10-26 at 01:13 +0100, list@... wrote:
> Hello, > > I have an AR5212 WLAN adapter that runs with the ath5k driver from linux > 2.6.31. I've tried NM 0.7.1 and 0.7.1_p20090824, and both fail to > operate that card correctly. It works flawlessly with wicd or > wpa_supplicant, but in nm-applet it says "device not ready". > In syslog I see: Oct 26 00:42:52 wiese NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed which means that the supplicant hasn't been correctly initialized; what is the contents of your: /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service file, and what do you get when you run this command (as root)? dbus-send --system --print-reply --dest=fi.epitest.hostap.WPASupplicant /fi/epitest/hostap/WPASupplicant fi.epitest.hostap.WPASupplicant.getInterface string:wlan0 you should get something like this: method return sender=:1.58 -> dest=:1.78 reply_serial=2 object path "/fi/epitest/hostap/WPASupplicant/Interfaces/0" Dan > Oct 26 00:42:47 wiese NetworkManager: <info> starting... > Oct 26 00:42:47 wiese NetworkManager: <info> Found radio killswitch > /org/freedesktop/Hal/devices/pci_168c_1014_rfkill_phy0_wlan > Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): driver supports > SSID scans (scan_capa 0x01). > Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): new 802.11 WiFi > device (driver: 'ath5k') > Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): exported as > /org/freedesktop/Hal/devices/net_00_05_4e_47_24_10 > Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the > supplicant... > Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the system > settings daemon... > Oct 26 00:42:52 wiese [25148.952901] ADDRCONF(NETDEV_UP): eth0: link is > not ready > Oct 26 00:42:52 wiese [25148.953399] e1000: eth0 NIC Link is Up 1000 > Mbps Full Duplex, Flow Control: RX/TX > Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): device state > change: 1 -> 2 (reason 2) > Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): bringing up device. > Oct 26 00:42:52 wiese [25148.986093] ADDRCONF(NETDEV_UP): wlan0: link is > not ready > Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): preparing device. > Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): deactivating > device (reason: 2). > Oct 26 00:42:52 wiese NetworkManager: supplicant_interface_acquire: > assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed > > BTW, this happens now after I changed the system from Ubuntu 9.04 to > Gentoo for performance reasons. In Ubuntu it used to work (also with > ath5k). I have no idea if they patched nm or ath5k what else they might > do differently. > > thanks for any hints... > _______________________________________________ > NetworkManager-list mailing list > NetworkManager-list@... > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ NetworkManager-list mailing list NetworkManager-list@... http://mail.gnome.org/mailman/listinfo/networkmanager-list |
|
|
Re: ath5k?
by list-34
::
Rate this Message:
Dan Williams wrote:
> Oct 26 00:42:52 wiese NetworkManager: supplicant_interface_acquire: > assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed > > which means that the supplicant hasn't been correctly initialized; > what is the contents of your: > > /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service # cat /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service [D-BUS Service] Name=fi.epitest.hostap.WPASupplicant Exec=/usr/sbin/wpa_supplicant -u User=root > > file, and what do you get when you run this command (as root)? > > dbus-send --system --print-reply > --dest=fi.epitest.hostap.WPASupplicant > /fi/epitest/hostap/WPASupplicant > fi.epitest.hostap.WPASupplicant.getInterface string:wlan0 > > you should get something like this: > > method return sender=:1.58 -> dest=:1.78 reply_serial=2 > object path "/fi/epitest/hostap/WPASupplicant/Interfaces/0" # dbus-send --system --print-reply --dest=fi.epitest.hostap.WPASupplicant /fi/epitest/hostap/WPASupplicant fi.epitest.hostap.WPASupplicant.getInterface string:wlan0 Error org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/libexec/dbus-daemon-launch-helper: Success Hmm... I don't know anything about DBUS, so I have no idea what to make of this. Any help is appreciated. But thanks for pointing me to the problem. > Dan > >> Oct 26 00:42:47 wiese NetworkManager: <info> starting... >> Oct 26 00:42:47 wiese NetworkManager: <info> Found radio killswitch >> /org/freedesktop/Hal/devices/pci_168c_1014_rfkill_phy0_wlan >> Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): driver supports >> SSID scans (scan_capa 0x01). >> Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): new 802.11 WiFi >> device (driver: 'ath5k') >> Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): exported as >> /org/freedesktop/Hal/devices/net_00_05_4e_47_24_10 >> Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the >> supplicant... >> Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the system >> settings daemon... >> Oct 26 00:42:52 wiese [25148.952901] ADDRCONF(NETDEV_UP): eth0: link is >> not ready >> Oct 26 00:42:52 wiese [25148.953399] e1000: eth0 NIC Link is Up 1000 >> Mbps Full Duplex, Flow Control: RX/TX >> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): device state >> change: 1 -> 2 (reason 2) >> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): bringing up device. >> Oct 26 00:42:52 wiese [25148.986093] ADDRCONF(NETDEV_UP): wlan0: link is >> not ready >> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): preparing device. >> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): deactivating >> device (reason: 2). >> Oct 26 00:42:52 wiese NetworkManager: supplicant_interface_acquire: >> assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed >> >> BTW, this happens now after I changed the system from Ubuntu 9.04 to >> Gentoo for performance reasons. In Ubuntu it used to work (also with >> ath5k). I have no idea if they patched nm or ath5k what else they might >> do differently. >> >> thanks for any hints... >> _______________________________________________ >> NetworkManager-list mailing list >> NetworkManager-list@... >> http://mail.gnome.org/mailman/listinfo/networkmanager-list > _______________________________________________ NetworkManager-list mailing list NetworkManager-list@... http://mail.gnome.org/mailman/listinfo/networkmanager-list |
|
|
Re: ath5k?
by list-34
::
Rate this Message:
Dan, thank you very much, and greetings from my girlfriend, who is happy
now. dbus-daemon-launch-helper must have been broken somehow. I just reinstalled dbus and now it works like a charm, even without restarting anything. list@... wrote: > Dan Williams wrote: >> Oct 26 00:42:52 wiese NetworkManager: supplicant_interface_acquire: >> assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed >> >> which means that the supplicant hasn't been correctly initialized; >> what is the contents of your: >> >> /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service >> > > # cat > /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service > [D-BUS Service] > Name=fi.epitest.hostap.WPASupplicant > Exec=/usr/sbin/wpa_supplicant -u > User=root > >> >> file, and what do you get when you run this command (as root)? >> >> dbus-send --system --print-reply >> --dest=fi.epitest.hostap.WPASupplicant >> /fi/epitest/hostap/WPASupplicant >> fi.epitest.hostap.WPASupplicant.getInterface string:wlan0 >> >> you should get something like this: >> >> method return sender=:1.58 -> dest=:1.78 reply_serial=2 >> object path "/fi/epitest/hostap/WPASupplicant/Interfaces/0" > > # dbus-send --system --print-reply > --dest=fi.epitest.hostap.WPASupplicant > /fi/epitest/hostap/WPASupplicant > fi.epitest.hostap.WPASupplicant.getInterface string:wlan0 > Error org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute > program /usr/libexec/dbus-daemon-launch-helper: Success > > Hmm... I don't know anything about DBUS, so I have no idea what to > make of this. Any help is appreciated. But thanks for pointing me to > the problem. > >> Dan >> >>> Oct 26 00:42:47 wiese NetworkManager: <info> starting... >>> Oct 26 00:42:47 wiese NetworkManager: <info> Found radio killswitch >>> /org/freedesktop/Hal/devices/pci_168c_1014_rfkill_phy0_wlan >>> Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): driver supports >>> SSID scans (scan_capa 0x01). >>> Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): new 802.11 WiFi >>> device (driver: 'ath5k') >>> Oct 26 00:42:47 wiese NetworkManager: <info> (wlan0): exported as >>> /org/freedesktop/Hal/devices/net_00_05_4e_47_24_10 >>> Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the >>> supplicant... >>> Oct 26 00:42:47 wiese NetworkManager: <info> Trying to start the system >>> settings daemon... >>> Oct 26 00:42:52 wiese [25148.952901] ADDRCONF(NETDEV_UP): eth0: link is >>> not ready >>> Oct 26 00:42:52 wiese [25148.953399] e1000: eth0 NIC Link is Up 1000 >>> Mbps Full Duplex, Flow Control: RX/TX >>> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): device state >>> change: 1 -> 2 (reason 2) >>> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): bringing up >>> device. >>> Oct 26 00:42:52 wiese [25148.986093] ADDRCONF(NETDEV_UP): wlan0: >>> link is >>> not ready >>> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): preparing device. >>> Oct 26 00:42:52 wiese NetworkManager: <info> (wlan0): deactivating >>> device (reason: 2). >>> Oct 26 00:42:52 wiese NetworkManager: supplicant_interface_acquire: >>> assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed >>> >>> BTW, this happens now after I changed the system from Ubuntu 9.04 to >>> Gentoo for performance reasons. In Ubuntu it used to work (also with >>> ath5k). I have no idea if they patched nm or ath5k what else they might >>> do differently. >>> >>> thanks for any hints... >>> _______________________________________________ >>> NetworkManager-list mailing list >>> NetworkManager-list@... >>> http://mail.gnome.org/mailman/listinfo/networkmanager-list >> > > _______________________________________________ > NetworkManager-list mailing list > NetworkManager-list@... > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ NetworkManager-list mailing list NetworkManager-list@... http://mail.gnome.org/mailman/listinfo/networkmanager-list |
| Free embeddable forum powered by Nabble | Forum Help |
