Nvidia Driver 304.37 Installation

Screen resolution, 3D Acceleration, nVidia, ATI
Forum rules
Before you post please read this
Post Reply
User avatar
Rudemeister
Level 3
Level 3
Posts: 165
Joined: Sat May 09, 2009 7:24 am

Nvidia Driver 304.37 Installation

Post by Rudemeister »

Open the terminal under Ubuntu 12.10/12.04/11.10/Linux Mint 13 or older and install the Nvidia driver with these commands:

sudo apt-add-repository ppa:xorg-edgers/ppa
sudo apt-get update
sudo apt-get install nvidia-current nvidia-settings

Then reboot your system to finish the installation.

Works for me!!!

:D
HP XW8600 Work Station
Dual Quad-Core 3Ghz Xeon CPU's
32GB PC2-5300 ECC DRAM
Nvidia GT520 2G GDDR3 Graphics
2TB Seagate Barracuda 7200 RPM
Linux Mint 16 KDE 64-bit
Windows 7 Professional 64-bit

User avatar
Rudemeister
Level 3
Level 3
Posts: 165
Joined: Sat May 09, 2009 7:24 am

Re: Nvidia Driver 304.37 Installation

Post by Rudemeister »

Added support for the following GPUs:

GeForce GTX 680M
Quadro K1000M
Quadro K2000M
Tesla K10

Removed the ability to enable SLI on GPUs with ECC enabled.
Fixed several bugs that prevented some RandR transform geometries from being applied.
Fixed a bug that caused frequent hangs or crashes on some systems.
Fixed a bug that would cause corruption and performance issues in certain OpenGL applications such as Amnesia: The Dark Descent on GeForce 6 and 7 GPUs.
Fixed a bug that caused applications that use DirectColor visuals, such as Enemy Territory: Quake Wars and Braid, to appear in shades of blue instead of the correct colors.
Modified handling of RRSetScreenSize requests to ignore requests that do not actually resize the screen.This reduces screen flicker in certain cases when using GNOME.
Added a new option, "--disable-nouveau" to nvidia-installer. This option changes the action that is chosen by default when Nouveauis detected by nvidia-installer. If the "--disable-nouveau" optionis set, then the default will be to attempt to disable Nouveau when it is detected; otherwise, no attempt will be made unless requested.
Added support for xserver ABI 13 (xorg-server 1.13).
Added support for RandR per-CRTC gamma manipulation through the RandR 1.2 RRGetCrtcGammaSize, RRGetCrtcGamma, and RRSetCrtcGamma requests.
Fixed a bug that caused RRSetOutputPrimary requests to incorrectly generate BadValue errors when setting the primary output to None.This caused gnome-settings-daemon to crash after changing the screen configuration in response to a display hotplug or the display change hot-key being pressed.
Fixed a problem where RENDER Glyphs operations would exhibit severe performance issues in certain cases, such as when used with gradients by Cairo and Chromium.
Fixed a bug that caused X to hang when resuming certain DisplayPort display devices (such as Apple brand mini-DisplayPort to dual-link DVI adapters) from power-saving mode.
Fixed a bug that caused an X screen to be extended to Quadro SDI Output devices by default. An X screen will still use an SDI Output device if it is the only display device available. To use a SDI Output device on an X screen with other display devices available, include the SDI Output device with either the "UseDisplayDevice" or "MetaMode" X configuration options.
Updated X11 modeline validation such that modes not defined in a display device's EDID are discarded if the EDID 1.3 "GTF Supported" flag is unset or if the EDID 1.4 "Continuous Frequency" flag is unset. The new "AllowNonEdidModes" token for the ModeValidationX configuration option can be used to disable this new check.
Fixed a bug, introduced in the 295.xx release series, with EDID detection on some laptop internal panels. This bug caused the laptop internal panel to show six small copies of the desktop.
Added support for FXAA, Fast Approximate Anti-Aliasing. Using regular anti-aliasing modes or Unified Back Buffers with FXAA is not currently supported.
Enhanced the functionality of the IncludeImplicitMetaModes X configuration option: Implicit MetaModes will be added for the primary display device, even if multiple display devices are in use when X is initialized.

Implicit MetaModes will be added for common resolutions, even
if there isn't a mode with that resolution in the mode pool of
the display device.

Extended the syntax of the IncludeImplicitMetaModes X
configuration option, e.g., to control which display device is
used for creation of implicit MetaModes.

See the description of the IncludeImplicitMetaModes X configuration
option in the README for details.

