On 12/08/2011 06:46 AM, caf4926 wrote:
>
> Please confirm what version of openSUSE you are using
> And post the result of
>
>
> Code:
> --------------------
> /sbin/lspci -nnk
> --------------------
We already know it is a 14e4:4315 device - you do not need to post the output of
lspci, but we do need what version of openSUSE you are using.
You cannot unblock the hard variety - only the switch will clear that. It worked
with 11.1 because that kernel did not pay any attention to the rfkill switch.
Please do the following:
Turn the switch off
Wait about 5 sec
Turn the switch on
Wait 5 sec again
Run the command ‘dmesg | tail -n30’ (without the ')
On 12/08/2011 12:31 PM, nhawkbr wrote:
>
> lwfinger;2415744 Wrote:
>> On 12/08/2011 06:46 AM, caf4926 wrote:
>>>
>>> Please confirm what version of openSUSE you are using
>>> And post the result of
>>>
>>>
>>> Code:
>>> --------------------
>>> /sbin/lspci -nnk
>>> --------------------
>>
>> We already know it is a 14e4:4315 device - you do not need to post the
>> output of
>> lspci, but we do need what version of openSUSE you are using.
>>
>> You cannot unblock the hard variety - only the switch will clear that.
>> It worked
>> with 11.1 because that kernel did not pay any attention to the rfkill
>> switch.
>>
>> Please do the following:
>>
>> 1. Turn the switch off
>> 2. Wait about 5 sec
>> 3. Turn the switch on
>> 4. Wait 5 sec again
>> 5. Run the command ‘dmesg | tail -n30’ (without the ')
>> 6. Post the output of #5
>
> lwfinger, I did what did you say. Nothing happened in dmesg, the output
> below happened when I performed modprobe b43
>
> 16.189042] systemd[1]: Unit cpufreq.service entered failed state.
> 16.662125] sky2 0000:05:00.0: eth0: enabling interface
> 16.662623] ADDRCONF(NETDEV_UP): eth0: link is not ready
> 27.566787] EXT4-fs (sda6): re-mounted. Opts:
> acl,user_xattr,commit=0
> 101.139676] b43-pci-bridge 0000:07:00.0: PCI->APIC IRQ transform:
> INT A → IRQ 19
> 101.139693] b43-pci-bridge 0000:07:00.0: setting latency timer to
> 64
> 101.147063] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16,
> vendor 0x4243)
> 101.147075] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F,
> vendor 0x4243)
> 101.147085] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor
> 0x4243)
> 101.147095] ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor
> 0x4243)
> 101.177090] ssb: Sonics Silicon Backplane found on PCI device
> 0000:07:00.0
> 101.274671] cfg80211: Calling CRDA to update world regulatory
> domain
> 101.323028] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
> 101.374145] ieee80211 phy0: Selected rate control algorithm
> ‘minstrel_ht’
> 101.374910] Registered led device: b43-phy0::tx
> 101.374940] Registered led device: b43-phy0::rx
> 101.374964] Registered led device: b43-phy0::radio
> 101.374987] Broadcom 43xx driver loaded Features: PMNLS,
> Firmware-ID: FW13 ]
> 101.435116] cfg80211: World regulatory domain updated:
> 101.435120] cfg80211: (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp)
> 101.435124] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
> (300 mBi, 2000 mBm)
> 101.435127] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz),
> (300 mBi, 2000 mBm)
> 101.435130] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
> (300 mBi, 2000 mBm)
> 101.435134] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
> (300 mBi, 2000 mBm)
> 101.435137] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz),
> (300 mBi, 2000 mBm)
> 101.629039] b43-phy0: Loading firmware version 508.154 (2009-08-18
> 00:58:22)
> 101.723107] b43-phy0: Radio hardware status changed to DISABLED
> 101.723368] b43-phy0: Radio turned on by software
> 101.723372] b43-phy0: The hardware RF-kill button still turns the
> radio physically off. Press the button to turn it on.
> 101.724252] ADDRCONF(NETDEV_UP): wlan0: link is not read
My sequence should have been done AFTER b43 is loaded. I want to see if the
system is noticing that the switch is changing. Note the “Radio hardware status
changed to DISABLED” above. That means the system found the switch to be OFF.
On 12/08/2011 01:26 PM, nhawkbr wrote:
>
> First I loaded module and after I did what you said.
> nothing happened when I did what you said, just this output that showed
> when I loaded the module.
>
> is there other thing that I could do?
I think your hardware is broken. For some reason, the rf switch line on the
interface is being held low.
As a work around, try blacklisting rfkill. If that does not work, then you will
need modify b43. I can help you with that, but try the other option first.
On 12/08/2011 05:56 PM, nhawkbr wrote:
>
> Hardware isn´t broken, because it works in Windows 7 and was working
> in Opensuse 11.1 (until last sunday).
As I told you earlier, 11.1 did not pay any attention to the rfkill switch. I
have no idea what Windows 7 does, nor do I wish to learn.
I did, however, write the kernel code that b43 uses to interrogate that switch.
If you did the command sequence that I wrote, and it added nothing to your dmesg
log, then the hardware is broken!
On 12/08/2011 07:14 PM, Larry Finger wrote:
> On 12/08/2011 05:56 PM, nhawkbr wrote:
>>
>> Hardware isn´t broken, because it works in Windows 7 and was working
>> in Opensuse 11.1 (until last sunday).
>
> As I told you earlier, 11.1 did not pay any attention to the rfkill switch. I
> have no idea what Windows 7 does, nor do I wish to learn.
>
> I did, however, write the kernel code that b43 uses to interrogate that switch.
> If you did the command sequence that I wrote, and it added nothing to your dmesg
> log, then the hardware is broken!
I’m sorry about the way I answered you earlier.
What happens in Windows 7 when you actuate the switch? Does it interrupt the
wireless?
Is the switch a slider with ON/OFF positions, or is it a push button? If the
latter, then you need the Windows Management Interface module for your laptop.
As you have not posted what you have (or I missed it), I don’t know which one
you need.
On 12/09/2011 11:16 AM, nhawkbr wrote:
>
> ideas for resolve my problem???
Not really. I will make sure that the wireless switch is working for b43 on
someone’s machine. I can no longer test here as my PCIe slot no longer functions.
On 12/09/2011 12:56 PM, Larry Finger wrote:
> On 12/09/2011 11:16 AM, nhawkbr wrote:
>>
>> ideas for resolve my problem???
>
> Not really. I will make sure that the wireless switch is working for b43 on
> someone’s machine. I can no longer test here as my PCIe slot no longer functions.
The test shows the code is working. Why it does not happen on your system is a
mystery. There is a standard pin for the chip, and for mini-PCIe cards.
The only way I know to disable RFKILL would be to make modifications to your
kernel source and rebuild it. Is that something you would consider?
of course. This modifications that you said is for I recompile kernel without rfkill module or make modifications in code? Recompile I can do it, but make modification in code I don´t have knowledge for it.