From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: update to 5.14.0
Date: Wed, 01 Sep 2021 22:22:40 +0200 [thread overview]
Message-ID: <20210901202240.MljG2Vq7Z5DfKYut3OiFmPffR7U26m5g7RGyAAPRRoU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32766@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/pull/32766#issuecomment-910705517
Comment:
>fix panel reset
Not sure what this does / how to reproduce the issue.
>in addition to SD/eMMC swap like your existing patch, it puts USB first so it can also be used to override eMMC/NVMe without taking the computer apart
We should probably just switch to that patch, it is much more common.
>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 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.
>strange issues like Fn-Alt-PrintScreen not working for magic sysrq combos
I'll try to test those if I have a minute.
next prev parent reply other threads:[~2021-09-01 20:22 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 [this message]
2021-09-01 20:43 ` Skirmisher
2021-09-07 1:30 ` CameronNemo
2021-09-29 21:18 ` [PR PATCH] [Closed]: " CameronNemo
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=20210901202240.MljG2Vq7Z5DfKYut3OiFmPffR7U26m5g7RGyAAPRRoU@z \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).