Wireless doesn't start on boot in Hardy 2.6.24-21

[mxyzptlk]

With kernel 2.6.24-21, wireless does not start on boot. The light does turn on, but somewhere in the boot process the kill switch is activated. This is on a Lenovo IdeaPad Y510 with a standard Intel PRO/Wireless 3945ABG card with the iwl3945 driver.

There is a wireless switch on the front of the laptop. The switch is set to on, but the wireless is off. Turning the switch off and then back on brings wireless back up.

This was the same on 2.6.24-20, but 2.6.24-19 works fine.

[mxyzptlk (mxyzptlk)]

Attaching dmesg

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[mxyzptlk (mxyzptlk)]

Ah, thanks Pedro. The logs are attached, and uname -r is 2.6.24-21-generic.

Quick question: The screen brightness on the Lenovo IdeaPads is reversed. We've been working on this in the ubuntuforums, but haven't had much luck. If I were to file a bug for that, would I need the same information -- kernel, dmesg, and lspci-vvnn, or would I need anything else? Except for a couple strange hardware issues, these are fantastic Linux machines.

Thanks again.

[mxyzptlk (mxyzptlk)]

Looking at the dmesg.log, the problem comes right at the end of the entire boot sequence -- and the wireless light is one up to this point, just before the GDM comes up.

The lines:

[ 28.284226] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 28.610486] iwl3945: Radio Frequency Kill Switch is On:
[ 28.610490] Kill switch must be turned off for wireless networking to work.

So someplace in there the kill switch was on. I'm not sure what happened in previous kernels, and I can't check at the moment, but when I can, I'll run a dmesg on 2.6.24-19-generic and see what the news is there.