Description of problem:
The wireless device on the Dell Inspiron 1520 works (from the kernel point of
view) - please see bug #328451.
The wireless interface wlan0 doesn't show up in System ->
Administration -> Network, not even when the interface is up and actually
running. As a consequence, it cannot be controlled easily, set up for DHCP, etc.
After the latest online updates: at system boot, wpa_supplicant fails, reporting
a missing file in /etc/wpa_supplicant... The same error is reported when one
attempts to manually start the wlan0 interface using the wlassistant utility -
wireless network is found, but wlasisstant cannot connect.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Please see bug #328451.
Wireless interface wlan0 cannot be controlled by Network Manager, like any
regular interface; after the latest online updates, it cannot be started by
wlassistant as well, apparently because of a missing file under
/etc/wpa_supplicant (wpa_supplicant initialization failure).
Wireless interface should be controlled like any other interface, in both text
and X mode - start at boot, take address through DHCP or by static
Analyzing the list of open bugs on wpa_supplicant as of October 18, 2007, it
seems there are "historical" compatibility issues about wpa_supplicant and
Network Manager, mostly of them unsolved since much older versions of Fedora.
Any help or idea, please ? Correct/canonical way to go ?
The missing file's name cannot be read at boot.
wpa_supplicant *is* started at boot, in ntsysv, but it reports FAILED.
However, here's what wlassistant says in background, when launched manually:
WPA client started. Waiting for status...
==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or
See my report at https://bugzilla.redhat.com/show_bug.cgi?id=375721
I have a screen image for f8 showing that the reason possibly for a missing file
may be that there is a space missing in the sequence -Dwextdbus... is it
possible that in a config file (but where?) it should instead be -Dwext dbus.... ?
*** This bug has been marked as a duplicate of 375721 ***
*** This bug has been marked as a duplicate of 244029 ***