Hi there,
I've updated my Pinebook Pro today. With actual kernel NVME Discs are working.
root@pinebook-pro ~]# uname -a Linux pinebook-pro.reschke.lan 5.13.13-200.fc34.aarch64 #1 SMP Thu Aug 26 16:51:14 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux [root@pinebook-pro ~]# nvme list Node SN Model Namespace Usage Format FW Rev ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 2018FV440610 WDC WDS250G2B0C-00PXH0 1 250,06 GB / 250,06 GB 512 B + 0 B 211070WD [root@pinebook-pro ~]# df -h Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf devtmpfs 1,9G 0 1,9G 0% /dev tmpfs 1,9G 1,2M 1,9G 1% /dev/shm tmpfs 767M 1,8M 766M 1% /run /dev/mapper/fedora_pinebook--pro-root 56G 6,1G 47G 12% / tmpfs 1,9G 3,1M 1,9G 1% /tmp /dev/mapper/fedora_pinebook--pro-homelv 216G 8,8G 196G 5% /home /dev/mmcblk2p2 976M 197M 713M 22% /boot /dev/mmcblk2p1 599M 5,9M 593M 1% /boot/efi tmpfs 384M 68K 384M 1% /run/user/1000 [root@pinebook-pro ~]#
The last thing what I want to have is external Monitor over USB-C.
Thanks to all who managed these.
Andreas
On Wednesday, 08 September 2021 at 14:02, Andreas Reschke wrote:
Hi there,
I've updated my Pinebook Pro today. With actual kernel NVME Discs are working.
Great news! Thanks for sharing. Now I can order an actual NVMe SSD for my unit. Could you try installing Fedora with LUKS disk encryption and checking if you're hitting https://bugzilla.redhat.com/show_bug.cgi?id=1990176 with 5.13 kernels?
Regards, Dominik
Am 08.09.21 um 23:23 schrieb Dominik 'Rathann' Mierzejewski:
On Wednesday, 08 September 2021 at 14:02, Andreas Reschke wrote:
Hi there,
I've updated my Pinebook Pro today. With actual kernel NVME Discs are working.
Great news! Thanks for sharing. Now I can order an actual NVMe SSD for my unit. Could you try installing Fedora with LUKS disk encryption and checking if you're hitting https://bugzilla.redhat.com/show_bug.cgi?id=1990176 with 5.13 kernels?
Regards, Dominik
Hello Dominik,
I've seen the same behavior, no prompt on keybord but works with serial connection (not really useful on a laptop ...)
Andreas
On Thursday, 09 September 2021 at 08:32, Andreas Reschke wrote:
Am 08.09.21 um 23:23 schrieb Dominik 'Rathann' Mierzejewski:
On Wednesday, 08 September 2021 at 14:02, Andreas Reschke wrote:
[...]
I've updated my Pinebook Pro today. With actual kernel NVME Discs are working.
Great news! Thanks for sharing. Now I can order an actual NVMe SSD for my unit. Could you try installing Fedora with LUKS disk encryption and checking if you're hitting https://bugzilla.redhat.com/show_bug.cgi?id=1990176 with 5.13 kernels?
[...]
I've seen the same behavior, no prompt on keybord but works with serial connection (not really useful on a laptop ...)
Thanks for confirming. I tried the first 5.13 kernel from koji, but it has the same issue, so the breaking change must have been introduced earlier in the development cycle and we have to do a bisection between 5.12.0 and 5.13 commit acd3d2859453 , which is 4637 commits, most of them merges.
I'll try to find some time to do it, but my time is very limited, so I really hope that someone will beat me to it.
As a reminder, here is the Fedora Wiki link with build instructions for "vanilla" upstream kernels: https://fedoraproject.org/wiki/Building_a_custom_kernel#Building_Vanilla_ups...
Regards, Dominik
Am 08.09.21 um 23:23 schrieb Dominik 'Rathann' Mierzejewski:
On Wednesday, 08 September 2021 at 14:02, Andreas Reschke wrote:
Hi there,
I've updated my Pinebook Pro today. With actual kernel NVME Discs are working.
Great news! Thanks for sharing. Now I can order an actual NVMe SSD for my unit. Could you try installing Fedora with LUKS disk encryption and checking if you're hitting https://bugzilla.redhat.com/show_bug.cgi?id=1990176 with 5.13 kernels?
Regards, Dominik
Hello Dominik,
I've tried the same (LUKS disk encryption) with actual Fedora 35 Beta and Fedora 34 with up2date 5.14.9-200.fc34.aarch64.
Same behavior: not really useful. I can see the prompt for password but only via serial console password was accepted.
Greetings
Andreas
W dniu 06.10.2021 o 17:25, Andreas Reschke pisze:
I've tried the same (LUKS disk encryption) with actual Fedora 35 Beta and Fedora 34 with up2date 5.14.9-200.fc34.aarch64.
Same behavior: not really useful. I can see the prompt for password but only via serial console password was accepted.
OK. Do you have working keyboard once you boot full system? If yes then there is hope.
Check which kernel modules handle keyboard, make sure they are in initramfs. And that they are loaded before LUKS starts.
On Wed, Oct 6, 2021 at 6:24 PM Marcin Juszkiewicz mjuszkiewicz@redhat.com wrote:
W dniu 06.10.2021 o 17:25, Andreas Reschke pisze:
I've tried the same (LUKS disk encryption) with actual Fedora 35 Beta and Fedora 34 with up2date 5.14.9-200.fc34.aarch64.
Same behavior: not really useful. I can see the prompt for password but only via serial console password was accepted.
OK. Do you have working keyboard once you boot full system? If yes then there is hope.
Check which kernel modules handle keyboard, make sure they are in initramfs. And that they are loaded before LUKS starts.
Yes, it works after boot, I suspect there's some change in module loading ordering, someone needs to bisect the problem on the kernel and I don't currently have the time to deal with it.
On Wednesday, 06 October 2021 at 19:59, Peter Robinson wrote:
On Wed, Oct 6, 2021 at 6:24 PM Marcin Juszkiewicz mjuszkiewicz@redhat.com wrote:
W dniu 06.10.2021 o 17:25, Andreas Reschke pisze:
I've tried the same (LUKS disk encryption) with actual Fedora 35 Beta and Fedora 34 with up2date 5.14.9-200.fc34.aarch64.
Same behavior: not really useful. I can see the prompt for password but only via serial console password was accepted.
OK. Do you have working keyboard once you boot full system? If yes then there is hope.
Check which kernel modules handle keyboard, make sure they are in initramfs. And that they are loaded before LUKS starts.
Yes, it works after boot, I suspect there's some change in module loading ordering, someone needs to bisect the problem on the kernel and I don't currently have the time to deal with it.
Just like Peter said. Yes, it's working after switching to real root, the module list is the same as in 5.12.x and the usb module for USB 1.1 support (ohci-hcd) is present in initramfs in both cases. I don't have time to bisect currently, either. The issue is reproducible even with the first 5.13 kernel from koji, i.e. 5.13.0-0.rc0.20210428gitacd3d2859453.2.fc35.aarch64
Disabling the unused USB-1.1 hub in device tree doesn't help.
Regards, Dominik
On Wednesday, 06 October 2021 at 23:51, Dominik 'Rathann' Mierzejewski wrote:
On Wednesday, 06 October 2021 at 19:59, Peter Robinson wrote:
On Wed, Oct 6, 2021 at 6:24 PM Marcin Juszkiewicz mjuszkiewicz@redhat.com wrote:
W dniu 06.10.2021 o 17:25, Andreas Reschke pisze:
I've tried the same (LUKS disk encryption) with actual Fedora 35 Beta and Fedora 34 with up2date 5.14.9-200.fc34.aarch64.
Same behavior: not really useful. I can see the prompt for password but only via serial console password was accepted.
OK. Do you have working keyboard once you boot full system? If yes then there is hope.
Check which kernel modules handle keyboard, make sure they are in initramfs. And that they are loaded before LUKS starts.
Yes, it works after boot, I suspect there's some change in module loading ordering, someone needs to bisect the problem on the kernel and I don't currently have the time to deal with it.
Just like Peter said. Yes, it's working after switching to real root, the module list is the same as in 5.12.x and the usb module for USB 1.1 support (ohci-hcd) is present in initramfs in both cases. I don't have time to bisect currently, either. The issue is reproducible even with the first 5.13 kernel from koji, i.e. 5.13.0-0.rc0.20210428gitacd3d2859453.2.fc35.aarch64
Disabling the unused USB-1.1 hub in device tree doesn't help.
FYI it looks like it's no longer reproducible on F35 with 5.14.12 and later kernels.
Regards, Dominik
Am 22.10.21 um 22:01 schrieb Dominik 'Rathann' Mierzejewski:
On Wednesday, 06 October 2021 at 23:51, Dominik 'Rathann' Mierzejewski wrote:
On Wednesday, 06 October 2021 at 19:59, Peter Robinson wrote:
On Wed, Oct 6, 2021 at 6:24 PM Marcin Juszkiewicz mjuszkiewicz@redhat.com wrote:
W dniu 06.10.2021 o 17:25, Andreas Reschke pisze:
I've tried the same (LUKS disk encryption) with actual Fedora 35 Beta and Fedora 34 with up2date 5.14.9-200.fc34.aarch64.
Same behavior: not really useful. I can see the prompt for password but only via serial console password was accepted.
OK. Do you have working keyboard once you boot full system? If yes then there is hope.
Check which kernel modules handle keyboard, make sure they are in initramfs. And that they are loaded before LUKS starts.
Yes, it works after boot, I suspect there's some change in module loading ordering, someone needs to bisect the problem on the kernel and I don't currently have the time to deal with it.
Just like Peter said. Yes, it's working after switching to real root, the module list is the same as in 5.12.x and the usb module for USB 1.1 support (ohci-hcd) is present in initramfs in both cases. I don't have time to bisect currently, either. The issue is reproducible even with the first 5.13 kernel from koji, i.e. 5.13.0-0.rc0.20210428gitacd3d2859453.2.fc35.aarch64
Disabling the unused USB-1.1 hub in device tree doesn't help.
FYI it looks like it's no longer reproducible on F35 with 5.14.12 and later kernels.
Regards, Dominik
Hello together,
I can confirm it. I've installed it with Fedora-Everything-netinst-aarch63-35_Beta-1.2.iso(5.14.10-300.fc35.aarch64) via VNC installation.
And it"s works! Now my Pinebook-Pro is also complete encrypt as my other x86-64 Laptop.
Thank you !!
Andreas
-
Andreas Reschke -
Dominik 'Rathann' Mierzejewski -
Marcin Juszkiewicz -
Peter Robinson