Hard blocked WiFi - SuSE 12.2

VintagePC · September 6, 2012, 1:45pm

Hi folks - Just did a zypper dup from 12.1 to 12.2, this is a 32 bit system (only extra repo I have enabled is Packman).

Issue I’m having is that my Wireless is hard blocked on cold boot (as reported by rfkill). This wasn’t an issue in SuSE 12.1

Rebooting to Windoze and back fixes the issue (as in I can connect and use it normally), but that’s a real nuisance.

My machine is a laptop, MSI M662. It does have a Wifi kill switch, but I’ve verified it’s on, and toggling it has no effect except for switching the soft block. What’s more, I rarely use it and always leave it enabled - so there’s no reason for the wifi to go into hard block because it’s out of sync with the switch or so (it’s a soft-switch like a key, not an on-off slider).

Device itself is rt73usb, is an MSI RT2573 (0db0:6877).

I’ve had a similar issue before, but that was an issue with the Networkmanager.state file not being reset properly, this time it has WirelessEnabled=true in it, so that’s not the issue.
Reloading the rt73/rt2x00 kernel modules has no effect.

I see nothing unusual in the dmesg output when reloading the kernel modules, and I do not have ndiswrapper installed at all (hasn’t been for ages).

I haven’t meddled much in the realm of Wifi config/tools, so I’m not sure what diags are available - if there’s output of something you’d like to see, let me know and I’ll post it.

russ8293 · September 6, 2012, 2:20pm

what wireless chip/card do you have?

VintagePC · September 6, 2012, 2:31pm

It’s an internal PCIE card, BTW.

russ8293 · September 6, 2012, 6:24pm

Im not sure

I’m have a similar issue sot of with 12.2 - mine shows as on and as working but does not detect the wifi accesspoint at all after booting up. if i turn the wireless switch off then back on, then it pops up and autoconnects

VintagePC · September 6, 2012, 9:11pm

Looks to be a driver bug. Using NDISWRAPPER the issue is not there, and it unblocks the device for the rt73usb driver.

lwfinger · September 6, 2012, 9:32pm

On 09/06/2012 02:16 PM, VintagePC wrote:
>
> Looks to be a driver bug. Using NDISWRAPPER the issue is not there, and
> it unblocks the device for the rt73usb driver.

When you use ndiswrapper, the entire rfkill setup is sidestepped. What you need
to do is provide the output of ‘/usr/sbin/rfkill list’. As the problem could be
any number of things, this will tell us which driver is at fault. It is probably
a wmi module.

VintagePC · September 6, 2012, 10:46pm

I’ll get you exact output tomorrow, but I do recall from memory that it gives phy0: followed by some card details, and then

Soft blocked: no
Hard blocked: yes

Mashing the button for Wifi toggles soft blocked (and rfkill event shows this registering), but hard block remains at “yes” until I either reboot to Windows or load ndiswrapper, then unload and reload rt73usb.

I’m NOT loading rt73usb and ndis at the same time, sorry if I wasn’t explicitly clear on that before. I know enough that bad things happen when you do this

VintagePC · September 7, 2012, 1:27pm

Exact output:

0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

that’s all.

e-jones · September 7, 2012, 2:29pm

I had exactly the same issue as VintagePC after installing 12.2. I have a broadcom BCM4312. I installed the drivers using sudo /usr/sbin/install_bcm43xx_firmware. I did the same with 12.1 and I could use the wlan as soon as the drivers had been installed. With 12.2 I had to do the same as VintagePC (booted into windows and then rebooted into 12.2) and wlan is working as it should.

lwfinger · September 7, 2012, 7:07pm

On 09/07/2012 07:36 AM, e-jones wrote:
>
> I had exactly the same issue as VintagePC after installing 12.2. I have
> a broadcom BCM4312. I installed the drivers using sudo
> /usr/sbin/install_bcm43xx_firmware. I did the same with 12.1 and I could
> use the wlan as soon as the drivers had been installed. With 12.2 I had
> to do the same as VintagePC (booted into windows and then rebooted into
> 12.2) and wlan is working as it should.

Please note that /usr/sbin/install_bcm43xx_firmware has ABSOLUTELY nothing to
do with installing drivers!!! It merely loads the firmware that Broadcom
refuses to let us redistribute. Please use the terminology correctly. Yes, the
driver will not work if the firmware is not available, but it is always a part
of the kernel. The firmware is a set of files in /lib/firmware/b43/.

