Ubuntu
linux-source-2.6.20 package

[feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

Bug #74278 reported by singularity
0
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: linux-image-2.6.19-7-386

As the summary says. This was not an issue with kernel 2.6.17. I _literally_ have to boot into Windows XP, and then restart, to get my wireless working again; rebooting Ubuntu does nothing; it says the killswitch is on and it cannot be turned off.

[44074.624000] ipw2200: Radio Frequency Kill Switch is On:
[44074.624000] Kill switch must be turned off for wireless networking to work.
...
ADDRCONF(NETDEV_UP): eth1: link is not ready

Tags: regression
Revision history for this message
singularity (singularity00) wrote :

"Good" dmesg after a Windows boot

Revision history for this message
singularity (singularity00) wrote :
Revision history for this message
singularity (singularity00) wrote :

Notice in my bad dmesg this:

[ 398.160000] atkbd.c: Unknown key pressed (translated set 2, code 0xb4 on isa0060/serio0).
[ 398.160000] atkbd.c: Use 'setkeycodes e034 <keycode>' to make it known.

That's normal; it's my wireless killswitch button (the pressable LED) which turns the radio on and off. But what _isn't_ normal is that the wireless _didnt_ go ON when I pressed it, it just stayed off.

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

please paste the content of /sys/class/net/eth1/device/rf_kill

Revision history for this message
singularity (singularity00) wrote :

paul@paul-laptop:~$ cat /sys/class/net/eth1/device/rf_kill
2

Revision history for this message
Nicolò Chieffo (yelo3) wrote : Re: [Bug 74278] Re: [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

2 means software kill. Try
$ sudo -s
# echo 0 > /sys/class/net/eth1/device/rf_kill

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

if it does not work, 2 might mean hardware kill.... So I have no solution.

Revision history for this message
singularity (singularity00) wrote :

I did try that. I get a "permission denied" even as root.

On 12/5/06, Nicolò Chieffo <email address hidden> wrote:
>
> if it does not work, 2 might mean hardware kill.... So I have no
> solution.
>
> --
> [feisty regression] ipw2200 broken after suspend, need to boot into
> WINDOWS to get it working again
> https://launchpad.net/bugs/74278
>

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

you must do it from a root shell, not using "sudo echo 0 > ....." did you do so?

Revision history for this message
Ben Collins (ben-collins) wrote :

Needs quiesce patch.

Changed in linux-source-2.6.19:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
singularity (singularity00) wrote :

Link to said patch? When will it be applied?

Revision history for this message
Ben Collins (ben-collins) wrote :

I'm a little lost now. Seems that this patch was already integrated in one form, so I'm not sure why ipw2200 isn't working right now.

Still checking into it.

Changed in linux-source-2.6.20:
importance: Medium → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.