Nvidia drivers
getnvidia-1.3
Try v1.3:
getnvidia-1.3.pet (edit: replaced by getnvdia-1.3-1.pet)
http://shino.pos.to/party/bridge.cgi?puppy/opt/
getnvidia-1.3.pet (edit: replaced by getnvdia-1.3-1.pet)
http://shino.pos.to/party/bridge.cgi?puppy/opt/
Last edited by shinobar on Sat 03 Nov 2018, 15:54, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Is this a 32bit program?getnvidia-1.3.pet
Is there a 64bit version or will it run in 64bit Puppies as is?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Hi bigpup.bigpup wrote:Is this a 32bit program?getnvidia-1.3.pet
Is there a 64bit version or will it run in 64bit Puppies as is?
Following shinobar's links in the thread shows some interesting stuff/ most notably all versions of both the 32 & 64 bit versions of getnvidia shinobar
has released, the 64-bitters ending in "64" with the latest being "getnvidia-1.1-64.pet "
And also a lot of other goodies there too.
.
Yes, but this is version 1.3
I do not see a 1.3 and a 1.3-64
I do not see a 1.3 and a 1.3-64
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
getnvidia-1.3 both for 32/64bit Puppies
getnvidia-1.3 is tested both on UPup-bb(32bit) and on Bionicpup64.
It depends on the NVIDIA*.run you choose, whether 32 or 64bit.
getnvidia-1.3.pet shows its version as '1.2'.
Uploaded 1.3-1.pet which shows correct getnvidia version.
getnvidia-1.3-1.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/
It depends on the NVIDIA*.run you choose, whether 32 or 64bit.
getnvidia-1.3.pet shows its version as '1.2'.
Uploaded 1.3-1.pet which shows correct getnvidia version.
getnvidia-1.3-1.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Ok, thx. I retested getnvidia-1.3-1 in xenial64 and in beaver64 with NVIDIA-Linux-x86_64-340.107 driver. The same error followed, namely:
cp:cannot stat '../log/nvidia-installer.log'
no such file or directory
tail: can't open 'nvidia-installer.log'
somewhat error occured
and I was advised to check the log. This line caught my attention:
./nvidia-installer:unrecognized option: '--install -libglvnd'
Maybe I should try older versions of 340. I don't know.
cp:cannot stat '../log/nvidia-installer.log'
no such file or directory
tail: can't open 'nvidia-installer.log'
somewhat error occured
and I was advised to check the log. This line caught my attention:
./nvidia-installer:unrecognized option: '--install -libglvnd'
Maybe I should try older versions of 340. I don't know.
Baraka, perhaps Shino's script needs an adjustment..
https://superuser.com/questions/1235420 ... -directory
You could probably create a blank "/var/log/nvidia-installer.log" and rerun Shino's program.
Then again, you may need a few other Pup specific goodies loaded before the installer flies..
https://www.reddit.com/r/linux4noobs/co ... a_drivers/
https://superuser.com/questions/1235420 ... -directory
You could probably create a blank "/var/log/nvidia-installer.log" and rerun Shino's program.
Then again, you may need a few other Pup specific goodies loaded before the installer flies..
https://www.reddit.com/r/linux4noobs/co ... a_drivers/
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
getnvidia-1.4
Tnx baraka for the testing.
I realized and hope fixed the 64bit problem reading your report.
Try v1.4:
getnvidia-1.4.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/
I realized and hope fixed the 64bit problem reading your report.
Try v1.4:
getnvidia-1.4.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Semme: It was a long shot, but I tried your idea nevertheless, with a sidenote: l was unable to install libglvnd. I'm not really convinced that they are indeed suited for 340 driver (too old). In the end, it didn't work, but thx. Note: the script checks automatically for those goodies; someone may believe something else after reading your post.
shinobar:
- in xenial64 4.9.58 the driver 340 installed corectly. wine passed the vlc test, and I think that everything is ok.
- in beaver64 4.18.15 the driver had built and loaded ok, but after I couldn't start xorg despite everything I tried (the OS is in the making, who knows what is happening, I could access the logs if you think it's worth a try).
- I'll see tomorrow if it runs in tahr64, maybe the result has some value to someone.
Much obliged for your effort.
LE: In xenial64 things are not ok in wine. This time, the error is related to opengl:
err:wgl:init_opengl Failed to load libGL: libGL.so.1: wrong ELF class: ELFCLASS64
err:wgl:init_opengl OpenGL support is disabled
Reading the forum I found this about it. Wine32 requests lib32, but the system offers lib64, hence the error. http://www.murga-linux.com/puppy/viewtopic.php?p=975088 666philb's post
When I'll have more time I may try jamesbond's method. It sounds familiar, I think it had already failed me, but I'm not very sure.
In tahr64 the situation is the same as in xenial64.
shinobar:
- in xenial64 4.9.58 the driver 340 installed corectly. wine passed the vlc test, and I think that everything is ok.
- in beaver64 4.18.15 the driver had built and loaded ok, but after I couldn't start xorg despite everything I tried (the OS is in the making, who knows what is happening, I could access the logs if you think it's worth a try).
- I'll see tomorrow if it runs in tahr64, maybe the result has some value to someone.
Much obliged for your effort.
LE: In xenial64 things are not ok in wine. This time, the error is related to opengl:
err:wgl:init_opengl Failed to load libGL: libGL.so.1: wrong ELF class: ELFCLASS64
err:wgl:init_opengl OpenGL support is disabled
Reading the forum I found this about it. Wine32 requests lib32, but the system offers lib64, hence the error. http://www.murga-linux.com/puppy/viewtopic.php?p=975088 666philb's post
When I'll have more time I may try jamesbond's method. It sounds familiar, I think it had already failed me, but I'm not very sure.
In tahr64 the situation is the same as in xenial64.
Last edited by baraka on Tue 20 Nov 2018, 18:14, edited 6 times in total.
- James186282
- Posts: 270
- Joined: Tue 08 Sep 2009, 19:14
- Location: Minnesota
I ended up crashing and burning with the 304 nvidia driver. Running an Nvidea routine *Why? it all worked.
Anyway I thought it might be time to open my wallet (gasp) and buy a slightly newer display board. I thought I was getting a discount special that used Nvidea 340.xx drivers but they had a shiny newer (open box) special on one with twice the video ram and three monitor connectors. So now its nvidia 410.xx on Xenialpup AMD64.
I probably went too far in the newness direction. If anyone hears screaming and puling out the last of my hairs I apologize in advance.
If you don't see an update its because I've smashed my head into the computer monitor.
Anyway I thought it might be time to open my wallet (gasp) and buy a slightly newer display board. I thought I was getting a discount special that used Nvidea 340.xx drivers but they had a shiny newer (open box) special on one with twice the video ram and three monitor connectors. So now its nvidia 410.xx on Xenialpup AMD64.
I probably went too far in the newness direction. If anyone hears screaming and puling out the last of my hairs I apologize in advance.
If you don't see an update its because I've smashed my head into the computer monitor.
Science is what we understand well enough to explain to a computer.
Art is everything else we do.
[i]Donald Knuth [/i]
Art is everything else we do.
[i]Donald Knuth [/i]
getnvidia-1.5
Avoid GL libraries confliction with some Puppy's.
Tested on bionicpup64.
getnvidia-1.5.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/
Tested on bionicpup64.
getnvidia-1.5.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
- James186282
- Posts: 270
- Joined: Tue 08 Sep 2009, 19:14
- Location: Minnesota
It ended up working pretty simply.
I got the devx files for xenial and loaded them (They were .sfs format)
I did the same fo the xebalpup 5.5 header files
I went tto the NVIDiA site and downloaded the 410 driver after double checking it was the one they suggested.
I then turned on permission to execute to the Nvidia .run file.
I went to Menu clicked exit then clicked exit to prompt.
I typed in the name of the nvidia .run file and it compiled up a nice new display driver.
hoo hoo1 Sometimes everything works...
I got the devx files for xenial and loaded them (They were .sfs format)
I did the same fo the xebalpup 5.5 header files
I went tto the NVIDiA site and downloaded the 410 driver after double checking it was the one they suggested.
I then turned on permission to execute to the Nvidia .run file.
I went to Menu clicked exit then clicked exit to prompt.
I typed in the name of the nvidia .run file and it compiled up a nice new display driver.
hoo hoo1 Sometimes everything works...
Science is what we understand well enough to explain to a computer.
Art is everything else we do.
[i]Donald Knuth [/i]
Art is everything else we do.
[i]Donald Knuth [/i]
I recently used Getnvidia to install one of the newest Nvidia drivers.
In the running of the Nvidia run package, compiling the driver, and installing the driver, it asks if I want to make a new xorg.conf.
CHOOSE NO!
If you say yes, it will make a xorg.conf that will not work in Puppy.
Use Puppies Xorgwizard if you need to do anything to xorg.conf.
After installing and using the Nvidia driver.
Nvidia X Server Settings control program.
It controls the settings for Nvidia graphics hardware when using the Nvidia driver.
There are Nvidia settings files being used by the driver.
This is very good at making setting adjustments.
Use it for making any setting changes.
"Warning"
On the X Server Display Configuration Window is an option:
Save to X Configuration File
DO NOT USE THIS OPTION
It will make an xorg.conf file that does not work in Puppy and replaces the working Puppy xorg.conf.
In the running of the Nvidia run package, compiling the driver, and installing the driver, it asks if I want to make a new xorg.conf.
CHOOSE NO!
If you say yes, it will make a xorg.conf that will not work in Puppy.
Use Puppies Xorgwizard if you need to do anything to xorg.conf.
After installing and using the Nvidia driver.
Nvidia X Server Settings control program.
It controls the settings for Nvidia graphics hardware when using the Nvidia driver.
There are Nvidia settings files being used by the driver.
This is very good at making setting adjustments.
Use it for making any setting changes.
"Warning"
On the X Server Display Configuration Window is an option:
Save to X Configuration File
DO NOT USE THIS OPTION
It will make an xorg.conf file that does not work in Puppy and replaces the working Puppy xorg.conf.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Hi bigpup,bigpup wrote:
"Warning"
On the X Server Display Configuration Window is an option:
Save to X Configuration File
DO NOT USE THIS OPTION
It will make an xorg.conf file that does not work in Puppy and replaces the working Puppy xorg.conf.
Good point about the xorg.conf file generated from nvidia setup program.
Its not that it won't boot with an xorg.conf from the nvidia setup program, its that there are some
puppy specific settings that nvidia does not include when it rebuilds the xorg.conf file.
Better to manually edit the puppy xorg.conf with the settings nvidia setup would write to the xorg.conf file
That way yu wil keep the puppy specific settings in xorg.conf
.
Last edited by perdido on Sat 17 Nov 2018, 05:48, edited 2 times in total.
If you look at your examples you can see that settings are missing from the Nvidia generated xorg.conf.
Sure, the basic monitor settings are there, some basic default input device settings, and that is about all.
Well, that is what you get the very first time you boot Puppy, default xorg.conf settings.
Nvidia xorg.conf got monitor setting changes into xorg.conf, but dropped custom settings for other settings in xorg.conf
Other Puppy config programs put stuff into xorg.conf.
Nvidia X server Settings program knows nothing about other Puppy settings that can be in xorg.conf
The Nvidia driver is being controlled by a different settings file when it is loaded and controlling graphics hardware.
A hidden file that the Nvidia Xserver settings program controls.
/root/.nvidia-settings-rc
Sure, the basic monitor settings are there, some basic default input device settings, and that is about all.
Well, that is what you get the very first time you boot Puppy, default xorg.conf settings.
Nvidia xorg.conf got monitor setting changes into xorg.conf, but dropped custom settings for other settings in xorg.conf
Other Puppy config programs put stuff into xorg.conf.
Nvidia X server Settings program knows nothing about other Puppy settings that can be in xorg.conf
The Nvidia driver is being controlled by a different settings file when it is loaded and controlling graphics hardware.
A hidden file that the Nvidia Xserver settings program controls.
/root/.nvidia-settings-rc
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
After taking everything into consideration I changed the postbigpup wrote:If you look at your examples you can see that settings are missing from the Nvidia generated xorg.conf.
Sure, the basic monitor settings are there, some basic default input device settings, and that is about all.
Well, that is what you get the very first time you boot Puppy, default xorg.conf settings.
Nvidia xorg.conf got monitor setting changes into xorg.conf, but dropped custom settings for other settings in xorg.conf
Other Puppy config programs put stuff into xorg.conf.
Nvidia X server Settings program knows nothing about other Puppy settings that can be in xorg.conf
The Nvidia driver is being controlled by a different settings file when it is loaded and controlling graphics hardware.
A hidden file that the Nvidia Xserver settings program controls.
/root/.nvidia-settings-rc
How does that saying go...."The road to Hell is paved with good intentions"
.
Shinobar: 1.5 pet solves everything in xenial64. I can't believe it. All the library conflicts are gone. This bug had years (blaming wine developers didn't help at all).
Thank you very much.
LE (complete results):
a) tahr64 and xenial64 (most important), 340 driver - I've found nothing wrong
b) beaver64 presents the following issues:
- "xwin" command doesn't start xorg, after an apparently flawless installation.
- xorg log said that nvidia driver couldn't be loaded, and nouveau was nowhere to be found - therefore black screen. I reloaded the nvidia.sfs from a fresh savefile and it worked after I manually chose "nvidia" in xorgwizard.
- tested with wine and a glx library error occured, this time explicitly saying that I have the wrong lib32 library
- mpv didn't start, again some library error.
- I remade the sfs without the silent option. A series of writing errors appeared in connecton with cuda library and something else, basically saying some version of cuda is already installed and if I want to bypass it.
I realize that this is a bad report. I should post the exact errors, but again, beaver64 is not fully ready. If you think it's the right time, I'll post them.
Imho, if 1.5 performs well with newer drivers maybe is enough. This is a 10+ years video card though.
Thank you very much.
LE (complete results):
a) tahr64 and xenial64 (most important), 340 driver - I've found nothing wrong
b) beaver64 presents the following issues:
- "xwin" command doesn't start xorg, after an apparently flawless installation.
- xorg log said that nvidia driver couldn't be loaded, and nouveau was nowhere to be found - therefore black screen. I reloaded the nvidia.sfs from a fresh savefile and it worked after I manually chose "nvidia" in xorgwizard.
- tested with wine and a glx library error occured, this time explicitly saying that I have the wrong lib32 library
- mpv didn't start, again some library error.
- I remade the sfs without the silent option. A series of writing errors appeared in connecton with cuda library and something else, basically saying some version of cuda is already installed and if I want to bypass it.
I realize that this is a bad report. I should post the exact errors, but again, beaver64 is not fully ready. If you think it's the right time, I'll post them.
Imho, if 1.5 performs well with newer drivers maybe is enough. This is a 10+ years video card though.
Last edited by baraka on Tue 20 Nov 2018, 13:40, edited 10 times in total.
Re:getnvidia-1.5
baraka, thank you for your co-operation and the report.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
- Hesse James
- Posts: 106
- Joined: Mon 08 Feb 2010, 18:41
Hello
A lot of communication recently...
Shinobar, I counldn't resist to test your version 1.5. I took the latest Nvidia 340.107 driver.
All previous problems seem to be ironed out. Thank you very much.
Some suggestions about a future PET-package:
It could be helpful to add a blacklist-file (like the one in the zip-file) into etc/modprobe.d. After a reboot the nouveau is blacklisted and doesn't disturb the nvidia-driver installation.
I also recommend to add this blacklist-file to the generated driver-PET and SFS-file. Then it is guaranteed, that nouveau is blacklisted when somebody takes this driver-file generated by somebody else.
As expected the newer kernels don't recognise these Nvidia-drivers. You have to use xorgwizard (set video driver + specify + enter 'nvidia' + done + xwin (enter)). This modification could also had been done previously by a modification of the xorg.conf by the getnvidia-pet so that the xorgwizard step is not necessary.
Last comment: separation of the 32bit libs from the 64bit libs and their placement into lib32 was a very good idea. Otherwise, 64bit libs are overriden at the end of the installation (as Baraka wrote). Therefor I left all the 32bit libs out of my previous SFS-builds (which might have been the problem of wine32 as prevously described).
Thank you again for your work.
Christian
P.S. By the way, I have a Nvidia-driver-SFS with 304.127 (64 bit) which can be run up to Bionic64-7.9.5 (Kernel 4.14.71) for very old graphic cards if somebody is interested in.
A lot of communication recently...
Shinobar, I counldn't resist to test your version 1.5. I took the latest Nvidia 340.107 driver.
All previous problems seem to be ironed out. Thank you very much.
Some suggestions about a future PET-package:
It could be helpful to add a blacklist-file (like the one in the zip-file) into etc/modprobe.d. After a reboot the nouveau is blacklisted and doesn't disturb the nvidia-driver installation.
I also recommend to add this blacklist-file to the generated driver-PET and SFS-file. Then it is guaranteed, that nouveau is blacklisted when somebody takes this driver-file generated by somebody else.
As expected the newer kernels don't recognise these Nvidia-drivers. You have to use xorgwizard (set video driver + specify + enter 'nvidia' + done + xwin (enter)). This modification could also had been done previously by a modification of the xorg.conf by the getnvidia-pet so that the xorgwizard step is not necessary.
Last comment: separation of the 32bit libs from the 64bit libs and their placement into lib32 was a very good idea. Otherwise, 64bit libs are overriden at the end of the installation (as Baraka wrote). Therefor I left all the 32bit libs out of my previous SFS-builds (which might have been the problem of wine32 as prevously described).
Thank you again for your work.
Christian
P.S. By the way, I have a Nvidia-driver-SFS with 304.127 (64 bit) which can be run up to Bionic64-7.9.5 (Kernel 4.14.71) for very old graphic cards if somebody is interested in.
- Attachments
-
- nvidia-installer-disable-nouveau.zip
- (278 Bytes) Downloaded 467 times