X Support and Config needed for Viewsonic VA1916W

Also, using Ubuntu 8.04

I fixed this using Nvidia-Settings software.

Easy fix for Ubuntu would to build configuration for Viewsonic VA1916w in the displayconfig-gtk

Monitor Specs:

ModelName "ViewSonic VA1916wSERIES"
HorizSync 24.0 - 82.0
VertRefresh 50.0 - 75.0

1440 x 900 @ 60, 75 Hz
1280 x 1024 @ 60, 75 Hz
1024 x 768 @ 60, 70, 72, 75 Hz
800 x 600 @ 56, 60, 72, 75 Hz
640 x 480 @ 60, 75 Hz
720 x 400 @ 70 Hz

James Westby wrote:
> ** Changed in: linux-meta (Ubuntu)
> Sourcepackagename: None => linux-meta
>
> ** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
> Sourcepackagename: linux-meta => linux-restricted-modules-2.6.24
>
>

 I added displayconfig-gtk to list. If it had the right configuration
for the monitor, the bug wouldnt exist. It's matter of x using the wrong
refresh rate for the monitor. It really is a simple fix and just needs
little attention. In the meantime, I fixed it using nvidia-settings but
thats not perfect.

ddcprobe output

This is the output that NV dumped in the Xorg log. It tested and generated modes.

Hi,

This doesn't appear to be a bug in displayconfig-gtk, it appears to be lower down than
that.

Thanks,

James

According to discussion on #ubuntu-x, the nvidia driver is unable to use 56Hz with the monitor, reassigning.

Hi kahrytan,

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.

No change. I didn't test in Intrepid due to the fact I couldn't test it. Intrepid is unusable. I am about to file a bug on intrepid when my hardy recovery is finished.

I did try to play Extreme Tux Racer in Intrepid when my tv tuner card was removed. Monitor still got out of range error. Bug still exists even Intrepid.

I can't use Intrepid as of yet due to major bug between tv tuner card and nvidia graphics card.

How hard is it to fix this freakin bug? All the information that is needed is easily found in the monitor's own manual.

 Thanks to this bug and tv tuner bug, I am making my switch back to Windows. obviously, ubuntu and linux developers blame closed source all of their bugs and ignore them.

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.

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.