Slackware-current X.org crashes with RX 550

ganscs · 02-26-2021, 03:20 PM

I upgraded my GPU to a "new" RX 550. On 14.2 it sorta-kinda worked (if you call the vesa driver 'working'), so I upgraded to current thinking the amdgpu driver will surely work on it. I was half right. The kernel does load the amdgpu module in and does switch to fb console at boot, but I cannot for the love of god get Xorg to work. I tried to generate a new config file with

Quote:

Xorg :0 -configure

and use it but no luck.

Code:

[  3674.980] (EE) AMDGPU(0): eglGetDisplay() failed
[  3674.980] (EE) AMDGPU(0): glamor detected, failed to initialize EGL.
[  3674.980] (WW) AMDGPU(0): amdgpu_glamor_pre_init returned FALSE, using ShadowFB
[  3674.980] (II) Loading sub module "shadow"
[  3674.980] (II) LoadModule: "shadow"
 
[  3675.017] (II) Initializing extension XFree86-DRI
[  3675.017] (II) Initializing extension DRI2
[  3675.017] (II) AMDGPU(0): Setting screen physical size to 508 x 285
[  3675.165] (EE)
[  3675.165] (EE) Backtrace:
[  3675.166] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x135) [0x591655]
[  3675.166] (EE) 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f49be6e3400]
[  3675.167] (EE) 2: /lib64/libc.so.6 (gsignal+0x9b) [0x7f49be52dadb]
[  3675.167] (EE) 3: /lib64/libc.so.6 (abort+0x102) [0x7f49be514526]
[  3675.168] (EE) 4: /lib64/libc.so.6 (__assert_fail_base.cold+0xf) [0x7f49be51441f]
[  3675.168] (EE) 5: /lib64/libc.so.6 (__assert_fail+0x42) [0x7f49be525492]
[  3675.169] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3675.169] (EE) 6: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f49bdf9bf13]
[  3675.169] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3675.169] (EE) 7: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f49bdf9c211]
[  3675.169] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3675.169] (EE) 8: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f49bdfa7c3d]
[  3675.170] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3675.170] (EE) 9: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f49bdfa9c6a]
[  3675.170] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3675.170] (EE) 10: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f49bdfab8f7]
[  3675.170] (EE) 11: /usr/libexec/Xorg (MapWindow+0x214) [0x46ab14]
[  3675.170] (EE) 12: /usr/libexec/Xorg (InitFonts+0x345) [0x443a95]
[  3675.171] (EE) 13: /lib64/libc.so.6 (__libc_start_main+0xcd) [0x7f49be5161ad]
[  3675.171] (EE) 14: /usr/libexec/Xorg (_start+0x2a) [0x42e18a]
[  3675.171] (EE)
[  3675.171] (EE)
Fatal server error:
[  3675.171] (EE) Caught signal 6 (Aborted). Server aborting
[  3675.171] (EE)
[  3675.171] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  3675.171] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  3675.171] (EE)
[  3675.247] (EE) Server terminated with error (1). Closing log file.

biker_rat · 02-26-2021, 09:26 PM

Did you use a kernel not compiled to glibc on your system?. Upgrade everything to latest current. And, then:
Erase any xorg.conf and/or anything in xorg.conf.d & erase any .drirc file in ~/. It should just work. If it doesn't try this xorg.conf below:

Section "Device"
Identifier "RX550"
Driver "amdgpu"
EndSection

If that doesn't work slackpkg update & slackpkg reinstall x (as root)

If that doesn't work. Substitute "modesetting" for "amdgpu" in above sample xorg.conf

bassmadrigal · 02-26-2021, 09:59 PM

Did you actually upgrade, like upgrade all the packages using either upgradepkg or slackpkg? Or was it a fresh install of -current?

ganscs · 02-26-2021, 10:44 PM

Quote:

Originally Posted by bassmadrigal

Did you actually upgrade, like upgrade all the packages using either upgradepkg or slackpkg? Or was it a fresh install of -current?

It was an upgrade with slackpkg. And since literally everything else is working I'd say I didn't screw up. Also, I think somebody is taking me for a fool.
Now for the poster above you: modesetting line instead of amdgpu did work, and X started, so for a workaround until I somehow get amdgpu working it's good I guess.

biker_rat · 02-27-2021, 04:30 AM

Those error messages are smoke & if there is smoke you should at least check for fire. Did you run slackpkg install-new & slackpkg clean-system when you upgraded using slackpkg? Everything on the ncurses list that says it came from slackware64 repo after you run slackpkg clean-system must be removed (at a minimum). Also run uname -r and verify you are booting the kernel version that you believe you are booting (if you use startx you could just note the kernel version just above your login prompt). No one is taking you for a fool. There are a lot of changes in slackware current in the past months & upgrading has not been as simple and smooth as normal during that period.

ganscs · 02-27-2021, 04:38 AM

Quote:

Originally Posted by biker_rat

Those error messages are smoke & if there is smoke you should at least check for fire. Did you run slackpkg install-new & slackpkg clean-system when you upgraded using slackpkg? Everything on the ncurses list that says it came from slackware64 repo after you run slackpkg clean-system must be removed (at a minimum). Also run uname -r and verify you are booting the kernel version that you believe you are booting (if you use startx you could just note the kernel version just above your login prompt). No one is taking you for a fool. There are a lot of changes in slackware current in the past months & upgrading has not been as simple and smooth as normal during that period.

I did everything by the book, I did my RTFM part thank you very much. I also tried the testing 5.11.1 kernel. Meanwhile my google-fu yielded a suspiciously similar problem https://forums.gentoo.org/viewtopic-...8-start-0.html here, where the solution was to rebuild mesa with some extra flags. At that point I said nope, I'm not doing that, I'm way past the age where I found tinkering with stuff fun, so thank you very much for trying to help but I'm not going to bother with current for now.

bassmadrigal · 02-27-2021, 11:30 AM

Quote:

Originally Posted by ganscs

It was an upgrade with slackpkg. And since literally everything else is working I'd say I didn't screw up. Also, I think somebody is taking me for a fool.
Now for the poster above you: modesetting line instead of amdgpu did work, and X started, so for a workaround until I somehow get amdgpu working it's good I guess.

I was just trying to get clarification. A lot of people say they "upgraded" by installing fresh (you said you "upgraded" your GPU by removing the old one and installing a new one), so I wanted to make sure we knew what we were dealing with. Don't take offense or assume someone is "taking me for a fool" just with some questioning on a forum. If you're quick to jump to things like that, it may make people not as likely to help you.

Your issue is the first I remember seeing of this on the forum, so even though you might've done the upgrade "by the book" (X issues in -current seem to be mostly tied to Intel hardware), it could still be an issue that isn't present on a fresh install.

Would you be willing to try using Slackware Live and see if the issue is present there?

ganscs · 02-27-2021, 11:35 AM

Quote:

Originally Posted by bassmadrigal

I was just trying to get clarification. A lot of people say they "upgraded" by installing fresh (you said you "upgraded" your GPU by removing the old one and installing a new one), so I wanted to make sure we knew what we were dealing with. Don't take offense or assume someone is "taking me for a fool" just with some questioning on a forum. If you're quick to jump to things like that, it may make people not as likely to help you.

Your issue is the first I remember seeing of this on the forum, so even though you might've done the upgrade "by the book" (X issues in -current seem to be mostly tied to Intel hardware), it could still be an issue that isn't present on a fresh install.

Would you be willing to try using Slackware Live and see if the issue is present there?

Will do the live but not today. Will report back.

ganscs · 03-06-2021, 04:02 AM

Quote:

Originally Posted by bassmadrigal

I was just trying to get clarification. A lot of people say they "upgraded" by installing fresh (you said you "upgraded" your GPU by removing the old one and installing a new one), so I wanted to make sure we knew what we were dealing with. Don't take offense or assume someone is "taking me for a fool" just with some questioning on a forum. If you're quick to jump to things like that, it may make people not as likely to help you.

Your issue is the first I remember seeing of this on the forum, so even though you might've done the upgrade "by the book" (X issues in -current seem to be mostly tied to Intel hardware), it could still be an issue that isn't present on a fresh install.

Would you be willing to try using Slackware Live and see if the issue is present there?

Although a bit late, I gladly report the issue is NOT present using Slackware Live. In hindsight I should have also tried the generic kernel instead of the huge kernel I've always been using but hindsight is 20/20 as they say.