Bug 1214010 - Display is loosing synchronisation
Summary: Display is loosing synchronisation
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-05 10:31 UTC by Hansi Meir
Modified: 2023-08-08 15:34 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hansi Meir 2023-08-05 10:31:09 UTC
Tumbleweed KDE Plasma X11
=========================

Irgendetwas muss imho im Kernel nach 6.3.7-1.2 passiert sein: 
das Display meines Notebooks funktioniert dann nur noch mit der max. Auflösung 2560x1600. 

Stelle ich über die Plasma Systemeinstellungen "Anzeige und Monitor" etwas anderes ein, ist die Synchronisation weg: die Anzeige flackert wild, ist verzerrt und voller vertikaler Streifen. Zum Glück stellt sich der alte Zustand wegen fehlender Bestätigung von selbst wieder her.

Lenovo Thinkbook 16p Gen2
AMD Ryzen 9 5900HX mit integrierter Radeon Grafik und außerdem einer Nvidia RTX 3060

Dies passiert ab Kernel 6.3.9, egal ob Nvidia-Treiber Paket G05 oder G06 installiert ist.

Ab Kernel 6.4 kommt ein weiteres Phänomen hinzu: 
boote ich "nvidia" bleibt der Bildschirm auf minimaler Helligkeit. 

Das Login Eingabefeld für das Passwort ist mit Mühe gerade noch erkennbar. 
Auch wenn ich mit init 3 boote, ist der Bildschirm so dunkel.

Es scheint also zwei Probleme zu geben:
- eines betrifft die Unterstützung der AMD-Treiber,
- ein anderes betrifft die Unterstützung der Nvidia-Treiber.

Ich habe das System aus einem Backup auf den Stand vom 18.06.2023 restored und habe nun
Kernel 6.3.7-1.2
Nvidia 525.118.04-8.1
laufen.

Beide habe ich für Updates gesperrt und anschließend habe ich alle Updates mittels
zypper -vv dup --details
eingespielt.

Es sind also alle anderen System- und Anwendungskomponenten auf dem neuesten Stand (soeben 05.08.2023), also auch der AMD Grafiktreiber.
Die o. g. Probleme tauchen nicht auf, deshalb vermute ich, das Problem liegt beim Kernel nach 6.3.7.

Aktuell: prime-select bootet "amd", im BIOS ist bei Grafik "switchable" eingestellt.

Bei
prime-select boot nvidia
muss im BIOS bei Grafik "discrete" eingestellt sein, andernfalls hängt das System, bevor es zum Login kommt.

__________________________________________________________________________
Falls die Meldung in englischer Sprache erforderlich ist, bitte ich um eine Rückmeldung.
Comment 1 Takashi Iwai 2023-08-06 07:09:11 UTC
Please report in English.
Comment 2 Hansi Meir 2023-08-08 13:38:24 UTC
Tumbleweed KDE Plasma X11
=========================

Imho something must have been changed in the kernel after 6.3.7-1.2:
the display of my notebook then *only* works with the maximum resolution of 2560x1600.

If I set something else via the "Display and Monitor" plasma system settings (e. g. 1920x1200), the synchronization is lost: the display flickers wildly, is distorted and full of vertical stripes. Fortunately, the old state is restored by itself due to the lack of confirmation.

Lenovo Thinkbook 16p Gen2
AMD Ryzen 9 5900HX with integrated Radeon graphics and also an Nvidia RTX 3060

This happens from kernel 6.3.9, regardless of whether Nvidia driver package G05 or G06 is installed.

Since kernel 6.4, another phenomenon is added:
If I boot "nvidia" the screen remains at minimum brightness.

The login input field for the password is barely recognizable.
Even when I boot with init 3 the screen is so dark.

So there seems to be two problems:
- one concerns AMD driver support,
- another concerns the support of Nvidia drivers.

I restored the system from a backup to the status of 06/18/2023 and now have
Kernels 6.3.7-1.2
Nvidia 525.118.04-8.1

I blocked both for updates and then I installed all updates using
zypper -vv dup --details
recorded.

So all other system and application components are up to date (just August 5th, 2023), including the AMD graphics driver.
Because there are no problems like described above, I suspect there is a kernel problem after 6.3.7.

Currently: prime-select boots "amd", in the BIOS "graphics" is set to "switchable".

On the other hand:
if prime select boot nvidia, "discrete" *must* be set for graphics in the BIOS, otherwise the system hangs before the login occurs.
Comment 3 Takashi Iwai 2023-08-08 13:46:29 UTC
You can still have 6.3.9 kernel in OBS history repo
  http://download.opensuse.org/history/
and please check whether 6.3.9 shows the same problem or not.
If not, it's possibly a regression between 6.3 and 6.4.

And, this bug deals with only AMD problem.  For Nvidia, open another bug report.
Comment 4 Hansi Meir 2023-08-08 14:57:01 UTC
I'm not really sure ...

Update: I've updated to current state

openSUSE Tumbleweed 20230807
KDE-Plasma-Version: 5.27.7
KDE-Frameworks-Version: 5.108.0
Qt-Version: 5.15.10
Kernel-Version: 6.4.8-1-default (64-bit)
Nvidia version: 535.86.05-10.1


Main problem "losing sync" is solved. Why, when it was an AMD problem?

But if prime-select boot nvidia or next-boot nvidia with "switchable" is set for graphics in the BIOS, the system hangs: when rotating cursor stops. ctrl-alt-del will be recognized and system shut down.

But: "prime-select nvidia" works if I make "log out" and "log in" only. Then nvidia driver works which I can se in "info" and Heaven Benchmark works with good frames.

Why is that an Nvidia driver problem if it works fine in this case but boot will not work?

But: if "prime-select boot nvidia" with "discrete" is set for graphics in the BIOS, system boot with success but with dark screen (login field is barely recognizable) and stays so dark, brightness cannot be changed. 

May be a special kernel parameter is necessary for this configuration?
Comment 5 Takashi Iwai 2023-08-08 15:01:11 UTC
Then it's been already addressed in 6.4.x.  Likely a regression in the 6.4, and fixed after that, something like the commit:
8ab7147dfae7d70402540da584f8fe36591b1308
   Revert "drm/amd/display: edp do not add non-edid timings"
    
Again, for Nvidia problem, open another bug report and concentrate only there.
Comment 6 Hansi Meir 2023-08-08 15:34:46 UTC
O.k., thank you very much for your efforts!