Page 8 of 10

Nvidia drivers for Xenial64 7.5

Posted: Sun 26 Nov 2017, 19:33
by Hesse James
Hello
666philb recently released his Xenial64 Pup 7.5 including a new kernel. So its time to change to a newer Nvidia driver. The ones that are offered by the Quickpet seem to be compiled with the previous Xenial64 7.0.8.6.
Despite the same kernel version number they don't work for me (the result is only a black screen ->for 340.104).
Moreover I like more a SFS-package.

Therefor I put together 2 packages, one for the 304.137 and one for the 340.104 driver. Both work with my old Nvidia card. I am not able to compile a newer driver.
Driver 304.137 http://www.mediafire.com/file/xb1r020bh ... nial64.sfs
MD5 f3d5f0ead1622818aac78dc129c64f95

Driver 340.104 http://www.mediafire.com/file/1tdgbr339 ... nial64.sfs
MD5 9d2140e09ec61fd427a54e46221b6861

Installation of the SFS as described some pages back.
Good luck.
Christian

nvidia drivers xenial64 7.5

Posted: Thu 25 Oct 2018, 07:14
by baraka
Hi,
I tested the drivers posted above on a 8600gt card and they're working but not very well in wine.
From the beggining, the problem is not dependent on wine version (32 vs 64 bit) or (I think) wine.
Example: vlc under wine. It installs and starts without problems, and only when I launch a file, it crashes. The error is something about glx and a three digit number(154?). An uneducated guess: is something related with indirect rendering. I tried to modify xorg ... but nothing.
The same applies to almost every game, every program, but the simple ones (without many requirements from the video driver).
The error has a long history. It reappers in all the tahr64 versions, exactly the same.
Note: the 32 bit driver gives no errors in any puppy I tested. Moreover, in linux mint64 17.3 (based on tahr) or newer all this never happened ones. Being the last driver for 8600 cards, the 340 was involved in all tests. Or more generally, I tried every driver package that xorg has recognized.
If someone has the same problem pls share. Even without a solution your input will be appreciated.
Thx.
Building my own driver is out of the question, a tone of errors.

Posted: Thu 25 Oct 2018, 08:17
by bigpup
Try following this to install a Nvidia driver.
http://www.murga-linux.com/puppy/viewtopic.php?t=110611

First delete and uninstall any Nvidia driver you now have.

Follow the above topic making sure to do what is stated and when it states to do it.

If you get errors. You have something you did not do correctly or something wrong with the install of Xenialpup64 7.5.
I have compiled/made Nvidia drivers, with no problem, in Xenialpup64 7.5, using this procedure.

About using Wine to run Windows programs.
What version of Wine and how you have Wine setup, can affect greatly how well it works.

Start a new topic about your Wine problems.
Post the topic in the beginners section of the forum.

Posted: Thu 25 Oct 2018, 09:13
by baraka
thx for the reply
getnvidia or manual install doesn't work for some time, after lucid i think. some libraries missing or elf, doesn't matter. I could post the exact error if someone is interested.
But the pets I've found worked except this tiny problem.

It's very unlikely to be wine related, to put it more bluntly, I tried at least 10 versions. Every one of them with the same error, glx blabla, again I could post the exact error if... anyway is something like this:
"Major opcode of failed request: 154 (GLX)"
This is happening only in 64 bit versions: tahr64 and xenial64, for beaver64 I've not found a suitable driver.

Vlc32 2.2.8 was used as benchmark (every test was made with 32 bit applications).
nvidia64 340 more or less
wine32 2.0.3 2.04 3.0 3.01 (all are working with vlc 2.2.8 in a pup32 like lucid, xenial, artful, tahr with nvidia32 340)
wine64 2.0.3 3.0 3.0.1
wine from quickpet and a lot more other versions.

Note: the default nouveau64 driver doesn't work either. An error emerges with wine in tahr64, xenial64 or beaver64 - I'm not convinced it's the same.

LE: the default nouveau64 works with wine and vlc32, sorry, it slipped my mind. The goal is to act likewise for the proprietary driver.

I retested getnvidia following the tutorial. Surprisingly the script produced a sfs file and installed a driver. nvidia-settings works, everything seems alright except the archive, the sfs file, has only 5MB in size. The GLX libraries are missing.

In the past I think I had disabled manually the nouveau driver and that messed up the getnvidia script. my bad.

Conclusion: nvidia drivers doesn't install correctly in xenial64 on my machine which is pretty generic.

