Nvidia drivers arent installing on pureos

[kieran]

ERROR: Unable to load the kernel module ‘nvidia.ko’. This happens most frequently when

• this kernel module was built against the wrong or improperly configured kernel sources,
• with a version of gcc that differs from the one used to build the target kernel,
• or if another driver, such as nouveau, is present and prevents the NVIDIA kernel module from obtaining ownership of the NVIDIA GPU(s),
• or no NVIDIA GPU installed in this system is supported by this NVIDIA Linux graphics driver release.

This is the kind of error message that I hate. It would be sooooo much easier if nVidia / whatever told you which of the four situations applies. (It could in theory be more than one.)

[lperkins2]

I’ve read the article from the Sway developer, and am aware of the proposed new allocator library. Follow the link to the library’s github page. Note that the last commit was from 2017… Maybe the parties at nvidia working on it had to quit, but were acting in good faith, maybe it was a publicity stunt by NVidia. Bottom line is it’s been almost 3 years and still crickets on getting GBM or something equivalent.

[opaqueotter]

An update for future readers (and entertainment of others trying to help), I managed to get it working good enough for my purposes but that basically meant turning my PureOS into a frankensteinOS .

Before explaining I will go ahead and give my usecase: I’m studying hashcat (a bruteforcing tool). I don’t need to actually run any games. I manage to use it now, but I’ve never tested this setup with any other case.

Ok on to the “solution”. Brace yourselves:

After removing everything nvidia related, I’ve:

Changed from boot mode from legacy to UEFI with secure boot disabled (this might not be necessary).

Edited /etc/apt/sources.list and commented out the default repos. Since PureOS 9 is based on Debian 10, I added their repositories such that it looks like this:

# Dropped purism in favor of Debian intirely
# deb https://repo.pureos.net/pureos/ amber main
# deb https://repo.pureos.net/pureos/ amber-security main
# deb https://repo.pureos.net/pureos/ amber-updates main


# Adding debian sources to install nvidia drivers
# See https://wiki.debian.org/SourcesList for more information.
deb http://deb.debian.org/debian buster main contrib non-free
deb-src http://deb.debian.org/debian buster main contrib non-free

deb http://deb.debian.org/debian buster-updates main contrib non-free
deb-src http://deb.debian.org/debian buster-updates main contrib non-free

deb http://security.debian.org/debian-security/ buster/updates main contrib non-free
deb-src http://security.debian.org/debian-security/ buster/updates main contrib non-free

#buster backports
deb http://deb.debian.org/debian buster-backports main contrib non-free
deb-src http://deb.debian.org/debian buster-backports main contrib non-free

deb http://ftp.de.debian.org/debian buster main contrib non-free

Probably some redundant stuff there by I didn’t bother cleaning it.

With that in place, run apt update, apt upgrade and apt dist-upgrade. Yeah I know. Sorry

WARNING: This will rid of the beautiful PureOS boot icon and animation (if you tell the setup queries to do so, which I did). It will replace it with Debian’s.

Finally, I’ve installed nvidia legacy drivers with aptitude install nvidia-legacy-390xx-driver.

Note: My system was quite broken from so many different attempts and apt remove --purges that doing only this was not enough. I also had to install missing firmware but I believe that is off topic and I don’t quite remember the steps to document here so I’ll avoid it to not mislead future readers.

Thanks for the help everyone.

PS: If you know how to I could get the PureOS boot logo and animation back, I’d love to hear it.

[reC]

instead of going to all that trouble to MAIM a perfectly pure OS you could have just used any of the pop-OS or ubuntu or manjaro-architect and be DONE with it …

if you have or are running last gen-ish non-open-hardware then it’s not worth it to install a pure OS directly on bare-metal … in a VM ? sure for playing around and testing but otherwise why torture yourself like that ?

but don’t mind me … i’m just here to speak my peace

[Traacker1]

This conversation is great for me since the PURITY thing is Philosophically great. But… I ain’t Stallman but really dig his obstinate ways and am grateful for his leadership model of knowingly being “inconvenienced” to be free. I don’t have his depth but…

The learning of the obvious, PureOS is Pure FOR THEE PURPOSE OF PURITY, is tough for folks of my ilk… I seem to need to “touch the stove” more than once to get the message of it hurts.

Thanks for asking this thread’s question and the very civil understanding guidance. Last night I was ready to sell my L13V4. But I want the convergence thing so much. Buying the L13V4 & two L5’s is my way to pull on the rope to convergence.

Thanks for the learning of what is so obvious to most, but NOT me. Angels you is, me thinks.

[Quarnero]

It would be sooooo much easier if nVidia / whatever told you which of the four situations applies.

Just found this official link (explaining ‘modeset’ kernel module parameter):
https://download.nvidia.com/XFree86/Linux-x86_64/396.51/README/kms.html

@opaqueotter, might be above link helps, for Wayland (used by PureOS) and Mir.