F5F Stay Refreshed Software Operating Systems ArchWiki instructions cause black screen during startup (AMDGPU)

ArchWiki instructions cause black screen during startup (AMDGPU)

ArchWiki instructions cause black screen during startup (AMDGPU)

Pages (2): Previous 1 2
W
Weegeeh
Member
Find
165
06-10-2025, 05:33 PM
#11
Typically a secure boot and closed drivers cause a black screen. At least most of my black screens over the past five years are due to this.
Reply
Reply
W
Weegeeh
06-10-2025, 05:33 PM #11

Typically a secure boot and closed drivers cause a black screen. At least most of my black screens over the past five years are due to this.

Reply
Reply
M
MrGoldenApple
Member
Find
166
06-12-2025, 04:05 PM
#12
I initially mixed up UEFI and Legacy BIOS. My understanding of Secure Boot isn't clear yet. It seems Manjaro doesn’t rely on the signed shim loader for its support, though I’m not certain. Also, both AMDGPU (new) and radeon (older) are open-source drivers, while the proprietary version is AMDGPU-PRO.
Reply
Reply
M
MrGoldenApple
06-12-2025, 04:05 PM #12

I initially mixed up UEFI and Legacy BIOS. My understanding of Secure Boot isn't clear yet. It seems Manjaro doesn’t rely on the signed shim loader for its support, though I’m not certain. Also, both AMDGPU (new) and radeon (older) are open-source drivers, while the proprietary version is AMDGPU-PRO.

Reply
Reply
F
FakieLife
Member
Find
154
06-13-2025, 01:52 AM
#13
Arch doesn't seem to cause a black screen on Manjaro, though it might happen on other systems.
Reply
Reply
F
FakieLife
06-13-2025, 01:52 AM #13

Arch doesn't seem to cause a black screen on Manjaro, though it might happen on other systems.

Reply
Reply
M
MCcookie333
Junior Member
Find
5
06-28-2025, 03:47 PM
#14
Thanks for the responses, everyone... I’ll check the secure boot settings and reply later. What bothers me is seeing many users with the same GPU as mine in Arch/Manjaro and Pop having it work, while others can’t. I think the AMD GPU drivers are kept up to date since new releases are coming out. Besides that secure boot issue... anyone else have ideas before I go back to what the ArchWiki recommends so I can get my original error back?
Reply
Reply
M
MCcookie333
06-28-2025, 03:47 PM #14

Thanks for the responses, everyone... I’ll check the secure boot settings and reply later. What bothers me is seeing many users with the same GPU as mine in Arch/Manjaro and Pop having it work, while others can’t. I think the AMD GPU drivers are kept up to date since new releases are coming out. Besides that secure boot issue... anyone else have ideas before I go back to what the ArchWiki recommends so I can get my original error back?

Reply
Reply
M
Mr_Ono
Junior Member
Find
31
06-28-2025, 08:55 PM
#15
It was quite an issue trying to get things working. I couldn't locate any information about secure boot in the BIOS settings. It looks like I'm still using legacy mode with Manjaro and UFEI, paired with Windows 10. Interestingly, I have three boot options even though only two operating systems are installed on separate drives. This might be contributing to the problem. The drive labeled PM SATA3 is where Manjaro is running, while the other has Windows 10 booting via the Windows 10 loader. Since my system is quite old, I haven't really experienced the advantages of UFEI, so I prefer sticking with legacy mode. However, I did see one UEFI option that didn't load properly—setting its priority to UFEI compatible fixed that but only showed a diagnostic window. If I switch back to legacy, it boots fine. It's unclear if the PM and SM labels on the drive names have any significance.
Reply
Reply
M
Mr_Ono
06-28-2025, 08:55 PM #15

It was quite an issue trying to get things working. I couldn't locate any information about secure boot in the BIOS settings. It looks like I'm still using legacy mode with Manjaro and UFEI, paired with Windows 10. Interestingly, I have three boot options even though only two operating systems are installed on separate drives. This might be contributing to the problem. The drive labeled PM SATA3 is where Manjaro is running, while the other has Windows 10 booting via the Windows 10 loader. Since my system is quite old, I haven't really experienced the advantages of UFEI, so I prefer sticking with legacy mode. However, I did see one UEFI option that didn't load properly—setting its priority to UFEI compatible fixed that but only showed a diagnostic window. If I switch back to legacy, it boots fine. It's unclear if the PM and SM labels on the drive names have any significance.

Reply
Reply
Pages (2): Previous 1 2