From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
Description of problem:
During setup, monitor (Viewsonic VG175) is detected as DDC with sane
refresh parameters, suggests 1600x1200, but it's an LCD, so I override
with 1280x1024x24. I get the Xconfigurator test screen, looks good, but
when I hit OK I get a black screen. Substitution with another monitor
indicates video is now coming at me at 127kHz H,
203Hz V, NN (!)
Using the boot disk, I am able to set up the monitor OK with Xconfigurator
with no problems.
Version-Release number of selected component (if applicable):
The same thing happened I think with Wolverine so I don't think it's
So are you seeing the behavior with the installer or Xconfigurator after
installation? Or both?
It's the installer -
After installation, Xconfigurator alone seems to work fine.
[I assumed the installer was actually running Xconfigurator behind the scenes,
because the test screen looked the same, but I realize now that's not
necessarily the case]
Can you run ddcprobe and attach the results here?
Created attachment 32540 [details]
Output of ddcprobe
BTW the installer showed the EISA ID (VSCdd00) rather than the model number,
that may be intentional though.
Here's the specs according to Viewsonic:
Hmm...part of the problem is that this monitor is not in the MonitorsDB file
from Xconfigurator. The installer doesn't share code with Xconfiguration, but
it does use the same video card and monitor databases. I think the problem
would be fixed by adding your monitor to this database. I would recommend
selecting the settings you want, but don't press the test button. Does that
write out a correct XF86Config file? I know that's not a great workaround, but
I think it will do for now. We'll have to fix this next release.
In the monitor screen, what does the installer put by default in the HSync and
Try putting "30-82" in the HSync box and "50-75" in the VSync box. Does that help?
I've added a line for your monitor to the MonitorsDB, so this problem should not
occur in future releases. Please reopen if you see this reappear in future
betas. Thanks for your report.