Stuck on "Reached target Graphical Interface" on AMD RX 6800

Support Graphics & Display
1

Firstly, Hello!

I’ve been using Manjaro for a good while now and it’s been the cleanest Linux experience I’ve had so far. However, after upgrading my hardware recently (Swapping away from an Intel + Nvidia build to purely AMD) and working yesterday, today I am stuck on boot as the title mentions. I have tried solutions from various other threads to no avail.

I have uninstalled the old Nvidia drivers, I have cleaned up my X11 config. I’d appreciate any ideas you might have.

I should also mention that booting into Windows still works fine, so I doubt the graphics card is to blame.

2

Hullo,
Can you get to TTY, runlevel3, or otherwise interact with the system?

Once there I guess we could have a look at

mhwd -l -li
inxi -Fazy

( you can also use pastebin services like here:
[HowTo] use public command-line pastebin services without installing anything! )

3

Output of inxi: https://paste.c-net.org/DeadlineAdamant

mhwd:
https://paste.c-net.org/CindyArrests

4

Huh. It appears you have 2 AMD cards:

Graphics:
  Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: ASRock
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-1,DP-2 empty: DP-3,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:73bf
    class-ID: 0300
  Device-2: AMD Raphael vendor: Gigabyte driver: N/A arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 17:00.0 chip-ID: 1002:164e class-ID: 0300
  Display: server: X.org v: 1.21.1.8 driver: X: loaded: radeon

And for whatever reason the ‘active’ one is using the old ‘radeon’ instead of amdgpu.

Kernel: 5.15.122-1-MANJARO

You probably want to use a newer kernel … 6.1+ ?

sudo mhwd-kernel -i linux61
5

Ah that’s most likely the onboard GPU, would Manjaro prefer that one by default? Also, you’re right, I should probably run a kernel update at some point.

6

New hardware … new kernel … If I were you I’d make the jump, check 6.1 is OK, then keep that in the pocket while removing everything older and testing 6.4+

Its possible some hardware stuff ‘clicks’ with the newer kernel.
Id have to check the cards particularly … but being from 2020 I rather assume they should be amdgpu ready.

1 Like
7

I am going to assume that you have your display plugged into the RX6800, what happens if you plug it into the Motherboard?

8

We have been seeing a few topics lately with newer AMD cards RX6xxx and up.

It appears the remedy for issue with those is to use the latest stable kernel - which is Linux 6.4

9

That’s good to know. I wasn’t at my machine yesterday, but I will be trying this fix later.

10

If the issue has not been resolved, I just remembered something, check ;

/etc/mkinitcpio.conf

and verify that “amdgpu” is in the MODULES list

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES="amdgpu"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries

Besure to remove any nvidia modules no longer being used.
Then run:

sudo mkinitcpio -P

Reboot

11

I believe I have my answer, it’s nothing Kernel or Driver related… A 20 year old monitor seems to have been causing it. The PC boots fine without it, it can display on it just fine if it’s connected after boot, but when it’s booting WITH it the issues begin. Thus, I’ll just replace this piece of trash I’ve only been using as a terminal and will move on. Thank you all for helping.

12

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