Fedora won't boot without nomodeset

Ask Fedora
, , ,
1

Hi. I’ve been trying to install Fedora 40 on my PC for a while now but even the Live USB gets stuck on a black screen if I don’t use the basic graphics mode. I decided to install it anyway but the problem persists on the installed OS. I think I’ve tried other distros a couple months ago, like Ubuntu 22.04 or Fedora 39, but they wouldn’t boot either. I tried to update the kernel to version 6.10, still nothing. Windows 10 was working fine, but I messed up its boot manager trying to dual boot with Fedora 40, so now I can’t access it either (but that’s another story).

My PC is a Dell Inspiron 5675 (Ryzen 5 1400 + RX 560D 2GB). I actually found an entry on this site reporting that this hardware has problems on Linux: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X]

So, right now I only have access to GRUB and Fedora 40 if I use nomodeset. Is there anything I can do to recover this installation?

1 Like
2

Added f40 and removed f39

3

Once you get to the desktop, is your GPU working normally? Which driver is being used?

This will tell you more about the driver that is loaded:

$ lspci -k

It should normally be amdgpu for your card. The boot log can provide additional information about issues surrounding the loading of the amdgpu driver:

$ sudo dmesg | grep amdgpu

Something you can check is if all the required firmware-packages are available on your system:

$ rpm -qa | grep firmware

You will need to have the amd-gpu-firmware package installed for your card to work properly.

1 Like
4 
$ lspci -k
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
	Subsystem: Dell Device 07ee
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
	Subsystem: Dell Device 07ee
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
	Subsystem: Dell Device 07ee
	Kernel driver in use: pcieport
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
	Subsystem: Dell Device 07ee
	Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
	Subsystem: Dell Device 07ee
	Kernel driver in use: pcieport
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
	Subsystem: Dell Device 07ee
	Kernel driver in use: piix4_smbus
	Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
	Subsystem: Dell Device 07ee
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
	Kernel driver in use: k10temp
	Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Dell Device 07ee
	Kernel driver in use: r8169
	Kernel modules: r8169
02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller (rev 02)
	Subsystem: ASMedia Technology Inc. Device 1142
	Kernel driver in use: xhci_hcd
02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller (rev 02)
	Subsystem: ASMedia Technology Inc. Device 1062
	Kernel driver in use: ahci
02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port (rev 02)
	Subsystem: ASMedia Technology Inc. Device 0201
	Kernel driver in use: pcieport
03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	Subsystem: ASMedia Technology Inc. Device 3306
	Kernel driver in use: pcieport
03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	Subsystem: ASMedia Technology Inc. Device 3306
	Kernel driver in use: pcieport
03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	Subsystem: ASMedia Technology Inc. Device 3306
	Kernel driver in use: pcieport
03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	Subsystem: ASMedia Technology Inc. Device 3306
	Kernel driver in use: pcieport
03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	Subsystem: ASMedia Technology Inc. Device 3306
	Kernel driver in use: pcieport
05:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
	Subsystem: Dell Device 0310
	Kernel driver in use: ath10k_pci
	Kernel modules: ath10k_pci
06:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
	Subsystem: Dell Device 07ee
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci
09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev cf)
	Subsystem: Dell RX 560D OEM OC 2 GB
	Kernel modules: amdgpu
09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
	Subsystem: Dell Device aae0
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
	Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
0a:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor (PSP) 3.0 Device
	Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor (PSP) 3.0 Device
	Kernel driver in use: ccp
	Kernel modules: ccp
0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
	Subsystem: Dell Device 07ee
	Kernel driver in use: xhci_hcd
0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
	Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
0b:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
	Subsystem: Dell Device 07ee
	Kernel driver in use: ahci
0b:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
	Subsystem: Dell Device 07ee
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

The “VGA Compatible Controller” correctly points out which GPU I’m using and it says that it uses amdgpu kernel modules.

sudo dmesg | grep amdgpu

This one returns nothing.

$ rpm -qa | grep firmware
linux-firmware-whence-20240709-1.fc40.noarch
amd-gpu-firmware-20240709-1.fc40.noarch
amd-ucode-firmware-20240709-1.fc40.noarch
atheros-firmware-20240709-1.fc40.noarch
brcmfmac-firmware-20240709-1.fc40.noarch
cirrus-audio-firmware-20240709-1.fc40.noarch
intel-audio-firmware-20240709-1.fc40.noarch
intel-gpu-firmware-20240709-1.fc40.noarch
mt7xxx-firmware-20240709-1.fc40.noarch
nvidia-gpu-firmware-20240709-1.fc40.noarch
nxpwireless-firmware-20240709-1.fc40.noarch
realtek-firmware-20240709-1.fc40.noarch
tiwilink-firmware-20240709-1.fc40.noarch
linux-firmware-20240709-1.fc40.noarch
iwlegacy-firmware-20240709-1.fc40.noarch
iwlwifi-dvm-firmware-20240709-1.fc40.noarch
iwlwifi-mvm-firmware-20240709-1.fc40.noarch
libertas-firmware-20240709-1.fc40.noarch
alsa-sof-firmware-2024.03-2.fc40.noarch

amd-gpu-firmware is there.

5

Everything looks good! If it’s not a problem for you to boot up using nomodeset, then you might just use it the way it currently is.

In case the detection of the GPU fails in early boot for some reason, you could try to force the amdgpu to be used by adding this kernel line (temporarily) instead of nomodeset:

amdgpu.dc=1

There is a chance though it will have no effect for your situation.

1 Like
6

Unfortunately, nomodeset makes me stuck on a very low resolution with ugly colors, so that’s why I’m looking for a fix.

amdgpu.dc=1 doesn’t boot either.

7

Since the GPU itself is detected okay when you reach the desktop, the issue might be in the detection of the output resolution (panel) instead.

I have no personal experience in that area, but below for instance is a thread from the Arch Linux forums describing a similar situation, where creating manual output modes (edid) helped to solve the problem:

https://bbs.archlinux.org/viewtopic.php?id=273784

1 Like
8

I think this might be the case. I’m using a pretty old Samsung monitor (LN19A330J1), 1440x900. It probably has a bad EDID and Windows have some workaround for it. I’ll try to fix that later. I don’t really know how to extract info from monitors or how to mess with EDID, so if anyone can help with that please post here. So far I tried hwinfo --monitors and got no results.

1 Like
9

Kernel.org Admin Guide EDID lists sources of EDID problems, then says:

Adding the kernel parameter “nomodeset” helps in most cases, but causes restrictions later on.

As a remedy for such situations, the kernel configuration item CONFIG_DRM_LOAD_EDID_FIRMWARE was introduced. It allows to provide an individually prepared or corrected EDID data set in the /lib/firmware directory from where it is loaded via the firmware interface

1 Like
10

So, I’ve tried to force a custom resolution with the “video=” parameter but I still got nothing. That said, I still think it’s a problem with the monitor, but I don’t feel like going through the hassle of fixing the EDID or whatever, so I’ll just stick to Windows 10 for now. Unfortunately I don’t have another monitor to test if it’s really the root cause.
This tutorial might be interesting for anyone willing to fix the EDID of a monitor: Guide how to achieve better resolution with broken EDID. Two methods are used: xorg.conf config and kernel params. · GitHub

Anyway, thanks for the help @litemotiv @gnwiii .

1 Like
11

Can you post the output of inxi -Fzxx so we have details of your hardware and software?

1 Like
12

Windows Overridiing Monitot EDID.

How to find EDID on Windows. Note that some reports say Microsoft omits parts of the EDID for high-end monitors – I assume capabilities Windows doesn’t support, so unlikely to affect your case.

1 Like
13 
$ inxi -Fzxx
System:
  Kernel: 6.10.3-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.4 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Desktop System: Dell product: Inspiron 5675 v: 1.5.0
    serial: <superuser required> Chassis: type: 3 v: 1.5.0
    serial: <superuser required>
  Mobo: Dell model: 07PR60 v: A01 serial: <superuser required> part-nu: 07EE
    UEFI-[Legacy]: Dell v: 1.5.0 date: 02/09/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
    charge: 55% (should be ignored) status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse serial: <filter>
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: AMD Ryzen 5 1400 bits: 64 type: MT MCP arch: Zen
    rev: 1 cache: L1: 384 KiB L2: 2 MiB L3: 8 MiB
  Speed (MHz): avg: 1395 high: 1550 min/max: 1550/3200 boost: enabled cores:
    1: 1375 2: 1375 3: 1375 4: 1375 5: 1365 6: 1550 7: 1374 8: 1375
    bogomips: 51098
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Baffin [Radeon RX 460/560D / Pro
    450/455/460/555/555X/560/560X] vendor: Dell driver: N/A arch: GCN-4 pcie:
    speed: 8 GT/s lanes: 1 bus-ID: 09:00.0 chip-ID: 1002:67ef
  Display: wayland server: X.Org v: 24.1.2 with: Xwayland v: 24.1.2
    compositor: gnome-shell driver: X: loaded: N/A unloaded: modesetting
    alternate: fbdev,vesa dri: swrast gpu: N/A display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96
  Monitor-1: Unknown-1 mapped: None-1 res: 1024x768 dpi: 96
  API: OpenGL v: 4.5 vendor: mesa v: 24.1.5 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: llvmpipe (LLVM 18.1.6 256 bits)
    device-ID: ffffffff:ffffffff
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / 560/560X]
    vendor: Dell driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 1
    bus-ID: 09:00.1 chip-ID: 1002:aae0
  Device-2: AMD Family 17h HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 0b:00.3 chip-ID: 1022:1457
  API: ALSA v: k6.10.3-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Dell driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168
  IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Dell driver: ath10k_pci v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 05:00.0 chip-ID: 168c:003e
  IF: wlp5s0 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-12:3 chip-ID: 0cf3:e007
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 1.35 TiB used: 4.7 GiB (0.3%)
  ID-1: /dev/sda vendor: A-Data model: SU650 size: 447.13 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-75WN4A0
    size: 931.51 GiB speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 194.31 GiB used: 4.32 GiB (2.2%) fs: btrfs dev: /dev/sda6
  ID-2: /boot size: 973.4 MiB used: 362.8 MiB (37.3%) fs: ext4
    dev: /dev/sda5
  ID-3: /home size: 194.31 GiB used: 4.32 GiB (2.2%) fs: btrfs
    dev: /dev/sda6
