New install - freezes on boot before Gnome login screen - NVIDIA

This is my 2nd day fighting Tumbleweed. I’m switching from PopOS, but so far it’s not going very well.

This is also my 3rd clean re-install and it’s always the same. Right after installation, it works OK, but kinda sluggish. Then I install NVIDIA drivers and it’s just downhill from here.

I’m on GTX 3060 (drivers v 550), secureboot is disabled. When I 1st reboot after installing NVIDIA drivers, it goes to 800x600 and usually freezes right before gnome login screen.

I have to try several hard resets and press CTRL+ALT+F1/F2 at the right millisecond to get to the login screen and then remember to switch to X11 (there are like 6 Gnome entries - I assume the 1st one “GNOME” is wayland?). Sometimes it works, sometimes it does not.

And even if it works, then there’s like 1:3 chance that it won’t boot back after another restart or shut-down and I have to try the previous steps again and again.

From what I’ve seen it’s most likely related to NVIDIA - “failed to apply atomic modset” and “nv_drm_atomic_commit/nvidia_drm” errors. Not sure if it can be reliably fixed, but other distros I tried just worked straight out of the box. Not sure why it is so hard here.

inxi -GSaz
System:
Kernel: 6.10.3-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.3.0
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.10.3-1-default
root=UUID=3d3359a1-4d43-4454-8c6e-3578b45d9951 splash=silent
resume=/dev/disk/by-uuid/3756e8ed-a743-4d02-bba6-1831877b528c
mitigations=auto quiet security=apparmor
Desktop: GNOME v: 46.4 tk: GTK v: 3.24.43 wm: gnome-shell
tools: gsd-screensaver-proxy avail: xscreensaver dm: GDM v: 46.2
Distro: openSUSE Tumbleweed 20240807
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Dell
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: none empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:3e92 class-ID: 0380
Device-2: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ZOTAC
driver: nvidia v: 550.100 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-06; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 1 speed: 2.5 GT/s
lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
off: DP-4 empty: DP-2,DP-3,HDMI-A-2 bus-ID: 01:00.0 chip-ID: 10de:2504
class-ID: 0300
Display: x11 server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.1
compositor: gnome-shell driver: X: loaded: modesetting,nvidia
alternate: intel dri: iris gpu: nvidia,nvidia-nvswitch display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x2160 s-size: <missing: xdpyinfo>
Monitor-1: DP-4 note: disabled model: Dell S3221QS serial:
built: 2023 res: 3840x2160 hz: 60 dpi: 140 gamma: 1.2
size: 697x392mm (27.44x15.43") diag: 806mm (31.7") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: OpenGL v: 4.6.0 vendor: nvidia v: 550.100 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
memory: 11.72 GiB
API: EGL Message: EGL data requires eglinfo. Check --recommends.

Hello @camtarret ,

How did you install the nvidia drivers. With “zypper inr”?

I followed a Youtube video, then the OpenSUSE wiki page and this last time I just added from Yast and rebooted. Always the same, not matter how it’s added.

Hello @camtarret ,

The first gnome entry is wayland. When you do succeed getting into gnome on x11, is it stable? Correct resolution?

@camtarret Hi and welcome to the Forum :smile:
So, this is a desktop system, do you want to use the Nvidia GPU direct, or use Prime Render Offload via switcherooctl and using the Intel gpu for the Monitor?

See this recent thread How might I enable graphics acceleration for Intel HD 630 on Gnome on X11

Yes, sir. When it works, it works. 4K resolution. The problem is that it probably won’t work after another restart/shut-down and I’ll have to spend another 20-40 minutes restarting and trying.

Just the NVIDIA probably at this point. I guess.

Hello @camtarret ,

I would use “journalctl -b BOOTNUMBER” to see if there are any helpful clues as to what is failing. “journalctl -b 1” will give you the logs prior to current boot. “2”, two boots back, etc. …

@camtarret then you need to go into the system BIOS and disable the Intel gpu. But before that you need to fire up YaST Bootloader and add fbdev=1 nvidia_drm.modeset=1 to the kernel command line options on the second tab, save and reboot.

I suspect that suse-prime is also installed, that needs to be removed to.

1: Aug 08 00:35:24 localhost.localdomain systemd[2100]: Queued start job for defaul - Pastebin.com

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.