SlackwareThis Forum is for the discussion of Slackware 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.
Hey, I've been following the beginners guide for my Slackware 14.2 install, and I'm working on the display configuration part, but I've run into some trouble and I need your help. For my hardware, I'm using an amd APU (ryzen 3 2200g) with no graphics card attached. I'm also doing an EFI setup with ELILO and the huge kernel (if that matters). I have not fully upgraded my slackpkg stuff yet, and I've chosen XFCE for my desktop environment.
The guide says to use either:
Code:
# X -configure
or
# xorgconfig
X -configure works ok for my single monitor when I "startx"; xorgconfig does not seem to be installed by default. My second monitor is undetected, according to my xrandr -q command. I checked out the xorg.conf man pages as well as the Multihead article on the arch wiki in order to write my own config file. Right now I have 2 files in my /etc/X11/xorg.conf.d/
The server fails on the device section, and I'm not sure how to continue. I've made sure that the xf86-video-amdgpu-1.1.0-x86_64-1.txz package is installed. Changing the driver back to "vesa" will start the server again, but it's the same result as the "X -configure" option. Is there something I'm missing?
Here is the modified .conf file I created based on what you sent me mrmazda, but I'm getting the same error I got before. Vesa is working, and xrandr -q shows the same "default" monitor connection. Also, I don't have a GPU connected; I'm using an APU and the onboard ports from my mobo.
That correlates to my comment in the first thread "The log reports no devices detected". I don't know what's missing that prevents any devices from being detected. What does
Code:
inxi -Gxx
report? Are there any clues to detection failure in the journal or dmesg?
Well, I did some more reading and figured I might need an LLVM of 5.0 or greater and Mesa of 18.0 or more for best compatibility with the 2200g APU I'm using. My slackware-14.2 inxi command was showing older versions of these, so, I installed slackware-current, but, it looks like these packages haven't changed since.
The chip ID according to pci-ids.ucw.cz is a Raven Ridge series APU, but it doesn't identify the actual model. The next line reports the (prescribed) amdgpu driver is neither in use nor available. Is package xf86-video-amdgpu actually installed? For server 1.18.3 you're probably on the right track about newness being an issue. It may be the primary or only issue, since 1.18.3 is more than 30 months old. Before deciding newness is a complete blocker, you might give the modesetting driver a try, but it looks to me like you're going to need a more thorough upgrade to current, which according to PACKAGES.TXT has 1.20.3.
I messed around with the modesetting driver a little bit, but I ended up doing a full upgrade instead. I double checked and, yes, the amdgpu driver package was installed. My command results and log errors are slightly different now, though, and the device section is being detected. I guess that is (some) progress.
inxi output while in the tty thing (before doing the default/vesa startx):
Code:
bash-4.4# inxi -Gxx
Graphics:
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
vendor: Micro-Star MSI driver: N/A bus ID: 38:00.0 chip ID: 1002:15dd
Display: server: X.Org 1.20.3 driver: none
unloaded: amdgpu alternate: fbdev resolution: 1920x1080~N/A
"Advanced Graphics aren't available while in the tty thing" (or something like that)
Xorg.0.log (I copied just the amdgpu part)
Code:
[ 9020.298] (II) LoadModule: "amdgpu"
[ 9020.298] (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
[ 9020.299] (II) Module amdgpu: vendor="X.Org Foundation"
[ 9020.299] compiled for 1.20.1, module version = 18.1.0
[ 9020.299] Module class: X.Org Video Driver
[ 9020.299] ABI class: X.Org Video Driver, version 24.0
[ 9020.299] (II) AMDGPU: Driver for AMD Radeon:
All GPUs supported by the amdgpu kernel driver
[ 9020.299] (--) using VT number 7
[ 9020.300] (II) AMDGPU(0): [KMS] drm report modesetting isn't supported.
[ 9020.300] (II) AMDGPU(1): [KMS] drm report modesetting isn't supported.
[ 9020.300] (EE) Screen 0 deleted because of no matching config section.
[ 9020.300] (II) UnloadModule: "amdgpu"
[ 9020.300] (EE) Screen 0 deleted because of no matching config section.
[ 9020.300] (II) UnloadModule: "amdgpu"
[ 9020.300] (EE) Device(s) detected, but none match those in the config file.
[ 9020.300] (EE)
Fatal server error:
[ 9020.300] (EE) no screens found(EE)
[ 9020.300] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 9020.300] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 9020.300] (EE)
[ 9020.306] (EE) Server terminated with error (1). Closing log file.
I changed my .conf files, but I'm still trying to figure out this "config section" thing.
When i try to find out a problem i like to do it methodically so maybe this will help you too:
- assume the CPU is OK
- next: Motherboard -> is there any setting in BIOS in relation to video output, maybe you have to enable some settings to get the secondary output enabled
- next: Monitor + cable -> is your monitor and cables in good working order (connected, powered on,etc)
- next: OS does your OS detect the monitor/video device, etc...
- next: configuration is the detected device(s) configured correctly?
So since your monitor is not detected correctly, i would go ahead and check the bios settings first (assuming your external monitor and cable is all good).
Well, I did some more reading and figured I might need an LLVM of 5.0 or greater and Mesa of 18.0 or more for best compatibility with the 2200g APU I'm using. My slackware-14.2 inxi command was showing older versions of these, so, I installed slackware-current, but, it looks like these packages haven't changed since.
If they didn't change, then I don't believe you successfully upgraded to -current. Both have been continually updated during -current's development process. LLVM was upgraded to v7.0 back in Sep 2018 and mesa was upgraded to v18.2.5 almost 2 weeks ago.
But you definitely need to be running -current to properly support Ryzen APUs. As you found, 14.2 is just too old to support them.
If they didn't change, then I don't believe you successfully upgraded to -current. Both have been continually updated during -current's development process. LLVM was upgraded to v7.0 back in Sep 2018 and mesa was upgraded to v18.2.5 almost 2 weeks ago.
Yes, my mistake bass, I had -current installed, but didn't do a full slack upgrade yet when I posted. Once upgraded, I was getting the correct output you are talking about (using the basic vesa driver to get the OpenGL stuff):
I'll mess around with the modesetting some more to see if I can get something going; if I can't, then it's not really a big deal. Do people ever just stick with the base terminal for stuff? I'm only going to be reading about slackpkg things for now and maybe a basic server setup. Mostly I just wanted to get a base system going before I continued.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.