Github messages for voidlinux
 help / color / mirror / Atom feed
From: Skirmisher <>
Subject: Re: pinebookpro-kernel: update to 5.14.0
Date: Wed, 01 Sep 2021 05:48:15 +0200	[thread overview]
Message-ID: <20210901034815.aZkItKQJbadyW3NoAX-_S8zZHWlZSK5QoMyGtdroR0Y@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

New comment by Skirmisher on void-packages repository

Makes sense.

I tested this kernel and your uboot/atf bump, with the following patches added:
- uboot
  - [fix panel reset](
  - [change boot order]( (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)
- atf
  - [attribute fix]( (apparently this breaks GCC 11, but the code is wrong in the first place; no functionality change)

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.

Other than that, the kernel seems to come up fine, although I did notice that when I got dropped into a rescue shell (for unrelated reasons) the keyboard didn't appear to work at all, though it works once I got into the booted system. I wasn't able to test much further than that, because sddm didn't start and trying to run Xorg would hang the system sometimes, in addition to strange issues like Fn-Alt-PrintScreen not working for magic sysrq combos. I don't have time to test a fresh install tonight.

  parent reply	other threads:[~2021-09-01  3:48 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 [this message]
2021-09-01 10:40 ` Johnnynator
2021-09-01 20:22 ` CameronNemo
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210901034815.aZkItKQJbadyW3NoAX-_S8zZHWlZSK5QoMyGtdroR0Y@z \ \ \

* 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).