Modified the handling of the RandR 1.0/1.1 requests RRGetScreenInfo and RRSetScreenConfig (e.g., `xrandr -q --q1` and `xrandr --size ...` and `xrandr --orientation ...`) such that they operate on MetaModes. This was the behavior in NVIDIA X driver versions 295.xx and earlier, but 302.xx releases altered the handling of these RandR 1.0/1.1 requests to operate on a single RandR output's modes.
With the above changes to IncludeImplicitMetaModes and RandR 1.0/1.1 handling, fullscreen applications (e.g., SDL-based applications, Wine), should have more resolutions available to them, and should interact better with multiple monitor configurations.
Fixed a bug that could cause G8x, G9x, and GT2xx GPUs to display a black screen or corruption after waking up from suspend.
Fixed several bugs that could cause some OpenGL programs to hang when calling fork(3).
Fixed an nvidia-settings bug that caused the results of ProbeDisplays queries made with the --display-device-string option to be formatted incorrectly.
Improved the responsiveness of updates to the nvidia-settings control panel when displays are hotplugged.
Fixed a bug that caused display corruption when setting some transforms, especially when panning a transformed display.
Fixed a bug that caused extra RandR events to be generated the first time a display is hotplugged.
Fixed a bug that caused X11 modelines with '@' in their names to be rejected.
Added support for DisplayPort 1.2 branch devices, which allow multiple displays to be connected to a single DisplayPort connector on a graphics board.
Fixed a bug that caused most OpenGL texture uploads to be slow when the context was bound rendering to an RGB overlay drawable.
Fixed a bug that caused audio over HDMI to not work after restarting the X server on some MCP7x (IGP) GPUs.
Updated the X configuration option "UseDisplayDevice" to honor the value "none" on any GPU.
Added support for DKMS in nvidia-installer. Installing the kernel module through DKMS allows the module to be rebuilt automatically when changing to a different Linux kernel. See the README and the nvidia-installer help text for the "--dkms" option.
Added RandR output properties _ConnectorLocation, ConnectorNumber, ConnectorType, EDID, _GUID, and SignalFormat. See the README for details on these properties.
Extended support for Base Mosaic to all G80+ SLI configurations with up to three displays.
Fixed a bug that caused some monitors to fail to wake from DPMS suspend mode when multiple DisplayPort monitors were attached to one GPU.
Removed controls for XVideo attributes from the "X Server XVideo Settings" page of the nvidia-settings control panel. XVideo attributes can be configured in XVideo player applications, or through utilities such as xvattr.
Fixed a bug that caused all ports on an XVideo adaptor to share color correction settings.
Removed support for the following X configuration options:

SecondMonitorHorizSync
SecondMonitorVertRefresh

Similar control is available through the NVIDIA HorizSync and
VertRefresh X configuration options. Please see the NVIDIA driver
README for details.

Fixed a bug that prevented NVIDIA 3D Vision Pro from working properly when switching between X servers on different VTs.
Added support for desktop panning when rotation, reflection, or transformation is applied to a display device (either through RandR or through the MetaMode syntax); panning would previously be ignored in that case.
Implemented hotfix for a privilege escalation vulnerability reported on August 1, 2012. For more details, see:
http://nvidia.custhelp.com/app/answers/detail/a_id/3140
HP XW8600 Work Station
Dual Quad-Core 3Ghz Xeon CPU's
32GB PC2-5300 ECC DRAM
Nvidia GT520 2G GDDR3 Graphics
2TB Seagate Barracuda 7200 RPM
Linux Mint 16 KDE 64-bit
Windows 7 Professional 64-bit

nomko

Re: Nvidia Driver 304.37 Installation

Post by nomko »

Just a link to the launchpad site would be more than enough :wink:

Another good PPA for NVidia drivers is the x-swat PPA: https://launchpad.net/~ubuntu-x-swat/+a ... x-updates/

The PPA you mention is more bleeding edge and upstream. For regular users who wants a stable system the x-swat PPA is more appropriate.

rootkowski
Level 3
Level 3
Posts: 110
Joined: Tue Jun 26, 2007 5:06 am
Location: Wirral, UK
Contact:

Re: Nvidia Driver 304.37 Installation

Post by rootkowski »

Just wondering, did anyone had any issues with the latest driver installation?

