Black screen on Boot, requires nomodeset

stengah1 · 2025-01-16 03:57:44

Getting a black screen right after 'triggering uevents' in boot. This is happening both on my arch system install and a usb installer. tested with both linux and linux-lts kernels.
Setting nomodeset in parameter allows me to boot with 800x600 set resolution.
linux-firmware is installed, mesa drivers, all updated.
I dual boot with windows 11, went in and disabled fast-boot.

journal logs at
https://rentry.co/xm5gvh9k pt1
https://rentry.co/u8nkyyc7 pt2

seth · 2025-01-16 10:00:34

To access the raw version of this page, a valid access code must be set in the metadata: SECRET_RAW_ACCESS_CODE.
You may request an access code by emailing support@rentry.co

For the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

V1del · 2025-01-16 10:27:38

Jan 15 21:01:33 archlinux kernel: amdgpu 0000:06:00.0: [drm] Cannot find any crtc or sizes

Is your monitor plugged into the wrong card?

seth · 2025-01-16 15:22:08

Getting a black screen right after 'triggering uevents' in boot … Setting nomodeset in parameter allows me to boot with 800x600 set resolution.

I don't see a second VGA device, not even by a (rough) pci id check.

Jan 15 21:01:37 archlinux sddm-greeter-qt6[665]: Adding view for ":0.0" QRect(0,0 0x0)

indicates a zero-output situation.

Try to add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters (it doesn't matter that you don't have an nvidia GPU, we just want to block the simpledrm device)

stengah1 · 2025-01-16 23:23:41

using nvidia_drm.modeset=1 indeed worked! now have native resolution. here is the output from journalctl:
http://0x0.st/8oUj.txt

should this be added to arch.conf or is there a better permanent fix? thanks

stengah1 · 2025-01-16 23:26:02

here is the current boot:
http://0x0.st/8oUL.txt

seth · 2025-01-17 10:20:54

I guess hdmi stumbles a second hdcp handshake when amdgpu takes over from the simplydumb device.
You can permanently add "nvidia_drm.modeset=1" to your bootloader config, but it's a hack that wa patched in because the nvidia driver had systematic trouble with the simplydumb driver and already was briefly removed.

Try whether you get away w/ "initcall_blacklist=simpledrm_platform_driver_init" instead (this however might apply toolate™ and therefore not cut it)

stengah1 · 2025-01-18 15:48:11

"initcall_blacklist=simpledrm_platform_driver_init" worked. the nvidia_drm.modeset=1, when used, didn't get me the brightness slider for my monitor, but this new parameter does.
current boot:
http://0x0.st/8HXr.txt

what would be the root cause of why these workarounds were not needed a week ago, for both the system install and install media?

seth · 2025-01-18 16:04:08

\o/

get me the brightness slider for my monitor

Does it also work?

What changed a week ago?
Chances are it's either a kernel regression (tested the LTS behavior?) when trying to hand over the drm control or some change in the setup (cable) has triggered a race control w/ your monitor (the hdcp handhshake is deliberately fragile and not error tolerant, some impedence on the signal from a second cable or whatnot can cause this. An inb4 you ask: it's so you don't steal valuable IP like Madam Webb…)

Arch Linux

#1 2025-01-16 03:57:44

Black screen on Boot, requires nomodeset

#2 2025-01-16 10:00:34

Re: Black screen on Boot, requires nomodeset

#3 2025-01-16 10:27:38

Re: Black screen on Boot, requires nomodeset

#4 2025-01-16 15:22:08

Re: Black screen on Boot, requires nomodeset

#5 2025-01-16 23:23:41

Re: Black screen on Boot, requires nomodeset

#6 2025-01-16 23:26:02

Re: Black screen on Boot, requires nomodeset

#7 2025-01-17 10:20:54

Re: Black screen on Boot, requires nomodeset

#8 2025-01-18 15:48:11

Re: Black screen on Boot, requires nomodeset

#9 2025-01-18 16:04:08

Re: Black screen on Boot, requires nomodeset

Board footer