Re: unable to bring up iwlagn wireless after update from 2.6.29.6 to 2.6.31-rc3

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

On Fri, 2009-07-17 at 01:09 +0300, Thomas Backlund wrote:

> Nope.
> Nothing gets logged when I press the rfkill...
> 
> I'd say that the rfkill rewrite killed my wireless :-(
> 
> Bluetooth works at it whould, but not the wireless
> 
> But now I have atleast found one way to get it working...
> 
> I've built the rfkill utility, and with it I can get the wireless working...

Thanks for the analysis!

> Here is the output when wireless works:
> [root@tmb-laptop rfkill]# ./rfkill list
> 0: acer-wireless: Wireless LAN
> 	Soft blocked: no
> 	Hard blocked: no
> 1: acer-bluetooth: Bluetooth
> 	Soft blocked: yes
> 	Hard blocked: no
> 2: phy0: Wireless LAN
> 	Soft blocked: no
> 	Hard blocked: no

Makes sense that it works at this point :)

> Pressing the rfkill button gets me this:
> [root@tmb-laptop rfkill]# ./rfkill list
> 0: acer-wireless: Wireless LAN
> 	Soft blocked: yes
> 	Hard blocked: no
> 1: acer-bluetooth: Bluetooth
> 	Soft blocked: yes
> 	Hard blocked: no
> 2: phy0: Wireless LAN
> 	Soft blocked: no
> 	Hard blocked: yes

So far so good. Your platform's soft-switch is wired to the card's hard
kill line. Mind trying

	./rfkill unblock 0

(or whatever ID the acer-wireless has) at this point to see what
happens? I would hope it goes back to the working state.

> And pressing it again gets this:
> [root@tmb-laptop rfkill]# ./rfkill list
> 0: acer-wireless: Wireless LAN
> 	Soft blocked: no
> 	Hard blocked: no
> 1: acer-bluetooth: Bluetooth
> 	Soft blocked: yes
> 	Hard blocked: no
> 2: phy0: Wireless LAN
> 	Soft blocked: yes
> 	Hard blocked: no
> 
> And after that I cant get wireless back until I again do a:
> ./rfkill unblock 2
> (works only when acer-wireless is no/no and Wireless LAN is yes/no)

Right. This is bad. The button press shouldn't have affected the
soft-state of the rfkill #2.

> Applying this patch:
> [PATCH] rfkill: fix rfkill_set_states() to set the hw state
> sent by Alan Jenkins does not help this issue either...
> 
> Any  suggestions how to fix the rfkill ?

I'll poke at the acer code to see what it's doing wrong...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]