LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices


Reply
  Search this Thread
Old 10-09-2020, 11:57 AM   #1
MF1296
LQ Newbie
 
Registered: Dec 2017
Location: Germany
Distribution: Fedora
Posts: 7

Rep: Reputation: Disabled
Two monitors connected to NVIDIA and AMD GPU - Xorg configuration issues


Hello,

I have some trouble figuring out the correct Xorg configuration. I have a laptop with a GTX1650 and an interal GPU of the AMD Ryzen 4600H. The Laptop monitor is connected to the internal GPU, while the external monitor is connected to the nvidia card via HDMI. I managed to get it running through the following Xorg.conf:

Quote:
Section "ServerLayout"
Identifier "layout"
Screen 0 "TV"
EndSection

Section "Device"
Identifier "GTX1650"
Driver "nvidia"
BusID "PCI:1:0:0"
Option "TripleBuffer" "true"
EndSection

Section "Screen"
Identifier "TV"
Device "GTX1650"
Option "AllowEmptyInitialConfiguration"
Option "DPI" "96 x 96"
EndSection

Section "Device"
Identifier "AMDRadeon"
Driver "amdgpu"
BusID "PCI:5:0:0"
EndSection

Section "Screen"
Identifier "Laptop"
Device "AMDRadeon"
EndSection

Section "DRI"
# Device "amdgpu"
EndSection
The XServer expands the Laptop's monitor to the right-hand side. Mouse and window moving is possible, but the problem is that the external monitor extremely suffers from Tearing and the nvidia GPU is always used for rendering. I want the Tearing to disappear and the internal AMD GPU to do Rendering by default, the nvidia gpu only on demand.

There are many things I don't understand at all. Why does the Xserver automatically place the external monitor at the right and the internal one at the left? Why is the internal monitor active at all? In the ServerLayout section only the external one is selected.

I hope you can help me. Tell me, if you need more information.

Thank's in advance.

Max
 
Old 10-10-2020, 02:12 PM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,469

Rep: Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354
The problem I see is: AMD & Nvidia.

If you want to use Nvidia proprietary drivers, they will overwrite the Mesa libGL* files in /usr/lib(64) in patent protected ways.
If you install the AMD proprietary drivers, they will overwrite the Mesa libGL* files in /usr/lib(64) in alternative patent protected ways.

To make the drivers fast, you're going to need proprietary drivers. To make them compatible, you're going to have to use slower OSS drivers.

You can see what's going on by posting the version numbers of your amd & nvidia drivers, and the output of 'ls -l /usr/lib/libGL*'
Examine what the symlink libGL.so points at. On Mesa, Mine points at libGL.so.1.7.0. The proprietary drivers will overwrite that symlink to libGL.so.<Nvidia-version> or libGL.so.<AMD_version>.


The AMD GPU is in an APU, right? Sell the Nvidia card, and convert to AMD GPUs is the simplest way out. You may not need the second card. It depends how many monitors you have.
 
Old 10-10-2020, 03:11 PM   #3
MF1296
LQ Newbie
 
Registered: Dec 2017
Location: Germany
Distribution: Fedora
Posts: 7

Original Poster
Rep: Reputation: Disabled
Quote:
lrwxrwxrwx. 1 root root 22 29. Jul 00:53 /usr/lib64/libGLdispatch.so.0 -> libGLdispatch.so.0.0.0
-rwxr-xr-x. 1 root root 771168 29. Jul 00:53 /usr/lib64/libGLdispatch.so.0.0.0
lrwxrwxrwx. 1 root root 32 10. Okt 10:11 /usr/lib64/libGLESv1_CM_nvidia.so.1 -> libGLESv1_CM_nvidia.so.450.80.02
-rwxr-xr-x. 1 root root 63688 10. Okt 10:11 /usr/lib64/libGLESv1_CM_nvidia.so.450.80.02
lrwxrwxrwx. 1 root root 29 10. Okt 10:11 /usr/lib64/libGLESv2_nvidia.so.2 -> libGLESv2_nvidia.so.450.80.02
-rwxr-xr-x. 1 root root 111472 10. Okt 10:11 /usr/lib64/libGLESv2_nvidia.so.450.80.02
lrwxrwxrwx. 1 root root 14 29. Jul 00:53 /usr/lib64/libGL.so.1 -> libGL.so.1.7.0
-rwxr-xr-x. 1 root root 558360 29. Jul 00:53 /usr/lib64/libGL.so.1.7.0
lrwxrwxrwx. 1 root root 15 29. Jul 03:33 /usr/lib64/libGLU.so.1 -> libGLU.so.1.3.1
-rwxr-xr-x. 1 root root 353408 29. Jul 03:33 /usr/lib64/libGLU.so.1.3.1
lrwxrwxrwx. 1 root root 26 10. Okt 10:11 /usr/lib64/libGLX_indirect.so.0 -> libGLX_nvidia.so.450.80.02
lrwxrwxrwx. 1 root root 20 29. Sep 15:14 /usr/lib64/libGLX_mesa.so.0 -> libGLX_mesa.so.0.0.0
-rwxr-xr-x. 1 root root 493424 29. Sep 15:17 /usr/lib64/libGLX_mesa.so.0.0.0
lrwxrwxrwx. 1 root root 26 10. Okt 10:11 /usr/lib64/libGLX_nvidia.so.0 -> libGLX_nvidia.so.450.80.02
-rwxr-xr-x. 1 root root 1123584 10. Okt 10:11 /usr/lib64/libGLX_nvidia.so.450.80.02
lrwxrwxrwx. 1 root root 15 29. Jul 00:53 /usr/lib64/libGLX.so.0 -> libGLX.so.0.0.0
-rwxr-xr-x. 1 root root 136344 29. Jul 00:53 /usr/lib64/libGLX.so.0.0.0
lrwxrwxrwx. 1 root root 27 29. Sep 15:14 /usr/lib64/libGLX_system.so.0 -> /usr/lib64/libGLX_mesa.so.0
It seems that the proprietary NVIDIA driver does not wipe MESA. Only using the AMD APU is not possible because the HDMI connector is physically connected to the NVIDIA chip.
 
Old 10-11-2020, 09:12 AM   #4
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,469

Rep: Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354Reputation: 2354
I've used the nvidia - not today or yesterday, but I've used it.

There's a kernel module, libGL* files and an X driver. I'm not an authority here any more, and you will have to get some others to comment. Some look like nvidia drivers [e.g. libGLESv1_CM_nvidia.so.450.80.02] but they have apparently renamed them in their code to allow Mesa and nvidia drivers to exist. I'm surprised, but pleased.

Don't know what AMD are up to there, so I'm not sure I'm much use to you at all.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Handbrake GPU Acceleration - Inexpensive AMD GPU for Old PC Mr. Macintosh Linux - Software 8 01-03-2018 03:11 PM
[SOLVED] fedora 25, Xorg, Amd gpu black screen DBabo Linux - Laptop and Netbook 1 07-05-2017 12:39 AM
how can I setup the amd GPU as a default gpu instead of intel graphics? divinefishersmith Linux - Newbie 33 08-22-2015 06:03 PM
AMD GPU and AMD overdrive stratotak Linux - Software 0 05-15-2014 11:45 AM
Triple Monitors Xorg with AMD&NVIDIA: XRANDR and Xinerama not working. kernel_geek Linux - Hardware 1 03-27-2011 02:07 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook

All times are GMT -5. The time now is 09:09 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration