*** This bug is a duplicate of bug 3731 ***
https://bugs.launchpad.net/bugs/3731
25 April 2007
Hi Bryce,
I will definitely assist you. I have 2 other monitors too, Viewsonic 17"
E70F CRT, and HP 17" HP71 CRT (1999 model) that I can test on after the
G90f+ is resolved.
Let me know what I need to do regarding download and burning to a CD to
test this.
When I run 7.04 in VirtualBox on XP I do get 1024x768.
It seems that "xresprobe" needs to be modified or a new tool designed
altogether. I guess it is as simple and as complex as querying the monitor
for resolutions and then presenting them as options. In theory simple enough
as an objective but a substantial challenge for you and a good Ubuntu
achievement if you can find a solution.
Just let me know what I need to do to assist.
Cheers,
Chris
On 4/25/07, Bryce Harrington <[EMAIL PROTECTED]> wrote:
>
> Hi Chris,
>
> Thanks for gathering this additional info; I know it's a pain.
>
> Yep, this does indeed look like another example of the infamous bug
> 3731. Looking at your xorg.conf file, Ubuntu seems to have detected
> your monitor, but failed to determine the h/v rates:
>
> Section "Monitor"
> Identifier "G90f+"
> Option "DPMS"
> EndSection
>
> Then in the Xorg.0.log file, you see where it takes a wild guess:
>
> (II) NV(0): G90f+: Using default hsync range of 31.50-37.90 kHz
> (II) NV(0): G90f+: Using default vrefresh range of 50.00-70.00 Hz
>
> Yet actually, looking up your monitor's documentation, the actual rates
> are very different:
>
> www.viewsoniceurope.com/data/60/G90f+_b.pdf
> Frequency: Fh: 30-97kHz; Fy: 50-180
>
> Then in the Xorg.0.log file you can see a sadly long list of rejected
> resolutions because they're beyond what it thinks the allowed ranges
> are.
>
> Unfortunately, a LOT of people run into this particular bug. It's
> because the installer relies on a tool called xresprobe, which has
> proven to be quite inadequate.
>
> The good news is that if you can get through the installation process,
> then you can just manually edit your xorg.conf file to insert the
> correct values in. Namely:
>
> Section "Monitor"
> Identifier "G90f+"
> Option "DPMS"
> HorizSync 30-97
> VertRefresh 50-180
> EndSection
>
> Of course, that won't help for getting it to boot off the LiveCD, and
> you're definitely right that this problem really must be fixed for
> Gutsy.
>
> Canonical recognizes this is a problem and has taken several steps.
> First, they've hired a dedicated Xorg maintainer (me; I officially start
> day after tomorrow). Second, they've slated time to talk about how
> we're going to solve these issues at the upcoming developer summit in
> May. Third, they've made this and a couple other major X features be
> critical items for the Gutsy release. I'm a little apprehensive about
> if all these things can be achieved by then, but hopefully with help
> from community members like you, it can be done.
>
> I'll drop a few more thoughts and ideas onto bug 3731, of ideas, things
> needing to be tested, etc. If you'd like to help make Ubuntu's X work
> robustly, I'd love it if you could join in the discussions and work on
> that bug.
>
> --
> Fiesty Fawn screen resolution bug at install
> https://bugs.launchpad.net/bugs/109483
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Fiesty Fawn screen resolution bug at install
https://bugs.launchpad.net/bugs/109483
You received this bug notification because you are a member of Kubuntu
Team, which is a subscriber of a duplicate bug (via bug 3731).
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
