Ubuntu
linux package

  1. Bug #1313196
  2. Comment #11

Comment 11 for bug 1313196

Revision history for this message
Mauro (mauromol) wrote :

I confirm acpi_osi='!Windows 2012' kernel boot parameter works for me, too (on an HP ProBook 450 G1), with Linux Mint 16 KDE (based on Ubuntu 13.10). I notice that there's a difference in "rfkill list" output with and without this kernel boot parameter:

- without it:
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

- with it:
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: hp-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
4: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

So, there are two new entries, hp-wifi and hp-bluetooth. When I press the switch to deactivate the wifi, the "hard blocked" for phy0 and hp-wifi turns to "yes" (I can't remember if it turns to yes even for the other two bluetooth entries).

Which other side effects may I have by using this kernel boot parameter?

Steffen, where should I put CONFIG_HP_WIRELESS=y? Is it meant to be a kernel boot parameter too? It seems to be more specific compared to acpi_osi...

Cristopher: I didn't forget your request. I'm going to try a newer kernel as soon as I have some spare time.