GNU bug report logs -
#53329
Integrated keyboard doesn't work (Lenovo N22)
Previous Next
Reported by: Jack Ridehalgh <jack <at> ridehalgh.uk>
Date: Mon, 17 Jan 2022 22:07:01 UTC
Severity: normal
Done: Leo Famulari <leo <at> famulari.name>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53329 in the body.
You can then email your comments to 53329 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#53329
; Package
guix
.
(Mon, 17 Jan 2022 22:07:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jack Ridehalgh <jack <at> ridehalgh.uk>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Mon, 17 Jan 2022 22:07:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
Due to the bug mentioned here on the Nix tracker
(https://github.com/NixOS/nixpkgs/issues/143223) and elsewhere it is not
possible to use the integrated keyboard on some Braswell laptops.
Would it be possible to include CONFIG_PINCTRL_CHERRYVIEW=y in the kernel
configuration so the keyboard functions correctly on these machines?
Sadly the kernel module does not work when trying to load via modprobe
and these machines are so low powered it's difficult to compile my own kernel.
Many thanks,
Jack
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53329
; Package
guix
.
(Mon, 17 Jan 2022 23:16:01 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
On Mon, Jan 17, 2022 at 09:36:55PM +0000, Jack Ridehalgh via Bug reports for GNU Guix wrote:
> Due to the bug mentioned here on the Nix tracker
> (https://github.com/NixOS/nixpkgs/issues/143223) and elsewhere it is not
> possible to use the integrated keyboard on some Braswell laptops.
Thanks for bringing this report to Guix. There is also this discussion
upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=194945
The upstream bug report suggests that this functionality worked until
Linux 4.9. Could you try with linux-libre-4.4? We have it packaged. I
don't recommend planning to stick with 4.4, but it would be interesting
as a test.
> Would it be possible to include CONFIG_PINCTRL_CHERRYVIEW=y in the kernel
> configuration so the keyboard functions correctly on these machines?
Yes, we can do that.
As shown here, this model is currently built as a module, although the
Bay Trail pinctrl stuff is built-in:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/aux-files/linux-libre/5.15-x86_64.conf?id=2c7f2b40e2dbee48075147a87c6cd9b611dc5ba9#n4704
It's been like that for several years.
> Sadly the kernel module does not work when trying to load via modprobe
> and these machines are so low powered it's difficult to compile my own kernel.
As the upstream discussion says, it would be great to understand why
this stuff doesn't work when built as a module. But, Debian builds all
of them into the kernel, and there must be a reason for that.
I'll make a Git branch in our repo that you can pull from to test the
fix.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53329
; Package
guix
.
(Mon, 17 Jan 2022 23:17:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53329
; Package
guix
.
(Tue, 18 Jan 2022 02:30:02 GMT)
Full text and
rfc822 format available.
Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):
On Mon, Jan 17, 2022 at 06:15:50PM -0500, Leo Famulari wrote:
> I'll make a Git branch in our repo that you can pull from to test the
> fix.
Try pulling from the wip-fix-53329 branch and reconfiguring your system
based on that. I've arranged to have a substitute for the x86_64 kernel
on that branch.
`guix pull --branch=wip-fix-53329 && guix system reconfigure ...`
https://git.savannah.gnu.org/cgit/guix.git/log/?h=wip-fix-53329
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53329
; Package
guix
.
(Tue, 18 Jan 2022 02:30:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53329
; Package
guix
.
(Tue, 18 Jan 2022 23:40:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 53329 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/html, inline)]
Reply sent
to
Leo Famulari <leo <at> famulari.name>
:
You have taken responsibility.
(Wed, 19 Jan 2022 01:35:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jack Ridehalgh <jack <at> ridehalgh.uk>
:
bug acknowledged by developer.
(Wed, 19 Jan 2022 01:35:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 53329-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Tue, Jan 18, 2022 at 11:39:14PM +0000, Jack Ridehalgh wrote:
>
> I can confirm the built-in kernel module in branch wip-fix-53329 has fixed the
> keyboard issue on my laptop. With regards to trying 4.4-lts, I would get a
> black screen on boot so I couldn't test that.
Great! I've deployed the fix on the "master branch", so you should get
it by default the next time you pull and reconfigure.
You might get a warning from `guix pull` about "downgrades" the next
time you pull, since the wip-fix-53329 branch forked off the main
branch... not sure. Anyways, it's safe to use --allow-downgrades this
time, if necessary. Check here for a reference on the subject:
https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix-pull.html
[signature.asc (application/pgp-signature, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 16 Feb 2022 12:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 75 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.