It's been a long time since the last comment to this bug report. Is
this bug still a problem with current -mga? It would be great if
someone could re-test against Jaunty (or Intrepid at least).
With how much the xserver has changed since this bug was originally
reported, I'm wondering if this
I can't test this, I don't believe I have that hardware anymore.
--
[mga] mode validation seems to treat ModeLines and DDC dtimings differently
https://bugs.launchpad.net/bugs/12502
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Okay, thanks for letting me know. Since the hardware is no longer
available for doing troubleshooting with, we'll have to close the bug
for now. However please feel free to reopen if you or anyone else has
the same HW and can reproduce this issue using the latest development
version of Ubuntu
** Tags added: valid-xorg-conf
--
[mga] mode validation seems to treat ModeLines and DDC dtimings differently
https://bugs.launchpad.net/bugs/12502
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Changed in: xserver-xorg-video-mga (Ubuntu)
Sourcepackagename: xorg = xserver-xorg-video-mga
--
[mga] mode validation seems to treat ModeLines and DDC dtimings differently
https://bugs.launchpad.net/bugs/12502
You received this bug notification because you are a member of Ubuntu
Bugs, which
I had a similar problem in Ubuntu Edgy.
So I don't want to add a new bug, and subscribe to this bug.
I have a Radeon X300 card with a 30 LCD TV Videoseven LTV30C, the native LCD
resolution is 1280x768.
But 1280x1024 is the maximum resolution reported and was detected OK and worked
fine with a
