Masaru Nomiya composed on 2022-08-16 08:10 (UTC+0900):
I learned for the first time that Intel driver and nvidia driver can coexist.
In other words, without nomodeset parameter, there is a conflict between the intel driver and the nvidia driver, resulting in a black screen. So, the nomodeset setteing suppresses the loading of the intel driver, then you can get to the login screen.
You may be wondering why the problem started with Tumbleweed. Since GPU (=Intel Corporation RocketLake-S GT1) is so new that the corresponding kernel module has only recently been developed, so the intel driver autoloading did not occur until then.
18 months isn't new in the PC world. Rocket Lake is more than 18 months old, at least one full generation prior to latest. Mine is one of the newer RKLs, yet six quarters old: https://ark.intel.com/content/www/us/en/ark/products/212270/intel-core-i5114... https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/QD...
To avoid this problem, replace the nomodeset in the kernel parameter with i915.modeset=0.
A normal average desktop PC with PCIe slots and graphics outputs supported by a CPU containing an IGP by default has a BIOS option set to prefer enabling only the add-in GPU if present. It shouldn't be necessary to disable the IGP in software, e.g using i915.modeset=0, but that doesn't mean disabling in software can't or shouldn't work. BIOS vary, and many are buggy. Martin's issue might be affected by updating his UEFI BIOS, or simply making a change to graphics settings in it. I'm guessing we're off the trail here, that i915.modeset=0 isn't going to work, and that this simpledrm/NVidia combo has a software bug, or a BIOS bug triggered by that combination. cf. https://gitlab.freedesktop.org/drm/intel/-/issues/4762 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata