From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Jessica Tallon <tsyesika@tsyesika.se>, 20433@debbugs.gnu.org
Subject: bug#20433: Keyboard not working on laptop with guixSD
Date: Sun, 17 Jan 2016 22:15:27 +0100 [thread overview]
Message-ID: <87lh7n52mo.fsf@gnu.org> (raw)
In-Reply-To: <87bn8l37pu.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 16 Jan 2016 15:43:57 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> So, using HIDBP is probably wrong and might very well be the cause.
>>> Looking at the module names again I searched the logs for “usbkbd” and,
>>> yes, the GuixSD logs contain this line:
>>>
>>> usbcore: registered new interface driver usbkbd
>>
>> Do you think we should remove usbkbd from (gnu system linux-initrd)?
>> Is there another module we should load instead?
>
> I don’t know why one would want to use “usbkbd” and thus HIDBP. As far
> as I understand “usbhid” should be sufficient.
Looking at the description you pasted, I agree with you.
I’ve removed usbkbd loading in commit b153f9f.
Jessica, could you confirm one way or another that usbkbd is the
culprit?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-01-17 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 8:22 bug#20433: Keyboard not working on laptop with guixSD Jessica Tallon
2015-05-01 20:26 ` Ludovic Courtès
2015-12-02 23:57 ` Jessica Tallon
2015-12-03 13:05 ` Jessica Tallon
2015-12-09 14:02 ` Ludovic Courtès
2016-01-13 13:14 ` Jessica Tallon
2016-01-13 14:24 ` Ludovic Courtès
2016-01-14 9:32 ` Jessica Tallon
2016-01-14 9:55 ` Ludovic Courtès
2016-01-14 14:03 ` Jessica Tallon
2016-01-15 20:50 ` Ricardo Wurmus
2016-01-16 13:54 ` Ludovic Courtès
2016-01-16 13:56 ` Ludovic Courtès
2016-01-16 14:43 ` Ricardo Wurmus
2016-01-17 21:15 ` Ludovic Courtès [this message]
2016-02-05 13:36 ` Ludovic Courtès
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=87lh7n52mo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=20433@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=tsyesika@tsyesika.se \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.