Nvidia 304.xx
To anybody using the Nvidia 304.xx series:
I was using 304.64 but updated to 304.88. I don't experience the black screen of death that 304.84 is famous for. :) |
No problems with the 310.40 here.
|
Quote:
Quote:
304.88 works fine here. |
304.88 fixes the blank virtual terminals/console problem in 304.84.
|
Quote:
|
Quote:
|
I now have 304.88 running on a 6150 chipset with the 3.8.8 kernel - at last!
I had to patch the kernel/nv-mmap.c file to not fail on VM_RESERVED, but it then built and installed and no longer failed on the ABI version. This is on a fully -current system and Pat's reverting to the earlier Xorg seems to have fixed the ABI problem (if I understand that correctly). [EDIT] Forgot to mention - on this system I had to turn off the vblank option. With it I got 60FPS, without ~2400. [/EDIT] |
Question for Woodman. Did you use the older SlackBuild version for the 304 series? Or rolled your own?
There's an old 6150 ADP video card gathering dust within an nvidia AMD2 chipset based PC. I'd like to put SlackWare 14 on. And the nvidia I have on file is the 304.51 using the older slackbuild. Would it work just updating the version number in that older slackbuild? Quote:
|
I used the build scripts for 13.37 (302.17) from slackbuilds.org. I changed the version and build numbers.
Note: The driver script has an incorrect sym link command: AS IS (line 154): ln -sf libnvcuvidv.so.$VERSION libnvcuvid.so CHANGE TO: ln -sf libnvcuvid.so.$VERSION libnvcuvid.so |
Quote:
|
Quote:
|
Question: I have the Nvidia GeForce 6150SE nForce 430 chipset and everything seems to be working fine out of the box with the generic 3.2.29 kernel and stock nouveau drivers on a fresh install of Slackware 14. At least nothing is crashing and I'm able to watch movies and such without problems. Is there any advantage to installing the proprietary driver that I may not be aware of? Thanks in advance for any input.
|
I'm using version 304.64 on Slackware 14 and it works fine (7600 GS).
Version 310.32 (from the slackbuild) didn't work at all, and log messages pointed me to 304.64, saying the card was supported up to that version. I had to fix several links and libraries, and I guess it would have been easier if I had modified the slackbuild for 13.37 instead. Quote:
http://nouveau.freedesktop.org/wiki/ http://nouveau.freedesktop.org/wiki/HardwareStatus Kind regards, Philip |
Thanks Philip, I suppose I was just looking for a good reason to load the Nvidia driver, but if everything is working well as is, I guess I will skip it.
|
Quote:
Philip |
I went ahead and installed the Nvidia 304.88 driver for my 6150SE and everything worked perfectly thanks to SlackBuilds (and a special shout out to Edward Koenig). I didn't even have to add/edit any config files afterwards since everything just worked. As Woodsman outlined above I used the kernel and driver build scripts from 13.37 and simply changed the version number. The only minor hassle was locating the 304.88 source files for nvidia-installer, nvidia-settings and nvidia-xconfig but some noodling around on the Nvidia website found all of those.
|
Quote:
:) |
Quote:
|
Can I assume that this is normal slackpkg behavior after blacklisting nouveau and that I can just ignore it?
Quote:
|
Put this in /etc/slackpkg/blacklist to solve that problem:
Code:
# Nouveau driver |
just installed nvidia 304.88 from nvidia's webiste now web browser crashes.
I have the 6150se graphics card on my tower and just installed the 304.88 graphics driver from nvidia's website. It seemed to go well, however now I can not open a web browser. As soon as I open firefox or seamonkey they immediately crash. Any ideas as to what is causing this?
Update: I upgraded to current with the 3.9.5 kernel and when I rebooted and tried to open firefox my system froze. I rebooted again and then firefox seemed to work. I wonder if it's going to freeze up occasionally? |
Woodsman you should probably submit a SlackBuild package to SlackBuilds.org to add another Legacy tier for Nvidia chipsets. A lot of laptops and workstations still use the 6x00/7x00 series graphics processors.
|
I am probably a latecomer to 3.10.5, but just updated to -current on an AMD/nvidia box.
Hit the nvidia kernel update problems with 304.88, quickly solved by Willy Sudiarto Raharjo's notes here. So 304.88 survives yet another round... |
Nice to hear. After today's current change log announcement, and this thread, I wondered how well 304.88 would survive. I haven't done any testing in current in a long while but expect to do so soon. I have no desire to buy a new motherboard. Nonetheless, I always hold my breath a wee bit when current gets closer to release because I don't know what third party packages will break. :)
|
I tends to install the latest kernel and find an appropriate patch for NVidia and VMWare and post it on my blog just in case someone else might need it...
GIad it help when Pat decided to take 3.10.5 into Current |
Thanks for your work willysr.
Your advice did the trick for me regarding the 304.88 drivers and the 3.10.5 kernel provided by Pat. :) I just have one question : You said on your blog to apply the patch with the command "apply". On my -Current box, when logged as root, the system claimed that the command "apply" was not found. So I did use the command "patch" with the same arguments as yours. Is the command "patch" just a symlink to the apply one ? Why couldn't I execute the command "apply" even if the man file was readable ? |
Long term, seems one of two events need to occur?
1. The nvidia folks update 304.88 to 304.89. 2. When Slackware 14.1 is released officially, the slackbuilds.org 304.88 maintainer incorporates the ArchLinux patch into the build script. In the short term, adventurous 3.10.x users need to slip the ArchLinux patch into the slackbuilds.org build script? Does this make sense? |
Quote:
It should be patch Fixed now :) |
Quote:
|
Quote:
While here let me say THANKS for all your contributions - they are appreciated! |
Quote:
|
That depends on the maintainer if he has the hardware to install slackware 14.1
|
A new release of 304.108, but no new kernel support added
Quote:
|
Nvidia produces their Linux drivers in the first place for their workstation users, which mostly run RHEL on their machines. Seeing that RHEL 7 will be based on Fedora 19, which shipped with a 3.9.5 kernel, it is not very likely that there will be an update for newer kernels in the near future for the legacy drivers, unless Red Hat decides to ship a newer kernel.
|
Quote:
I'm using it now with kernel 3.10.6. m23 |
How You made it?
The patch not work.
I have Nvidia source 304.88 32-bit driver. After patching it i got: ERROR: Unable to build the NVIDIA kernel module. I have current kernel 3.10.9-smp 32-bit I tried patching several times. From http://bitc.bme.emory.edu/~lzhou/blogs/?p=379 i downloaded patched files to. Always error. I hate Nvidia. |
did you install the kernel-source package as well?
i have mine working nicely with 3.10.9 |
The patch does work, I'm running the blob at the moment on a 3.10 kernel
Code:
$ uname -r Code:
# lspci -k | grep -A2 VGA http://us.download.nvidia.com/XFree8...86-304.108.run //edit: Now running 304.108 - kernel module builds ok on 3.10 |
Yes :) 304.108 works fine.
Thanks! It's funny so Nvidia.com still recommends 304.88 for GeForce 7 Series on Linux 32-bit. |
I have NVidia 304.108 working with Linux Kernel 3.11 (only need one single patch). It's available on my SlackHacks if anyone is interested on building Linux Kernel 3.11
|
The above patch also works for nvidia-325.15 on 3.11.
I was planning to stay with 3.10.y this time, but O_TMPFILE looks really useful. |
Does the 304.108 release still need a patch for the 3.10.x kernel (which will be the kernel version released with 14.1)?
|
Quote:
|
Quote:
I would love to make this work in OpenMandriva 2013 Beta but I keep getting one of 2 results, This if I click on the patch and select to "Save As': Code:
# chmod a+x NVIDIA-Linux-x86_64-304.108.run Code:
NVIDIA-Linux-x86_64-304.108]$ patch -p1 < /home/dwight/Downloads/nvidia-3.11.patch Edit: Or is this patch only for x86 and I'm using x86_64? |
Use the raw version on my github repository
|
You also should be logged in as root or be running in superuser mode.
|
Try this one: nvidia-3.11.patch
|
Quote:
|
For those of you who still use older Nvidia cards and need the Nvidia driver if the nouveau driver is still a bit "weak," you should ping the Nvidia SBo script maintainer. He still maintains legacy173.xx, and legacy304.xx in addition to the latest long lived branch. Since he no longer has functional cards with older GPUs, it difficult to fully test those for script defects. Fighting to get buggy 13.37 or earlier scripts to work is a bit silly.
|
I still use the 304.xx sources. I have not yet tested in 14.1 but I will be doing that when I find time to start testing 14.1 (soon I hope!). I can't maintain the SBo build package but I will be among those who will continue testing and using simply out of need. Thus I will post comments and questions to the forum as needed.
Currently I'm using 304.108 on two 14.0 systems. No problems encountered but the 14.0 kernel does not require special attention or patching of the 304.xx sources. :) |
All times are GMT -5. The time now is 12:51 AM. |