I installed the 5.13.1-300 kernel. Booting this kernel, the display (after the GRUB menu) becomes black. Serial connection works. I booted again the 5.13 kernel, but no way, the display is black. So I selected the previous 5.12.14-300 kernel, and the display continues to be black. Mh? Uninstalling the 5.13.1 kernel and booting again with the 5.12.14 one, then the display starts to work again.
Do you have any idea why if the 5.13 rpm is installed the display doesn't work even booting a previous kernel? (Or I'm missing something?)
Ciao, A.
On Tue, Jul 13, 2021 at 9:51 AM Alessio alciregi@posteo.net wrote:
I installed the 5.13.1-300 kernel. Booting this kernel, the display (after the GRUB menu) becomes black. Serial connection works. I booted again the 5.13 kernel, but no way, the display is black. So I selected the previous 5.12.14-300 kernel, and the display continues to be black. Mh? Uninstalling the 5.13.1 kernel and booting again with the 5.12.14 one, then the display starts to work again.
Do you have any idea why if the 5.13 rpm is installed the display doesn't work even booting a previous kernel? (Or I'm missing something?)
No, there's an issue if the DP is enabled and that kernel didn't have the fix, it will be in the next 5.13 build.
On Tue, 2021-07-13 at 09:54 +0100, Peter Robinson wrote:
On Tue, Jul 13, 2021 at 9:51 AM Alessio alciregi@posteo.net wrote:
I installed the 5.13.1-300 kernel. Booting this kernel, the display (after the GRUB menu) becomes black.
No, there's an issue if the DP is enabled and that kernel didn't have the fix, it will be in the next 5.13 build.
Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display works.
Thanks, A.
On Thursday, 15 July 2021 at 08:47, Alessio wrote:
On Tue, 2021-07-13 at 09:54 +0100, Peter Robinson wrote:
On Tue, Jul 13, 2021 at 9:51 AM Alessio alciregi@posteo.net wrote:
I installed the 5.13.1-300 kernel. Booting this kernel, the display (after the GRUB menu) becomes black.
No, there's an issue if the DP is enabled and that kernel didn't have the fix, it will be in the next 5.13 build.
Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display works.
With 5.13.4-200.fc34 I get blank display until Xorg starts. Serial works as usual. Known issue?
Regards, Dominik
On Sat, 24 Jul 2021, Dominik 'Rathann' Mierzejewski wrote:
Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display works.
With 5.13.4-200.fc34 I get blank display until Xorg starts. Serial works as usual. Known issue?
Pinebook? Or Pinebook Pro? On Pinebook I get blank display on resume from suspend - have to use power button (normal shutdown). Network is still active, and I can login remotely.
On Saturday, 24 July 2021 at 01:55, Stuart D Gathman wrote:
On Sat, 24 Jul 2021, Dominik 'Rathann' Mierzejewski wrote:
Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display works.
With 5.13.4-200.fc34 I get blank display until Xorg starts. Serial works as usual. Known issue?
Pinebook? Or Pinebook Pro? On Pinebook I get blank display on resume from suspend - have to use power button (normal shutdown). Network is still active, and I can login remotely.
Pinebook Pro. I have to use serial or blindly type the LUKS password to get it to boot. :)
Regards, Dominik
I've seen this too. No screen updates (although backlight goes off and on) between the efi stub and the gdm login screen. Seems to be a regression with the console setup.
-r
On Sat, 2021-07-24 at 21:05 +0200, Dominik 'Rathann' Mierzejewski wrote:
On Saturday, 24 July 2021 at 01:55, Stuart D Gathman wrote:
On Sat, 24 Jul 2021, Dominik 'Rathann' Mierzejewski wrote:
Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display works.
With 5.13.4-200.fc34 I get blank display until Xorg starts. Serial works as usual. Known issue?
Pinebook? Or Pinebook Pro? On Pinebook I get blank display on resume from suspend - have to use power button (normal shutdown). Network is still active, and I can login remotely.
Pinebook Pro. I have to use serial or blindly type the LUKS password to get it to boot. :)
Regards, Dominik -- Fedora https://getfedora.org%C2%A0 | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Am 25.07.21 um 18:11 schrieb Ralph Giles:
I've seen this too. No screen updates (although backlight goes off and on) between the efi stub and the gdm login screen. Seems to be a regression with the console setup.
-r
On Sat, 2021-07-24 at 21:05 +0200, Dominik 'Rathann' Mierzejewski wrote:
On Saturday, 24 July 2021 at 01:55, Stuart D Gathman wrote:
On Sat, 24 Jul 2021, Dominik 'Rathann' Mierzejewski wrote:
Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display works.
With 5.13.4-200.fc34 I get blank display until Xorg starts. Serial works as usual. Known issue?
Pinebook? Or Pinebook Pro? On Pinebook I get blank display on resume from suspend - have to use power button (normal shutdown). Network is still active, and I can login remotely.
Pinebook Pro. I have to use serial or blindly type the LUKS password to get it to boot. :)
Regards, Dominik -- Fedora https://getfedora.org%C2%A0 | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Hi there,
I've updated my Pinebook Pro today with kernel kernel-core-5.13.5-200.fc34.aarch64, same behavior: no screen. Only serial is working. So I've switched back to working kernel-5.12.13-300.fc34.aarch64.
Greetings
Andreas
On Fri, Jul 30, 2021 at 12:32 PM Andreas Reschke arm_ml@rirasoft.de wrote:
[snip]
Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display works.
With 5.13.4-200.fc34 I get blank display until Xorg starts. Serial works as usual. Known issue?
I see that the rockchipdrm fix that unregisters the early framebuffers got reverted in kernel-5.13.3-200.fc34:
https://src.fedoraproject.org/rpms/kernel/c/f513b403b05ef868f3e0aa14a4c5e57b...
I don't know if that was a mistake or done deliberately.
Best regards, Javier
On Fri, Jul 30, 2021 at 11:55 AM Javier Martinez Canillas javier@dowhile0.org wrote:
On Fri, Jul 30, 2021 at 12:32 PM Andreas Reschke arm_ml@rirasoft.de wrote:
[snip]
> Indeed. Just installed 5.13.2-300.fc34.aarch64 and the display > works. With 5.13.4-200.fc34 I get blank display until Xorg starts. Serial works as usual. Known issue?
I see that the rockchipdrm fix that unregisters the early framebuffers got reverted in kernel-5.13.3-200.fc34:
https://src.fedoraproject.org/rpms/kernel/c/f513b403b05ef868f3e0aa14a4c5e57b...
I don't know if that was a mistake or done deliberately.
It was deliberately, because the patch I pulled back from 5.14 broke the 5.13 rebase and at the time I couldn't remember why I'd pulled that patch back and I had no intention of blocking the 5.13 rebase due to major CVEs for the rest of Fedora. This is a great example of why I generally don't backport patches. Anyway, there is a PR in that should fix this for the next kernel update.
On Fri, Jul 30, 2021 at 8:32 PM Peter Robinson pbrobinson@gmail.com wrote:
On Fri, Jul 30, 2021 at 11:55 AM Javier Martinez Canillas
[snip]
I don't know if that was a mistake or done deliberately.
It was deliberately, because the patch I pulled back from 5.14 broke the 5.13 rebase and at the time I couldn't remember why I'd pulled that patch back and I had no intention of blocking the 5.13 rebase due to major CVEs for the rest of Fedora. This is a great example of why I generally don't backport patches. Anyway, there is a PR in that should fix this for the next kernel update.
Understood. Thanks a lot Peter for pulling that back!
Best regards, Javier
Hello, Peter!
On Friday, 30 July 2021 at 20:32, Peter Robinson wrote:
On Fri, Jul 30, 2021 at 11:55 AM Javier Martinez Canillas javier@dowhile0.org wrote:
On Fri, Jul 30, 2021 at 12:32 PM Andreas Reschke arm_ml@rirasoft.de wrote:
[snip]
>> Indeed. Just installed 5.13.2-300.fc34.aarch64 and the >> display works. > With 5.13.4-200.fc34 I get blank display until Xorg starts. > Serial works as usual. Known issue?
I see that the rockchipdrm fix that unregisters the early framebuffers got reverted in kernel-5.13.3-200.fc34:
https://src.fedoraproject.org/rpms/kernel/c/f513b403b05ef868f3e0aa14a4c5e57b...
I don't know if that was a mistake or done deliberately.
It was deliberately, because the patch I pulled back from 5.14 broke the 5.13 rebase and at the time I couldn't remember why I'd pulled that patch back and I had no intention of blocking the 5.13 rebase due to major CVEs for the rest of Fedora. This is a great example of why I generally don't backport patches. Anyway, there is a PR in that should fix this for the next kernel update.
Is it this one? https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1288
Regards, Dominik
-
Alessio -
Andreas Reschke -
Dominik 'Rathann' Mierzejewski -
Javier Martinez Canillas -
Peter Robinson -
Ralph Giles -
Stuart D Gathman