Multiple issues, probably GPU problems

Hey everyone! New Linux user here (well, I’m not new, but I want to definitely switch from Windows to Linux before W11).

I’m loving Fedora so far but I think I have messed up my setup.
Everything was working out of the box but I’ve been seeing some visual bugs (like glitching) and I thought it was the nvidia drivers (I was using the default ones)… so I tried installing other repos (negativo17, and I can’t remember the other one, I found it here).
Now I’m back with the original drivers.

The problem is that I can’t login sometimes (I have to startx) and when I can (and this happens with startx) my mouse turns into a cross (“X”) for a few seconds.

Here’s my journalctl -p 3 -xb output:

jun 27 10:48:23 fedora kernel: x86/cpu: SGX disabled by BIOS.
jun 27 10:48:23 fedora kernel: ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
jun 27 10:48:23 fedora kernel: ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
jun 27 13:48:27 fedora kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
jun 27 13:48:27 fedora kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
jun 27 13:48:27 fedora kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
jun 27 13:48:27 fedora kernel: ucsi_ccg 0-0008: probe with driver ucsi_ccg failed with error -110
jun 27 13:48:28 fedora kernel: 
jun 27 13:48:28 fedora /usr/bin/nvidia-powerd[948]: Found unsupported configuration. Exiting...
jun 27 13:48:37 fedora gnome-session-binary[1412]: Unrecoverable failure in required component org.gnome.Shell.desktop
jun 27 13:48:38 fedora gdm[1335]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 27 13:48:38 fedora gdm[1335]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 27 13:48:46 fedora gdm-password][1994]: gkr-pam: unable to locate daemon control file
jun 27 13:48:47 fedora gdm[1335]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 27 13:48:50 fedora systemd[2009]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2313.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 175 and the job result is failed.
jun 27 13:48:50 fedora systemd[2009]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2318.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 179 and the job result is failed.
jun 27 13:48:50 fedora systemd[2009]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2323.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 183 and the job result is failed.
jun 27 13:48:50 fedora systemd[2009]: Failed to start app-gnome-xdg\x2duser\x2ddirs-2339.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 187 and the job result is failed.
jun 27 13:48:53 fedora gdm[1335]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

Any idea what’s going on?
The other problem is there as well, I’m always seeing ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.

Thanks!

You’ve said a lot here. . . What exactly did you do and what do you currently have? I personally use Negativo17 and have for a long time. The Supported way here on the forums is to use the RPMFusion repos: Howto/NVIDIA - RPM Fusion

Also, please post the results of inxi -Fzxx so we can see your hardware specs.

I’m currently using the RPM Fusion repo. What I did is switched between repos and now I’m back to RPM

This is the output of that command:

System:
  Kernel: 6.9.5-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.2 tk: GTK v: 3.24.42 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Desktop System: Micro-Star product: MS-7B49 v: 1.0
    serial: <superuser required>
  Mobo: Micro-Star model: Z370 PC PRO (MS-7B49) v: 1.0
    serial: <superuser required> UEFI: American Megatrends v: 1.70
    date: 04/03/2019
Battery:
  ID-1: hidpp_battery_0 charge: 100% condition: N/A volts: 4.2 min: N/A
    model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse serial: <filter>
    status: full
