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.
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.
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.
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