From: Skirmisher <Skirmisher@users.noreply.github.com>
Subject: Re: pinebookpro-kernel: update to 5.14.0
Date: Wed, 01 Sep 2021 22:43:17 +0200 [thread overview]
Message-ID: <20210901204317.dazn0n7YIVJLB0z7F_zAmUu42uh98CyBBXPiH97d4xA@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
New comment by Skirmisher on void-packages repository
> > fix panel reset
> Not sure what this does / how to reproduce the issue.
I haven't seen it either, but the commit message says it's something to do with warm reboots, and seems to work around it by basically power-cycling the panel regulator.
> > U-boot framebuffer console works, but when it hands off to the kernel, it doesn't handle the LCD properly, and it flickers brightly several times before the kernel gets a handle on it. It's...pretty bad.
> Yeah I noticed that on both 5.10 and 5.14 with the new u-boot. It was not as bad with 5.10 from what I could tell, but it still had a noticeable flicker.
> Is this specific to us/Void or is it also the case for other distros?
I can't imagine why it would be specific to Void, unless a config option is somehow the culprit, or someone has come up with a patch I didn't see. But I haven't checked on other distros specifically, or asked other users.
> > I did notice that when I got dropped into a rescue shell (for unrelated reasons) the keyboard didn't appear to work at all
> > I haven't looked into the changed config, is it possible that the module changed from built-in to module?
> I did not change any built ins to modules (at least purposefully...). I wonder if it happens on both 5.10 and 5.14, or just on 5.14.
I did confirm that all the relevant drivers (ehci_hcd/etc., usbhid, hid-generic) are still built in, which is what made it weird. But I also haven't tested it again, since changing the kernel cmdline is kind of a manual process.
> > strange issues like Fn-Alt-PrintScreen not working for magic sysrq combos
> I'll try to test those if I have a minute.
It might well be a keyboard firmware issue too, in which case it has nothing to do with Void. Maybe I'll try reverting to the stock firmware (which has its own issues...) and see if that changes its behavior.
next prev parent reply other threads:[~2021-09-01 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 19:02 [PR PATCH] " CameronNemo
2021-08-30 19:03 ` [PR PATCH] [Updated] " CameronNemo
2021-08-31 2:52 ` ericonr
2021-08-31 6:00 ` CameronNemo
2021-08-31 7:45 ` Skirmisher
2021-08-31 22:40 ` CameronNemo
2021-08-31 22:40 ` CameronNemo
2021-09-01 3:48 ` Skirmisher
2021-09-01 10:40 ` Johnnynator
2021-09-01 20:22 ` CameronNemo
2021-09-01 20:43 ` Skirmisher [this message]
2021-09-07 1:30 ` CameronNemo
2021-09-29 21:18 ` [PR PATCH] [Closed]: " CameronNemo
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).