A true mainline Linux Kernel for the Pinebook Pro

[tsys]

I'm currently in the middle of the examination period at my university and had to prepare for a couple of exams over the course of the last three weeks.

Good luck with your exams, I hope everything works well for you.

Thanks! All going pretty good for me so far 

[ssfrfr@]

s3 also doesn't seem to work with the presence of an NVMe device.

Not in general. I have an NVMe drive installed and it works fine for me. Are there any errors in the kernel message log? Those might help to figure out what is going wrong.

from my system, 5.6.0-rc4 custom build from gitlab.manjaro.org:
[   92.398922] PM: suspend entry (s2idle)
[   92.410407] Filesystems sync: 0.011 seconds
[   92.413114] dwmmc_rockchip fe310000.mmc: pre_suspend failed for non-removable host: -38
[   92.413833] Freezing user space processes ... (elapsed 0.003 seconds) done.
[   92.417714] OOM killer disabled.
[   92.417999] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[   92.420304] printk: Suspending console(s) (use no_console_suspend to debug)
[   98.476403] rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!
[   98.476426] PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x130 returns -110
[   98.476432] PM: Device f8000000.pcie failed to suspend noirq: error -110
[   98.496671] PM: noirq suspend of devices failed
[   98.726837] usb usb5: root hub lost power or was reset
[   98.726844] usb usb6: root hub lost power or was reset
[   98.906339] usb usb7: root hub lost power or was reset
[   98.906347] usb usb8: root hub lost power or was reset
[   98.906806] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn
[   99.012380] nvme nvme0: 6/0/0 default/read/poll queues
[   99.070831] OOM killer enabled.
[   99.071110] Restarting tasks ... done.
[   99.074307] PM: suspend exit

my NVME is a Samsung PM951 I pulled out of a surface book.

It goes to sleep, then wakes right back up.

[amiraeva]

s3 also doesn't seem to work with the presence of an NVMe device.

Not in general. I have an NVMe drive installed and it works fine for me. Are there any errors in the kernel message log? Those might help to figure out what is going wrong.

from my system, 5.6.0-rc4 custom build from gitlab.manjaro.org:
[   92.398922] PM: suspend entry (s2idle)
[   92.410407] Filesystems sync: 0.011 seconds
[   92.413114] dwmmc_rockchip fe310000.mmc: pre_suspend failed for non-removable host: -38
[   92.413833] Freezing user space processes ... (elapsed 0.003 seconds) done.
[   92.417714] OOM killer disabled.
[   92.417999] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[   92.420304] printk: Suspending console(s) (use no_console_suspend to debug)
[   98.476403] rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!
[   98.476426] PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x130 returns -110
[   98.476432] PM: Device f8000000.pcie failed to suspend noirq: error -110
[   98.496671] PM: noirq suspend of devices failed
[   98.726837] usb usb5: root hub lost power or was reset
[   98.726844] usb usb6: root hub lost power or was reset
[   98.906339] usb usb7: root hub lost power or was reset
[   98.906347] usb usb8: root hub lost power or was reset
[   98.906806] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn
[   99.012380] nvme nvme0: 6/0/0 default/read/poll queues
[   99.070831] OOM killer enabled.
[   99.071110] Restarting tasks ... done.
[   99.074307] PM: suspend exit

my NVME is a Samsung PM951 I pulled out of a surface book.

It goes to sleep, then wakes right back up.

For what it's worth, I get a very similar error with an Intel 660p 1 TB in dmesg. Goes to sleep then wakes back up soon after.

[bsammon]

I asked this a while back, but I didn't get around to following up on the responses:
Can anyone give a brief (or not-so-brief, if appropriate/preferred) summary of how to build/install the kernel?
I'm running Debian, and if it's preferred/recommended, I'll build Debian kernel packages, but it's not my specific preference--mainly I prefer whatever's simplest.

I used to regularly compile kernels many years ago, but it's been quite a few years.

[xmixahlx]

i shared a script. see my sig.

[bsammon]

Is anyone seeing a problem with a dim screen when booting a kernel built from recent versions of this?
I've built a kernel from a March 6 28ceb942df48e14ee1c2006 git commit, and booting it to no-X login.  Initially, and for around 3/4 of a second, the screen is at normal brightness, but at some point in the boot-up, the screen(/backlight?) gets very dim, and stays that way until I reboot.

I have some more investigation I can do, but I thought I'd check and see if anyone's run into something like this.
I'll post what I learn from my investigations if I don't find a solution in this thread.

[wdt]

https://forum.pine64.org/showthread.php?...48&page=23

[bsammon]

Hmm... that's interesting.  I've noticed that I see the same behavior when I used the 5.5 kernel distributed as a .deb for danielt's Debian stuff, which suggests that this is a change between 5.4 and 5.5.

I'm not sure whether this change is considered a "bug" or a "feature", but I will say that it kinda sucks that this upgrade changes things from "I don't ever need to have a screen-brightness applet" to "my system is not usable until I find a screen-brightness applet".  (or just downgrade back to the older kernel, which is what I'm doing for the interim)

As it happens, I don't use a desktop environment (I use the fvwm window manager), so the "find a screen-brightness applet" issue is not quite as simple as "go to the control panel".

The manjaro forum thread indirectly pointed to by wdt has some interesting ideas for my no-desktop-environment situation.

[bsammon]

I think this screen-brightness issue merits a thread of its own.

[xmixahlx]

screen brightness change is due to removal of the brightness gauge in the dts. it now uses the default scale of 4096 not 256.

set using percentage rather than set values, and make sure your brightness keys work and you will be fine.