ArchWiki instructions cause black screen during startup (AMDGPU)
ArchWiki instructions cause black screen during startup (AMDGPU)
Hello .. again .. Nayr438 - I didn't reply in the old discussion, but in short, it produced the same outcome and my mind went wild. I had to step away for a month. Now moving on to this new problem... It's the identical situation... My current configuration is an I5 2500, R9 290, 16GB RAM, Manjaro KDE installed. Still using the 5.9 kernel because of a time-shift rollback (I accidentally modified GRUB before this post due to too much frantic work). This time somehow, "vulkan" is working thanks to updated Radeon drivers. I can run vxcube without issues and see no errors when checking it with "vulkaninfo". However, I'm still unable to launch any Proton games in Steam... I can get a few through Wine, but I'd like to use the amdgpu-pro driver so I can fully utilize Proton for my GPU. I think I have all the necessary drivers installed and I'm back where I was before I messed up the GRUB... The drivers I currently have are: - My main problem is that when following the Archwiki guide, whatever I do, it always ends in a complete black screen, making it impossible to even access the tty2 screen for troubleshooting. ... I've double-checked: - I made sure amdgpu is listed first in the Mkinitcpio modules (though I only added amdgpu) - Set module parameters via the kernel command line in both amdgpu.conf and radeon.conf files - Included modconf in the HOOKS array of /etc/mkinitcpio.conf and regenerated the initramfs (believe it covers the early KMS start issue) - Verified that installing the amdgpu-pro-libgl AUR package is required for 32-bit apps - Tried a fix on this site with the same issue as me but using a 390 — https://gitlab.freedesktop.org/mesa/mesa/-/issues/1222 - Still, every time I boot, I get a black screen. ... If I modify /etc/modprobe.d/amdgpu.conf to options amdgpu with si_support=0 and cik_support=1, it lets me boot normally and I can restore tty2. I've also seen someone on Reddit say the GDM was loading before the amdgpu driver... I don't fully grasp what they mean, so I haven't tried that yet. But nothing else seems to work. I'm at a bit of a dead end here. ... Some people reported success with a very similar setup — it probably should work for me too... But honestly, I'm stuck and can't figure out the next steps.**
Earlier I mentioned avoiding amdgpu-pro. DXVK in Proton runs against the standard mesa stack, which is also where community updates happen. When amdgpu-pro is on top, it replaces the default mesa versions. It exists mainly for workstation projects built with Windows Driver Implementation, but it creates more issues than benefits outside those scenarios. In gaming situations it usually underperforms. Also, your R9 280 isn't listed as supported in the latest amdgpu-pro release.
The only situation requiring AMDGPU-PRO drivers is when you must utilize OpenCL. That's all. For other scenarios, a free AMDGPU open-source driver that comes with the default kernel and doesn't require any configuration is much preferable. Thanks for the time spent on this...
Hey everyone, thanks for the help... To be clear, I own a 290, not a 280 (that was in the past). The info looks like this: Inxi -G Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Hawaii PRO [Radeon R9 290/390] driver: radeon v: kernel Display: x11 server: X.Org 1.20.13 driver: loaded: ati, radeon unloaded: modesetting resolution: 1920x1080~60Hz OpenGL: renderer: AMD HAWAII (DRM 2.50.0 5.9.16-1-MANJARO LLVM 12.0.1) v: 4.5 Mesa 21.3.0-devel (git-fce0027d91) The main reason I’m using amdgpu-pro is because I previously tried that setup with POPos and couldn’t even run Vulkan with the default drivers. Every time I followed a guide, I encountered errors when trying to run vulkaninfo—it kept failing to locate the right firmware for my GPU. After some research, I discovered it’s likely only the pro version of the driver supports AMD GPU + OpenGL 4.6 (probably GCN2.0). I haven’t tested this on Manjaro yet, but I’m planning to give it a shot and let you know what happens. Honestly, I’m not optimistic based on what I saw in Pop—just search for “AMD Hawaii Vulkan steam” and you’ll probably find similar problems. Maybe the 200 range is just a bad luck for Linux. Fingers crossed!
Most games using OpenGL don’t work well on AMD GPU even with Mesa enabled. You might be dealing with compatibility problems because Mesa isn’t widely recognized for supporting older OpenGL versions.
Hello ... Here are the findings. Initially, everything seemed correct, but after booting, I encountered black screens and no TTY2 functionality. If I disabled nomodeset, TTY2 became available. After removing the "blacklist radeon" and updating the initialization files, a GUI appeared, though Vulkan stopped working and games in Steam would crash with DX11 errors.
Earlier, I installed the latest Proton update. Two games—Supraland and Abzu—worked as expected, but another game, Sea of Thieves, required specific AMDGPU-pro drivers. After removing those drivers and rebooting with the default Mesa stack, the issue persisted.
I also tried clicking a link you provided, which helped me understand the problem better. The processes I captured show warnings before a black screen appeared, followed by a TTY2 boot after a reboot. Eventually, I removed the Radeon blacklist, updated the mkiniticpo, and rebooted successfully. Now I have a working desktop.
When checking Vulkaninfo, I encountered similar errors as with PopOS. It seems this GPU has significant issues on Linux. If I attempt to load Abzu or Supraland now, it won’t start at all. Any advice would be appreciated, or should I revisit the AMDGPU-pro wiki?
There seems to be an issue with editing or deleting those specific images.
It seems unclear what you're asking about. When you imported TKG's packages, they likely included everything needed for Mesa and Vanilla Arch Kernel, both with support turned on. The only possible issue might be AMDGPU not recognizing your card or a bug in the AMDGPU implementation. Unfortunately, I don't have a fix since you've already tried all other solutions. If this is true, AMDGPU-PRO could be the only viable path forward, though I can't advise on it.
Are you certain it isn't related to the secure-boot function in BIOS?
I hadn't considered that before; I'm uncertain whether it impacts the driver directly. The previous time I used an experimental card, it ran on an older system. Still, I'd assume if the Radeon driver recognizes it and loads properly, the newer AMDGPU driver should too. The biggest worry is that AMDGPU has been in experimental support for these cards for a long time, so I'm not completely confident they're being maintained.