LinuxQuestions.org - [SOLVED] Slackware multi monitor config

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware multi monitor config (https://www.linuxquestions.org/questions/slackware-14/slackware-multi-monitor-config-4175643001/)

The existence of /dev/dri/card0 does not depend on presence of a APU/GPU device in a card slot.

You shouldn't have to point anything anywhere to use the X modesetting driver. I use the modesetting driver for most gfx hardware here, and I've never before heard of, much less used or needed, the kmsdev option. If the gfx hardware is supported by the kernel's modesetting functionality, and nothing is preventing its use (e.g. nomodeset on kernel cmdline, or blacklisting), /dev/dri/card0 should exist. When it does, and no configuration option specifies otherwise, and no card-specific X video driver is available (e.g. amdgpu, radeon), and absent a bug, the X server's integrated modesetting driver will be used.

Possibly your reinstallation has failed to include required components. What do the commands I used for comments 11 & 14 report?

Code:

bash-4.4# uname -a

Linux pallaria.localhost 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64 AMD Ryzen 3 2200G with Radeon Vega Graphics AuthenticAMD GNU/Linux



(inxi while on XFCE with the vesa/default driver)

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: amdgpu,apm,ark,ati,chips,cirrus,glint,i128,i740,intel,mach64,mga,modesetting,neomagic,nouveau,nv,openchrome,radeon,rendition,s3,s3virge,savage,siliconmotion,sis,sisusb,tdfx,tga,trident,tseng,v4l,vboxvideo,vesa,vmware,voodoo 

  resolution: 1920x1080~N/A 

  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.2.6 

  compat-v: 3.1 direct render: Yes 



(XFCE/vesa)

bash-4.4# xrandr --listproviders

Providers: number : 0



(the xorg conf i'm trying to get working)

bash-4.4# cat /etc/X11/xorg.conf.bkp

Section "Device"

        Identifier "AMD"

        Driver "modesetting"

EndSection



Section "Monitor"

        Identifier "ddvi"

        Option "Primary" "true"

        Option "PreferredMode" "1920x1080"

EndSection



Section "Screen"

        Identifier "screenRight"

        Device "AMD"

        Monitor "ddvi"

EndSection



(XFCE/vesa)

bash-4.4# xrandr

xrandr: Failed to get size of gamma for output default

Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080

default connected 1920x1080+0+0 0mm x 0mm

  1920x1080      0.00* 

  640x480        0.00

It looks like you have in incomplete upgrade to -current, or at the very least, you're still booting the old kernel since you're running the 4.4 kernel and -current includes the 4.19 kernel.

What is your bootloader? If it is lilo, you need to ensure you have the 4.19 kernel packages installed and then run lilo to write it to the MBR. If you're using elilo, you'll need to run eliloconfig (after ensuring your kernel packages are upgraded) so it can copy the kernel over to the right directory.

yeah...I've been blacklisting the kernel because in previous installs it killed my keyboard input @ the tty login (I tried a few diff kb's too). I also tried downloading the 4.19.6 kernel separately to do a build myself and add it to elilo conf, but I couldn't get it to boot. So, I went ahead and un-blacklisted/upgraded all to see if maybe the new BIOS version would help the keyboard work. Unfortunately, it didn't.

I dunno, I've heard somewhere that ps/2 ports may work in cases where usb's aren't picked up. I could try that. It's weird though because the login is still showing as kernel 4.4.14

Quote:

Originally Posted by jpallaria (Post 5932414)

I dunno, I've heard somewhere that ps/2 ports may work in cases where usb's aren't picked up. I could try that. It's weird though because the login is still showing as kernel 4.4.14

This means it is still booting the 4.4 kernel and the reason your keyboard doesn't work is the system can no longer find the 4.4 modules (since they were replaced with the 4.19 modules).

What steps are you taking to upgrade the kernel?

Also, if you have no problems wiping, you may want to just use Alien Bob's -current installer rather than installing 14.2 and then trying to upgrade.

http://bear.alienbase.nl/mirrors/sla...4-current-iso/

Ok, the step missing was the elilo reinstall with eliloconfig after upgrading, but before reboot. I was under the impression that elilo will update itself automatically once you reboot.

Here are the steps I did:
- slackpkg update/install-new/upgrade-all (I upgraded slackpkg first before doing everything else)
- eliloconfig
- reboot

Now I'm on 4.19.6, and it's working. Both modesetting and amdgpu devices will launch with X, and multihead seems to be working. Here are some of my outputs for things:

Code:

bash-4.4# inxi -Gxx

Graphics:

  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] 

  vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: 38:00.0 chip ID: 1002:15dd 

  Display: server: X.Org 1.20.3 driver: amdgpu resolution: 1920x1080~60Hz 

  OpenGL: renderer: AMD RAVEN (DRM 3.27.0 4.19.6 LLVM 7.0.0) v: 4.5 Mesa 18.2.6 

  compat-v: 4.4 direct render: Yes

 

bash-4.4# xrandr --listproviders

Providers: number : 1

Provider 0: id: 0x57 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 4 associated providers: 0 name:Unknown AMD Radeon GPU @ pci:0000:38:00.0



bash-4.4# xrandr -q

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384

HDMI-A-0 disconnected (normal left inverted right x axis y axis)

DisplayPort-0 disconnected (normal left inverted right x axis y axis)

DVI-D-0 disconnected (normal left inverted right x axis y axis)

HDMI-A-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm

  1920x1080    60.00*+

  1600x1200    60.00  

  1680x1050    59.88  

  1280x1024    75.02    60.02  

  1440x900      59.90  

  1280x960      60.00  

  1280x800      60.00  

  1152x864      75.00  

  1280x720      60.00  

  1024x768      75.03    70.07    60.00  

  832x624      74.55  

  800x600      72.19    75.00    60.32    56.25  

  640x480      75.00    72.81    66.67    59.94  

  720x400      70.08  



bash-4.4# cat /etc/X11/xorg.conf

Section "Device"

        Identifier "AMD"

        Driver "amdgpu"

EndSection



Section "Monitor"

        Identifier "ddvi"

        Option "Primary" "true"

        Option "DPMS" "off"

        Option "PreferredMode" "1920x1080"

EndSection



Section "Screen"

        Identifier "ScreenLeft"

        Device "AMD"

        Monitor "ddvi"

EndSection



bash-4.4# uname -a

Linux box2.localhost 4.19.6 #1 SMP Sat Dec 1 17:38:04 CST 2018 x86_64 AMD Ryzen 3 2200G with Radeon Vega Graphics AuthenticAMD GNU/Linux

Only weirdness I'm seeing is, my xrandr shows the DVI port as HDMI-A-1 instead of DVI-D-0. The HDMI port uses HDMI-A-0. They both work fine, it was just something I noticed. Besides that, I would say my problem is solved. Thank you for helping me.

Quote:

Originally Posted by jpallaria (Post 5932671)

Ok, the step missing was the elilo reinstall with eliloconfig after upgrading, but before reboot. I was under the impression that elilo will update itself automatically once you reboot.

As long as the kernel gets updated in the EFI partition, you don't need to run anything to "save" it like you do with lilo. The problem is the kernel package stores the kernels in /boot/, so you would need to move or copy the kernel to /boot/efi/EFI/Slackware/. If you keep it as the same name as the previous kernel (like just calling it vmlinuz), you don't even have to touch elilo.conf. Just move the kernel in there and reboot.

But if you don't want to do it the manual way, eliloconfig can do it for you (but if you have customizations in elilo.conf, they will be overwritten.