Not sure if this is the right place to ask this, just caught up with this announcement. I have an older PC, pre-UEFI (bios) running just fine with what I assume are the older proprietary Nvidia driver, the card is an GTX-1650.
I remember setting this up a couple of years ago, and the Endeavour OS image file came with two separate files, a ‘normal’ one, and one labelled something like Endeavour-nvidia. That’s the one I used and it loaded up correctly.
I’m assuming this new application is not something I would benefit from, or is that wrong. (If it ain’t broke, don’t fix it?)
Secondly, I have another old PC I’m about to install a GTX 1050 card in, is there any difference in how I should load the OS, or is it just like before this new application came on the scene?
Endeavour comes with 1 iso file. When you boot it up it gives you a menu to boot/install in normal mode or nvidia mode. Last week i installed the normal one on my brother in laws notebook (forgot to select the nvidia option). Everything worked except the nvidia card. I installed the nvidia-inst tool and installed the driver nvidia-inst --32.
I’ll answer this here because nvidia-inst may not be known to all new EndeavourOS users.
If you installed using the Nvidia selection then it should be OK.
But if something is not working as expected, or you’d like to change something, then nvidia-inst might be a useful tool. It is not required however.
Based on given options nvidia-inst will recommend which packages to remove and which to install.
To see its recommendations you can simply run
nvidia-inst --test
But as said above, if all works as expected, there’s not really a reason to fix something that’s not broken.
To see all options run command
nvidia-inst --help
Are you going to reinstall or do a fresh install? If the latter, then simply select the Nvidia option on the boot menu and install normally.
For the record, always use the latest EndeavourOS ISO when installing.
Download it only from here: https://endeavouros.com
Yes, that’s undoubtably what I did, the boot gave two options rather than two files. So you can load the regular version, install this new tool, and add the drivers later. I know with the original setup, most of the time you update the system, it loads and recompiles the system with the updated driver, which is slow build. I’m guessing whether you use the proprietary driver or the open source one, on these older machines that process of recompilation each time will be slow.
Guessing, the performance of both drivers will be similar in operation.
It will be a new installation on a new (old) machine. I don’t even still have the boot stick from well over a year ago. I guess this card as being a pascal family probably benefits more from the old propriety drivers? The GTX 1650 in the previous machine being a newer architecture might run better with the open source driver?
Not sure if it’s just my system, but running nvidia-inst from the LTS kernel had it install nvidia-open instead of nvidia-open-lts and got me stuck after reaching target Graphical Interface. Alt-Tab-F2 got me a terminal and installing nvidia-open-lts through pacman fixed it.
Or install your respective kernel headers, so the dkms version of the drivers correctly integrate:
sudo pacman -S linux-lts-headers
When using dkms drivers @weewilliewayne, you’ll need to have the kernel headers installed for every kernel you have installed.
The above example I gave, only installs for the LTS kernel headers, but if you also have the standard kernel installed, you’ll need to install its headers too (in the event you choose to start with that kernel).
Ah, that explains it. I added and switched to the LTS kernel but did not install the LTS headers, and didn’t quite understand the nature of the dkms drivers. Thanks for the info!
Yeah dkms drivers are a one driver for all kernels solution, provided each kernel has it’s respective headers installed.
The downside to dkms drivers is they take a little longer to install and update, as it needs to be integrated with the kernel every time the driver or the kernel is updated.
The alternative is a kernel specific driver, for each kernel.
If you are gaming on that system, you may need to make sure you have lib32-nvidia-utils installed, as @manual had noted you previously had it installed.
Yeah I put everything back together after the hang up. I only posted here in case it was something wrong with the script. But occam’s razor was right and it was my mistake lol.
I’d like to know if you have instability on the system in any moment due the proprietary drives of nvidia. I have to buy a new laptop, but I want a stable system. I’m afraid that nvidia has some instability problem
