Skip to content

Black Screen After Updating to linux-cachyos 6.14.7-5 #460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
boggedbrush opened this issue May 20, 2025 · 8 comments
Closed

Black Screen After Updating to linux-cachyos 6.14.7-5 #460

boggedbrush opened this issue May 20, 2025 · 8 comments
Labels
bug Something isn't working

Comments

@boggedbrush
Copy link

Summary

After updating the kernel from 6.14.6-2 to 6.14.7-5 on CachyOS, the system fails to boot and shows a black screen.
Rolling back via a Btrfs snapshot to the previous kernel immediately restores boot.
Limine was already updated and working fine before the kernel update.


System Info

  • Kernel (Working): 6.14.6-2-cachyos
  • Kernel (Broken): 6.14.7-5-cachyos
  • Bootloader: Limine 9.3.2 (working as expected)
  • Root FS: Btrfs
  • Boot Mode: EFI
  • ESP: Mounted at /boot, formatted as FAT32
  • Init System: systemd
  • CPU: AMD Ryzen 5 5600X
  • GPU: AMD Radeon RX 6800
  • DE: KDE Plasma 6 (Wayland)
  • Limine installed to: /dev/nvme1n1

Repro Steps

  1. Run:

    sudo pacman -Syu
    # Accept upgrade for linux-cachyos to 6.14.7-5
  2. Reboot

  3. System fails to boot and shows black screen

  4. Restore snapshot with 6.14.6-2 → system boots normally


Notes

  • This appears to be a regression in linux-cachyos 6.14.7-5
  • Issue is likely isolated to the kernel update itself — no other changes made
@1Naim 1Naim transferred this issue from CachyOS/CachyOS-PKGBUILDS May 20, 2025
@1Naim
Copy link
Member

1Naim commented May 20, 2025

Using the broken kernel, can you:

  1. Boot normally -> black screen happens
  2. Go to TTY3 ctrl + alt + f3, and grab logs sudo cachyos-bugreport.sh. If you succeeded here, just upload the log and await further instructions
  3. If 2 failed, continue here.
  4. Force shutdown and try booting into the broken kernel again, but this time add 3to kernel cmdline (press e in boot menu and add 3 at the end of the line)
  5. Get previous boot logs with journalctl -b -1 | paste-cachyos and send the log.

@1Naim 1Naim added the bug Something isn't working label May 20, 2025
@boggedbrush
Copy link
Author

boggedbrush commented May 20, 2025

Thank you for the quick comment!

I attempted steps 1 and 2. Unfortunately, I got no response after pressing Ctrl + Alt + F3, the monitor continued to display "No Signal".

For step 4, I understood that you wanted me to add 3 to the end of the kernel command line. I wasn’t entirely sure where to place it, so I tried two versions:

  • Appending 3 directly to the root=UUID=... string
  • Adding a space and placing 3 right after the root=UUID=... entry

Both attempts resulted in the same black screen, with no response from Ctrl + Alt + F3.

It’s possible this could be user error, or maybe my keyboard is interfering, it requires me to press Fn before the F-keys.

I’ve attached a screenshot of my Limine config showing the broken kernel (without 3 added):

Image

@ptr1337
Copy link
Member

ptr1337 commented May 21, 2025

Can you try to pass "nomodeset" when booting?

@boggedbrush
Copy link
Author

Using nomodeset I was able to run the command from 1Naim's comment: sudo cachyos-bugreport.sh, you can take a look at the logs here.

I hope this helps, and thank you for your time!

@boggedbrush
Copy link
Author

Thank you for all the suggestions!

After removing my custom amdgpu.conf and updating to the very latest Mesa packages, I can now successfully boot into 6.14.7-5-cachyos with no black screen. I’m not certain whether it was the removal of my modprobe tweaks or the recently updated Mesa drivers that fixed it, but in any case the regression no longer reproduces here.

I’m happy to mark this issue as closed, but I’ll leave it open in case you’d like to keep digging into the root cause. Just let me know!

@1Naim
Copy link
Member

1Naim commented May 21, 2025

Yeah i'll close this. For reference, can you share what you had in your custom amdgpu.conf? Thanks.

@1Naim 1Naim closed this as completed May 21, 2025
@boggedbrush
Copy link
Author

I had these options in my amdgpu.conf to fix sleep issues I've been having:

options amdgpu runpm=0
options amdgpu dpm=0
options amdgpu baco=0 aspm=0
options amdgpu dc=0

@1Naim
Copy link
Member

1Naim commented May 21, 2025

Yeah, those don't really look right. Please file an issue at https://gitlab.freedesktop.org/drm/amd/-/issues to get it tracked and fixed. Make sure an there isn't an existing issue that is already tracking this though before creating a new one.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants