[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
** Also affects: linux-backports-modules-2.6.24 (Ubuntu) Importance: Undecided Status: New -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I've tested the iwl3945 from both the linux-backports-modules package and the linux-ubuntu-modules package. I've discovered that turning the kill switch from on (wireless disabled) to off (wireless enabled) does not reactivate the driver when using iwl3945 version 1.2.25 from linux- backports-modules. This does work with iwl3945 driver version 1.2.20 from linux-ubuntu-modules. This happens whether the kill switch is enabled when booting or disabled when booting and then enabled later. Other users having this bug report can verify the version of the driver they are using via 'modinfo iwl3945' or 'apt-cache policy linux- backports-modules-hardy-generic'. It is possible to workaround this bug by reloading the driver via 'rmmod iwl3945' and 'modprobe iwl3945'. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
** Changed in: linux-backports-modules-2.6.24 (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team) Status: New = Triaged -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I have install Linux backport modules to get the LED working on my laptop again. The problem now is the switch to turn the wireless on / off is borked, I can turn the wireless off and the LED turns off too, but the wireless does not turn back on again operating the switch. Laptop: Acer Aspire 5601AWLMi Wireless / Driver: Intel 3945ABG / iwl3945 uname -a Linux quails-laptop 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686 GNU/Linux -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
Answering to myself in https://bugs.launchpad.net/ubuntu/+source/linux- ubuntu-modules-2.6.24/+bug/193970/comments/19. Forget it, it's ridiculous, the hardware wifi switch was off and the driver does the right thing: disables the device. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I'm suffering this problem but just with kernel 2.6.24-14-generic. It worked fine until 2.6.24-12 (included). My laptop is a x61s, with 3945ABG. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I have both the latest kernel (2.6.24-12-generic) and an older one (2.6.24-5-generic) and also the Gutsy kernel (as I just loaded the Hardy kernel on Gutsy). This problem does not happen on the 2.6.24-5 kernel. That uses the 1.1.17 module. I updated the module on the 2.6.24-12 to 1.2.26k from http://www.linuxwireless.org/en/users/Download as 1.2.0 didn't work for me, and I have this problem with it. It would appear it's something that changed in the kernel. I have the same driver set up for the Gutsy kernel, I will try and see if it happens there too. If it doesn't, then it's not a driver issue. I did notice that when the wifi is turned off, my wavelan panel says the device is there, while if the problem isn't happening (that is, on the other kernel and driver) it says the interface is not available. When I turn the wifi on, the panel will see the wifi interface. I will report back here with the findings in the Gutsy kernel. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I've done some testing. I rebooted every time with the switch turned on (wifi off, kill switch on). Every time the network was shown disabled. When I did a sudo ifup wlan, the interface came back on. As long as the switch was on, the network was on DISABLED state shown on lshw -C network. When I turned the switch off (wifi on), the status didn't change. As I brought the interface up, the status changed in lshw. This was the case in both the Gutsy kernel, as well in the Hardy kernel. If there haven't been any changes to hal from 2.6.24-5 to 2.6.24-12, then the problem lies with the driver. Module 1.1.17 doesn't have any problem and it also shows my wavelan panel with the proper info. Kill switch on, no such device, switch off, device is seen and starts functioning. I hope this info helps with solving this bug. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
same here. `modprobe -r iwl3945 modprobe iwl3945` is a workaround but sometimes modprobe -r hangs while cpu on 100% -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
The problem is definitely in the driver. It has to do with the way that initialization happens. It only polls for the device if it's turned on. Needs to be rewritten to allow proper detection. This bug will need to be dealt with upstream rather than in Ubuntu. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
** Tags added: regression -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
Federico, you reported this problem as well - which wireless card do you have? Mary and I have the Intel Corporation PRO/Wireless 3945ABG (driver=iwl3945). Maybe this problem is related to the driver? It's still unclear to me whether the driver or hal or some other software is causing this problem. ** Changed in: hal (Ubuntu) Status: New = Confirmed ** Changed in: linux-meta (Ubuntu) Status: New = Confirmed -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I have a Intel Corporation PRO/Wireless 3945ABG like you :P. I think the problem is in the driver because with ipw3945 (the proprietary driver) I don't have this problem :P -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
Current version of hal: 0.5.10+git20080301-1ubuntu1 Current behaviour: - if starting system with killswitch on, no wireless networks are found until after /etc/init.d/hal restart - if I turn the killswitch off and immediately (say 2 to 4 seconds at most) turn it back on, everything is fine. iwlist scan shows no interfaces during the off period, but sees them again when switched back on - if I turn the killswitch off and wait until Network Manager notices that there's no network available (about 20 or 30 seconds), Network Manager stupidly tries to re-associate with the access point, eventually asks for its WPA key and continues showing wireless networks available in its drop-down list. This may be a separate bug in NM, I'll recheck that behaviour when this one is fixed. iwlist scan does not show any interfaces even when the switch is turned back on. sudo /etc/init.d/hal restart does not seem to help after the switch has been off this long either, I have no alternative but to reboot my machine. - if I turn the killswitch off, suspend to RAM, resume, iwlist scan shows no interfaces. Again, sudo /etc/init.d/hal restart does not help -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I did some further testing to find out why it worked for me yesterday. I could find out that wireless will work if you just restart hal (sudo /etc/init.d/hal restart) after you've disabled the kill switch. You can enable/disable the kill switch then without restarting hal every time. I didn't check if it would be enough to restart hal right after booting (without disabling the kill switch first), but I will try this later. If a restart of hal solves this problem, then I think hal is started to early - or hal is missing some initialisation for the wireless network. I will assign hal to this bug to clarify this issue. ** Also affects: hal (Ubuntu) Importance: Undecided Status: New -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I have to mention that I'm using the hal package provided by Martin Pitts PPA deb http://ppa.launchpad.net/pitti/ubuntu hardy main because of this fix: * Add debian/patches/05_fix_dell_brightness.patch: Fix Dell brightness backend. (LP: #191725) Don't know if this hal makes any difference. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
Mary, could you try the network-manager 0.7, which is in the PPA of Alexander Sack? deb http://ppa.launchpad.net/asac/ubuntu hardy main Either it's because of this version of network-manager or because of the latest kernel update, but today switching on wireless worked without the need of an reboot. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
I don't know what you mean by latest kernel update, probably best to specify versions for clarity. I have linux-image-2.6.24-11-generic package 2.6.24-11.17, which seems to be the latest and which still has this bug. I will test the new network manager now. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
Christian I tried network-manager 0.7 and it doesn't work. It gave me this error: [EMAIL PROTECTED]:~$ nm-applet nm-applet: symbol lookup error: nm-applet: undefined symbol: dbus_method_dispatcher_new And it wont start. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot
Mary, could you try the network-manager 0.7, which is in the PPA of Alexander Sack? deb http://ppa.launchpad.net/asac/ubuntu hardy main Neither the latest kernel version (supplied in the last comment) nor using this version of network-manager 0.7~~svn20080121t191418+eni1-0ubuntu0~pre7 (and associated upgrades to wpasupplicant 0.6.1~git20071119-1ubuntu1~asac1 plus several libraries) made wireless work for me if it was turned off at boot. It still does not work until I do a second boot with wireless switched on. If people want me to do more testing, please let me know whether I should test against the PPA network-manager or the Hardy version. I can only test about once every 24 hours, as tests involve rebooting my machine at least twice. -- iwl3945: Wireless can't be activated if kill switch was on at boot https://bugs.launchpad.net/bugs/193970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
