Integrated keyboard doesn't work (Lenovo N22)

  • Done
  • quality assurance status badge
Details
2 participants
  • Jack Ridehalgh
  • Leo Famulari
Owner
unassigned
Submitted by
Jack Ridehalgh
Severity
normal
J
J
Jack Ridehalgh wrote on 17 Jan 2022 22:36
(address . bug-guix@gnu.org)
87mtju8262.fsf@ridehalgh.uk
Hello,

Due to the bug mentioned here on the Nix tracker
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
L
L
Leo Famulari wrote on 18 Jan 2022 00:15
(name . Jack Ridehalgh via Bug reports for GNU Guix)(address . bug-guix@gnu.org)(address . 53329@debbugs.gnu.org)
YeX4pvFWeTGtrYzD@jasmine.lan
On Mon, Jan 17, 2022 at 09:36:55PM +0000, Jack Ridehalgh via Bug reports for GNU Guix wrote:
Toggle quote (4 lines)
> 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:


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.

Toggle quote (3 lines)
> 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:


It's been like that for several years.

Toggle quote (3 lines)
> 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.
L
L
Leo Famulari wrote on 18 Jan 2022 03:29
(name . Jack Ridehalgh via Bug reports for GNU Guix)(address . bug-guix@gnu.org)(address . 53329@debbugs.gnu.org)
YeYl9LBo7nkE365d@jasmine.lan
On Mon, Jan 17, 2022 at 06:15:50PM -0500, Leo Famulari wrote:
Toggle quote (3 lines)
> 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 ...`

J
J
Jack Ridehalgh wrote on 19 Jan 2022 00:39
(name . Leo Famulari)(address . leo@famulari.name)(address . 53329@debbugs.gnu.org)
b5681635-6838-4987-b0be-9d29e83f1db6@email.android.com
Attachment: file
L
L
Leo Famulari wrote on 19 Jan 2022 02:34
(name . Jack Ridehalgh)(address . jack@ridehalgh.uk)(address . 53329-done@debbugs.gnu.org)
YedqpMKBDPIfpj76@jasmine.lan
On Tue, Jan 18, 2022 at 11:39:14PM +0000, Jack Ridehalgh wrote:
Toggle quote (5 lines)
>
> 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:

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAmHnaqQACgkQJkb6MLrK
fwi9YxAAisQdmv+PX4qxPskL/r5MbTv2kQwKkM1Z378NJ392JEfqwWZdbzMJdt6W
TwuFQNiIxtf7bS3FHcjDcfMEwQLKWFGq6zgrQTSBk0Y9Fss6Zvv4JT4iFZwjU5oF
1tKD67e/XDkz4dB2Q8t3mkw1jsCVY35Kcd45c1WWvNXWCTj330F3CaJEZlVEUez+
jrcNmwP+EU9zFkVL9l1Kyfr5+3qorn0pSiwuz12iO8eBnFaPPuoUEwmtpjpxE5Gw
74Wh9SHBkdJZc89l/lv6liA5TeAlwupYDOx6n8B610LGhIStVvOd9XevakpYQ76j
qnhaoQbSQkRXjMWQ0Eha34epQMyu3J7NjkqZHqE2RG581HXiN5Xn9iHjskCeT3u6
FPzr17kgh1ac04lxvFVe4IU+dxR+4EsrFKhc+vGeb9Pkf04/oYAeXv4pR0zmwLwh
QH/sCSzOToIBS4h0HwQF1QKZQArqbKU7ini+4IiGLgjQesa1Ew7mQW35drgOwZcc
y5RNYWoCkWMUk435EkudVeNlg6fF3LFdmy5cnSvMVcjVk3jqjnBOEdE9wuZDWhPE
7Dn4naCvNd09e/SAgni+aG0uNjYqrZvEtt9+rYQi+LoU/RkQ0Dh2WAZvfkrZqDtQ
S5ON3A/SHZPJGY69xeIVfV2XoNil1VmOlcOp6hZhw5YJVVvV0d4=
=CQqL
-----END PGP SIGNATURE-----


Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 53329@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53329
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch