I have a ASUS ExpertBook B1 with Intel i5-1235U CPU. When I try to boot the Live ISO Fedora-Workstation-Live-x86_64-41-1.4.iso it is stuck in a black screen doing nothing.
I also tried Debian 12 Live ISO and this one is working.
My question is how to debug this further? Is there any hotkey I can press or command to add so I can see what’s going on and where it gets stuck.
Secure Boot had to be disabled in order to make it boot at all.
I also tried using the iGPU and the Intel Xe GPU (added a RAM DIMM) with the same result.
I tried the linked ISO Fedora-Workstation-Live-42-20250213.n.0.x86_64.iso (verified its checksum) but it has the same issue independent if “start & test” or just “start” is chosen. Device can be turned off instantly with the power button after the selection is made.
Does your system have you have Intel Iris Xe Graphics? There are other reports of black screen due to the i915 driver crashing with Xe graphics. You could try a Fedora 41 respin.
Run inxi -Fzxx using the Debian Live environment (you may have to install inxi in the live environment) and post the output here (as pre-formatted text) so we can understand the hardware configuration.
I have a similar issue. You may be able to get to the secondary terminal (t2) by hitting CTL+ALT+F2 at the black screen. Then log in. I’ve tried downgrading MESA, different kernels, neither worked for me. Going to try downgrading the Intel VAAPI driver next. But that is an after coffee task. I run Fedora Plasma spin on 2 machines. I also tried a clean install of Fedora 41 and even Ultramarine. Both booted normally but had the black screen after the first update.
Update: I ran Debian 12 the whole time successfully and now tried to upgrade to Debian 13 and after the first reboot it has the same issue like Fedora and also the Debian 13 Live ISO with GNOME is not working and showing the same behaviour like Fedora. Maybe there is a regression kernel issue?
I looked up current kernel versions of these distros:
Debian 12: 6.1
Debian 13: 6.12
Fedora 41 and 42: 6.15
I am a bit out of ideas on where to turn to with this issue and how to produce any error that will help identify the problematic component.