I observe the same problem on an old thinkpad 770Z with a trident cyber 9397dvd
video card, than the one described here:
When gdm starts, the screen becomes completely white, and only the hw cursor
remains reactive. The laptop still runs fine, and is reacheable with ssh. When
switching back to a VT, the console is also completely garbled (vesafb is in
use), but it still works. I suspect a problem with the trident driver.
I use the Fedora development packages (xorg-x11-6.8.2-20 currently)
Here's 2 reports from our bugzilla:
*** Bug 2457 has been marked as a duplicate of this bug. ***
Here is a possible workaround that I found :
. switch the LCD off (Fn-F3) (APM is in use, the laptop is too old for ACPI)
. switch it on again, and the screen is okay again.
The problem can be reproducted easily :
. switch to a VT (then the VGA screen out is garbled again : it only displays
white vertical strips)
. switch back to X (then the white screen is back)
. and previous workaround still works.
Same here. FC4 install, Trident 3DImage975 (Blade 3D (generic)). The X server
doesn't hang, just a blank screen. Nothing interesting in the logs.
Here is a little experiment I did:
1. Logged in as root from the text console;
2. Typed 'X&', the xserver loaded with a *white* background (not that
micro-checked pattern) with the 'X' cursor in the middle of the screen;
3. Went back to the console with Ctrl-Alt-F1 and typed 'DISPLAY=:0.0 xterm&';
4. Back to X, nothing new, same white background with the X cursor, *but*, when
I moved the cursor to the region of the screen where the xterm should have been
shown (the top-left quarter), the cursor disappeared, indicating that some kind
of window was there (and for some strange reason, the invisible window makes the
pointer disappear when it is over). Moving the cursor out of that region makes
it appear again. While the cursor is over that window, I can type commands and
even close the xterm window (^D).
Created attachment 2919 [details] [review]
patch to make monodoc stuff install to $prefix
Created attachment 2920 [details] [review]
I met same problem during FC4 install. Mine is a Trident Cyber9525DVD PCI/AGP
card. A workaround is to tweak /etc/X11/xorg.conf, replace driver from "trident"
(In reply to comment #7)
> I met same problem during FC4 install. Mine is a Trident Cyber9525DVD PCI/AGP
> card. A workaround is to tweak /etc/X11/xorg.conf, replace driver from "trident"
> to "vesa"
This is not a good workaround because (at least) Totem doesn't work in FC4,
> This is not a good workaround because (at least) Totem doesn't work in FC4,
> please see
This is the only workaround I've found. Otherwise I can only use console.
For movie viewer, I prefer mplayer and it works fine with vesa driver in my fc4
box. The only issue is hindered full screen display.
Try replacing the X server module "libvgahw.a" with the one I've provided
at the following URL:
Anyone experiencing this problem, who tries this test with good results,
should CC themselves on Red Hat bug:
I've added this fd.o bug to our tracker, and will update this one if we
can conclude it is the same problem.
I suggested that someone replace the libvgahw file as MGA users, Intel users
found worked to workaround the FC4 version of the file. Bug 3557 was filed to
track same cure, different problem types of bugs.
The white screen was resolved by replacing the same library.
Replacing libvgahw.a with ftp://people.redhat.com/mharris/libvgahw.a in fc4
solves the blank white screen problem for my Trident Cyber9525DVD PCI/AGP card.
Replacing libvgahw.a with ftp://people.redhat.com/mharris/libvgahw.a on
FC4/Trident CyberBladeXP solves white screen problem.
The fixed libvgahw.a from ftp://people.redhat.com/mharris/libvgahw.a worked for
me on a Toshiba Satellite 1800 using a Trident CyberBlade XPAi1, with a fresh
installation of Fedora FC4 (and a separate install of FC3!!). The white screen
has gone away.
I just replaced my libvgahw.a file with the one from mharris and it fixed the
problems I was having with fc4 on a HP Pavilion n5430 laptop with a cyberbladexp.
With the old libvgahw.a it would totally hose my screen even after I had exited X.
*** Bug 3958 has been marked as a duplicate of this bug. ***
Closing. gcc4 bug caused miscompilation.