From: Alex Henrie <alexhenrie24@gmail.com>
To: linux-input@vger.kernel.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Corentin Chary <corentin.chary@gmail.com>
Subject: Re: I'd like to donate an Asus Q500A laptop
Date: Tue, 19 Apr 2016 23:04:46 -0600 [thread overview]
Message-ID: <CAMMLpeSFSsn14C_pp4dpPPs3rAsripMXetV0GJg9kM-gOvvt_w@mail.gmail.com> (raw)
In-Reply-To: <CAMMLpeSMi_pXSwHgMUy3MS_c0gaQgtSU6DHO1cN4qgAHC_dnmQ@mail.gmail.com>
2016-04-19 15:14 GMT-06:00 Alex Henrie <alexhenrie24@gmail.com>:
> Dear kernel developers,
>
> I have been trying to use Linux on an Asus Q500A laptop, but ran into
> a couple of problems:
>
> 1. The Caps Lock and Num Lock LEDs do not turn on
> 2. The volume control keys act like stuck letter keys (see
> http://ubuntuforums.org/showthread.php?t=2170285 for an example of
> another Q500A owner complaining about this)
>
> I am quite certain that these are both kernel bugs. I contacted the
> Asus platform driver maintainer, Corentin Chary, but he said that the
> bugs are more likely problems in the input drivers. If you are a
> kernel developer interested in looking into them, the Q500A is
> currently going for about $200-300 on eBay, which is low enough that
> it would not be a problem at all for me to just buy one and send it to
> you as a donation.
>
> Let me know, and thank you for your work on Linux!
Correction: The Caps Lock LED works, the Num Lock LED does not. There
is no Scroll Lock LED.
-Alex
next prev parent reply other threads:[~2016-04-20 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 21:14 I'd like to donate an Asus Q500A laptop Alex Henrie
2016-04-20 5:04 ` Alex Henrie [this message]
[not found] ` <57171045.5050507@de.bosch.com>
2016-04-20 5:22 ` Alex Henrie
2016-04-28 4:54 ` Alex Henrie
[not found] ` <57219D21.2040406@de.bosch.com>
2016-05-10 2:38 ` Alex Henrie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMMLpeSFSsn14C_pp4dpPPs3rAsripMXetV0GJg9kM-gOvvt_w@mail.gmail.com \
--to=alexhenrie24@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).