Red Hat Bugzilla – Bug 43421
(Trident CyberBlade i1) does not display Xwindows correctly on a Compaq 12XL300 Laptop
Last modified: 2007-04-18 12:33:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Description of problem:
After configuring X on my Compaq 12XL300 Laptop, using the Trident
CyberBlade (Generic) driver, The Screen display is black on 2/3rds of the
screen from the left side, the other 1/3 of the screen is perfect.
Steps to Reproduce:
1.Install RedHat 7.1 on a Compaq 12LX300
2.Configure Xwindows with the Trident CyberBlade (Generic) driver, and
Generic Laptop Display Panel 800 X 600.
Actual Results: 2/3rds of the screen is black, the other 1/3 is perfect.
If you hit Ctrl+Alt+Backspace, you cannot see the root prompt, but you can
enter commands, after reboot, the screen displays fine.
Expected Results: X windows should work.
lspci -v --results
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade i1
(rev6a) (prog-if 00 [VGA])
Subsystem: Compaq Computer Corporation CyberBlade i1 AGP
Flags: bus master, fast Back2Back, 66Mhz, medium devsel, latency 64, IRQ 9
Memory at f5000000 (32-bit, non-prefetchable) [size-8M]
Memory at f4100000 (32-bit, non-prefetchable) [size-128M]
Memory at f4800000 (32-bit, non-prefetchable) [size-8M]
Expansion ROM at <assigned> [disabled] [size=64k]
Campabilities:  AGP version 1.0
Capabilities:  Power Management version 1
Please attach your X server logs and config files via the attachment link below.
Created attachment 20433 [details]
The config files from /etc/X11 directory
Created attachment 20434 [details]
The log files from /var/log
The trident driver works in Mandrake 8.0. I installed in on my laptop and it worked, I don't know if you could check out their distro and port the driver to
Red Hat or not, but I would like that.
Uncompressed file attachments only please, so I can read them right
in the browser...
I will check Mandrake's XFree86 and see if there are any Trident
Please reattach new logfile and config if you can, to save me some time
working on this. Thanks.
Can you try
in your Device section.
Assuming the problem is no longer occuring now. Please reopen
the bug report if the problem recurs, and provide responses to the
information requested previously please, so we can help troubleshoot.