You are not logged in.
Hi,
After upgrading to nvidia-319.17 and linux-3.9.2-1-ARCH and rebooting, I tried to run a windows game (Orbiter) in wine, and resolution dropped to 1024x768, even though the game was configured to run at my screen resolution 1600x900. I tried changing back in nvidia-settings, but it doesn't list resolutions higher than 1024x768 any more. I also tried the method in Arch Wiki for xrandr, with the modeline:
"1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
When I try to add it to my current display, however:
$ xrandr --addmode DVI-I-0 1600x900_60.00
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 35
Current serial number in output stream: 36
$
Any ideas on how to fix my resolution back to 1600x900 are welcome.
Thanks!
EDIT: Tried rolling back to nvidia-*313 and kernel-3.8.8-2, didn't help at all.
EDIT1: Tried rolling back to nvidia-304xx-* with kernel-3.9.2-1 to use onboard GeForce 6150SE instead of my PCIe GTX 650, didn't help either.
EDIT2: Tested the monitor with another system, does 1600x900 without any problems, and that shows up on xrandr too, unlike on the system with the problem, where I can't set the resolution with xrandr.
Last edited by SgrA (2013-05-14 16:51:13)
Offline
I play wine games in a separate X, so in case something like this happens, I just restart the X server. This brute-force approach has always fixed my issues.
Offline
Can reset the screen, e.g.:
# Old: nvidia-settings --assign CurrentMetaMode='DFP-0: 1920x1080'
nvidia-settings --assign CurrentMetaMode="DFP-0: 1920x1080 { ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0 }"
# To reset e.g. brightness
nvidia-settings --load-config-only
For convenience, put that in a script to be executed by xbindkeys, e.g. in ~/.xbindkeysrc:
"nvidia-settings --assign CurrentMetaMode='DFP-0: 1920x1080'"
Alt+Control+Shift + r
Running in a separate X session is also doable. It depends on whether one wants e.g. Skype conversations to interrupt the game
Edit: Changed the nvidia-settings line.
Last edited by brebs (2014-08-09 20:34:45)
Offline
nvidia-settings --assign CurrentMetaMode='DFP-0: 1920x1080' # To reset e.g. brightness nvidia-settings --load-config-only
I tried that, but with 'CRT-0: 1600x900' to suit my current configuration, but it didn't do anything, nor did it spit out any errors.
Offline
$ xrandr
Screen 0: minimum 8 x 8, current [b]1024 x 768[/b], maximum 16384 x 16384
DVI-I-0 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.0*+
800x600 72.2 60.3 56.2
640x480 59.9
512x384 60.0
400x300 72.2
320x240 60.1
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
$ xrandr --output DVI-I-0 --fb [b]1600x900[/b]
xrandr
Screen 0: minimum 8 x 8, current [b]1600 x 900[/b], maximum 16384 x 16384
DVI-I-0 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1024x768+0+0
1024x768 60.0*+
800x600 72.2 60.3 56.2
640x480 59.9
512x384 60.0
400x300 72.2
320x240 60.1
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
$
But the actual screen size doesn't increase. Instead, the screen area becomes scrollable, and scrolls around when I move the mouse around edges.
Offline
I had the same problem, I workarounded changing the resolution BEFORE starting the game and putting it correctly after. Just write a little bash script like:
xrandr -s 1024x768
start the game
xrandr -s 0
Offline
The system was not able to read the monitor's EDID. The VGA cable from the monitor to a VGA-DVI adapter connected to my graphics card was replaced with a real DVI cable, and this fixed the problem. The fact that EDID was not being read was clear after going through /var/log/Xorg.0.log, which had several messages about it.
Marked as solved, thanks everyone for their time.
Offline