Bug#684352: Compaq Presario V4000T: Wifi kill switch always on unless ACPI=off is used
tags 684352 - moreinfo
# regression
severity 684352 important
quit
David Smith wrote:
> Some people think it might be a problem in networkmanager, but trying to
> find the problem there hasn't really gone anywhere.
Yeah, it's more likely to be a kernel, firmware, or hardware bug.
[...]
> Kernel from Squeeze(linux-image-2.6.32-5-686): The problem completely
> disappears.
Very useful, thanks.
[...]
> Kernel from Expiermental(linux-image-3.5-trunk-686-pae): System crashes on
> "Waiting for /dev to be populated". Unable to test, although I'm not sure
> if I'm installing the kernel properly.
That might be another instance of the same problem as
<http://bugs.debian.org/688711>.
> ACPI Dump attached.
Thanks!
If you prevent the hp-wmi driver from loading (just running
echo 'blacklist hp-wmi' >/etc/modprobe.d/ds-blacklist-hpwmi.conf
and rebooting should do the trick, but check "lsmod" output to be
sure), does that avoid rfkill trouble?
If so, please send a summary of symptoms to platform-driver-x86@vger.kernel.org,
cc-ing linux-wireless@vger.kernel.org, Anssi Hannula <anssi.hannula@iki.fi>,
and either me or this bug log so we can track it. Be sure to mention
- steps to reproduce the problem, expected result, actual result,
and how the difference indicates a bug (should be simple enough)
- which kernel versions you have tested and what happened with each
- full "dmesg" output from booting and reproducing the bug on an
affected kernel, as an attachment
- PCI registers for your wireless card (from running "lspci -vv -s06:05.0"
as root)
- any other weird symptoms or observations
- a link to http://bugs.debian.org/684352 for the backstory
Hopefully someone upstream can suggest steps to perform or a patch to
try to further track down the cause.
Another hint: another tack would be to try various kernels to narrow
down when this regression was introduced. There are various
pre-compiled kernel versions at
<http://snapshot.debian.org/package/linux-2.6/>. It would be
interesting to see whether 2.6.38 and 2.6.39 exhibit this.
Good luck,
Jonathan
Reply to: