Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#876303: linux-source-4.9 kernel regression eeepc-wmi
133 views
Skip to first unread message
Oscon
Sep 20, 2017, 2:30:02 PM9/20/17
to
Package: linux-source-4.9
Version: >=4.9.25
eeepc-wmi doesn't work with my Eee PC netbook (Asus X101) after kernel upgrade
from 3.14.79 to 4.9.y. So some Eee WMI hotkeys don't work with the new kernel.
kern.log:
-------
[ 1.043620] eeepc_wmi: Found legacy ATKD device (ASUS010)
[ 1.043632] eeepc_wmi: WMI device present, but legacy ATKD device is also
present and enabled
[ 1.043650] eeepc_wmi: You probably booted with acpi_osi="Linux" or
acpi_osi="!Windows 2009"
[ 1.043662] eeepc_wmi: Can't load eeepc-wmi, use default acpi_osi
(preferred) or eeepc-laptop
evtest output:
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Sleep Button
/dev/input/event2: Power Button
/dev/input/event3: Power Button
/dev/input/event4: Video Bus
/dev/input/event5: AT Translated Set 2 keyboard
/dev/input/event6: HDA Intel Headphone
/dev/input/event7: SynPS/2 Synaptics TouchPad
------------
eeepc-laptop is not good for Asus X101. It works only with acpi_osi=Linux, but
the KEY_BRIGHTNESSDOWN and KEY_BRIGHTNESSUP don't work in this case.
I have to use eeepc-wmi.
The patch "Use acpi_dev_found() " is the cause of the problem. /part of
vanilla kernel/
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/drivers/platform/x86/eeepc-wmi.c?h=v4.9.51
...
I removed this patch from my kernel source, and eeepc_wmi works correct.:
kern.log:
[ 1.048511] input: Eee PC WMI hotkeys as /devices/platform/eeepc-
wmi/input/input5
evtest output:
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Sleep Button
/dev/input/event2: Power Button
/dev/input/event3: Power Button
/dev/input/event4: Video Bus
/dev/input/event5: Eee PC WMI hotkeys
/dev/input/event6: AT Translated Set 2 keyboard
/dev/input/event7: HDA Intel Headphone
/dev/input/event8: SynPS/2 Synaptics TouchPad
I suggest to remove the bad patch /for example with attachment/ from the
kernel source .
I am using Debian GNU/Linux 8.9, 4.9.25/4.9.30 based kernel and libc6
2.19-18+deb8u10.
Thanks
Oscon
Debian Bug Tracking System
Sep 24, 2017, 4:30:02 PM9/24/17
to
Processing control commands:
> tag -1 moreinfo
Bug #876303 [linux-source-4.9] linux-source-4.9 kernel regression eeepc-wmi
Added tag(s) moreinfo.
--
876303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> tag -1 moreinfo
Bug #876303 [linux-source-4.9] linux-source-4.9 kernel regression eeepc-wmi
Added tag(s) moreinfo.
--
876303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Ben Hutchings
Sep 24, 2017, 4:30:04 PM9/24/17
to
Control: tag -1 moreinfo
On Wed, 2017-09-20 at 20:22 +0200, Oscon wrote:
> Package: linux-source-4.9
>
> Version: >=4.9.25
>
> eeepc-wmi doesn't work with my Eee PC netbook (Asus X101) after kernel upgrade
> from 3.14.79 to 4.9.y. So some Eee WMI hotkeys don't work with the new kernel.
[...]
How did you determine this? It doesn't appear to make any functional
change.
Are you still putting an acpi_osi parameter on the kernel command line?
Ben.
--
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.
On Wed, 2017-09-20 at 20:22 +0200, Oscon wrote:
> Package: linux-source-4.9
>
> Version: >=4.9.25
>
> eeepc-wmi doesn't work with my Eee PC netbook (Asus X101) after kernel upgrade
> from 3.14.79 to 4.9.y. So some Eee WMI hotkeys don't work with the new kernel.
> I have to use eeepc-wmi.
>
> The patch "Use acpi_dev_found() " is the cause of the problem.
[...]
>
> The patch "Use acpi_dev_found() " is the cause of the problem.
How did you determine this? It doesn't appear to make any functional
change.
Are you still putting an acpi_osi parameter on the kernel command line?
Ben.
--
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.
Debian Bug Tracking System
Sep 25, 2017, 9:10:03 AM9/25/17
to
Processing control commands:
> tag -1 - moreinfo
Bug #876303 [src:linux] linux-source-4.9 kernel regression eeepc-wmi
Removed tag(s) moreinfo.
> tag -1 - moreinfo
Bug #876303 [src:linux] linux-source-4.9 kernel regression eeepc-wmi
Removed tag(s) moreinfo.
Roland Miyamoto
Jan 3, 2018, 7:40:02 AM1/3/18
to
Dear Ben Hutchings,
Dear kernel developers,
First I want to thank you all for your amazing work.
It moves me to see how you all work on this humongous project so successfully and coordinatedly.
I am not a kernel developer and I watch in awe how you accomplish all this.
Nonetheless, I plead for rolling back to the old test
if (eeepc_wmi_check_atkd()) {...}
in eeepc_wmi_probe() that was in effect until kernel 4.6.7
rather than the new test
if (acpi_dev_found(EEEPC_ACPI_HID)) {
used as of kernel 4.7.x
because the new test prevents loading eeepc-wmi
while the old one loads it,
just as Oscon has described.
I own seven boxes Eee PC 1001PXD
https://www.asus.com/Laptops/Eee_PC_1001PXD/
and want to prepare them with Debian 9 and give them to people for free
who cannot or do not want to afford to buy a new laptop.
Also I want to encourage improving the current drivers for Asus EeePCs.
In order to support your work, I offer to send one or two of my boxes
for testing purposes to kernel and driver developers.
And, of course, I am willing to desribe all the relevant bugs
that I have encountered on these boxes in sufficient detail whenever required.
Please let me know how else I can support.
And, of course, I will pay the postage.
Cheers, and again thank you for your awesome work!
Roland
On Mon, 25 Sep 2017 14:03:26 +0100 Ben Hutchings <b...@decadent.org.uk> wrote:
> Control: tag -1 - moreinfo
>
> -------- Forwarded Message --------
> From: Oscon <os...@upcmail.hu>
> To: Ben Hutchings <b...@decadent.org.uk>
> Subject: Re: Re: Bug#876303: linux-source-4.9 kernel regression eeepc-wmi
> Date: Mon, 25 Sep 2017 08:12:55 +0200
> Message-id: <1944222.XpyFCHbg37@osconsfortress>
>
> A következÅ‘t Ãrta ekkor: 2017. szeptember 24. 21:21:58
>
> Thank you for the answer.
>
> ------------
> I am not developer, sorry. :-(
>
> But I can write my experience details:
>
> The problem is - a bit :-) - complicated / or chaotic ? :-) /
>
> eeepc_wmi driver doesn't load any more in asus x101 netbook with the 'use
> acpi_dev_found()' patch.
>
> No matter there is in module or compiled in the kernel. Always:
> I did try with combination: eeepc_wmi compiled in kernel, and atkbd in module,
> but eeepc_wmi didn't load with same message.
>
Dear kernel developers,
First I want to thank you all for your amazing work.
It moves me to see how you all work on this humongous project so successfully and coordinatedly.
I am not a kernel developer and I watch in awe how you accomplish all this.
Nonetheless, I plead for rolling back to the old test
if (eeepc_wmi_check_atkd()) {...}
in eeepc_wmi_probe() that was in effect until kernel 4.6.7
rather than the new test
if (acpi_dev_found(EEEPC_ACPI_HID)) {
used as of kernel 4.7.x
because the new test prevents loading eeepc-wmi
while the old one loads it,
just as Oscon has described.
I own seven boxes Eee PC 1001PXD
https://www.asus.com/Laptops/Eee_PC_1001PXD/
and want to prepare them with Debian 9 and give them to people for free
who cannot or do not want to afford to buy a new laptop.
Also I want to encourage improving the current drivers for Asus EeePCs.
In order to support your work, I offer to send one or two of my boxes
for testing purposes to kernel and driver developers.
And, of course, I am willing to desribe all the relevant bugs
that I have encountered on these boxes in sufficient detail whenever required.
Please let me know how else I can support.
And, of course, I will pay the postage.
Cheers, and again thank you for your awesome work!
Roland
On Mon, 25 Sep 2017 14:03:26 +0100 Ben Hutchings <b...@decadent.org.uk> wrote:
> Control: tag -1 - moreinfo
>
> -------- Forwarded Message --------
> From: Oscon <os...@upcmail.hu>
> To: Ben Hutchings <b...@decadent.org.uk>
> Subject: Re: Re: Bug#876303: linux-source-4.9 kernel regression eeepc-wmi
> Date: Mon, 25 Sep 2017 08:12:55 +0200
> Message-id: <1944222.XpyFCHbg37@osconsfortress>
>
> A következÅ‘t Ãrta ekkor: 2017. szeptember 24. 21:21:58
> > Control: tag -1 moreinfo
> >
> > On Wed, 2017-09-20 at 20:22 +0200, Oscon wrote:
> >
> > On Wed, 2017-09-20 at 20:22 +0200, Oscon wrote:
> > > Package: linux-source-4.9
> > >
> > > Version: >=4.9.25
> > >
> > > eeepc-wmi doesn't work with my Eee PC netbook (Asus X101) after kernel
> > > upgrade from 3.14.79 to 4.9.y. So some Eee WMI hotkeys don't work with
> > > the new kernel.
> >
> > [...]
> > >
> > > Version: >=4.9.25
> > >
> > > eeepc-wmi doesn't work with my Eee PC netbook (Asus X101) after kernel
> > > upgrade from 3.14.79 to 4.9.y. So some Eee WMI hotkeys don't work with
> > > the new kernel.
> >
> >
> > > I have to use eeepc-wmi.
> > >
> > > The patch "Use acpi_dev_found() " is the cause of the problem.
> >
> > > I have to use eeepc-wmi.
> > >
> > > The patch "Use acpi_dev_found() " is the cause of the problem.
> >
> > [...]
> >
> > How did you determine this? It doesn't appear to make any functional
> > change.
>
> Hello !
> >
> > How did you determine this? It doesn't appear to make any functional
> > change.
>
>
> Thank you for the answer.
>
> ------------
> I am not developer, sorry. :-(
>
> But I can write my experience details:
>
> The problem is - a bit :-) - complicated / or chaotic ? :-) /
>
> eeepc_wmi driver doesn't load any more in asus x101 netbook with the 'use
> acpi_dev_found()' patch.
>
> No matter there is in module or compiled in the kernel. Always:
>
> [ 1.043620] eeepc_wmi: Found legacy ATKD device (ASUS010)
> [ 1.043632] eeepc_wmi: WMI device present, but legacy ATKD device is also
> present and enabled
> [ 1.043650] eeepc_wmi: You probably booted with acpi_osi="Linux" or
> acpi_osi="!Windows 2009"
> [ 1.043662] eeepc_wmi: Can't load eeepc-wmi, use default acpi_osi
> (preferred) or eeepc-laptop
>
> It seems eeepc-wmi does see the acpi keyboard device, and don't load any more.
> [ 1.043620] eeepc_wmi: Found legacy ATKD device (ASUS010)
> [ 1.043632] eeepc_wmi: WMI device present, but legacy ATKD device is also
> present and enabled
> [ 1.043650] eeepc_wmi: You probably booted with acpi_osi="Linux" or
> acpi_osi="!Windows 2009"
> [ 1.043662] eeepc_wmi: Can't load eeepc-wmi, use default acpi_osi
> (preferred) or eeepc-laptop
>
> I did try with combination: eeepc_wmi compiled in kernel, and atkbd in module,
> but eeepc_wmi didn't load with same message.
>
saw...@xsmail.com
May 30, 2019, 6:10:03 PM5/30/19
to
Good morning:
Could you tell me the status of this bug (876303)?
ie: will it be fixed for 5.0?
Thanks in advance.
Best,Carlos Izzo Videla
Could you tell me the status of this bug (876303)?
ie: will it be fixed for 5.0?
Thanks in advance.
Best,Carlos Izzo Videla
Debian Bug Tracking System
May 15, 2021, 11:10:02 AM5/15/21
to
Your message dated Sat, 15 May 2021 07:57:16 -0700 (PDT)
with message-id <609fe14c.1c69f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #876303,
regarding linux-source-4.9 kernel regression eeepc-wmi
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
with message-id <609fe14c.1c69f...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #876303,
regarding linux-source-4.9 kernel regression eeepc-wmi
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
0 new messages