Until last Friday I was running my Mint 13 Cinnamon on the stock driver but since there was a new version from Nvidia I decided to install the proprietary driver instead and get ready for some weekend gaming! I wanted to make the installation simple for myself so I opened Additional Drivers app to do it for me. But after downloading the driver it always failed to install it properly (I can't remember what it was complaining about now sorry). So I thought I'd be tricky and disabled the ppa (x-swat), installed the driver version that comes in the repos by default (295.40) rebooted and all was fine. Then I re-enabled the ppa and updated the driver. And that turned out to be a mistake. After the next reboot no X! I went CTRL+Alt+1 and tried a few things (among else startx, but it was complaining that the nvidia driver was missing its kernel module!), but ended up uninstalling the nvidia driver. After that I had X running on VESA which was rather awful, but then I disabled x-swat again and re-installed the nvidia driver 295.40 and that's what I'm running now.

So it wasn't a huge problem to solve, but I was very surprised it even occurred! I've never had issues with nvidia drivers and suddenly this. I might feel a bit more adventurous today and try installing the update again, but I'm not so sure. Any thoughts anyone? :)

User avatar
Rudemeister
Level 3
Level 3
Posts: 165
Joined: Sat May 09, 2009 7:24 am

Re: Nvidia Driver 304.37 Installation

Post by Rudemeister »

Hmmm. The only drivers I have ever had problems with were the Windows drivers. I also know that when I had downloaded the Linux driver direct from Nvidia and tried to do their installation instructions to do the "run" file, it did not work either. But the extra drivers and the PPA drivers have been flawless for me. I have a Nvidia Quadro NVS 510M in an HP laptop with a dual core processor and 4GB of ram. What hardware do you have?
HP XW8600 Work Station
Dual Quad-Core 3Ghz Xeon CPU's
32GB PC2-5300 ECC DRAM
Nvidia GT520 2G GDDR3 Graphics
2TB Seagate Barracuda 7200 RPM
Linux Mint 16 KDE 64-bit
Windows 7 Professional 64-bit

GeneC
Level 7
Level 7
Posts: 1598
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: Nvidia Driver 304.37 Installation

Post by GeneC »

rootkowski wrote:.........Then I re-enabled the ppa (X-SWAT)and updated the driver. And that turned out to be a mistake. After the next reboot no X! ............ Any thoughts anyone? :)
I had the same.
Thought to run

Code: Select all

sudo nvidia-xconfig
Re-boot.
That worked for me.

rootkowski
Level 3
Level 3
Posts: 110
Joined: Tue Jun 26, 2007 5:06 am
Location: Wirral, UK
Contact:

Re: Nvidia Driver 304.37 Installation

Post by rootkowski »

I have a gtx 460, with i5 760, 8GB RAM, OCZ Vertex3.

I'll have another go at updating the drivers now, just have to remember the command for nvidia-xconfig ;)

Will report back soon!

rootkowski
Level 3
Level 3
Posts: 110
Joined: Tue Jun 26, 2007 5:06 am
Location: Wirral, UK
Contact:

Re: Nvidia Driver 304.37 Installation

Post by rootkowski »

Well, this time it just worked! No fixes necessary. That's good news I suppose :)

The only thing I did since re-installing the 295.40 version on Friday was to save settings to X configuration file from within the nvidia settings app. Maybe that made all the difference. Though on the other hand when it failed it was complaining about kernel module and not about misconfigured X. Computers are great when they choose to do their own thing for no apparent reason lol

Thanks for all the help!

User avatar
Rudemeister
Level 3
Level 3
Posts: 165
Joined: Sat May 09, 2009 7:24 am

Re: Nvidia Driver 304.37 Installation

Post by Rudemeister »

After I did this installation of the 304.37 Nvidia drivers, I decided to see what would happen if I did this:

sudo apt-get update
sudo apt-get dist-uprgrade

Lo and behold! My kernel was also upgraded to 3.5.0-10-Generic. I'm not sure what the results of doing this would be. This is the same kernel that is going into Ubuntu 12.10 Quantal Quetzal. So I looked up this kernel and here is what I found:

http://www.h-online.com/open/features/W ... 37461.html

I'll let you know what my experience is in using this. I did it on my laptop and my desktop too. Both machines have had Linux Mint 13 KDE 32-bit installed.
HP XW8600 Work Station
Dual Quad-Core 3Ghz Xeon CPU's
32GB PC2-5300 ECC DRAM
Nvidia GT520 2G GDDR3 Graphics
2TB Seagate Barracuda 7200 RPM
Linux Mint 16 KDE 64-bit
Windows 7 Professional 64-bit

User avatar
Oscar799
Level 19
Level 19
Posts: 9928
Joined: Tue Aug 11, 2009 9:21 am
Location: United Kingdom

Re: Nvidia Driver 304.37 Installation

Post by Oscar799 »

Moved here by moderator
Image

Post Reply

Return to “Graphics Cards & Monitors”