getnvidia-1.2

Posted: Mon 29 Oct 2018, 12:13
by shinobar
Not fully tested but hope to be usable:
getnvidia-1.2.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/

Re: Nvidia drivers for Xenial64 7.5

Posted: Mon 29 Oct 2018, 21:55
by James186282
Hesse James - I just wanted to thank you for doing the work to get NVIDIA 304.137 going. I spent many hours and gave up. I thought it was impossible. The generic driver limits my page oriented display to 768x1024.

Do you think having a native driver helps get VirtualBox running!?!?

Hesse James wrote:Hello
666philb recently released his Xenial64 Pup 7.5 including a new kernel. So its time to change to a newer Nvidia driver. The ones that are offered by the Quickpet seem to be compiled with the previous Xenial64 7.0.8.6.
Despite the same kernel version number they don't work for me (the result is only a black screen ->for 340.104).
Moreover I like more a SFS-package.

Therefor I put together 2 packages, one for the 304.137 and one for the 340.104 driver. Both work with my old Nvidia card. I am not able to compile a newer driver.
Driver 304.137 http://www.mediafire.com/file/xb1r020bh ... nial64.sfs
MD5 f3d5f0ead1622818aac78dc129c64f95

Driver 340.104 http://www.mediafire.com/file/1tdgbr339 ... nial64.sfs
MD5 9d2140e09ec61fd427a54e46221b6861

Installation of the SFS as described some pages back.
Good luck.
Christian

Posted: Mon 29 Oct 2018, 22:20
by James186282
James - Wow. Zero fooling around. I just loaded the .sfs file and restarted the machine. Your driver works on my good old (but reliable) GeForce 7600 GS. This is SO much better at the higher resolutions the NVIDA native driver provides.

Posted: Tue 30 Oct 2018, 05:31
by baraka
shinobar: thank you for your suggestion.

The 1.2 and the 1.1-64 both are producing in a 64bit environment (xenial64) a 5-6MB sfs file. Obviously an error, the 340 driver can't be that small.

Another result: nouveau64 works with wine in xenial64 (like I said before), but not in beaver64. The same error has appeared constantly. It is the error that Hesse James's driver gives.
Again, imho I think that is something wrong with the GLX libraries or render mode.

Re: Nvidia drivers

Posted: Thu 01 Nov 2018, 13:25
by shinobar
baraka wrote:Again, imho I think that is something wrong with the GLX libraries or render mode.
Well, i think some optional packages need for some puppy.

Posted: Fri 02 Nov 2018, 04:41
by baraka
Ok. Apart from testing, I can't be of any help.
For the time being I'll stick with the 32 bit puppies. They still perform well enough for me.

getnvidia-1.3

Posted: Sat 03 Nov 2018, 05:53
by shinobar
Try v1.3:
getnvidia-1.3.pet (edit: replaced by getnvdia-1.3-1.pet)
http://shino.pos.to/party/bridge.cgi?puppy/opt/

Posted: Sat 03 Nov 2018, 06:22
by bigpup
getnvidia-1.3.pet
Is this a 32bit program?
Is there a 64bit version or will it run in 64bit Puppies as is?

Posted: Sat 03 Nov 2018, 12:22
by perdido
bigpup wrote:
getnvidia-1.3.pet
Is this a 32bit program?
Is there a 64bit version or will it run in 64bit Puppies as is?
Hi bigpup.

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.

.

Posted: Sat 03 Nov 2018, 12:37
by bigpup
Yes, but this is version 1.3
I do not see a 1.3 and a 1.3-64

getnvidia-1.3 both for 32/64bit Puppies

Posted: Sat 03 Nov 2018, 15:43
by shinobar
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/

Posted: Sat 03 Nov 2018, 17:28
by baraka
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.

Posted: Sat 03 Nov 2018, 19:04
by Semme
Baraka, perhaps Shino's script needs an adjustment..

https://superuser.com/questions/1235420 ... -directory

:idea: 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/

getnvidia-1.4

Posted: Sun 04 Nov 2018, 16:58
by shinobar
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/

Posted: Mon 05 Nov 2018, 11:53
by csipesz
Dear Shinobar, i tried your getnvidia1.2+1.3 pets on a new UpupCC system(32bit) and it's working!
OMG, finally somewhere! Thank you, very much! Now only for the 64 bit platform should be equally good workin stuff...

Posted: Mon 05 Nov 2018, 16:17
by baraka
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.