Hi y’all. As the title says, after selecting a kernel to boot in grub, 2/3 of the time I get a blank screen. There’s no real tie or common trait between when it does/doesn’t work, the same boot options will work one time and not another.
Nomodeset seems to have no real effect, if anything, working less.
It always boots if I use the 5.0.9 kernel, but using 5.1.15 or 5.1.16 has the possibility of leading to this blank screen.
I’m using an Asus UX333FA laptop, with an i5-8265U processor and integrated graphics. Running Fedora 30 with the 5.1.16 kernel, using KDE if that makes a difference.
Any help would be so appreciated, thanks.
Two suggestions:
Enable ssh on your system and try to connect to it once the system boots with a black screen. if you are able to connect, you can then check your dmesg and other log files, which should probably point to the issue.
If you have a discrete graphics card, go into the BIOS and see if you can switch from running on integrated graphics to running on that. If one boots but not the other, you’ll know where the problem is.
Immediately after a failed boot, once you can boot normally, run journalctl -b-1 -e to see the logs from the previous boot (which failed), starting at the end, and then look for any errors or similar.
Hello @drgatto and welcome to the community.
Please take a minute to go over the posts in the #start-here category if you haven’t had a chance yet.
Even if the model is different, it is still an Asus, but the behavior is similar to this one: https://discussion.fedoraproject.org/t/fedora-new-kernel-not-working-after-dnf-upgrade-refresh/73075
Could you try to pass dis_ucode_ldr to the kernel?
1 Like
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31929, resource id: 29360147, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31934, resource id: 73400325, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31938, resource id: 71303173, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31942, resource id: 69206021, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31946, resource id: 67108869, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31950, resource id: 65011717, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31954, resource id: 62914565, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31958, resource id: 60817413, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31962, resource id: 58720261, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31966, resource id: 56623109, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31970, resource id: 44040197, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31974, resource id: 35651589, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31978, resource id: 31457285, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31982, resource id: 27262981, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31986, resource id: 23068677, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31990, resource id: 75497483, major code: 18 (ChangeProperty), minor code: 0
plasmashell[2044]: org.kde.plasma.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
plasmashell[2044]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/applet/CompactApplet.qml:64: TypeError: Cannot read property 'Layout' of null
sddm[1784]: Authentication error: "Process crashed"
sddm[1784]: Auth: sddm-helper crashed (exit code 15)
kscreen_backend_launcher[2174]: The X11 connection broke (error 1). Did the X11 server die?
xdg-desktop-por[2458]: xdg-desktop-portal-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
kdeinit5[1997]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
systemd[1]: pcscd.service: Main process exited, code=exited, status=1/FAILURE
localhost.localdomain systemd[1]: pcscd.service: Failed with result 'exit-code'.
wpa_supplicant[1735]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
systemd-cryptsetup[3683]: Device luks-b8a44946-d5a9-4c49-89ff-0d91613e0303 is still in use.
systemd-cryptsetup[3683]: Failed to deactivate: Device or resource busy
systemd-cryptsetup[3682]: Device luks-ea54c722-96cb-4aee-9df6-07412fd04cc5 is still in use.
systemd-cryptsetup[3682]: Failed to deactivate: Device or resource busy
systemd-cryptsetup[3684]: device-mapper: remove ioctl on luks-18bcac55-8352-495d-bc54-43cc6ab7d8ac failed: Device or resource busy
systemd-cryptsetup@luks\x2db8a44946\x2dd5a9\x2d4c49\x2d89ff\x2d0d91613e0303.service: Failed with result 'exit-code'.
Judging from the errors maybe a luks problem? I see stuff about X too, which would explain why it’s just a blank screen.
Any thoughts?
dis_ucode_ldr seemed to boot every time, thanks a lot.
Is adding that to the default grub options the best/most permanent solution untill an update fixes this? The post mainly talked about enabling that by default in future kernels, which isn’t too big of a deal for me relative to outright fixing it.
You could look if there is a BIOS update for this Asus model. In the bug report linked in the other post, someone suggests to update the BIOS.
Yup, that solved it. Thanks.
1 Like
Hello @drgatto, glad that you solved the issue.
Could you add a comment on the bug mentioned in the other topic? 1724262 – Fedora doesn't boot in ASUS VivoBook after update
This document could be useful: How to file a bug :: Fedora Docs