Yesterday I tried to install Fed30 beta-1.7 on a Dell Precision 5530. (late 2018 model, i5-8300H & UHD graphics 630, came with Ubuntu 18.04 and had Fed29 installed and working without problems) Almost immediately after the first few lines of the startup messages the screen went black and nothing further happened. Could not get any info in this state (Ctrl-Alt-Fn not working) and had to use long press of power button to quit.
Today I booted Fed29 on this laptop and there were updates waiting. Updated and restarted and to my surprise the same thing happened as when trying to install Fed30 beta. After the Dell logo when you would expect the gdm screen the screen went black and stayed that way. The updates included the 5.03 kernel. I could now of course activate the grub menu and boot with the old 4.20.16 kernel and look with journalctl in the previous boot journal. There seem to be some things going on with hibernate and suspend that should not happen and maybe some other irregularities. Should I file a bug report for Fed30 or for the kernel and what info should I attach.
I have no time for this today, will have to wait till tomorow. I also found this: https://bugs.freedesktop.org/show_bug.cgi?id=110193
AV
On Tue, 2019-03-26 at 16:28 +0100, AV wrote:
Yesterday I tried to install Fed30 beta-1.7 on a Dell Precision 5530. (late 2018 model, i5-8300H & UHD graphics 630, came with Ubuntu 18.04 and had Fed29 installed and working without problems) Almost immediately after the first few lines of the startup messages the screen went black and nothing further happened. Could not get any info in this state (Ctrl-Alt-Fn not working) and had to use long press of power button to quit.
Today I booted Fed29 on this laptop and there were updates waiting. Updated and restarted and to my surprise the same thing happened as when trying to install Fed30 beta. After the Dell logo when you would expect the gdm screen the screen went black and stayed that way. The updates included the 5.03 kernel. I could now of course activate the grub menu and boot with the old 4.20.16 kernel and look with journalctl in the previous boot journal. There seem to be some things going on with hibernate and suspend that should not happen and maybe some other irregularities. Should I file a bug report for Fed30 or for the kernel and what info should I attach.
It certainly sounds like a kernel bug. Can you file a report against the kernel package with the full journal output for an affected boot? Thanks!
Had the same thing happen on my Lenovo W530 on F29.
Issue is there regardless of kernel (4.20 or 5.0.3)
I created bug 1692817, I found 2 work arounds so far.
1) switch from gdm to sddm or another dm 2) or remove rhgb from GRUB_CMDLINE_LINUX
Upon further testing this morning appears like reintroduction of 1643302 issue
-Mike 304.638.8909 This plant powered email is RFC 1925 compliant. No electrons were harmed during composition.
On Mar 26, 2019, at 11:46 AM, Adam Williamson adamwill@fedoraproject.org wrote:
On Tue, 2019-03-26 at 16:28 +0100, AV wrote: Yesterday I tried to install Fed30 beta-1.7 on a Dell Precision 5530. (late 2018 model, i5-8300H & UHD graphics 630, came with Ubuntu 18.04 and had Fed29 installed and working without problems) Almost immediately after the first few lines of the startup messages the screen went black and nothing further happened. Could not get any info in this state (Ctrl-Alt-Fn not working) and had to use long press of power button to quit.
Today I booted Fed29 on this laptop and there were updates waiting. Updated and restarted and to my surprise the same thing happened as when trying to install Fed30 beta. After the Dell logo when you would expect the gdm screen the screen went black and stayed that way. The updates included the 5.03 kernel. I could now of course activate the grub menu and boot with the old 4.20.16 kernel and look with journalctl in the previous boot journal. There seem to be some things going on with hibernate and suspend that should not happen and maybe some other irregularities. Should I file a bug report for Fed30 or for the kernel and what info should I attach.
It certainly sounds like a kernel bug. Can you file a report against the kernel package with the full journal output for an affected boot? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
On Tue, 2019-03-26 at 12:15 -0400, Michael Erwin wrote:
Had the same thing happen on my Lenovo W530 on F29.
Issue is there regardless of kernel (4.20 or 5.0.3)
Then it's probably not actually the same bug. Since for AV, 4.20 works.
AdamW, You are correct. I could get to the text terminals and login with either kernel.
-Mike 304.638.8909 This plant powered email is RFC 1925 compliant. No electrons were harmed during composition.
On Mar 26, 2019, at 12:43 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Tue, 2019-03-26 at 12:15 -0400, Michael Erwin wrote: Had the same thing happen on my Lenovo W530 on F29.
Issue is there regardless of kernel (4.20 or 5.0.3)
Then it's probably not actually the same bug. Since for AV, 4.20 works.
Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org