Version: unknown (using 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)), Kubuntu packages) Compiler: cc OS: Linux (x86_64) release 2.6.31-17-generic Since I've installed the new 4.4 package, I cannot use the wifi anymore :(
Created attachment 39245 [details] Knetwork applet with wifi disabled
Created attachment 39246 [details] some info about my system As you can see the wifi card in the "base system" is up and running
Do cnetworkmanager or nm-applet see the wireless card? Is the card listed in /etc/network/interfaces? (this prevents NM from seeing it on *ubuntu)
$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback As you can see nor eth0 nor wlan0 are listed in the file ...
(In reply to comment #3) > Do cnetworkmanager or nm-applet see the wireless card? Is the card listed in > /etc/network/interfaces? (this prevents NM from seeing it on *ubuntu) Is there some error log where I can check why KNetwork part does not see that in the "vanilla linux part" the wlan0 is up and running?
Other news about my problem... if I try to UP the interface I get the following error # ifconfig wlan0 up SIOCSIFFLAGS: Unknown error 132
The solution that I've found for this problem is: 1) Switch off the wireless part (on my xps dell I have a switch to turn off BT and wifi) 2) # rmmod iwlagn && rfkill block all && rfkill unblock all && modprobe iwlagn && rfkill unblock all 3) turn on the switch... In this way it works, but I don't think it is a solution :(
i may be complicating matters by overlapping software. here is what i noticed. hardware works fine in fc12-gnome hardware forgetfully (need manual re-enable at boot) works in fc13-gnome hardware doesnt seem to work in fc13-kde as described below and in attached log(s). 0) there is an entry in messages about the radio kill switch rfkill0 having "driver <unknown>" that looks interesting. [rfkill list seems to always say that there is no software nor hardware blocks] [working from comment#7 above and cycling the radios hardware switch a few times rapidly seems to have an effect on some of the informational commands that seem to indicate that it should be connected but i havent got it to actually connect] [never got errors that comment#7 above got] 1) iwlist command responded differently at some point if i asked it generically vs if i ask it and also give it the hidden bssid. something to the effect of 'scanning not supported' vs lots of information about the wireless connection. 2) system config network wont allow me to enable/disable/delete wire or wireless (buttons grayed out always) though i seem to be able to add new and edit current. 3) there is an entry in messages about invalid bssid [caused because using hidden bssid?] 4) there seems to be a noteworthy amount of failed starts and crashes when starting various network configuration applications in f13-kde. as a test i am trying to do as much as possible (and as simply as possible) by way of gui because thats how avg users will often have to do it so we need it to work well. for example it seems like i can only start knetworkmanager from tray icon as from menu it never appears [i gather that is because its already running but doesnt get pulled to foreground?]. 5) **[at some point there is a mysterious blurb in messages about an invalid wep key (which i an not using on purpose as the install uses wpa2-personal so i am not sure where its getting that part)]** 6) {anyway i have had good user feedback on the kde user interface and just need wifi and printing to start experimenting with (implimentation may wait for default on-access virus checking and some codecs will be nice too :') ) keep up the good work.} 7) [related link: https://bugzilla.redhat.com/show_bug.cgi?id=516788]
related downstream link note the error of kde's bug report comment#6 above on this downstream links comment#7 at https://bugzilla.redhat.com/show_bug.cgi?id=586808
Created attachment 48179 [details] var log messages this is the messages log referred to in comment#8 it has interesting parts including: *zaph* : possible rf kill switch driver identification *pow* : entry about invalid bssid *foom* : entry about 'wep' key entry when there should be 'wpa2' entry instead? tune in next time!
Created attachment 48364 [details] var log messages without wep errors dont know how i managed to get the wep errors in the messages log from comment#10 but i did manage to get rid of them. this is am updated messages log. still cant connect with hidden ssid wpa2 and still gets labeled as 'insecure network' in the connection dialog.
Created attachment 52073 [details] iwlist from fc14beta-kde livecd where wifi no connect to hidden
Created attachment 52074 [details] var log messages of fc14beta-kde where couldnt connect with hidden wifi
where for comment#12 and comment#13 fedora core 14 beta kde livecd looks to be using knetworkmanager-0.9-0.20.20100603.fc14.x86_64.rpm though now i see knetworkmanager-0.9-0.25.20100920.fc14.x86_64.rpm is available so guess i will have to repeat test
(In reply to comment #11) > Created an attachment (id=48364) [details] > var log messages without wep errors > > dont know how i managed to get the wep errors in the messages log from > comment#10 but i did manage to get rid of them. > > this is am updated messages log. > The last two lines indicate a knetworkmanager problem in bad bssid format. there is a patch for this issue in bug 238046 *But*, the reporter's issue is something different. It appears to be connected with drivers and hardware. I think the culprit may be dell_laptop platform driver - rmmod it could help. References: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/523143 http://ubuntuforums.org/showthread.php?t=1377829 https://bugzilla.redhat.com/show_bug.cgi?id=601258 https://bugzilla.redhat.com/show_bug.cgi?id=627214 dmesg and rfkill list would help.
Hi, I found the problem Often when I start the system, in the file /var/lib/NetworkManager/NetworkManager.state the value WirelessEnabled is set to faulse. I have to change it to true and restart the system. Hope it helps.
Yeah, /var/lib/NetworkManager/NetworkManager.state is a file that should preserve settings over reboot. However, it's not meant to be edited directly. It gets probably to false state due to rfkill/driver bad behaviour. See e.g. https://bugzilla.redhat.com/show_bug.cgi?id=595931 about that.
Is this still happening?
(In reply to comment #18) > Is this still happening? Not for me. tnx