Arch Linux

smilzoboboz

Member

Registered: 2010-06-01

Posts: 21

modes issue after nvidia 302.17 driver upgrade

I use a laptop with a nVidia GeForce 8400M GS video card.
Long time ago (290.xx drivers) I used to add custom modes (from modelines obtained with cvt) with xrandr.
Then I wasn't able to do that anymore and some display modes vanished from "xrandr -q" list, plus tty broke (but it's stated to be an upstream bug).
With 302.17 drivers I have only native mode:

$ xrandr
Screen 0: minimum 8 x 8, current 1440 x 900, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 367mm x 230mm
   1440x900       59.9*+
DVI-I-0 disconnected (normal left inverted right x axis y axis)

when I try so set a custom mode i get:

$ cvt 1440 900 60
# 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz
Modeline "1440x900_60.00"  106.50  1440 1528 1672 1904  900 903 909 934 -hsync +vsync
$ xrandr --newmode "1440x900_60.00"  106.50  1440 1528 1672 1904  900 903 909 934 -hsync +vsync
$ xrandr
Screen 0: minimum 8 x 8, current 1440 x 900, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 367mm x 230mm
   1440x900       59.9*+
DVI-I-0 disconnected (normal left inverted right x axis y axis)
  1440x900_60.00 (0x262)  106.5MHz
        h: width  1440 start 1528 end 1672 total 1904 skew    0 clock   55.9KHz
        v: height  900 start  903 end  909 total  934           clock   59.9Hz
$ xrandr --addmode LVDS-0 "1440x900_60.00"
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  153 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  29
  Current serial number in output stream:  30

Btw I already tried EDID override... (which resulted in a blank -black-, flickering screen no matter what custom modeline I put)

PS: I used 1440x900 to demonstrate that even if it's automatically set, it isn't recognized.

Gusar

Member

Registered: 2009-08-25

Posts: 3,607

Re: modes issue after nvidia 302.17 driver upgrade

Read the changelog of the driver, it's deliberate. I don't agree with it (and I'm not the only one), but going by the discussion at nvnews, the nvidia folks are working on some stuff. So we'll see what the 304 driver will bring.

Also, adding modes through the xrandr command-line utility isn't supported yet. That too is possibly material for the 304 driver. In the mean time there's MetaModes, read the documentation on how those work.

smilzoboboz

Member

Registered: 2010-06-01

Posts: 21

Re: modes issue after nvidia 302.17 driver upgrade

well, thanks, I actually didn't check the changelog...

I tried setting Metamodes (btw is usage that "simple" or I missed something?):

Option         "MetaModes"  "1440x900; 1280x800; 1152x720; 1024x640; 768x480; 576x360; 1024x768; 800x600; 640x480; 480x360"

but also that didn't work:

[  4158.743] (II) NVIDIA dlloader X Driver  302.17  Tue Jun 12 18:39:24 PDT 2012
[  4158.743] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  4158.747] (II) NVIDIA(0): Creating default Display subsection in Screen section
        "Screen0" for depth/fbbpp 24/32
