@suse_paul Can you select the above in the BIOS?
it resulted in a display with an extremely low resolution that made the desktop nearly unusable.
so I switched the BIOS option back to “Dynamic graphics”
@suse_paul That’s to be expected since it’s likely using the nvidia card and not configured.
So can you change back again and post the following output;
inxi -Gxz
xrandr --listproviders
xrandr --listmonitors
But, on boot (after you enable the card) at grub press the e key to edit, use the arrow keys to scroll down to the linux/linuxefi line and press end. I want you to change the nosimplefb=0 to nvidia_drm.modeset=1 press the F10 key to boot and run the above commands, also plug in the external moinitor, does it work now?
the display showed the same bad resolution.
inxi -Gxz
Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
driver: N/A arch: Ampere bus-ID: 01:00.0
Device-2: Syntek Integrated Camera type: USB driver: uvcvideo
bus-ID: 3-6:3
Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5
driver: N/A resolution: 800x600~75Hz
API: OpenGL v: 4.5 Mesa 22.3.5 renderer: llvmpipe (LLVM 15.0.7 256 bits)
direct render: Yes
xrandr --listproviders
xrandr: Failed to get size of gamma for output default
Providers: number : 0
xrandr --listmonitors
xrandr: Failed to get size of gamma for output default
Monitors: 1
0: +*default 800/212x600/159+0+0 default
the external monitor did not work
Those are inert skeleton files containing only comments, created in 2011.
they are not present
ll /etc/X11/xorg.conf.d
insgesamt 4
-rw-r--r-- 1 root root 447 11. Mär 14:22 00-keyboard.conf
@mrmazda I just wanted to be sure nothing is being re-created… 
@suse_paul I’m out of ideas as to why the driver does not show up for that gpu…
Perhaps you could try a Tumbleweed Live USB and boot from that to see if get any further information back from /sbin/lspci -nnk | grep -EA3 "VGA|display|3D" output.
@suse_paul Is this a dual boot system at all? How old is the system and has in had linux on it and all working ok?
it is a dual boot with windows 11 pro.
it is the first installation of linux/opensuse on this laptop - installed just a few weeks ago. running on an external USB drive.
it was not fully working fine:
therefore I activated kexec/kdump.
but I had similar problems (screen freezing) already with a former laptop.
@suse_paul ok, so you see both GPU’s in windows 11? I’m assuming the external monitor works fine there? If so, can you identify if it’s using the intel or nvidia gpu to power.
Can you check the power settings in windows to make sure it’s (nvidia) not being powered off on shutdown as well.
I messed up the windows installation :(, and I have to check whether I can repair it…
I’ll check first the Tumblweed live …
@suse_paul Ahh, then I wonder if that (Windows) has disabled the external monitor port, it has a bad habit of doing that for devices…
So why not look at a fresh install of windows and Leap 15.5? Blow it all away, use the live USB to partition the device and just download the windows iso image and install etc? Or if it’s new, just log in to Lenovo support and request a free (I guess they still have it) install/recovery media?
1 Like
thank you for your effort!
I will check the installs.
(Tumbleweed live didn’t boot - it stopped with security issue)
I tried to boot into a Leap live, KDE as well as Gnome.
Both tries ended up in a grub prompt.
Can that be related to the monitor problem?
Is there anything I can do to boot a live system?
@suse_paul add the grub option nomodeset and see if that helps.
Nomodeset disables multiple display support.
What happens when you log in as root under Wayland?
I have this issue on 1 of my nvidia laptops. I login as root under wayland and the external monitor works. Then log out of root, switch to X11, and then login as your regular user and the external monitor works.
nothing, there is no difference
I could restore windows.
when I attach the monitor there, it connects immediately.
this is shown in journalctl if the monitor is attached:
Apr 20 18:03:18 legion dbus-daemon[2210]: [session uid=1000 pid=2210] Activating via systemd: service name='org.kde.kscreen.osdService' unit='plasma-kscreen-osd.service' requested by ':1.11' (uid=1000 pid=2345 comm="/usr/bin/kded5 ")
Apr 20 18:03:18 legion systemd[2166]: Starting KScreen OSD service...
Apr 20 18:03:18 legion dbus-daemon[2210]: [session uid=1000 pid=2210] Successfully activated service 'org.kde.kscreen.osdService'
Apr 20 18:03:18 legion systemd[2166]: Started KScreen OSD service.
Apr 20 18:03:18 legion kscreen_osd_service[8571]: qrc:/qml/OsdSelector.qml:71:9: QML Heading: Binding loop detected for property "verticalAlignment"
and this after I click in the kscreen popup:
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: XRandR::setConfig
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: Requested screen size is QSize(2560, 1600)
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: Needed CRTCs: 1
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: Actions to perform:
Priorities: false
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: Change Screen Size: false
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: Disable outputs: false
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: Change outputs: false
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: Enable outputs: false
Apr 20 18:03:21 legion kscreen_backend_launcher[2644]: kscreen.xrandr: XRandR::setConfig done!