[Intrepid] nVidia NV25 [GeForce4 Ti 4600] displays slightly offset

[Aaron Whitehouse]

Binary package hint: xorg

I am testing the Intrepid Alpha 4 live CD on my HTPC with an nVidia NV25 [GeForce4 Ti 4600].

The Samsung 1360x768 LCD TV and Dell LCD monitor work at the correct resolution and seem fine, but are about 10-15 pixels offset to the right (the running green "logout" man cuts of on the inside of his front leg). Taking a screen capture works correctly and is not offset.

The following modelines are reported in xorg.0.log:
$ grep 1360 /var/log/Xorg.0.log
(II) NV(0): h_active: 1360 h_sync: 1424 h_sync_end 1536 h_blank_end 1792 h_border: 0
(II) NV(0): Modeline "1360x768"x0.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz)
(II) NV(0): Estimated virtual size for aspect ratio 1.7800 is 1360x768
(II) NV(0): Not using default mode "1360x768" (monitor doesn't support reduced blanking)
(--) NV(0): Virtual size is 1360x768 (pitch 1360)
(**) NV(0): *Driver mode "1360x768": 85.5 MHz, 47.7 kHz, 60.0 Hz
(II) NV(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz)
(**) NV(0): *Default mode "1360x768": 84.8 MHz, 47.7 kHz, 59.8 Hz
(II) NV(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz)

Please let me know if there is anything that I can send to help out.

[lspci]
00:00.0 Host bridge: Intel Corporation 82850 850 (Tehama) Chipset Host Bridge (MCH) (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4600] (rev a3)

[Aaron Whitehouse (aaron-whitehouse)]

I just tested this with another LCD screen and it is offset by the same amount, so it will be the graphics card driver rather than the screen (which makes sense). It's an:
nVidia Corporation NV25 [GeForce4 Ti 4600]

lspci output attached.

[Aaron Whitehouse (aaron-whitehouse)]

Note that the proprietary drivers in Hardy work correctly (not offset).

[Aaron Whitehouse (aaron-whitehouse)]

Tested with Alpha 6 and this is still a problem.

[Aaron Whitehouse (aaron-whitehouse)]

As filed in Launchpad:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/262857

Binary package hint: xorg

I am testing the Intrepid Beta live CD on my HTPC with an nVidia NV25 [GeForce4 Ti 4600].

The Samsung 1360x768 LCD TV and Dell LCD monitor work at the correct resolution and seem fine, but are 12 pixels offset to the right (the running green "logout" man cut of on the inside of his front leg in the Alphas and, now that the top bar has changed, the red "power" symbol is hard against the edge of the screen). Taking a screen capture works correctly and is not offset.

The following modelines are reported in xorg.0.log:
$ grep 1360 /var/log/Xorg.0.log
(II) NV(0): h_active: 1360 h_sync: 1424 h_sync_end 1536 h_blank_end 1792 h_border: 0
(II) NV(0): Modeline "1360x768"x0.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz)
(II) NV(0): Estimated virtual size for aspect ratio 1.7800 is 1360x768
(II) NV(0): Not using default mode "1360x768" (monitor doesn't support reduced blanking)
(--) NV(0): Virtual size is 1360x768 (pitch 1360)
(**) NV(0): *Driver mode "1360x768": 85.5 MHz, 47.7 kHz, 60.0 Hz
(II) NV(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz)
(**) NV(0): *Default mode "1360x768": 84.8 MHz, 47.7 kHz, 59.8 Hz
(II) NV(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz)

My lspci is:
http://launchpadlibrarian.net/17569081/lspci.txt

Note that the proprietary drivers in Hardy work correctly (not offset).

The version of -nv is 2.1.10-1ubuntu2.

A Gimp file showing the offset amount is:
http://launchpadlibrarian.net/18348801/screenshot.xcf
and a PNG is
http://launchpadlibrarian.net/18348803/screenshot.png

Please let me know if I can be of any further assistance.

[Aaron Whitehouse (aaron-whitehouse)]

Still a problem with Intrepid Beta (although the logout man isn't there anymore, so the offset means that the red "power" symbol is hard against the edge of the screen).

[Aaron Whitehouse (aaron-whitehouse)]

It looks as though it is 12px offset to the right.

[Aaron Whitehouse (aaron-whitehouse)]

And a PNG

[Marc Kaplan (marc-kaplan)]

If this is not a production machine, would it be possible for you to test your card with the latest build of Jaunty? If possible, please upgrade rather than doing a fresh install so we know if it breaks during the upgrade.

We are trying to determine which cards will be broken with the new xorg and need to have their pciids added; and which ones work out of the box.

See Bug 333040

Thank you in advance for you help.

[uber_n00ber (shannonsnz)]

I'm not sure if this is relevant information or helpful, so will let you decide.

I was also affected by this bug on a dual-boot WinXP/Ubuntu 9.04 machine after a clean install using a Geforce4 Ti 4200 (64MB) and a Dell1907FP LCD monitor over VGA. For me, the shut down icon at the top right was cut clean in half by the offset to the right.

The fix for me was using the restricted drivers via System > Administration > Hardware Drivers.

[Bryce Harrington (bryce)]

Thank you for reporting this issue about xserver-xorg-video-nv. Starting
with Lucid, Ubuntu is transitioning to using the -nouveau video driver
by default instead of -nv. The reason for this change is because
upstream development for the -nv driver has been quite slow. We are
quite pleased with the upstream development speed for -nouveau, and hope
this will translate into swifter bug fixes as well.

Because of this, I'm closing this bug report at this time. I'm marking
it wontfix because what you describe is probably a valid issue, but we
do not have further plans to work on it in Ubuntu. If you would still like
to see this issue investigated, I would encourage you to file it
upstream at http://bugs.freedesktop.org/.

[Corbin Simpson (mostawesomedude)]

Nobody is supporting xf86-video-nv and it will be going away at some point in the future. If your problem persists with nouveau or the proprietary driver provided by nVidia, please re-file accordingly. We apologize for the inconvenience.

This is part of an automated bulk action; if you believe that this bug was closed in error, then change the targeted component and reopen it.