Black Screen on Boot, new AMD GPU

Made a new install. I can’t boot into either the live USB or the actual installation I made without using nomodeset as a kernel parameter to avoid an unresponsive black screen. I’ve tried updating my system while in this mode to get the required drivers, but no luck.
I am using a RX6700.

Hi Snowkbs

I am also new to Linux but I will try to get any information that may help, even is someone else more experienced than me can use it.

If you have access to the terminal is it possible to get the results and post for us. It just gives us an idea of the hardware and how the system is set up.

inxi -Fxxc0z

Just to clarify when you say new install, was this a new install as in the OS was installed fresh while the new GPU was inserted? If not then was a different GPU installed prior to this new AMD GPU, which one was it? I’m just making sure as the title says new GPU but the message says new Install so I’m just making sure.

I was wondering because usually the graphics drivers for AMD a part of Linux install from what I’m aware and Odd the Live USB would also have this issue unless there is something in the BIOS causing this.

Before commenting this, I just updated my BIOS, it did not fix the problem.
It is a fresh install on a brand new SSD, and has no Nvidia drivers.

This is the output of the inxi:

System:
  Kernel: 6.10.3-arch1-2 arch: x86_64 bits: 64
    compiler: gcc v: 14.2.1
  Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A
    wm: kwin_x11 dm: SDDM Distro: EndeavourOS
    base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: B560M PRO-VDH
    WIFI (MS-7D18) v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: 1.90
    date: 07/06/2024
CPU:
  Info: 6-core model: Intel Core i5-10400F bits: 64
    type: MT MCP arch: Comet Lake rev: 5 cache: L1: 384 KiB
    L2: 1.5 MiB L3: 12 MiB
  Speed (MHz): avg: 800 min/max: 800/4300 cores: 1: 800
    2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800
    10: 800 11: 800 12: 800 bogomips: 69629
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1
    sse4_2 ssse3 vmx
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT /
    6800M/6850M XT] vendor: XFX driver: N/A arch: RDNA-2
    pcie: speed: 16 GT/s lanes: 16 bus-ID: 03:00.0
    chip-ID: 1002:73df
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland
    v: 24.1.2 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: radeon
    alternate: fbdev,vesa 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
    size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: swrast
    surfaceless: drv: swrast x11: drv: swrast
    inactive: gbm,wayland
  API: OpenGL v: 4.5 vendor: mesa v: 24.1.5-arch1.1
    glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM
    18.1.8 256 bits) device-ID: ffffffff:ffffffff
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: Intel vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
    chip-ID: 8086:f0c8
  Device-2: AMD Navi 21/23 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
  API: ALSA v: k6.10.3-arch1-2 status: kernel-api
  Server-1: PipeWire v: 1.2.2 status: active with:
    1: pipewire-pulse status: active 2: wireplumber
    status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi
    v: kernel bus-ID: 00:14.3 chip-ID: 8086:43f0
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 05:00.0
    chip-ID: 10ec:8125
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    bus-ID: 1-14:8 chip-ID: 8087:0026
  Report: btmgmt ID: hci0 rfk-id: 0 state: down
    bt-service: disabled rfk-block: hardware: no
    software: no address: N/A
Drives:
  Local Storage: total: 953.87 GiB used: 9.49 GiB (1.0%)
  ID-1: /dev/nvme0n1 vendor: TeamGroup model: TM8FP6001T
    size: 953.87 GiB speed: 31.6 Gb/s lanes: 4
    serial: <filter> temp: 44.9 C
Partition:
  ID-1: / size: 936.82 GiB used: 9.39 GiB (1.0%) fs: ext4
    dev: /dev/dm-0
    mapped: luks-b31a69ea-86bd-4659-9af2-07ff9da839b7
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 55.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 24 GiB available: 23.37 GiB
    used: 1.91 GiB (8.2%)
  Processes: 283 Power: uptime: 0m wakeups: 0
    Init: systemd v: 256 default: graphical
  Packages: pm: pacman pkgs: 1051 Compilers: gcc: 14.2.1
    Shell: Bash v: 5.2.32 running-in: konsole inxi: 3.3.35

I will mention that I had to do an offline install as calamares/the installer program would get stuck at 13% with the online install, like another user I found with the same problem. I updated upon booting the system immediately ofc.

What do you mean with “unresponsive black screen”? What part of the boot process doesn’t work? This looks like a failure to load the login manager for some reason, but i have no information to confirm that.
If you press ctrl-alt-f3 in the black screen, does it bring you to tty?
If so, does journalctl -b -u *loginmanager*.service tells you any error?

If ctrl-alt-f3 does not work, boot with nomodeset and use journalctl -b -1, this will be useful only if last time you booted you got a black screen.

Pipe either command with journalctl *** | eos-sendlog and post it here

Sorry, maybe i was not precise enough.

Your login manager is sddm, so the command should be journalctl -b -u sddm.service | eos-sendlog. Again, do this if you manage to access to tty, otherwise, boot to the black screen and then the next boot (with nomoedset) do journalctl -b -1 | eos-sendlog. This will produce a link in the terminal that you have to copypaste here, so that it is easier to read for whoever stumbles on this post. That link will contain all the info outputted by journalctl, so don’t copy them again here

1 Like

I am um. Flabbergasted rn. I do not understand what just happened.
I did the ctrl-alt-f3, but instead of bringing a command line, it flashed the underscore for one second and then I got the login page with my drivers 100% working.

lspci -k | grep -A 3 -E "(VGA|3D)"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (rev c5)
        Subsystem: XFX Limited Device 6606
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
1 Like

Was your iGPU disabled in BIOS? Or maybe it was set to primary? What I presume happened was the iGPU was still set as the display/screen, but you didn’t have any cable connected to the output on the motherboard. Linux thought there was no screen. Then ctr-alt-F3 triggered an display/screen reset and the correct output/display/gpu was selected and driver loaded.

I do not believe the i5-10400f has an integrated GPU.
What I believe caused the change was tinkering around with the HDMI cable a bunch while I was on screen in nomodeset mode and then restarting. That’s really the only explanation I’ve got. And then what you mentioned about the ctrl-alt-f3.
Good luck to anyone with my problem in the future because I honestly don’t know exactly what did it.

The F models have no iGPU.
… Was your monitor connected to the dGPU? Just to be sure, since you mentioned fiddling with the cable

It was, but I saw on another post about how these ports can be very finicky so I decided to make sure just in case.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.