Yet another "GUI won't start" issue

[Mangoist]

Apologies for expanding this family of problems, but here I am with this one. First, system specs:

Motherboard: ASUS X570-Plus
CPU: AMD Ryzen 7 3700X
GPU: MSI Radeon RX 5700
Debian build: 10.3

I installed by forcing UEFI mode, and the BIOS is set to boot UEFI only (CSM is on).

I have installed the non-free AMD drivers according to here: https://wiki.debian.org/AtiHowTo. I have not installed the proprietary drivers. I've also installed "firmware-linux" as suggested in other threads. I have chosen KDE as my display manager.

I can boot to console, but typing "startx" results in the following (extracted with "cat /var/log/Xorg.0.log | grep EE"):

Code: Select all

[  2266.695] (EE) open /dev/dri/card0: No such file or directory
[  2266.695] (EE) open /dev/dri/card0: No such file or directory
[  2266.695] (EE) Unable to find a valid framebuffer device
[  2266.695] (EE) Screen 0 deleted because of no matching config section.
[  2266.695] (EE) Screen 0 deleted because of no matching config section.
[  2266.695] (EE)
[  2266.696] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[  2266.696] (EE)

I've tried generating a xorg.conf file using "X -configure", but all I get is this:

Code: Select all

[  1771.338] (EE) Screen 0 deleted because of no matching config section.
[  1771.338] (EE) Screen 0 deleted because of no matching config section.
[  1771.338] (EE) Screen 0 deleted because of no matching config section.
[  1771.338] (EE) Screen 0 deleted because of no matching config section.
[  1771.338] (EE) Device(s) detected, but none match those in the config file.
[  1771.338] (EE)
[  1771.338] (EE) no screens found(EE)
[  1771.338] (EE)

However, when I had previously (and accidentally) installed Debian using BIOS compatibility mode instead of UEFI, I didn't have this problem (though I still had to start the display manager manually with "startx"). Instead, I was having the screen go black for seconds every minute or so, which proved irritating enough to make me reinstall.

Some other threads have mentioned hardware issues. At this point, I'm wondering if I should give up and get Kubuntu...

[Head_on_a_Stick]

CPU: AMD Ryzen 7 3700X
GPU: MSI Radeon RX 5700

3rd generation Ryzen is poorly supported by the stock Debian buster kernel and Debian doesn't have the Navi firmware required by that GPU, even in the unstable or experimental repositories.

You can try the newer kernel version from the buster-backports repository (see my [FAQ] guide in the HowTo section for details) and MX Linux's newer firmware package from here but that might not be enough because you'll still be using an old version of the xserver-xorg-video-amdgpu DDX driver.

I have installed the non-free AMD drivers

No you didn't, you installed the non-free firmware. But that won't support your card, as I have explained above.

I've tried generating a xorg.conf file using "X -configure"

That method is obsolete, don't use it.

I'm wondering if I should give up and get Kubuntu...

Nobody here gives a flying crap which operating system you use.

[Mangoist]

Thanks for the info. I'll see if there's something I can do with it.

I don't quite understand the hostility though.

[Head_on_a_Stick]

I don't quite understand the hostility though.

It's my nature, I'm a very grumpy individual. And your "threat" of switching to Kubuntu irked me.

[Mangoist]

Sorry, didn't mean it to come off that way. I'm just frustrated because I've been banging at this for weeks now.

[oswaldkelso]

I don't quite understand the hostility though.

It's my nature, I'm a very grumpy individual. And your "threat" of switching to Kubuntu irked me.

hoas. Get out your leather jacket, DA and say it

https://invidio.us/watch?v=fbMKjLe-RFA

[stevepusser]

It's been reported that this MX buster-based respin gets to a GUI with the AMD 5700 XT--you can try it in a live session and find out: https://archive.org/details/mx19x64updated

[Mangoist]

Just an update on this. I've gone ahead and installed Bullseye instead. It seems to have most of the firmware you need, except Navi. Apparently the Navi firmware is live on a particular repository: https://www.reddit.com/r/debian/comment ... n_testing/. Gonna report back once I try getting that going.

[Mangoist]

I finally got this working! I'll list out what I did to help others who might have a similar issue (starting point: Bullseye):

1. Make yourself part of the sudo group

• Add an IP address to the Ethernet port, since it won't have gone up automatically due to lack of firmware

• Install AMD drivers (see references) and "firmware-realtek" and "make"

• (Probably optional) Install "vulkan-tools vulkan-utils vulkan-validationlayers"

• Download the latest firmware blobs from the AMDGPU Git project: http://git.kernel.org/?p=linux/kernel/g ... rmware.git. You can download the GZ with "wget" and unzip it somewhere, or use the "git clone" command (I did the former)

• Install the blobs with "make install" (must be in the parent folder you got)

• (Optional) Setup Git folder to receive latest updates

• Create blacklist file with the line "blacklist radeon"

After a reboot I was all set. Hope this helps.

References:
ATI How To (for installing non-free drivers): https://wiki.debian.org/AtiHowTo
Using Git: https://wiki.debian.org/UsingGit
Kernel Mode Blacklisting: https://wiki.debian.org/KernelModuleBlacklisting
https://www.reddit.com/r/debian/comment ... n_testing/

[stevepusser]

Why do you think you needed a newer amdgpu driver in Bullseye? We already know that the Bullseye version works with the 5700 XT when backported to Buster.

[KoO]

I can tell you that with the 1.187mx19+1 firmware update running MX19 AHS my new RX5600 xt card works perfectly. Thanks Stevo

Linux mx-ahs 5.6.0-trunk-amd64 #1 SMP Debian 5.6.4-1~mx19+1 (2020-04-19) x86_64 GNU/Linux
/sys/class/hwmon/hwmon0 = amdgpu

Code: Select all

07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:731f] (rev ca)
	Subsystem: Sapphire Technology Limited Navi 10 [1da2:e411]
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

The same can be said for Debian Bullseye.. Thanks you so much Ubuntu

Linux debian 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux

Code: Select all

amdgpu-pci-0700
Adapter: PCI adapter
vddgfx:      775.00 mV 
fan1:           0 RPM  (min =    0 RPM, max = 3200 RPM)
edge:         +42.0°C  (crit = +118.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
junction:     +42.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
mem:          +44.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
power1:        9.00 W  (cap = 160.00 W)

Code: Select all

07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca)
	Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1da2:e411]
	Kernel driver in use: amdgpu           
	Kernel modules: amdgpu

[shaggyinjun]

The issue I faced and what worked for me.

• I wasn't able to connect to internet
  installing firmware-atheros_20200619-1_all.deb fixed this issue. I downloaded this file, put it inside the usb drive which had the installation image and then reinstalled debian. This allowed Debian installation to find the file while trying to configure the network.
  https://packages.debian.org/sid/all/fir ... s/download
• GUI won't start up.
  I upgraded kernel version to 5.7.0-1-amd64. The issue was fixed immediately and plasma started after a reboot. I am not sure what other side effects this may have, but for the moment Debian is up and running.
  
  https://wiki.debian.org/HowToUpgradeKernel

Laptop: ASUS Vivobook 15 X512D
CPU: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx

[stevepusser]

You don't have the same AMD GPU, but as noted in another thread here, Bullseye now has a snapshot of the firmware from April, and Sid just got one from June (and I'm backporting that to MX) which should be in Bullseye soon. Still nothing in buster-backports yet.