Linux x64 (AMD64/EM64T) Display Driver

M. Schmitt
M. Schmitt
Joined: 27 Jun 05
Posts: 478
Credit: 15872262
RAC: 0
Topic 196492

save 304.37 Certified?

Best regards
from Michael

Michael Karlinsky
Michael Karlinsky
Joined: 22 Jan 05
Posts: 888
Credit: 23502182
RAC: 0

Linux x64 (AMD64/EM64T) Display Driver

Quote:

save 304.37 Certified?

Best regards
from Michael

You mean, is it save to install 304.37? Don't know, I use 295.71 which fixes the privilege escalation issue.

KR
Michael

M. Schmitt
M. Schmitt
Joined: 27 Jun 05
Posts: 478
Credit: 15872262
RAC: 0

That's what I use 295.71 too,

That's what I use 295.71 too, but it shows only 2 WU,s on my GTX 570 oc2.

See here

Khangollo
Khangollo
Joined: 17 Feb 11
Posts: 42
Credit: 928047659
RAC: 0

RE: That's what I use

Quote:
That's what I use 295.71 too, but it shows only 2 WU,s on my GTX 570 oc2.


Use value 0.333333 for "GPU utilization factor" in E@H Preferences and it will be running 3 after a project update or two.
I'm running 3 on GTX 570 and 295.71 (and before 295.71 as well).

And I'm not really inclined to upgrade drivers, too. If it works - don't touch it - is what I've learned so far with drivers the hard way.

MaU38.gif

M. Schmitt
M. Schmitt
Joined: 27 Jun 05
Posts: 478
Credit: 15872262
RAC: 0

X11 is running here, that's

X11 is running here, that's my main working host so I cant switch X11 of.

May be I try it on my 6-core AMD. My GFX in there is a 460 oc2, with one GIG of RAM. I have a script that I can run without X11.

I'm curious about drivers too.

Michael Karlinsky
Michael Karlinsky
Joined: 22 Jan 05
Posts: 888
Credit: 23502182
RAC: 0

RE: X11 is running here,

Quote:

X11 is running here, that's my main working host so I cant switch X11 of.

May be I try it on my 6-core AMD. My GFX in there is a 460 oc2, with one GIG of RAM. I have a script that I can run without X11.

I'm curious about drivers too.

Hallo Micha,

ich bin mir nicht ganz im Klaren, worauf Du hinaus willst. Ein Treiber-Upgrade wird nicht dazu führen, dass du mehr WUs pro Karte laufen lassen kannst. Mehr als zwei WUs + X ist aus meiner Erfahrung nicht möglich.

Was den Treiber 304.37 angeht, denke ich wird dieser klaglos funktionieren -- denke ich -- allerdings ist ein Upgrade auch nicht nötig, wenn die neuen Features, bzw. Bug-Fixes nicht genutzt werden.

Meine Strategie ist, immer dann den Update durchzuführen, wenn die Distri einen Kernel-Update zur Verfügung stellt. Dann muss ich den Treiber ja sowieso neu kompileren, dann kann ich auch gleich den neuen nehmen.

Grüße,
Michael

PS: gut zu wissen:

"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."

M. Schmitt
M. Schmitt
Joined: 27 Jun 05
Posts: 478
Credit: 15872262
RAC: 0

RE: RE: X11 is running

Quote:
Quote:

X11 is running here, that's my main working host so I cant switch X11 of.

May be I try it on my 6-core AMD. My GFX in there is a 460 oc2, with one GIG of RAM. I have a script that I can run without X11.

I'm curious about drivers too.

Hallo Micha,

ich bin mir nicht ganz im Klaren, worauf Du hinaus willst. Ein Treiber-Upgrade wird nicht dazu führen, dass du mehr WUs pro Karte laufen lassen kannst. Mehr als zwei WUs + X ist aus meiner Erfahrung nicht möglich.

Das glaube ich auch nicht.

Quote:

Was den Treiber 304.37 angeht, denke ich wird dieser klaglos funktionieren -- denke ich -- allerdings ist ein Upgrade auch nicht nötig, wenn die neuen Features, bzw. Bug-Fixes nicht genutzt werden.

Meine Strategie ist, immer dann den Update durchzuführen, wenn die Distri einen Kernel-Update zur Verfügung stellt. Dann muss ich den Treiber ja sowieso neu kompileren, dann kann ich auch gleich den neuen nehmen.

Ich habe mir schon mal mit Dem Distritube Treiber das ganze System zerschossen, daher installiere ich die eher von der Nvidia-Seite.

Quote:

Grüße,
Michael

PS: gut zu wissen:

Quote:
"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."

Das DKMS Modul ist bei mir installiert. Das funktioniert aber nicht. Ich kann jedesmal DKMS installieren, oder so was mit Update machen...
Das passt sich keinem neuen Kernel an. Und dann muss ich VirtualBox neu installieren.

Quote:

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

Deswegen will ich's ja auf meinem 6-Core AMD probieren, den kann ich OHNE X11 laufen lassen.

siehe hier

SJC_Steve
SJC_Steve
Joined: 20 Jul 11
Posts: 28
Credit: 519973212
RAC: 418841

Khangollo wrote; RE: Use

Khangollo wrote;

Quote:
Use value 0.333333 for "GPU utilization factor" in E@H Preferences and it will be running 3 after a project update or two.
I'm running 3 on GTX 570 and 295.71 (and before 295.71 as well).

I'm running a GT 640 and BOINC shows only 1 WU on the GPU. My E@H Preferences don't have a "GPU utilization factor".

I'm using;
Ubuntu 12.04 LTS
BOINC 7.0.27 (x86)
Nvidia Driver 295.40

Thanks for any advise,
Steve

Michael Karlinsky
Michael Karlinsky
Joined: 22 Jan 05
Posts: 888
Credit: 23502182
RAC: 0

RE: Khangollo

Quote:
Khangollo wrote;
Quote:
Use value 0.333333 for "GPU utilization factor" in E@H Preferences and it will be running 3 after a project update or two.
I'm running 3 on GTX 570 and 295.71 (and before 295.71 as well).

I'm running a GT 640 and BOINC shows only 1 WU on the GPU. My E@H Preferences don't have a "GPU utilization factor".

I'm using;
Ubuntu 12.04 LTS
BOINC 7.0.27 (x86)
Nvidia Driver 295.40

Thanks for any advise,
Steve

Did you check here: http://einstein.phys.uwm.edu/prefs.php?subset=project?

Michael

M. Schmitt
M. Schmitt
Joined: 27 Jun 05
Posts: 478
Credit: 15872262
RAC: 0

Linux x64 (AMD64/EM64T)

Linux x64 (AMD64/EM64T) Display Driver NVIDIA Empfehlung 295.75 31.8.2012

This driver runs like a charm.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.