Bug#609911: [Debian-eeepc-devel] Bug#609911: Bug#609911: eeepc-acpi-scripts: Wireless cannot be switched off with EEEPC 1016P

2011-01-15 Thread Luca Niccoli
On 14 January 2011 14:06, Ben Hutchings b...@decadent.org.uk wrote: I think it would be better to make this a quirk in the kernel, if that's possible.  There is an existing blacklist that modifies the kernel's responses to OSI queries.  If you can provide the sys_vendor and product_version

Bug#609911: [Debian-eeepc-devel] Bug#609911: Bug#609911: eeepc-acpi-scripts: Wireless cannot be switched off with EEEPC 1016P

2011-01-15 Thread Ben Hutchings
On Sat, 2011-01-15 at 13:59 +0100, Luca Niccoli wrote: On 14 January 2011 14:06, Ben Hutchings b...@decadent.org.uk wrote: I think it would be better to make this a quirk in the kernel, if that's possible. There is an existing blacklist that modifies the kernel's responses to OSI

Bug#609911: [Debian-eeepc-devel] Bug#609911: Bug#609911: eeepc-acpi-scripts: Wireless cannot be switched off with EEEPC 1016P

2011-01-14 Thread Luca Niccoli
Do you think it would be acceptable to ship a grub 2 hook that appends acpi_osi=Linux to the kernel command line if update-grub is run on an affected model? I think it is technically feasible and reasonably safe, but I don't know how late it is to ship something that messes with the boot system.

Bug#609911: [Debian-eeepc-devel] Bug#609911: Bug#609911: eeepc-acpi-scripts: Wireless cannot be switched off with EEEPC 1016P

2011-01-14 Thread Ben Hutchings
On Fri, 2011-01-14 at 13:49 +0100, Luca Niccoli wrote: Do you think it would be acceptable to ship a grub 2 hook that appends acpi_osi=Linux to the kernel command line if update-grub is run on an affected model? I think it is technically feasible and reasonably safe, but I don't know how late