5

I go to the Displays, and the maximum resolution I have there is 1360x768 (16:9). However, on Windows 8.1 I can have the 1680x1050(16:10) resolution, without any type of problems. Because of this, I tried to add a custom resolution using xrandr:

xrandr --newmode "1680x1050_60.00"  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync

xrandr --addmode DVI-I-0 "1680x1050_60.00"

However, after typing the last command, this appears:

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:  39
 Current serial number in output stream:  40

I also typed xrandr, and I confirmed that DVI-I-0 is the only that says is connected:

Screen 0: minimum 8 x 8, current 1360 x 768, maximum 16384 x 16384
DVI-I-0 connected primary 1360x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00 +
   1360x768      59.96*   59.80  
   1152x864      60.00  
   800x600       72.19    60.32    56.25  
   680x384       59.96    59.80  
   640x480       59.94  
   512x384       60.00  
   400x300       72.19  
   320x240       60.05  
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
  1680x1050_60.00 (0x2ae) 146.250MHz
          h: width  1680 start 1784 end 1960 total 2240 skew    0 clock  65.29KHz
          v: height 1050 start 1053 end 1059 total 1089           clock  59.95Hz

Also, I'm running Ubuntu 15.10.

How can I have the 1680x1050(16:10) resolution? Thanks for any help you can give me.

EDIT: Forgot to say - Before Ubuntu, I had Linux Mint, where I also had the same problem. However as I said before, I don't have this problem on Windows.

EDIT2: On the following link there is the /var/log/Xorg.0.log file: http://pastebin.com/sjSLScjK , and also I have an ASUS Monitor.

1 Answers1

2

Ok, at the time of writing this answer, you don't have a menu bar, and I haven't seen your xorg.conf file yet, but I believe I know enough to know what you need to do, and I believe you will be able to make changes to your xorg.conf file from recovery mode if you can't do it in normal boot mode without a menu bar.

First of all, I believe the [ 28.338] (WW) NVIDIA: GPU:0: Unable to read EDID for display device DVI-I-0 warnings are significant, but I don't think anything is "wrong", more that it might be a limitation of your monitor, or VGA cables, or your computer, or some combination. My computer, VGA, TV combination also does not detect the EDID automatically.

Wikipedia has an entry on EDID that you may find a useful reference: https://en.wikipedia.org/wiki/Extended_Display_Identification_Data

You have already created an xorg.conf file, but for completeness I will include the steps in this answer. You follow Alexander Malakhov's answer in this question:

  1. Alt+Ctrl+F1 to switch to console mode
  2. Stop the X server by stopping the display manager: sudo service gdm stop (or sudo service lightdm stop if you have Lubuntu and/or LXDE environment).
  3. sudo X -configure to create an xorg.conf.new file
  4. sudo mv xorg.conf.new /etc/X11/xorg.conf to rename and move the file to where the xorg.conf goes
  5. sudo service gdm start or sudo service lightdm start to restart the display manager and X server. sudo start gdm and sudo start lightdm also work.

You now have the file /etc/X11/xorg.conf file. What it says now and what it should say depends on your own system. I shall share the relevant parts of my own xorg.conf file (correctly configured for my system) here and talk you through it.

But first, how to edit it? If everything is working correctly, then you can edit it by opening a terminal and typing sudo nano /etc/X11/xorg.conf. If you are having trouble editing it in normal boot mode, then you can edit it in recovery mode: start your computer, and from the grub boot menu, select "Advanced options", then the recovery mode of your most recent kernel, then select the root shell prompt. You will need to enter the command: mount -o remount,rw / to make everything read-write. Then you can edit the xorg.conf file with the command nano /etc/X11/xorg.conf (sudo is not needed in root shell prompt mode). (When you are done with root shell prompt, enter exit, then select "Resume normal boot", you might then need to reboot to see if changes have taken effect.)

This link gives helpful info on recovery mode.

Here are the relevant parts of my xorg.conf file, yours may differ. You can access the xorg.conf manual by typing man xorg.conf into a terminal, or you can find it in several places on the internet, like here. There is also an Ubuntu wiki on it here.

Section "Monitor"
    Identifier   "Monitor0"
    VendorName   "Monitor Vendor"
    ModelName    "Monitor Model"
        HorizSync       28.0 - 83.0
        VertRefresh     56.0 - 75.0
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "SWcursor"              # [<bool>]
        #Option     "kmsdev"                # <str>
        #Option     "ShadowFB"              # [<bool>]
    Identifier  "Card0"
    Driver      "sis"
    BusID       "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    SubSection "Display"
        Viewport   0 0
        Depth     1
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     4
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     8
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     15
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
                 Modes     "1360x768"
    EndSubSection
EndSection

I believe you would have the correct Driver in your Section "Device", yours should be something like nvidia.

Next, let's look at Section "Screen". You may, like me, have a number of subsections, in which case the only one you need to worry about is the Depth 24 subsection. Insert the line:

Modes "1680x1050"

into that subsection. Your computer was not able to determine the screen size using EDID, so we are manually telling the computer what the screen size is.

I believe this is the change you need to make to get it working. Reboot the machine and see if the resolution is fixed.

There is a chance you may need to make a further change: in the Section "Monitor" section, you can see HorizSync and VertRefresh lines in my xorg.conf. You may also need these lines in yours. However, the range you need to specify for both lines depends on your monitor. If you have the manual for your monitor, look in the "specifications" towards the back of the manual. If you do not have the manual, ASUS appear to provide them on their website, but I do not know the model name/number of your monitor. You may be able to get the model name/number from a sticker on the back of the monitor.

Somewhere in the Specifications section of the manual is a tabulated list of resolutions, and corresponding horizontal and vertical values. You want the HorizSync range to include all horizontal values for every resolution that you might use: find the lowest value in the list and make that the lower limit, and make the upper limit the same as the highest value in the list. Likewise, with the VertRefresh, use the lowest and highest values in the Vertical column (an ASUS manual I have picked at random just calls this "Refresh Rate"). If you add the HorizSync and VertRefresh lines, then save and reboot to see if this fixes the problem.

Please do share by comment, at which point, if any, the resolution issue is fixed. If it is still not fixed, we may need to look at your /etc/X11/xorg.conf and /var/log/Xorg.0.log files again.