CPU:
  Info: 6-core model: Intel Core i7-8700 bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
  Speed (MHz): avg: 802 high: 824 min/max: 800/4600 cores: 1: 824 2: 800
    3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
    bogomips: 76799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: Micro-Star MSI
    driver: nvidia v: 550.90.07 arch: Turing pcie: speed: 2.5 GT/s lanes: 16
    ports: active: none off: DP-2,HDMI-A-1 empty: DP-1,DP-3 bus-ID: 01:00.0
    chip-ID: 10de:1f06
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 24.1.0
    compositor: gnome-shell driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    display-ID: :1 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96
  Monitor-1: DP-2 mapped: DP-3 note: disabled pos: right
    model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102 diag: 551mm (21.7")
  Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: primary,left
    model: Samsung LF27T35 res: 1920x1080 dpi: 82 diag: 686mm (27")
  API: OpenGL v: 4.6.0 vendor: nvidia v: 550.90.07 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
  Device-2: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f9
  Device-3: Kingston HyperX Cloud Flight Wireless
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-5:2 chip-ID: 0951:1723
  API: ALSA v: k6.9.5-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
    v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.69 TiB used: 7.59 GiB (0.3%)
  ID-1: /dev/sda vendor: Kingston model: SA400S37960G size: 894.25 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-2: /dev/sdb vendor: Western Digital model: WD20EARX-00ZUDB0
    size: 1.82 TiB speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 243.14 GiB used: 7.19 GiB (3.0%) fs: btrfs dev: /dev/sda6
  ID-2: /boot size: 973.4 MiB used: 356.8 MiB (36.7%) fs: ext4
    dev: /dev/sda5
  ID-3: /boot/efi size: 96 MiB used: 49.5 MiB (51.5%) fs: vfat
    dev: /dev/sda2
  ID-4: /home size: 243.14 GiB used: 7.19 GiB (3.0%) fs: btrfs
    dev: /dev/sda6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: nvidia temp: 34 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 29%
Info:
  Memory: total: 32 GiB available: 31.28 GiB used: 2.84 GiB (9.1%)
  Processes: 362 Power: uptime: 33m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: Compilers: gcc: 14.1.1 Shell: Bash v: 5.2.26
    running-in: gnome-terminal inxi: 3.3.34

1 Like

Are you Dual Booting with Windows ? :thinking:

1 Like

Ah, yes, forgot about that. I am dual booting with W10.
I see that error after grub but the OS boots

But that error message is fine. I’m trying to fix the infinite login loop :slightly_smiling_face:

From what we can see with the inxi output the gpu seems normal.
The message about nvidia-powerd is just an alert since that gpu is not supported by the powerd daemon. It can be ignored totally.

Just a final check on the gpu status please post dnf list installed \*nvidia\* and lsmod | grep nvidia.

I don’t think the login loop has anything to do with the GPU driver.

2 Likes

dnf list installed \*nvidia\*:

Installed Packages
akmod-nvidia.x86_64                            3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.9.5-200.fc40.x86_64.x86_64       3:550.90.07-1.fc40        @@commandline                   
nvidia-gpu-firmware.noarch                     20240610-1.fc40           @updates                        
nvidia-modprobe.x86_64                         3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64                         3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64                     3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64           3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64             3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64                3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64               3:550.90.07-1.fc40        @rpmfusion-nonfree-nvidia-driver

lsmod | grep nvidia:

nvidia_drm            135168  11
nvidia_modeset       1605632  11 nvidia_drm
nvidia_uvm           6823936  0
nvidia              60592128  166 nvidia_uvm,nvidia_modeset
i2c_nvidia_gpu         12288  0
video                  77824  1 nvidia_modeset

How can I diagnose what’s going on with the login loop?

Once again I had the loop problem but this time the output of journalctl is different:

jun 27 22:11:14 fedora kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
jun 27 22:11:14 fedora kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
jun 27 22:11:14 fedora kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
jun 27 22:11:14 fedora kernel: ucsi_ccg 0-0008: probe with driver ucsi_ccg failed with error -110
jun 27 22:11:15 fedora kernel: 
jun 27 22:11:16 fedora /usr/bin/nvidia-powerd[950]: Found unsupported configuration. Exiting...
jun 27 22:11:31 fedora gdm-password][1996]: gkr-pam: unable to locate daemon control file
jun 27 22:11:32 fedora gdm[1343]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 27 22:11:32 fedora systemd[2008]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2215.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 157 and the job result is failed.
jun 27 22:11:33 fedora systemd[2008]: Failed to start org.gnome.Shell@wayland.service - GNOME Shell on Wayland.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 51 and the job result is failed.
jun 27 22:11:33 fedora gdm[1343]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

Did you at one point have Gnome and another DE installed ?