On 12/10/2013 12:58 AM, Matthew Garrett wrote: > On Fri, Dec 06, 2013 at 01:24:02PM +0800, Aaron Lu wrote: >> /* >> + * The bluetooth functionality is unconditionally enabled >> + * after a S3 cycle on Thinkpad X201 under Win8 mode. >> + */ > > Can you describe this in a little more detail? Does the thinkpad-acpi > rfkill code just not work? Yes it works, the problem is, even the bluetooth is disabled before hibernate, it will be enabled after resume. As Jeffery has put in comment #14: " With thinkpad_acpi blacklisted, Bluetooth is enabled on boot. I can't turn it off unless I run "modprobe thinkpad_acpi" beforehand. After turning Bluetooth off, I ran "rmmod thinkpad_acpi" before hibernating. I verified that thinkpad_acpi isn't loaded (with lsmod) before hibernating and after resuming. Bluetooth is enabled on resume. I tried this same test with the acpi_osi="!Windows 2012" kernel parameter (and thinkpad_acpi blacklisted). Bluetooth is disabled on boot. I verified that thinkpad_acpi isn't loaded (with lsmod) before hibernating and after resuming. Bluetooth is disabled on resume. " But I made a mistake in the comment, it's a S4 cycle, not a S3. > >> + /* >> + * The hardware switch for enable/disable wifi on >> + * Dell Latitude E6230 is broken under Win8 mode. >> + */ > > Can you define "broken"? Do you see the same behaviour under Windows 8? As Wouter has put in comment #12: " I also have trouble with this commit, it disables my hardware switch for enable/disable wifi. See [1] for full explanation. When I add acpi_osi="!Windows 2012" it fixes my issue. " -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
