Blank screen on Dell XPS 13 after upgrading to kernel 6.16.9

I have a Dell XPS 13 laptop (9350, BIOS 1.13.0). Everything except the built-in camera has been working well up through kernel 6.16.8. I upgraded to 6.16.9. When I try to boot into that new kernel, very early, the screen goes blank and just stays that way. The Fedora logo never appears. I can reboot by hitting Ctl+Alt+Delete. I’ve looked at messages from journalctl and I don’t see much. There are some messages about unreportable oopses that I don’t understand.

Also, it seems to be trying to run X rather than Wayland. I see errors from /usr/libexec/gdm-x-session (Unable to run X server) in the logs when booting 6.16.9, and nothing from /usr/libexec/gdm-wayland-session.

In contrast, when booting successfully with 6.16.8, I see information from /usr/libexec/gdm-wayland-session and nothing from /usr/libexec/gdm-x-session.

I haven’t been able to find any posts about this problem.

How do I troubleshoot this?

In the bottom right if the login screen, is there a setting to launch as x or wayland?

If not, tell us which desktop you are on.

The boot process doesn’t get that far. I never see the GDM login screen. I’ve been using Gnome and Wayland.

If you can select a working kernel, sinply go with that.

If when you update again, the new kernel also does not work, increase the number of kernels your system can retain from 3 to 5.

Lots of people have been having kernels that don’t work for 1 or 2 updates, it usually resolves, if not after next update, also file a bug with bugzilla.redhat.com

Hey, I’m having the same issue on 6.16.9-200, by any chance are you using Intel Arc (the xe driver) for your graphics? (I think most modern Intel igpus and discrete gpus are using the xe driver)
Not 100% sure if that’s the cause, as I’ve tried plugging an HDMI into my motherboard (amd cpu with no igpu) instead of my arc card and still nothing displays. Not sure how to proceed right now. I’ve tried grub2-editenv - unset menu_auto_hide as I wanted to boot into an older kernel, however that menu still fails to display. Uncertain if it’s because I should be issuing a different command, or the display fails so thoroughly to show anything that even grub doesn’t show up.

I should also say that the tty does not display either, however I was able to use the tty and systemctl start sshd.service without display output. Bizarrely meaning that the only way to issue commands to my desktop is through my laptop, also running completely up to date Fedora. (I guess the AMD graphics is the difference maker??)

To get the grub menu to display, hold shift while booting, or tap esc.

Unfortunately, I’m still not seeing grub. :frowning:
I would like to hope this is a me issue, maybe I’m mashing esc too much or holding shift too early or something.

However, I started cockpit and checked the logs for this boot and saw this happening about 4 times every minute. How should I go about getting useful information from this?

10:06 PM - Process 1577 (gdm) crashed in get_fallback_session_name() - gdm
10:06 PM - [no data] - systemd-coredump
10:06 PM - Gdm: GdmSession: no session desktop files installed, aborting... - gdm

Abrtd.service says this:
PROBLEM_REPORT gdm killed by SIGTRAP #1 [gdm] get_fallback_session_name #2 [gdm] gdm_session_start_session #3 [libffi.so.8] ffi_call_unix64 #4 [libffi.so.8] ffi_call_int.lto_priv.0 #5 [libffi.so.8] ffi_call

Also looks like a few abrt services are combined using over a gig of ram. Hopefully this is getting reported? I have automatic problem reporting on.

If you cant access a new TTY with ctrl+alt+f3

after boot,

then try booting from a Live USB and delete the newest kernel or recover your system.

1 Like

I’m not confident in my ability to chroot and uninstall the latest kernel, but i found this command sudo grub2-set-default 2 accomplished the same-ish thing and got my computer working. Currently typing this from my computer, running 6.16.7-200, no problems anymore. Thank you for the help!

3 Likes

Great work! You’ve got what it takes, keep it up :slight_smile:

As far as I know, it’s using the Xe driver and the integrated video device. The xe module shows up in lsmod when running a working kernel. I haven’t done any manual configuration of the video driver. There’s no separate GPU on this laptop.

Hi Darian, if you aren’t seeing GRUB, that’s a different problem from mine. On my laptop, GRUB works fine, and the boot process at least starts, then something goes wrong and the screen goes blank after GRUB launches the kernel. It won’t switch to another virtual console, at least not that I can see.

Yeah not sure what’s going on with my grub, but thankfully it looks like the latest kernel (6.16.10-200) has fixed this on my computer. Hope it also solves this on your computer. It sounds like you won’t need to use a virtual console to update if you’re getting commands to it. In my case I had to use the virtual console without any display and just login and enable sshd without seeing what I was typing.

I just ran dnf upgrade and it installed kernel 6.16.10. I booted into 6.16.10, and now everything seems to be working. So someone must have fixed something. Yay!