[SOLVED] Unable to start xwindows with Radeon RX480
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just upgraded my box with a Radeon RX480 card and I have not been able to start KDM. I think the drivers are installed ok (I've used the Ubuntu link from https://www.amd.com/es/support/previ.../radeon-rx-480). The card works in Windows. The monitor is a LG 24MP400.
When the computer boots it stalls starting the session manager. If I try the autogenerated file the screen goes black and I have to reboot the computer with the botton.
uname -a
Code:
Linux bossanova 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux
[ 12.164] (--) Log file renamed from "/var/log/Xorg.pid-1486.log" to "/var/log/Xorg.0.log"
[ 12.166]
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[ 12.166] Build Operating System: linux Debian
[ 12.166] Current Operating System: Linux bossanova 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64
[ 12.166] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-amd64 root=UUID=5185e8cd-a162-40ff-936f-05e397587222 ro quiet
[ 12.166] Build Date: 16 December 2021 05:08:23PM
[ 12.166] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support)
[ 12.166] Current version of pixman: 0.40.0
[ 12.166] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 12.166] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 12.166] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 11 11:13:57 2022
[ 12.170] (==) Using config file: "/etc/X11/xorg.conf"
[ 12.170] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 12.172] Data incomplete in file /etc/X11/xorg.conf
Undefined Screen "Screen1" referenced by ServerLayout "X.org Configured".
[ 12.172] (EE) Problem parsing the config file
[ 12.172] (EE) Error parsing the config file
[ 12.172] (EE)
Fatal server error:
[ 12.172] (EE) no screens found(EE)
[ 12.172] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 12.172] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 12.172] (EE)
[ 12.172] (EE) Server terminated with error (1). Closing log file.
Thank you so much for your time.
Last edited by bocabits; 05-12-2022 at 03:19 AM.
Reason: Solved
again, your generated conf file is incorrect. That's why it is stopped:
Code:
[ 12.172] Data incomplete in file /etc/X11/xorg.conf
Undefined Screen "Screen1" referenced by ServerLayout "X.org Configured".
[ 12.172] (EE) Problem parsing the config file
[ 12.172] (EE) Error parsing the config file
Just remove that file and try to boot and start X again. Probably it will just work without that.
From the other hand you need to post the mentioned log file (after fixing or removing that conf file).
I have just upgraded my box with a Radeon RX480 card and I have not been able to start KDM.
Upgraded from what? Are xserver-xorg-video-amdgpu and firmware-amd-graphics installed? If they are installed, and /etc/X11/xorg.conf does not exist, and there is no residue from having had NVidia drivers installed and incompletely purged, X should just work automatically.
My motherboard crashed so I replaced it with an ASUS Prime B550MK but kept most of my components including the Radeon RX 400 graphic controller. I've installed Debian 11 and I can't get KDM to start. When the system boots, the screen remains black with a cursor blinking on the left upper corner.
I have installed the official driver from ATI and get this message
Code:
Obj:1 http://security.debian.org/debian-security bullseye-security InRelease
Obj:2 http://deb.debian.org/debian bullseye InRelease
Obj:3 http://deb.debian.org/debian bullseye-updates InRelease
Obj:4 https://packages.microsoft.com/repos/edge stable InRelease
Des:5 https://repo.radeon.com/amdgpu/5.4.3/ubuntu focal InRelease [5.457 B]
Des:6 https://repo.radeon.com/rocm/apt/5.4.3 focal InRelease [2.603 B]
Des:7 https://repo.radeon.com/amdgpu/5.4.3/ubuntu focal/main amd64 Packages [13,5 kB]
Des:8 https://repo.radeon.com/rocm/apt/5.4.3 focal/main amd64 Packages [31,9 kB]
Descargados 53,4 kB en 2s (32,9 kB/s)
Leyendo lista de paquetes...
Leyendo lista de paquetes...
Creando árbol de dependencias...
Leyendo la información de estado...
No se pudieron instalar algunos paquetes. Esto puede significar que
usted pidió una situación imposible o, si está usando la distribución
inestable, que algunos paquetes necesarios aún no se han creado o se
han sacado de «Incoming».
La siguiente información puede ayudar a resolver la situación:
Los siguientes paquetes tienen dependencias incumplidas:
amdgpu-lib32 : Depende: libdrm2-amdgpu:i386 pero no es instalable
Depende: libdrm-amdgpu-amdgpu1:i386 pero no es instalable
Depende: libllvm-amdgpu:i386 pero no es instalable
Depende: libwayland-amdgpu-client0:i386 pero no es instalable o
libwayland-client0:i386 pero no es instalable
Depende: libwayland-amdgpu-server0:i386 pero no es instalable o
libwayland-server0:i386 pero no es instalable
Depende: libwayland-amdgpu-egl1:i386 pero no es instalable o
libwayland-egl1:i386 pero no es instalable
Depende: libxatracker2-amdgpu:i386 pero no es instalable
Depende: libgbm1-amdgpu:i386 pero no es instalable
Depende: libegl1-amdgpu-mesa:i386 pero no es instalable
Depende: libegl1-amdgpu-mesa-drivers:i386 pero no es instalable
Depende: libglapi-amdgpu-mesa:i386 pero no es instalable
Depende: libgl1-amdgpu-mesa-glx:i386 pero no es instalable
Depende: libgl1-amdgpu-mesa-dri:i386 pero no es instalable
Depende: mesa-amdgpu-va-drivers:i386 pero no es instalable
Depende: mesa-amdgpu-vdpau-drivers:i386 pero no es instalable
rocm-llvm : Depende: libstdc++-5-dev pero no es instalable o
libstdc++-7-dev pero no es instalable o
libstdc++-11-dev pero no es instalable
Depende: libgcc-5-dev pero no es instalable o
libgcc-7-dev pero no es instalable o
libgcc-11-dev pero no es instalable
If you hadn't installed proprietary software you shouldn't need, I would have suggested after your cursor has been on black screen a minute or more, from a vtty login prompt, instead of startx, try systemctl restart gdm.
AMD does a really good job of making the drivers in standard distro repos work well, but sometimes cmdline options are required as workarounds for known issues.
GDM is the worst possible choice for getting Plasma to work. Plasma really isn't ready for Wayland yet. Try LightDM, SDDM, XDM or TDM instead of GDM for running KDE, and for an X11 session, not Wayland, and purge the non-standard drivers. For some use cases they are an upgrade from working drivers, but they are not a replacement for non-working drivers, as are NVidia's.
https://wiki.archlinux.org/title/SDDM
(this is a bit offtopic here)
That is an interesting issue, gdm for gnome and kdm for kde, and that was an obvious choice long time ago. They're still not interchangeable these days, but in theory they should be. LightDM is a good choice too.
Personally, I always try to simplify things: try getting xorg to run first and don't put a display manager in the mix until you successfully get xorg running.
I have reinstalled debian and KDE (from the debian installer). No ATI official driver this time. Apparently sddm works fine, but I get no login screen and have to open a console and run startx to get KDE.
Code:
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-03-24 17:03:43 CET; 4min 55s ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 697 (sddm)
Tasks: 2 (limit: 9223)
Memory: 12.8M
CPU: 13ms
CGroup: /system.slice/sddm.service
└─697 /usr/bin/sddm
mar 24 17:03:43 bossanova systemd[1]: Started Simple Desktop Display Manager.
mar 24 17:03:43 bossanova sddm[697]: Initializing...
mar 24 17:03:43 bossanova sddm[697]: Starting...
mar 24 17:03:43 bossanova sddm[697]: Logind interface found
# xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 76.00*
# xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 76.00*
To find out why we need to see Xorg.0.log pastebin'd (pastebinit /var/log/Xorg.0.log) and input/output from inxi -Gaz run from within Konsole, after first removing B_ALLOW_UPDATE=false from /etc/inxi.conf and then running inxi -U as root or with sudo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.