nvidia-settings wrong resolution of external display

[Dag Rende]

Hi,

A new problem with Ubuntu 8.04 is that I can't use an external monitor any more. Something that worked in both 7.10 and 8.04 beta. I have tried the default open source nv driver and System>Preferences>Screen Resolution, and it sees that I have a sony external display, but all other functions fail, both cloned and not cloned.

I added the restricted nvidia driver using the System>Administration >Hardware Drivers dialog.
I added nvidia-settings package using synaptic.
I connected my Sony Bravia KDL-32U2000 (has a PC D-sub contact and resolution 1280x768))
I started nvidia-settings, saw the external display rectangle, selected it and chose Twinview.
Now the only seectable resolutions are 640x480 and 320x200. Normally this contains the full 1280x768 resolution.

-------------------
I have a Lenovo Thinkpad T61 type 6460-8NG with an Nvidia Quadro NVS 140M 512MB.
dag@tp:~$ apt-cache policy nvidia-settings
nvidia-settings:
  Installed: 1.0+20080304-0ubuntu1
  Candidate: 1.0+20080304-0ubuntu1
  Version table:
 *** 1.0+20080304-0ubuntu1 0
        500 http://se.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status
It reports nvidia driver 169.12

[Dag Rende (dag-s)]

I installed the package read-edid and got an interesting result below.
The result is the same using driver nv or restricted driver.

Edid result with the Sony display:
----------------------
dag@tp:~$ sudo get-edid|parse-edid
parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x11110 "NVIDIA"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination supports DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call failed

The EDID data should not be trusted as the VBE call failed
EDID claims 255 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
parse-edid: EDID checksum failed - data is corrupt. Continuing anyway.
parse-edid: first bytes don't match EDID version 1 header
parse-edid: do not trust output (if any).

 # EDID version 255 revision 255
Section "Monitor"
 Identifier "___:ffff"
 VendorName "___"
 ModelName "___:ffff"
 # DPMS capabilities: Active off:yes Suspend:yes Standby:yes

 Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
  DotClock 655.350000
  HTimings 4095 4350 4605 8190
  VTimings 4095 4158 4221 8190
  Flags "Interlace" "+HSync" "+VSync"
 EndMode
 Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
  DotClock 655.350000
  HTimings 4095 4350 4605 8190
  VTimings 4095 4158 4221 8190
  Flags "Interlace" "+HSync" "+VSync"
 EndMode
 Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
  DotClock 655.350000
  HTimings 4095 4350 4605 8190
  VTimings 4095 4158 4221 8190
  Flags "Interlace" "+HSync" "+VSync"
 EndMode
 Mode "4095x4095" # vfreq 9.770Hz, hfreq 80.018kHz
  DotClock 655.350000
  HTimings 4095 4350 4605 8190
  VTimings 4095 4158 4221 8190
  Flags "Interlace" "+HSync" "+VSync"
 EndMode
EndSection
--------------------------------
I also tried another external display - a Viewsonic VE710b, and it works as external display.

Edid from that display looks normal:

-----------------
dag@tp:~$ sudo get-edid|parse-edid
parse-edid: parse-edid version 1.4.1
get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x11110 "NVIDIA"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination supports DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE cal...

[Dag Rende (dag-s)]

.xsession_errors after
- booting
- connecting TV
- opening nvidia x server settings
- clicking detect displays
- select display and selecting twinview
- checking resolution choices (that are 640x480 and 320x200)

[Bryce Harrington (bryce)]

Hi dag-s,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

[abrichr (abrichr)]

I'm having similiar problems, but with Ubuntu 8.10.

I have an nVidia GeForce Go 7600 on a Compal HEL80 laptop. My external monitor is a Soyo Topaz S, with a native resolution of 1920x1200. The nv driver upon default install detects this without a problem.

I installed the nvidia-glx-177 driver through the Restricted Driver Manager. Upon reboot, my laptop's display was displaying correctly, but Nvidia-Xsettings shows a max resolution of 1360x768, which my monitor is unable to display correctly. I ran:

sudo dpkg-reconfigure -phigh xserver-xorg
sudo nvidia-xconfig

And received an error about the driver not being specified in the Device section. Upon restarting X, there was no change in Nvidia-Xsettings. I set it to 1024x768, which is displaying correctly.

I installed read-edid, and ran:

sudo get-edid > /tmp/get-edid.dat

I have attached the contents of get-edid.dat, as well as the output of lspci -vvnn.

I have also attached /var/log/Xorg.0.log.

I will attempt to fix this problem with Xrandr.

[abrichr (abrichr)]

Following the guide at https://wiki.ubuntu.com/X/Config/Resolution, I performed the following steps:

$ gtf 1920 1200 60

  # 1920x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 193.16 MHz
  Modeline "1920x1200_60.00" 193.16 1920 2048 2256 2592 1200 1201 1204 1242 -HSync +Vsync

$ xrandr --newmode "1920x1200_60.00" 193.16 1920 2048 2256 2592 1200 1201 1204 1242 -HSync +Vsync

$ xrandr --addmode 0x1ac 1920x1200_60.00

$ xrandr
Screen 0: minimum 320 x 240, current 1024 x 768, maximum 1920 x 1200
default connected 1024x768+0+0 0mm x 0mm
   1024x768 50.0*
   800x600 51.0 52.0 53.0
   680x384 54.0 55.0
   640x480 56.0
   576x432 57.0
   512x384 58.0
   400x300 59.0 60.0 61.0
   320x240 62.0
   1920x1200_60.00 60.0

$ xrandr --output 0x1ac --mode 1920x1200_60.00
xrandr: Configure crtc 0 failed

The resolution is now visible under System -> Preferences -> Screen Resolution, but selecting it and clicking "Apply" does nothing.

[abrichr (abrichr)]

I installed nvidia-glx-96, and ran sudo nvidia-xconfig --add-argb-glx-visuals -d 24. Now compiz runs at the full 1920x1200 resolution :)

[overtoperative (josh-baylor)]

I'd been having problems displaying to my Bravia from my Nvidia 8600GTS. I tried using the nvidia-xsettings tool to enable the TV, which was visible, but it would complain that the modeline was not valid. It looks like the virtual line in my screen section was preventing the nvidia-settings tool from working:

Virtual 1600 1200

I commented it out and was able to use all of the nvidia-settings options.

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.