OK, I tried all, the driver is definitely inside the directory, “no such file or directory”. I’ll reinstall again and try to get the LTS!
1 Like
Thanks a lot anyway. I’ll install a different distro then, so I don’t get people to quit all their development because I’m causing too much work.
1 Like
It’s not the “.run” file that can’t be found. bash is complaining that it can’t find “install-driver”.
1 Like
Apparently, that no longer matters. I think the thread can be safely removed.
Thank you, @Tidda and @Markus. I corrected the README file by pre-pending ./ to pre-install-driver and install-driver.
bash ./pre-install-driver
bash ./install-driver 520 or path-to-run-file
The repo is online and set to public archive. I wish to not maintain this any longer. Life is like a relay e.g. I ran my lap or two with NVIDIA Driver installation on Clear Linux.
1 Like
@marioroy may you share the link to the public archived version of the repo pls?
The repo was taken offline due to many regressions outside my control; e.g. regressions in Firefox, GNOME, VA-API NVDEC backend driver, NVIDIA proprietary 525 driver, and the missing gears icon on the login screen.
I completed my 3rd major revision for the repo. There is one more test I want to validate before re-releasing to the public.
Highlights:
- Resolves Firefox crashing since CL 37700.
- Resolves the missing gears icon on the login screen.
- GNOME on Xorg and GNOME on Wayland working.
- Support for the NVIDIA 525 display driver; particularly HW decode acceleration in Firefox. If you have an NVIDIA Optimus laptop, choose 520 or prior release.
- Updates to the complementary Chromium-Freeworld installer-updater script; fetches and install libffi 3.4.x dependency to /usr/local/lib64. Now, able to run the current Chromium-Freeworld release.
- Updates to install-driver to accommodate GNOME expecting NVIDIA files residing in standard locations. The /opt/nvidia path now contains mainly lib32 and lib64. This alleviated many hacks for making things work. Accordingly, updated the
swupd’s picky list in/etc/swupd/config. - Also updates to the post-OS update trigger script; lesser hacks.
In summary, the experience since some time ago has been getting worst and worst per each OS release. Eventually, there’s a limit to the number of hacks needed to make things work.
So, I invited my imaginary friend named Grace. We all sat together in a room; Firefox, GNOME, Mesa, NVDEC driver, NVIDIA display driver, and not to forget CL OS. What is it with you guys? Can’t you guys get along?
Obviously, everybody got along with Grace at their side. 
Moments prior to re-releasing the “nvidia-driver-on-clear-linux” update, I thought to do a cursory check against the latest Clear Linux 37810 OS. Unfortunately, the NVIDIA modules do not build on 37810. I reverted back to 37800.
Edit: Tool chain fixed in CL 37850. CL 37840 not tested. Awaiting CL 37850 or later CL release to become current (not staging) before re-releasing the NVIDIA driver automation. So that folks do not experience the installation failing due to regression with the tool chain in CL 37810.
Thanks for doing it! Looking forward to a new automation script. I have my clean CL installed to test it.
cheers.
Completed 3rd re-release.
Recommendations:
- Choose the LTS kernel during the OS installation (advanced tab). Edit: The Native kernel is now supported.
- Not sure which display driver? Choose v520 over v525. I found v520 to be more stable than v525. One reason is that v525 may be unstable for Microsoft Edge (stalling while changing video quality on YouTube, requiring page refresh).
The list of Browser installer-updater automation has grown. Can you spot the new addition?
- Brave Browser
- Chromium-Freeworld
- Google Chrome
- Microsoft Edge
- Vivaldi
The difficult decision is which Clear Linux OS release? Choose CL 37860 or later for NVIDIA graphics. Or rather, do not install CL 37810-37850.
Running Linux 6.1? See the Epilogue section in the README file. It may require adding the kernel ibt=off parameter for recent Intel CPUs.
Have a prior “nvidia-driver-on-clear-linux” installation? The 3rd makeover is different; particularly the display driver installation. Also, the launch scripts for the various browsers have changed. Copy anew launch scripts, et cetera as described in the documentation.
GNOME on Xorg or Wayland? It depends on whether you want to run Chrome or like browser. Device-level font scaling in Chrome doesn’t work on Wayland. This is problematic for HiDPI monitors.
Hi,
I’ve tested the new script. CL 37800, 520 driver. After a reboot I’ve got a black screen with a mouse pointer. Subsequent reboots - only black screen. Not sure where to look for a problem. I tried to fix the CL by forced repair - did not help. To be honest, it does not help to make the CL my distro of choice, at least for my hardware Dell XPS 9550 which runs Ubuntu 22.04 without any issues.
Best regards and thanks for the effort!
-W
Not mentioned is what kernel lts or native. You may need the ibt=off parameter. CL 37860 has been released with updated X11.
I’m feeling the same way. I’m unable to test NVIDIA Optimus hardware. Maybe, the issue is with the nvidia-drm-outputclass.conf file under /etc/X11/xorg.conf.d. Perhaps, it’s a bad idea in the install-driver script to overwrite nvidia-drm-outputclass.conf. That section can be commented out. I understand if you have given up on CL.
Not knowing which kernel you had installed, the README file contains info on disabling Indirect Branch Tracking.
sudo mkdir -p /etc/kernel/cmdline.d
sudo tee /etc/kernel/cmdline.d/disable-ibt.conf >/dev/null <<'EOF'
ibt=off
EOF
sudo clr-boot-manager update
There isn’t much more that I can do with the repository. I will add an uninstaller script which will uninstall the nvidia driver, remove configuration added to /etc including the trigger script, and restore CL lib-opengl.
The repository was updated to support Kernel 6.0 and Kernel 6.1. I’m not sure when you had obtained the repo. Due to the re-release (I did it twice yesterday), it requires re-cloning from scratch e.g. git pull may not work. Thus, removing the directory and re-clone.
@Watergap, I saw that you had success here at one point. That rules out the nvidia-drm-outputclass.conf configuration.
Installing KDE on top of GNOME may not work. I’m not sure the steps folks are using installing KDE successfully. That is a CL question.
That leaves the ibt=off kernel parameter if running Linux 6.1.
I have installed 37800 Native. As to the KDE:
sudo swupd bundle-add desktop-kde
It worked fine with Plasma(X11) config. It was installed before NVIDIA script.
May be KDE is the issue.
My interest to CL was ignited by reading a performance review especially in Java. By running a java2d benchmark test I found little to no difference between CL and Ubuntu.
I may give another try with a different version of CL and GNOME.
Thanks again.
Ah, I thought that NVIDIA drivers were not an issue anymore, that’s a shame.
I hope either NVIDIA makes their drivers open-source someday, so this issue with propietary stuff won’t happen again. Or another company such as AMD or Intel overtake NVIDIA in terms of graphical performance for Blender for example… or CL just somehow manages to get along with NVIDIA’s propietary stuff.
I did a clean installation of CL 37860 + latest NVIDIA 525, Native kernel + default Gnome. It works without any issues without any tweaking of the automation script. I suspect some glitch exists when a different desktop is used. I tried the KDE and Xfce desktops - got a black screen.
cheers.
I ran the following swupd commands on top of a Clear Linux GNOME installation with success. Uninstall the desktop-autostart bundle to remove the gdm-autostart package from the system. The desktop-kde-apps bundle is not required.
sudo swupd bundle-remove desktop-autostart
sudo swupd bundle-add desktop-kde
sudo swupd bundle-add desktop-kde-apps # optional
Verified configuration: Kernel 6.1.1, NVIDIA 520 proprietary driver, and selected “Plasma (X11)” from the Sessions drop-down menu. “Plasma (Wayland)” works too.
See also:
The following Exec entries in desktop files work in GNOME, but not in KDE. 
$ grep "^Exec" ~/.local/share/applications/chromium-freeworld.desktop
Exec=/bin/bash -c "\$HOME/bin/run-chromium-freeworld %U"
Exec=/bin/bash -c "\$HOME/bin/run-chromium-freeworld"
Exec=/bin/bash -c "\$HOME/bin/run-chromium-freeworld --incognito"
The following works in GNOME and KDE.
$ grep "^Exec" .local/share/applications/chromium-freeworld.desktop
Exec=/bin/bash -c "exec $HOME/bin/run-chromium-freeworld %U"
Exec=/bin/bash -c "exec $HOME/bin/run-chromium-freeworld"
Exec=/bin/bash -c "exec $HOME/bin/run-chromium-freeworld --incognito"
I updated the desktop files in the nvidia-driver-on-clear-linux repository.
Some tips:
Running Chrome or derivative browser? Preferably run on Xorg versus Wayland. The VDPAU-backend VA-API driver does not work in Wayland. Another reason is that device font-scaling does not work in Chrome using HiDPI monitors.
Running Microsoft Edge? Install the NVIDIA 520 driver versus 525. For my use case, the 520 driver is more stable.
Desktop stutters or tears while moving windows? Enable “Force Full Composition Pipeline”, documented in the top-level README file.
Update:
Installing a kernel manually or have multiple kernels (LTS and native)? Run check-kernel-dkms manually including after OS updates. That will check non-running kernel(s) and refresh NVIDIA modules, if needed. The script installs missing dkms bundles and runs dkms autoinstall per each kernel on the system.
An issue ticket (feature request) was created for uninstalling a kernel.