[Bug 566321] New: Wireless radio always ON after boot, LED always ON regardless but works after suspend
http://bugzilla.novell.com/show_bug.cgi?id=566321 http://bugzilla.novell.com/show_bug.cgi?id=566321#c0 Summary: Wireless radio always ON after boot, LED always ON regardless but works after suspend Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs@forge.provo.novell.com ReportedBy: linuxoid.au@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 I have openSUSE 11.2 installed on an Asus UL30A-QX130V laptop which has an Intel 5100 series a/g/n wireless module. I have two problems: 1. Wireless is always ON on boot 2. Wireless LED always ON no matter what wireless radio does I can use Fn-F2 to disable the radio, but the LED always stays ON. BUT, if I suspend the laptop to RAM/HDD, bring it back out of suspend and then press Fn-F2 ON/OFF, the LED follows the radio, that is it switches ON/OFF... until it reboots. - Wi-fi is Intel Wireless WiFi Link 5100 ABGN PCI - Bluetooth is Broadcom BT-253 USB. - Wifi driver is ipw-firmware-8-109.2 - Can't find a bluetooth driver/firmware - Running KDE-4.3 & network controlled with NetworkManager I also have a Dell laptop which also comes with Fn-F2 radio switch function, same as my Asus laptop. But the radio stays OFF in Dell on boot and LED works properly but radio is always ON in Asus on boot and LED always stays ON (unless after suspend). But if they work as they should in one laptop and not in the other, this means Linux can do this but some config has to be changed on Asus. There's gotta be something in the boot config somewhere, I just don't know where to look. Or maybe the asus_laptop module has to be fixed. Reproducible: Always Steps to Reproduce: 1. Boot - wireless radio ON 2. Fn-F2 - radio OFF, LED ON, Fn-F2 - radio ON, LED ON, Fn-F2 - radio OFF, LED ON 3. Reboot - radio ON again, LED ON or 1. Boot - wireless radio ON 2. Fn-F2 - radio OFF, LED ON, Fn-F2 - radio ON, LED ON, Fn-F2 - radio OFF, LED ON 3. Suspend to RAM/HDD 4. Power up from suspend - radio OFF, LED OFF 5. Fn-F2 - radio OFF, LED OFF, Fn-F2 - radio ON, LED ON, Fn-F2 - radio OFF, LED OFF 6. Reboot - radio ON again, LED ON Actual Results: 1. Wireless always ON on boot 2. LED always ON regardless of wireless state Expected Results: 1. If powered down with wireless OFF - it should power up with wireless OFF 2. LED should follow wireless state Here are my modules from lsmod: Module Size Used by nfs 405312 0 lockd 95636 1 nfs fscache 52016 1 nfs nfs_acl 4072 1 nfs auth_rpcgss 56800 1 nfs sunrpc 266984 5 nfs,lockd,nfs_acl,auth_rpcgss af_packet 28680 4 ip6t_LOG 7980 6 xt_tcpudp 4104 2 xt_pkttype 2248 3 xt_physdev 2968 2 ipt_LOG 7660 6 xt_limit 4076 12 vboxnetadp 116012 0 vboxnetflt 125804 0 vboxdrv 1737004 1 vboxnetflt rfcomm 89960 6 snd_pcm_oss 60032 0 snd_mixer_oss 22728 1 snd_pcm_oss snd_seq 78528 0 snd_seq_device 10460 1 snd_seq sco 24076 2 bridge 75144 1 stp 3340 1 bridge llc 8848 2 bridge,stp bnep 23208 2 l2cap 50696 16 rfcomm,bnep autofs4 36816 1 edd 13232 0 i915 282536 1 drm 227808 2 i915 i2c_algo_bit 8396 1 i915 cpufreq_conservative 10360 0 cpufreq_userspace 4364 0 cpufreq_powersave 2152 0 acpi_cpufreq 11544 0 ip6t_REJECT 6856 3 nf_conntrack_ipv6 26600 4 ip6table_raw 3720 1 xt_NOTRACK 2248 4 ipt_REJECT 4136 3 xt_state 2920 8 iptable_raw 3560 1 iptable_filter 4520 1 ip6table_mangle 5000 0 nf_conntrack_netbios_ns 3400 0 nf_conntrack_ipv4 14232 4 nf_conntrack 102912 5 nf_conntrack_ipv6,xt_NOTRACK,xt_state,nf_conntrack _netbios_ns,nf_conntrack_ipv4 nf_defrag_ipv4 2856 1 nf_conntrack_ipv4 ip_tables 24536 2 iptable_raw,iptable_filter ip6table_filter 4552 1 ip6_tables 26072 4 ip6t_LOG,ip6table_raw,ip6table_mangle,ip6table_fil ter x_tables 30768 12 ip6t_LOG,xt_tcpudp,xt_pkttype,xt_physdev,ipt_LOG,x t_limit,ip6t_REJECT,xt_NOTRACK,ipt_REJECT,xt_state ,ip_tables,ip6_tables fuse 87984 1 loop 22292 0 dm_mod 101448 0 arc4 2568 2 ecb 4168 2 cryptomgr 109904 0 aead 10792 1 cryptomgr pcompress 3560 1 cryptomgr crypto_blkcipher 18028 2 ecb,cryptomgr crypto_hash 17416 1 cryptomgr snd_hda_codec_intelhdmi 17964 1 btusb 20156 2 bluetooth 122372 9 rfcomm,sco,bnep,l2cap,btusb crypto_algapi 25904 7 arc4,ecb,cryptomgr,aead,pcompress,crypto_blkcipher ,crypto_hash snd_hda_codec_realtek 317868 1 iwlagn 206280 0 snd_hda_intel 37088 2 iwlcore 239468 1 iwlagn mac80211 257312 2 iwlagn,iwlcore snd_hda_codec 111112 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_ hda_intel snd_hwdep 11216 1 snd_hda_codec cfg80211 123264 3 iwlagn,iwlcore,mac80211 sg 40128 0 snd_pcm 117808 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 32152 2 snd_seq,snd_pcm snd 97608 15 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,s nd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_h da_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer uvcvideo 74196 0 videodev 46848 1 uvcvideo v4l1_compat 19148 2 uvcvideo,videodev v4l2_compat_ioctl32 12776 1 videodev serio_raw 7916 0 pcspkr 3720 0 rfkill 28176 2 bluetooth,cfg80211 iTCO_wdt 15056 0 atl1c 45868 0 iTCO_vendor_support 4908 1 iTCO_wdt snd_page_alloc 12600 2 snd_hda_intel,snd_pcm intel_agp 37136 1 video 29156 1 i915 ac 6416 0 battery 15824 0 asus_laptop 25100 0 button 8360 0 ext4 401040 3 jbd2 115072 1 ext4 crc16 2504 1 ext4 fan 6352 0 thermal 25160 0 processor 56900 3 acpi_cpufreq thermal_sys 21888 4 video,fan,thermal,processor Here's the dmesg output: # dmesg | grep iw [ 6.432564] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27kds [ 6.432569] iwlagn: Copyright(c) 2003-2009 Intel Corporation [ 6.432733] iwlagn 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 6.432747] iwlagn 0000:02:00.0: setting latency timer to 64 [ 6.432827] iwlagn 0000:02:00.0: Detected Intel Wireless WiFi Link 1000 Series BGN REV=0x6C [ 6.465516] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [ 6.465618] iwlagn 0000:02:00.0: irq 28 for MSI/MSI-X [ 7.144104] phy0: Selected rate control algorithm 'iwl-agn-rs' [ 21.434223] iwlagn 0000:02:00.0: firmware: requesting iwlwifi-1000-3.ucode [ 21.450874] iwlagn 0000:02:00.0: loaded firmware version 128.50.3.1 [ 21.532277] Registered led device: iwl-phy0::radio [ 21.532342] Registered led device: iwl-phy0::assoc [ 21.532397] Registered led device: iwl-phy0::RX [ 21.536039] Registered led device: iwl-phy0::TX [28847.593250] Registered led device: iwl-phy0::radio [28847.593317] Registered led device: iwl-phy0::assoc [28847.593369] Registered led device: iwl-phy0::RX [28847.593425] Registered led device: iwl-phy0::TX -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=566321 http://bugzilla.novell.com/show_bug.cgi?id=566321#c1 G J <cuisineconcepts@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cuisineconcepts@gmail.com --- Comment #1 from G J <cuisineconcepts@gmail.com> 2010-01-08 08:50:01 UTC --- I can also confirm that wireless (and bluetooth) are always turned on at boot. I have a Thinkpad X60s with Intel 3945ABG network card. I think that the radio states should remember their last state from the last shutdown. However my wireless led does turn off and on with the appropriate radio state. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=566321 https://bugzilla.novell.com/show_bug.cgi?id=566321#c2 Uwe Drechsel <uwedr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX --- Comment #2 from Uwe Drechsel <uwedr@suse.com> 2011-08-26 12:53:19 CEST --- The lifecycle of openSUSE 11.2 ended on May 12th 2011. I'm closing this bug to make it easier to focus on upcoming releases. Thank you for reporting this issue and we are sorry that we have not be able to fix it before this version reached its end of life. If you would still like to see this bug fixed and are able to reproduce it against a maintained version, please reopen this bug and change the 'version' of this bug to the applicable version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=566321 https://bugzilla.novell.com/show_bug.cgi?id=566321#c3 --- Comment #3 from Uwe Drechsel <uwedr@suse.com> 2011-08-26 12:57:45 CEST --- The lifecycle of openSUSE 11.2 ended on May 12th 2011. I'm closing this bug to make it easier to focus on upcoming releases. Thank you for reporting this issue and we are sorry that we have not be able to fix it before this version reached its end of life. If you would still like to see this bug fixed and are able to reproduce it against a maintained version, please reopen this bug and change the 'version' of this bug to the applicable version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com