If you had to boot Window$ in order to get the rfkill switch to work correctly,
it is because Window$ leaves the machine in a condition from which we do not
know how to recover. If you never shut down Window$ with the wifi off, you
should be OK. I cannot duplicate the condition, as my laptop has a physical
switch, and does not use any of that wmi (Window$ Management Interface) crap,
which was invented so that laptop vendors could save $0.50 by mot including a
switch.

e-jones · September 7, 2012, 7:51pm

Sorry for the wrong terminology. Main thing for me is that wlan is working.

VintagePC · September 7, 2012, 8:47pm

lwfinger:

On 09/07/2012 07:36 AM, e-jones wrote:
>
> I had exactly the same issue as VintagePC after installing 12.2. I have
> a broadcom BCM4312. I installed the drivers using sudo
> /usr/sbin/install_bcm43xx_firmware. I did the same with 12.1 and I could
> use the wlan as soon as the drivers had been installed. With 12.2 I had
> to do the same as VintagePC (booted into windows and then rebooted into
> 12.2) and wlan is working as it should.

Please note that /usr/sbin/install_bcm43xx_firmware has ABSOLUTELY nothing to
do with installing drivers!!! It merely loads the firmware that Broadcom
refuses to let us redistribute. Please use the terminology correctly. Yes, the
driver will not work if the firmware is not available, but it is always a part
of the kernel. The firmware is a set of files in /lib/firmware/b43/.

If you had to boot Window$ in order to get the rfkill switch to work correctly,
it is because Window$ leaves the machine in a condition from which we do not
know how to recover. If you never shut down Window$ with the wifi off, you
should be OK. I cannot duplicate the condition, as my laptop has a physical
switch, and does not use any of that wmi (Window$ Management Interface) ****,
which was invented so that laptop vendors could save $0.50 by mot including a
switch.

I don’t even boot windows in the first place, except in very rare circumstances

lwfinger · September 7, 2012, 10:26pm

On 09/07/2012 01:56 PM, VintagePC wrote:

> I don’t even boot windows in the first place, except in very rare
> circumstances

In that case, and your Fn “switch” is not working, then the wmi module for your
laptop model is not doing the job.

VintagePC · September 8, 2012, 1:04am

Where can I find more info on this?
Output of lsmod is below, i don’t see anything related to WMI there… assuming the modules would have wmi in the name.

Module                  Size  Used by
nls_utf8               12493  0 
loop                   22991  0 
af_packet              30681  4 
ndiswrapper           221457  0 
xt_LOG                 17247  10 
xt_tcpudp              12756  2 
xt_limit               12541  10 
xt_pkttype             12456  3 
nf_conntrack_ipv6      14060  3 
nf_defrag_ipv6         13654  1 nf_conntrack_ipv6
ip6t_REJECT            12826  3 
ipt_REJECT             12485  3 
ip6table_raw           12603  1 
xt_NOTRACK             12456  4 
iptable_raw            12598  1 
iptable_filter         12706  1 
ip6table_mangle        12620  0 
nf_conntrack_netbios_ns    12585  0 
nf_conntrack_broadcast    12541  1 nf_conntrack_netbios_ns
nf_conntrack_ipv4      14501  3 
nf_defrag_ipv4         12649  1 nf_conntrack_ipv4
ip_tables              17987  2 iptable_raw,iptable_filter
xt_conntrack           12664  6 
nf_conntrack           80683  6 nf_conntrack_ipv6,xt_NOTRACK,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ipv4,xt_conntrack
ip6table_filter        12711  1 
ip6_tables             17969  3 ip6table_raw,ip6table_mangle,ip6table_filter
x_tables               26087  15 xt_LOG,xt_tcpudp,xt_limit,xt_pkttype,ip6t_REJECT,ipt_REJECT,ip6table_raw,xt_NOTRACK,iptable_raw,iptable_filter,ip6table_mangle,ip_tables,xt_conntrack,ip6table_filter,ip6_tables
cpufreq_conservative    13495  0 
cpufreq_userspace      12973  0 
cpufreq_powersave      12554  0 
fuse                   80298  4 
snd_hda_codec_realtek    71363  1 
snd_hda_intel          32351  5 
snd_hda_codec         122027  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep              13272  1 snd_hda_codec
snd_pcm_oss            52915  0 
arc4                   12473  0 
snd_pcm                92793  4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq                63569  0 
pcmcia                 55392  0 
snd_timer              24318  3 snd_pcm,snd_seq
snd_seq_device         14137  1 snd_seq
sr_mod                 21872  0 
snd_mixer_oss          22101  1 snd_pcm_oss
yenta_socket           40362  0 
cdrom                  41398  1 sr_mod
sg                     35635  0 
iTCO_wdt               17652  0 
i2c_i801               17499  0 
acpi_cpufreq           18377  0 
mperf                  12603  1 acpi_cpufreq
pcmcia_rsrc            18063  1 yenta_socket
pcmcia_core            22277  3 pcmcia,yenta_socket,pcmcia_rsrc
snd                    70407  18 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_pcm,snd_seq,snd_timer,snd_seq_device,snd_mixer_oss
firewire_ohci          39609  0 
firewire_core          61024  1 firewire_ohci
iTCO_vendor_support    13502  1 iTCO_wdt
crc_itu_t              12627  1 firewire_core
soundcore              14599  1 snd
sdhci_pci              18219  0 
sdhci                  37225  1 sdhci_pci
mmc_core              108295  2 sdhci_pci,sdhci
snd_page_alloc         14036  2 snd_hda_intel,snd_pcm
battery                18267  0 
joydev                 17161  0 
serio_raw              13155  0 
r8169                  59674  0 
pcspkr                 12630  0 
ac                     12929  0 
coretemp               13204  0 
edd                    14103  0 
microcode              22850  0 
autofs4                37327  2 
i915                  455813  3 
drm_kms_helper         45453  1 i915
drm                   231978  4 i915,drm_kms_helper
i2c_algo_bit           13197  1 i915
button                 13626  1 i915
video                  18841  1 i915
scsi_dh_emc            17061  0 
scsi_dh_rdac           17171  0 
scsi_dh_hp_sw          12745  0 
scsi_dh_alua           16940  0 
scsi_dh                14178  4 scsi_dh_emc,scsi_dh_rdac,scsi_dh_hp_sw,scsi_dh_alua
fan                    12823  0 
processor              43487  3 acpi_cpufreq
ata_generic            12779  0 
ata_piix               26359  4 
thermal                18230  0 
thermal_sys            19935  4 video,fan,processor,thermal