[  4158.747] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[  4158.747] (==) NVIDIA(0): RGB weight 888
[  4158.747] (==) NVIDIA(0): Default visual is TrueColor
[  4158.747] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[  4158.747] (**) NVIDIA(0): Option "NoLogo"
[  4158.747] (**) NVIDIA(0): Option "TripleBuffer"
[  4158.747] (**) NVIDIA(0): Option "OnDemandVBlankInterrupts"
[  4158.747] (**) NVIDIA(0): Option "MetaModes" "1440x900; 1280x800; 1152x720; 1024x640; 768x480; 576x360; 1024x768; 800x600; 640x480; 480x360"
[  4158.747] (**) NVIDIA(0): Enabling 2D acceleration
[  4160.423] (II) NVIDIA(GPU-0): Display (LPL (DFP-0)) does not support NVIDIA 3D Vision
[  4160.424] (II) NVIDIA(GPU-0):     stereo.
[  4160.429] (II) NVIDIA(0): NVIDIA GPU GeForce 8400M GS (G86M) at PCI:1:0:0 (GPU-0)
[  4160.429] (--) NVIDIA(0): Memory: 524288 kBytes
[  4160.429] (--) NVIDIA(0): VideoBIOS: 60.86.51.00.42
[  4160.429] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[  4160.429] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[  4160.433] (--) NVIDIA(0): Valid display device(s) on GeForce 8400M GS at PCI:1:0:0
[  4160.433] (--) NVIDIA(0):     CRT-0
[  4160.433] (--) NVIDIA(0):     TV-0
[  4160.434] (--) NVIDIA(0):     LPL (DFP-0) (connected)
[  4160.434] (--) NVIDIA(0):     DFP-1
[  4160.434] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[  4160.434] (--) NVIDIA(0): TV-0: 400.0 MHz maximum pixel clock
[  4160.434] (--) NVIDIA(0): TV encoder: (null)
[  4160.434] (--) NVIDIA(0): LPL (DFP-0): 330.0 MHz maximum pixel clock
[  4160.434] (--) NVIDIA(0): LPL (DFP-0): Internal Dual Link LVDS
[  4160.434] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[  4160.434] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[  4160.434] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  4160.434] (**) NVIDIA(0):     device LPL (DFP-0) (Using EDID frequencies has been
[  4160.434] (**) NVIDIA(0):     enabled on all display devices.)
[  4160.434] (WW) NVIDIA(0): No valid modes for "1280x800"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "1152x720"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "1024x640"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "768x480"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "576x360"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "1024x768"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "800x600"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "640x480"; removing.
[  4160.435] (WW) NVIDIA(0): No valid modes for "480x360"; removing.
[  4160.435] (II) NVIDIA(0): Validated modes:
[  4160.435] (II) NVIDIA(0):     "1440x900"
[  4160.435] (II) NVIDIA(0): Virtual screen size determined to be 1440 x 900
[  4160.439] (--) NVIDIA(0): DPI set to (98, 99); computed from "UseEdidDpi" X config
[  4160.439] (--) NVIDIA(0):     option
[  4160.439] (--) Depth 24 pixmap format is 32 bpp
[  4160.439] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[  4160.455] (II) NVIDIA(0): Setting mode "1440x900"
[  4160.734] (II) Loading extension NV-GLX
[  4160.759] (==) NVIDIA(0): Disabling shared memory pixmaps
[  4160.759] (==) NVIDIA(0): Backing store disabled
[  4160.759] (==) NVIDIA(0): Silken mouse enabled
[  4160.760] (**) NVIDIA(0): DPMS enabled

I'll wait miracles on 304.xx drivers (:arr: if only nouveau was a little more fast... I play only a 11 years old 2D fighting game and with nouveau it doesn't reach 60fps)

Last edited by smilzoboboz (2012-06-20 09:56:37)

MrCode

Member

Registered: 2010-02-06

Posts: 373

Re: modes issue after nvidia 302.17 driver upgrade

Apologies for the (semi-)necrobump, but I'm having this exact same problem; 295.xx series = tons and tons of MetaModes; MetaModes galore, without even explicitly specifying them in 20-nvidia.conf!   302.xx series = 1366x768_60 +0+0…and that's it.  No extra MetaModes added in 20-nvidia.conf are registered by nvidia-settings.

EDIT: GPU is a GeForce 310M, laptop is a Samsung R580, if that's at all meaningful.

Last edited by MrCode (2012-06-28 02:20:39)

Gusar

Member

Registered: 2009-08-25

Posts: 3,607

Re: modes issue after nvidia 302.17 driver upgrade

Reposting the exact same thing I posted at the Gentoo forums yesterday :

Go to nvnews,net, there's several threads there discussing modes. Basically, the way modes are handled has changed significantly in the 3xx series of the driver, and some stuff isn't even complete yet, so it's a bit of a pain in the butt right now. But the threads at nvnews.net will give you pointers.

boomshalek

Member

Registered: 2007-10-12

Posts: 113

Re: modes issue after nvidia 302.17 driver upgrade

A workaround posted in nvnews.net worked for me:

In your xorg.conf or your  xorg.conf.d/...
you need to replace the @ of the modeline entries (i.e. aaaaxbbbb@60)  with _ (i.e. aaaaxbbbb_60).

EDIT: Source

Last edited by boomshalek (2012-07-10 09:21:11)