Vitooo wrote: ⤴Mon Oct 02, 2023 6:27 pmIt is in "hybrid" mode at the moment, both GPUs are enabled. I used to set this option in "discrete" mode (only NVIDIA gpu), but the battery consumption was very high.
Did it help the issue with the scaling? I'm asking to see if we can pinpoint where the issue might be originating. While there have been a lot of AMD driver bugs, there is also the additional factor in this case that there are two GPUs in the computer. That can sometimes complicate determining the source of a problem.
Vitooo wrote: ⤴Mon Oct 02, 2023 6:27 pmSo, I hope this explanation is clear enough!
Yes, it was all good and your system sounds to be in good shape now.
Vitooo wrote: ⤴Mon Oct 02, 2023 6:27 pmI have a question to ask BEFORE installing the latest AMDGPU drivers manually.
There are no amdgpu drivers for you to install manually. You should be using the drivers which load automatically from the kernel.
The information I posted is for linux-firmware which are support files for the amdgpu drivers so they can function to their fullest potential (and sometimes they are tweaked to fix bugs).
Vitooo wrote: ⤴Mon Oct 02, 2023 6:27 pm
As I commented before, it seems that the USB-C video connector is NOT attached to the AMDGPU, but to the NVIDIA GPU.
I never said your TV was connected to the AMDGPU. I made the point earlier in the topic that your LAPTOP SCREEN was connected to the AMDGPU. In fact, the inxi data you posted indicates your TV is connected to the Nvidia GPU. That's never been a question.
Additionally, I said the AMDGPU is the primary renderer. I did NOT say it was the only one. The primary renderer loads first and that is what shows as the GPU in inxi. However, there are laptops for which both renderers load, but only one shows in the inxi field. I've not yet figured out why that happens; I presume it has something to do with the way the ports/screens are wired to the GPUs.
Vitooo wrote: ⤴Mon Oct 02, 2023 6:27 pmIn order to know which GPU is gpu:0:
In order to know which GPU is GPU-0, I check /var/log/Xorg.0.log. That is a better place to check because it has the information for both Nvidia and AMD. Running the Nvidia settings info will not tell you about AMD.
A word of caution: the Nvidia tools are mainly designed assuming that your computer only has Nvidia. That is not true in your case so be careful with data you find online telling you to do something from the command line because you may end up shutting out the AMD GPU (ask all the people who got black screens because they unknowingly shut out their AMD or Intel onboard GPUs).
Vitooo wrote: ⤴Mon Oct 02, 2023 6:27 pmI really don't know how Cinnamon Desktop controls the independent scaling (maybe it uses xrandr?)
FYI: You cannot make changes to Nvidia-controlled screens using xrandr. You can only use xrandr for open-source drivers (AMD, Intel, nouveau).
It's possible this issue may be a bug in Cinnamon (or muffin) or this could be an issue because there are two different graphics drivers involved. I don't know the best way to describe the problem to search through the Cinnamon bugs to see if it has already been mentioned. I did take a quick check through the muffin issues a couple of days ago, but I couldn't find what I thought I remembered seeing in the past.
There are
many AMD bugs and I don't have the time right now to hunt through them to see if something like this has happened. I know people have run into odd issues because of dual-graphics, but I'm not sure of a good way to narrow down the bug list to see if there is something like this.
Vitooo wrote: ⤴Mon Oct 02, 2023 6:27 pm
As you requested, I'm sharing my system info again:
Here's where the data indicates which
ports are active. Sometimes the data for
active and
off are not accurate, but the sum of those two are usually what have screens attached to them.
Device-1:
NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo driver: nvidia
v: 525.125.06 pcie: speed: 2.5 GT/s lanes: 8
ports: active: none off: DP-3 empty: DP-4,eDP-2
bus-ID: 01:00.0 chip-ID: 10de:2520
Device-2:
AMD Cezanne vendor: Lenovo driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 16
ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 05:00.0 chip-ID: 1002:1638
Notice in this part that display drivers for both AMD and Nvidia are loaded. However, the gpu field only shows amdgpu.
Display: x11 server: X.Org v: 1.21.1.4
driver: X: loaded: amdgpu,ati,nvidia
unloaded: fbdev,modesetting,nouveau,vesa
gpu: amdgpu display-ID: :0 screens: 1
Additionally, the renderer showing is AMD. That is why I said AMD was the primary (primary does not mean only one; primary implies there is a secondary).
OpenGL:
renderer: RENOIR (renoir LLVM 15.0.7 DRM 3.49 6.2.0-33-generic)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
You can see the specifics of which port is attached to which monitor by running
xrandr --verbose. Check my explanation on how to interpret it near the bottom of
this post. Now that I look closer at that topic, you both have the same computer and the same problem.
You do have a slightly different CPU than the other person.
Here are the
AMD issues if you want to see if there are any
Lenovo ThinkBook 16p Gen 2 users who have posted bugs.
That would seem to indicate there either is not a MUX or it is some type of special MUX switch. 