lwfinger · September 8, 2012, 3:24am

On 09/07/2012 06:06 PM, VintagePC wrote:
>
> lwfinger;2484667 Wrote:
>> On 09/07/2012 01:56 PM, VintagePC wrote:
>>
>>> I don’t even boot windows in the first place, except in very rare
>>> circumstances
>>
>> In that case, and your Fn “switch” is not working, then the wmi module
>> for your
>> laptop model is not doing the job.
>
> Where can I find more info on this?
> Output of lsmod is below, i don’t see anything related to WMI there…
> assuming the modules would have wmi in the name.
>
>
> Code:
> --------------------
> Module Size Used by
> nls_utf8 12493 0
> loop 22991 0
> af_packet 30681 4
> ndiswrapper 221457 0
> xt_LOG 17247 10
> xt_tcpudp 12756 2
> xt_limit 12541 10
> xt_pkttype 12456 3
> nf_conntrack_ipv6 14060 3
> nf_defrag_ipv6 13654 1 nf_conntrack_ipv6
> ip6t_REJECT 12826 3
> ipt_REJECT 12485 3
> ip6table_raw 12603 1
> xt_NOTRACK 12456 4
> iptable_raw 12598 1
> iptable_filter 12706 1
> ip6table_mangle 12620 0
> nf_conntrack_netbios_ns 12585 0
> nf_conntrack_broadcast 12541 1 nf_conntrack_netbios_ns
> nf_conntrack_ipv4 14501 3
> nf_defrag_ipv4 12649 1 nf_conntrack_ipv4
> ip_tables 17987 2 iptable_raw,iptable_filter
> xt_conntrack 12664 6
> nf_conntrack 80683 6 nf_conntrack_ipv6,xt_NOTRACK,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ipv4,xt_conntrack
> ip6table_filter 12711 1
> ip6_tables 17969 3 ip6table_raw,ip6table_mangle,ip6table_filter
> x_tables 26087 15 xt_LOG,xt_tcpudp,xt_limit,xt_pkttype,ip6t_REJECT,ipt_REJECT,ip6table_raw,xt_NOTRACK,iptable_raw,iptable_filter,ip6table_mangle,ip_tables,xt_conntrack,ip6table_filter,ip6_tables
> cpufreq_conservative 13495 0
> cpufreq_userspace 12973 0
> cpufreq_powersave 12554 0
> fuse 80298 4
> snd_hda_codec_realtek 71363 1
> snd_hda_intel 32351 5
> snd_hda_codec 122027 2 snd_hda_codec_realtek,snd_hda_intel
> snd_hwdep 13272 1 snd_hda_codec
> snd_pcm_oss 52915 0
> arc4 12473 0
> snd_pcm 92793 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
> snd_seq 63569 0
> pcmcia 55392 0
> snd_timer 24318 3 snd_pcm,snd_seq
> snd_seq_device 14137 1 snd_seq
> sr_mod 21872 0
> snd_mixer_oss 22101 1 snd_pcm_oss
> yenta_socket 40362 0
> cdrom 41398 1 sr_mod
> sg 35635 0
> iTCO_wdt 17652 0
> i2c_i801 17499 0
> acpi_cpufreq 18377 0
> mperf 12603 1 acpi_cpufreq
> pcmcia_rsrc 18063 1 yenta_socket
> pcmcia_core 22277 3 pcmcia,yenta_socket,pcmcia_rsrc
> snd 70407 18 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_pcm,snd_seq,snd_timer,snd_seq_device,snd_mixer_oss
> firewire_ohci 39609 0
> firewire_core 61024 1 firewire_ohci
> iTCO_vendor_support 13502 1 iTCO_wdt
> crc_itu_t 12627 1 firewire_core
> soundcore 14599 1 snd
> sdhci_pci 18219 0
> sdhci 37225 1 sdhci_pci
> mmc_core 108295 2 sdhci_pci,sdhci
> snd_page_alloc 14036 2 snd_hda_intel,snd_pcm
> battery 18267 0
> joydev 17161 0
> serio_raw 13155 0
> r8169 59674 0
> pcspkr 12630 0
> ac 12929 0
> coretemp 13204 0
> edd 14103 0
> microcode 22850 0
> autofs4 37327 2
> i915 455813 3
> drm_kms_helper 45453 1 i915
> drm 231978 4 i915,drm_kms_helper
> i2c_algo_bit 13197 1 i915
> button 13626 1 i915
> video 18841 1 i915
> scsi_dh_emc 17061 0
> scsi_dh_rdac 17171 0
> scsi_dh_hp_sw 12745 0
> scsi_dh_alua 16940 0
> scsi_dh 14178 4 scsi_dh_emc,scsi_dh_rdac,scsi_dh_hp_sw,scsi_dh_alua
> fan 12823 0
> processor 43487 3 acpi_cpufreq
> ata_generic 12779 0
> ata_piix 26359 4
> thermal 18230 0
> thermal_sys 19935 4 video,fan,processor,thermal

Usually the modules have wmi in the name, but not all do. In any case, none of
yours are wmi modules. What is the make and model of your laptop? That will
determine what module you need.

VintagePC · September 8, 2012, 6:51pm

It’s an MSI M662, I believe it also goes by “MSI 1024” internally.

Chipset is Intel 945GM.

Edit: Just tried loading msi-laptop.ko and msi-wmi.ko

Got this in dmesg:
[24293.042705] wmi: Mapper loaded
[24293.049054] msi_wmi: This machine doesn’t have MSI-hotkeys through WMI
[24298.808248] msi_laptop: driver 0.5 successfully loaded

Well, that explains why there’s no WMI modules loaded

VintagePC · September 8, 2012, 7:04pm

Huh. Well, that seems to have done the trick, loading the MSI-laptop.ko module now makes the hard block toggle on and off when I push the wifi key.

This laptop was sold without an OS (well, it came with FreeDOS) which might explain why it doesn’t have a WMI interface… especially since they have a variant of it that comes with Windows, but the appearance is different.

Thanks for all the help!

lwfinger · September 9, 2012, 12:14am

On 09/08/2012 12:06 PM, VintagePC wrote:
>
> Huh. Well, that seems to have done the trick, loading the MSI-laptop.ko
> module now makes the hard block toggle on and off when I push the wifi
> key.
>
> Thanks for all the help!

I am glad we could help. You need to add that module to MODULES_LOADED_ON_BOOT
if you have not already done that.

VintagePC · September 9, 2012, 3:56pm

Gaah… I spoke too soon. No luck after cold boot today, still hard-locked and the module didn’t do anything for me.
weird.

lwfinger · September 9, 2012, 4:27pm

On 09/09/2012 09:06 AM, VintagePC wrote:
>
> Gaah… I spoke too soon. No luck after cold boot today, still
> hard-locked and the module didn’t do anything for me.
> weird.

The only other advice is to check the BIOS for any setting that might help. You
should also check with MSI to see if there is a newer BIOS that might fix the
issue. Otherwise, I have no further suggestions.