Bug 49840 - incorrect X configs for Trident Cyberblade / Compaq 12XL125 generated
Summary: incorrect X configs for Trident Cyberblade / Compaq 12XL125 generated
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-24 15:02 UTC by Chris Ricker
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-05 17:39:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
incorrect generated XF86Config (16.33 KB, text/plain)
2001-08-10 22:17 UTC, Chris Ricker
no flags Details
XF86Config from 7.1 (9.68 KB, text/plain)
2001-08-10 22:21 UTC, Chris Ricker
no flags Details

Description Chris Ricker 2001-07-24 15:02:39 UTC
Text install, updates 07192001 disk

anaconda detects the right video chipset, but then generates totally borked
X configs.  The X 4 config generated only includes resolutions higher than
the LCD supports, and the X 3 config similar includes no valid modes.

anaconda is also still defaulting to X 3 for this chipset, even though X 4
now supports it.

Comment 1 Michael Fulbright 2001-07-24 15:58:22 UTC
Please try again when Beta 3 is out.

Comment 2 Glen Foster 2001-07-24 20:43:02 UTC
This defect is considered MUST-FIX for Fairfax.

Comment 3 Chris Ricker 2001-08-05 14:28:44 UTC
Still true with Beta 3 (GUI install)

both XF86 3 and 4 config files are generated.  neither are correct.  System
defaults to XF86 3.

Comment 4 Michael Fulbright 2001-08-07 14:16:54 UTC
Did you choose the proper monitor type to match your LCD?

Comment 5 Chris Ricker 2001-08-07 14:23:11 UTC
I let it auto-detect, which is what I've done in the past.

My correct LCD type isn't listed....

Comment 6 Michael Fulbright 2001-08-09 03:24:44 UTC
Try using the "Generic Laptop Display Panel 1024x768" (assuming your laptop can
do 1024x768, pick the correct one if not).

What monitor did it autoprobe, btw?

Comment 7 Chris Ricker 2001-08-10 15:37:44 UTC
Here's what it autoprobed:

Section "Monitor"
    Identifier  "Probed Monitor"
    VendorName  "Unknown"
    ModelName   "Unknown"
    HorizSync   46.876
    VertRefresh 75.121
    ModeLine    "800x600" 48.002 800 832 928 1024 600 604 608 624 -HSync -VSync

Comment 8 Michael Fulbright 2001-08-10 16:48:54 UTC
Could you attach the working XF86Config(-4?) that you used in 7.1, and also the
config file the installer now creates? I'd like to compare them.

Comment 9 Chris Ricker 2001-08-10 22:17:53 UTC
Created attachment 27353 [details]
incorrect generated XF86Config

Comment 10 Chris Ricker 2001-08-10 22:21:16 UTC
Created attachment 27354 [details]
XF86Config from 7.1

Comment 11 Chris Ricker 2001-08-10 22:31:25 UTC
Sorry if there are three attachments instead of two -- bugzilla is balking again.

XF86Config is the broken config generated by beta3.  It can be fixed simply by
switching SVGA from Probed Monitor to Unprobed Monitor.

XF86Config-7.1 is the config I used on RH 7.1.

I've never gotten an XF86Config-4 that works with that LCD and video card, even
though the chipset is supported by XFree86 4.

Comment 12 Michael Fulbright 2001-08-13 15:58:03 UTC
Did it work when you manually chose "Generic Laptop Display Panel 1024x768"
(assuming your laptop can do 1024x768, pick the correct one if not)?

Could you attach the output from ddcprobe for this machine (its in the anaconda

Comment 13 Chris Ricker 2001-08-13 17:47:17 UTC
It still didn't work.  Here's ddcprobe:

[root@localhost root]# ddcprobe 
VESA 2.0 detected.
Memory installed = 128 * 64k blocks = 8192kb
Supported standard modes:
EDID read failed. (No DDC-capable monitor attached?)
[root@localhost root]# 

Comment 14 Michael Fulbright 2001-08-14 15:31:54 UTC
So to summarize, DDC probing does not work (not surprising, since it isn't
supposed to be able to handle LCDs), and specifying a monitor manually also
creates a bad XF86Config (its putting the wrong monitor section).

Does this sound correct?

Comment 15 Chris Ricker 2001-08-14 15:42:22 UTC

Comment 16 Michael Fulbright 2001-08-14 21:34:47 UTC
I've done an install on a machine with a older Neomagic chipset and it failed to
DDD probe the LCD. I picked 'Generic LCD 1024x768" and rebooted. X came up fine.
This was a GUI text case.

When I tried the TUI case - it looks like for my Neomagic it defaulted to 256k
of video RAM, which is not enough.  How much does the card configuration screen
default to for you?

Comment 17 Chris Ricker 2001-08-21 06:50:32 UTC
It defaulted to 8192k for me

I've done a fresh install, text mode, with RC1.  With RC1, it's the same as
beta3.  It detects the right chipset and right amount of memory.  It doesn't
detect the LCD.  When I tell it to use the generic 1024x768 LCD, it generates
broken X configs.

Comment 18 Chris Ricker 2001-09-05 17:39:28 UTC
RC2 works for me, though I still have to force it to use the generic 1024x768
LCD instead of unprobed.  Also, only XFree86 3 works in RC2, even though XFree86
4 supports the chipset.

Comment 19 Michael Fulbright 2001-09-05 21:50:39 UTC
Great glad to hear its finally working. Hopefully we can probe LCDs better in
the future.

Note You need to log in before you can comment on or make changes to this bug.