On Wed, 2014-10-08 at 00:10 +0200, poma wrote: > Starting Network Manager... > <info> NetworkManager (version 0.9.10.0-5.git20140704.fc21) is starting... > <info> WEXT support is enabled > <info> WiFi hardware radio set enabled > <info> Loaded device plugin: > /usr/lib/NetworkManager/libnm-device-plugin-wifi.so > <info> WiFi enabled by radio killswitch; enabled by state file > <info> Networking is enabled by state file > Started Network Manager. > <info> (ra0): driver does not support SSID scans (scan_capa 0x00). > <info> (ra0): using WEXT for WiFi device control > <info> (ra0): new 802.11 WiFi device (driver: 'usb' ifindex: 5) > <info> (ra0): exported as /org/freedesktop/NetworkManager/Devices/4 > <info> (ra0): device state change: unmanaged -> unavailable (reason > 'managed') [10 20 2] > <info> (ra0): preparing device > <warn> (ra0): error 100 getting card mode > <error> [1412709645.317223] [platform/wifi/wifi-utils-wext.c:160] > wifi_wext_set_mode(): (ra0): error setting mode 2
Ugh, looks like you're using WEXT, which is historically quite problematic because different drivers expected different sequences of WEXT requests. Any driver that uses WEXT and is not upstream is automatically suspect, unfortunately... > <info> wpa_supplicant started > <info> (ra0) supports 1 scan SSIDs > <info> (ra0): supplicant interface state: starting -> ready > <info> (ra0): device state change: unavailable -> disconnected (reason > 'supplicant-available') [20 30 42] > <info> (ra0): supplicant interface state: ready -> disconnected > <info> (ra0) supports 1 scan SSIDs > <info> startup complete > <info> (ra0): supplicant interface state: disconnected -> inactive > ... > <info> (ra0): disconnecting for new activation request. > <info> (ra0): device state change: activated -> deactivating (reason 'none') > [100 110 0] > <info> NetworkManager state is now DISCONNECTING > <info> (ra0): device state change: deactivating -> disconnected (reason > 'none') [110 30 0] > <info> (ra0): deactivating device (reason 'none') [0] > <info> (ra0): canceled DHCP transaction, DHCP client pid 1144 > <info> NetworkManager state is now DISCONNECTED > <info> Activation (ra0) starting connection 'bla' > <info> Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled... > <warn> Connection disconnected (reason -3) > <info> (ra0): supplicant interface state: completed -> disconnected > <info> Activation (ra0) Stage 1 of 5 (Device Prepare) started... > <info> (ra0): device state change: disconnected -> prepare (reason 'none') > [30 40 0] > <info> NetworkManager state is now CONNECTING > <info> Activation (ra0) Stage 2 of 5 (Device Configure) scheduled... > <info> Activation (ra0) Stage 1 of 5 (Device Prepare) complete. > <info> Activation (ra0) Stage 2 of 5 (Device Configure) starting... > <info> (ra0): device state change: prepare -> config (reason 'none') [40 50 0] > <info> Activation (ra0/wireless): connection 'bla' has security, and secrets > exist. No new secrets needed. > <info> Config: added 'ssid' value 'bla' > <info> Config: added 'mode' value '1' > <info> Config: added 'frequency' value '2412' > <info> Config: added 'key_mgmt' value 'NONE' > <info> Config: added 'auth_alg' value 'OPEN' > <info> Config: added 'wep_key0' value '<omitted>' > <info> Config: added 'wep_tx_keyidx' value '0' > <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete. > <info> Config: set interface ap_scan to 2 > <info> (ra0): supplicant interface state: disconnected -> associating > <warn> Activation (ra0/wireless): Ad-Hoc network creation took too long, > failing activation. The driver did not emit the SIOCGIWAP event, indicating that it had successfully completed Ad-Hoc AP setup. This is a driver bug. > <info> (ra0): device state change: config -> failed (reason > 'supplicant-timeout') [50 120 11] > <info> NetworkManager state is now DISCONNECTED > <warn> Activation (ra0) failed for connection 'bla' > <warn> Connection disconnected (reason -3) > <info> (ra0): supplicant interface state: associating -> disconnected > <info> (ra0): device state change: failed -> disconnected (reason 'none') > [120 30 0] > <info> (ra0): deactivating device (reason 'none') [0] > <warn> (ra0): error 100 getting card mode > <error> [1412717534.522258] [platform/wifi/wifi-utils-wext.c:160] > wifi_wext_set_mode(): (ra0): error setting mode 2 > > > IBSS works via Wicd although not reliable. > BTW AP/WPA2, is it possible at all? NM supports AP mode if wpa_supplicant supports it on the device, but given the information you've provided here, the driver looks very fragile and I wouldn't expect it to work. WPA2 may be possible, but again the driver is quite suspect. The driver is just bad, I'm afraid... Dan _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
