How To Set Resolution to 1680x1050 on Ubuntu

inoculos · 11-12-2011, 08:57 PM

You want the latest nvidia driver, Im kinda bogged down right now but hit alt f2 and type nvidia-settings and see if you have an option for your resolution there. If not you will have to add it to a configuration file before it shows up. Hopefully tomorrow I will be able to be of more help, sorry.

can you post the outcome of xrandr?

in a terminal type in xrandr, then copy and paste the output here'.

im just leaving all this below so I can find it later, it is a work report I made about adding resolution to a comp at work on fedora 14. It is the manual way to add a resolution, look through it and see if any of it makes sense.

I The Steps I used to add 1280x720 resolution to fedora14 on Seattle 155 and a high res Samsung PN43D490A1D Plasma HD TV

1) I obtained the desired resolution from google
2) This was used with the cvt command to obtain a modeline
3) the modeline info was used with the xrandr command(s)
4) after verifying that the commands work they are added to the
/etc/gdm/Init/default file at the bottom before exit 0

This method works in the way adding modes to the xorg.conf used to work. I also attempted to create an xorg.conf file but this resulted in a complete os lockup. init 3, gdm stop, etc all resulted in a lockup, therefore X -configure could not be used to create an xorg.conf file. I found another method which worked. This is in part II. Even though the xorg.conf creation worked my editing of it caused a complete os lockup.

A summary of the struggle follows with the successful method in part III

nisuser@seattle155 ~]$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 4096 x 4096
VGA1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 933mm x 532mm
1024x768 60.0 + 75.1 70.1
832x624 74.6
800x600 72.2 75.0 60.3
640x480 72.8 75.0 66.7 60.0
720x400 70.1
cvt 1280 720
[nisuser@seattle155 ~]$ cvt 1280 720
# 1280x720 59.86 Hz (CVT 0.92M9) hsync: 44.77 kHz; pclk: 74.50 MHz
Modeline "1280x720_60.00" 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync
[nisuser@seattle155 ~]$ xrandr --newmode "1280x720_60.00" 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync
[nisuser@seattle155 ~]$ xrandr --addmode VGA1 1280x720_60.00
[nisuser@seattle155 ~]$ xrandr --output VGA1 --mode 1280x720_60.00

the working commands that need to be added to the startup script:

xrandr --newmode "1280x720_60.00" 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync

xrandr --addmode VGA1 1280x720_60.00

xrandr --output VGA1 --mode 1280x720_60.00

II How to create xorg.conf

From FedoraProject
Jump to: navigation, search

Fedora releases since Fedora 10 do not create a /etc/X11/xorg.conf file, used to configure the X server, by default. The X configuration is automatically determined each time X is started. In most cases, this works well and there is no need to manually specify X configuration information.

If you need to make manual changes to X configuration for any reason, you will first need to create a /etc/X11/xorg.conf file.
Xorg -configure

You can create a basic xorg.conf using the X executable itself. As root run:

Xorg :1 -configure

This will create the file /root/xorg.conf.new, which you can then copy to /etc/X11/xorg.conf:

cp -r /root/xorg.conf.new /etc/X11/xorg.conf

Even though I was able to create the xorg.conf, adding the mode line resulted in complete os lockup

III Successful method: Best results were from adding the following to the bottom of
/etc/gdm/Init/Default
just before exit 0

xrandr --newmode "1280x720_60.00" 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync
xrandr --addmode VGA1 1280x720_60.00
xrandr --output VGA1 --mode 1280x720_60.00

After all this Jesse pointed out that the vid card age was probably to blame for all this.
The End

cascade9 · 11-13-2011, 03:50 AM

Quote:

Originally Posted by phdam8

Are they on the additional drivers in the system settings menu?

Yes, they should be.

Quote:

Originally Posted by inoculos

I recommend reading through this as well

https://help.ubuntu.com/community/Bi...erHowto/Nvidia

A uselful link for a newbie to ubuntu....I wonder if phdam8 even looked at it.

Quote:

Originally Posted by phdam8

Oh, just to add, I see many proprietary drivers to download, but which one do I download? Can I download multiples of them?

Dont. Just dont. Having different versions of the nVidia drivers (eg nvidia-current and nvidia-173) can lead to all sorts of stupid problems.

Its a lot easier to use 'jockey' (additional drivers in system settings menu) to get the nVidia drivers with ubuntu and sodding around with synaptic.

RockDoctors idea to create an xorg.conf file is good. IIRC there are some issues with the GF 7025 onboard video and the nvidia drivers.

BTW, the most likely cause of your (and RockDoctors) problem is EDID (Extended display identification data). Some monitors and/or monitor/video card setups means that the system cant get the EDID and so the display is limited to XXXXxXXX resolution.

RockDoctor · 11-13-2011, 07:09 AM

I know my system's problem is an imporoper EDID from the monitor. And I've got a bunch of

Code:

Nov 13 07:06:56 Pyrope kernel: [ 5590.265012] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 74
Nov 13 07:06:56 Pyrope kernel: [ 5590.265014] Raw EDID:
Nov 13 07:06:56 Pyrope kernel: [ 5590.265016]  	c0 16 10 1e 01 18 02 14 00 4f 04 20 07 10 14 00
Nov 13 07:06:56 Pyrope kernel: [ 5590.265018]  	4f 11 01 03 08 2f 1e 78 0a b5 34 a5 56 4a 9a 25
Nov 13 07:06:56 Pyrope kernel: [ 5590.265020]  	10 50 54 af cf 00 81 80 81 8f 95 00 95 0f 01 01
Nov 13 07:06:56 Pyrope kernel: [ 5590.265022]  	01 01 01 01 01 01 1c 39 90 30 62 1a 27 40 68 b0
Nov 13 07:06:56 Pyrope kernel: [ 5590.265024]  	36 00 d9 28 11 00 00 18 00 00 00 fe 00 0a 20 20
Nov 13 07:06:56 Pyrope kernel: [ 5590.265026]  	20 20 20 20 20 20 20 20 20 20 00 00 00 fc 00 4d
Nov 13 07:06:56 Pyrope kernel: [ 5590.265028]  	42 57 2d 53 45 52 49 41 4c 0a 20 20 00 00 00 ff
Nov 13 07:06:56 Pyrope kernel: [ 5590.265030]  	00 0a 20 20 20 20 20 20 20 20 20 20 20 20 00 33

blocks (with different timestamps, of course) in /var/log/messages to prove it