Swap:
  ID-1: swap-1 type: zram size: 7.64 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 27.1 C mobo: 25.0 C
  Fan Speeds (rpm): fan-1: 1997 fan-2: 475
Info:
  Memory: total: 8 GiB available: 7.64 GiB used: 2.09 GiB (27.4%)
  Processes: 1015 Power: uptime: 2m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: Compilers: N/A Shell: Bash v: 5.2.26 running-in: gnome-terminal
    inxi: 3.3.34
1 Like
14

If the video=... override doesn’t work, then I would tend to think it is not a EDID problem. It could be a regression in the amdgpu driver or firmware. Unfortunately those problems are very difficult to debug. It can be done, but it might require a serial connection or something similar. The below link shows an example of what the debugging process might look like.

https://bugzilla.kernel.org/show_bug.cgi?id=196117

P.S. This appears to be the main bug tracking system for the amdgpu driver. (I’ve set the link to show bugs tagged “Polaris” which I believe is what your video card is.)

1 Like
15

video= didn’t appear to have much effect on my (working) amdgpu system when i was testing with grub earlier, so i’m not sure if it behaves reliably enough for a good diagnosis.

1 Like
16

The correct syntax for the video= parameter is a bit tricky.

Excerpted from the Arch Wiki: [1]

The format is:

video=<driver>:<conn>:<xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]

  • <driver>: Specify a video mode at bootup.
  • <conn>: Specifies the video connection type, such as VGA, DVI, HDMI, etc., see /sys/class/drm/ for available connectors
  • <xres>: The horizontal resolution in pixels.
  • <yres>: The vertical resolution in pixels.
  • [M]: Enables the use of VESA Coordinated Video Timings (CVT) to calculate the video mode timings instead of looking up the mode from a database
  • [R]: Enables reduced blanking calculations for digital displays when using CVT. This reduces the horizontal and vertical blanking intervals to save bandwidth.
  • [-<bpp>]: Specifies the color depth or bits per pixel (e.g., -24 for 24-bit color).
  • [@<refresh>]: Specifies the refresh rate in Hz.
  • [i]: Enables interlaced mode.
  • [m]: Adds margins to the CVT calculation (1.8% of xres rounded down to 8 pixels and 1.8% of yres)
  • [e]: output forced to on
  • [D]: digital output forced to on (e.g. DVI-I connector)
  • [d]: output forced to off

You can override the modes of several outputs using video= several times, for instance, to force DVI to 1024x768 at 85 Hz and TV-out off:

video=DVI-I-1:1024x768@85 video=TV-1:d

To get the name and current status of connectors, you can use the following shell oneliner:

$ for p in /sys/class/drm/*/status; do con=${p%/status}; echo -n "${con#*/card?-}: "; cat $p; done
DVI-I-1: connected
HDMI-A-1: disconnected
VGA-1: disconnected

It might just be that you had a typo when specifying the connector name or something like that. I expect that that parameter should work quite reliably.

  1. https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes ↩︎

1 Like
17

I tried video=1440x900 (native resolution), video=1024x768 (nomodeset runs in this resolution), video=1440x900@60 and video=1024x768@60. I didn’t try to specify other values such as the connection.

I’m currently using a DVI x VGA cable on my monitor, I remember trying with a HDMI x VGA cable too, both would work fine on Windows but not on Linux. This monitor has an HDMI port but it behaves weirdly even on Windows, as if it’s trying to force 1080p on the screen, I believe it’s because it was made for using as a TV rather than a PC monitor. I don’t have a HDMI cable right now to test Fedora with it though.

Anyway, I just did a Windows 10 clean install and everything works as intended. Maybe I’ll try Fedora again when I get a proper setup, as of now I think it’s better to stick with Windows.

1 Like
18

There appear to be several polaris-related bugs in the amdgpu issue tracker that have come up recently (within the last month or so). Some of them look very similar to what you are reporting. I wouldn’t be surprised if it takes another month, two, or possibly more for the fix to be found, implemented, and to work its way through the pipeline to the end users’ systems. Were I you, I would boot into Fedora Linux with the nomodeset option maybe once every two weeks and run sudo dnf update kernel*, then reboot without the nomodeset parameter and see if the new kernel works. If not, wait another two weeks and repeat until (hopefully) the problem gets resolved. (Also, keep an eye on that issue tracker for updates.)

2 Likes
19

For me, it looks like a bug in the video driver.
At first, read a bit: QA/Sysrq - Fedora Project Wiki , you may want to enable Sysrq.
So what I would do is boot without nomodeset.
On black screen, Alt-PrintScreen-S (To force error toward disk logs),
Alt-PrintScreen-R (to reboot) … if not working… hold power to force poweroff.

Then I would reboot with nomodeset, then at the command prompt: systemctl -b -1 -p4, and read the errors.

-b -1 is last boot
-p4 means of priority at least 4 … 3 would show less messages, 5 more

1 Like