DJA wrote: > Lan Barnes wrote: >>.. >> ------------------------------------------------------------------------ >> >> [EMAIL PROTECTED] lbarnes]# service network restart >> Shutting down interface wlan0: [ OK ] >> Shutting down loopback interface: [ OK ] >> Bringing up loopback interface: [ OK ] >> Bringing up interface wlan0: Error for wireless request "Set Mode" >> (8B06) : >> SET failed on device wlan0 ; Invalid argument. >> [ OK ] > > That error is probably not fatal. It seems only to indicate that a > particular parameter is unknown to the driver. IOW, common.
I sent another post before I saw this, and I bet DJA is right. The other suggestion _may_ give additional information and tips about your chipset, but is probably not central to the immediate problem. >.. > wmaster0 is showing the same MAC, so it's the same hardware, but I > suspect it's reflecting a different function. Did you preserve or copy your old etc/sysconfig/network-scripts, maybe? >.. > > BTW, ifconfig is informationally useful only if Wifi is already working, > useless otherwise. Always use it's cousin iwconfig for manually > configuring, testing, and using wireless. But even then only if you are > using CLI. Otherwise, see below. I _have_ found it useful for things like "ifconfig wlan0 up" to workaround bugs in driver (or startup-script) code. And I do think you can use it for another experiment that LB and I already did on sat. Namely assign an (unused local) ip and just try pinging your router. >.. > What is wmaster0? Is this a artifact of your particular Wifi chipset? I > know that Fedora does on occasion do some weird things regarding > assignment of Wifi interface names. I'm wondering it that's an alias for > wlan0 and your card/chipset is in the wrong mode. E.g it's in Ad-hoc mode. I concur that it might be cleaner to get rid of wmaster0. Is there an /etc/sysconfig/network-scripts/ifcfg-wmaster0 you can delete or another alias somewhere?? > General tips learned through much pain: > > Since you are a GUI guy (that's okay, so am I), you should have both > NetworkManager and his brother NetworkManagerDispatcher running as > services. In Gnome test and manage the card (once it's working) with > nm-applet; in KDE, with Knetworkmanager. All of these programs are > included in Fedora. They all work well. Don't use system-conf-network to > manage Wifi if you can help it. It is at odds with (and inferior to) > NetworkManager. I've heard that advice too. I've not pursued testing it, but I have indeed had decent success with NetworkManager. >.. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
