Hi all !
Thanks very much Aaron for your advices, I realy appreciate your respons
to my problem.
Well, now I have done some testing on my machine, and I have change the
driver for my graficcard to a VESA-driver instead off the
S3VIRGE-driver. To see what happends.
And YES !!!
Now it works allright when I logout of KDE and X into runlevel 3, there
is no "colorsallad" anymore.
Instead there is a normal terminal, that I can use, as supposed to.
But, now I use the VESA-driver instead off the S3VIRGE-driver, that I
supposed to have.
How can I get the S3VIRGE-driver to work for my graficcard ?
What is the differenses between the VESA-driver and the S3VIRGE-driver ?
Why is the VESA-driver working and not the S3VIRGE-driver ?
Thanks very much !!!
Philip Moller
Sweden
akonstam@xxxxxxxxxxx wrote:
On Sun, Aug 14, 2005 at 03:45:37PM +0930, Tim wrote:
On Sun, 2005-08-14 at 00:52 +0000, Philip Moller wrote:
When I log out from KDE and X into textmode (runlevel 3), the screen
resolution changes to colorsallad.
I see a similar thing, but I'm using Gnome:
As soon as the PC is running in level 5, the text mode virtual consoles
get corrupted in different ways: Occasionally yellow text on magenta
backgrounds, or more often the usual white text and black background
colours; but always with a blue border, and the first vertical set of
pixels from the text belonging at the left of the screen being on the
right hand side of the screen, right of the 80th column, and above it
(sorry, but I don't know a way to provide a screenshot of a text mode
screen).
Dropping back to run level 3 doesn't help, the damage was done the
moment run level 5 started. If run level 5 was never started (e.g. I
booted in run level 3 and stayed there) the screen is fine.
I have a s3virge dx graficcard.
Runing fc4 on a dell Optiplex GX110.
Mine's an on-board i810 (very low spec, I know, but a bog standard
chipset for a very long time), built into a Gigabyte 6WMMC7 motherboard
(which has no AGP slot for a upgrading to a more decent graphic card).
And it runs fine with Red Hat 9.0 and Fedora Core 3 Linux.
Well here is the thing. The file libvgahw.a is hinky on some hardware
in FC4. So there are two possible solutions. The one I know works is
to copy that file from a FC3 system. And I think updating the rpm that
gives us that file might solve some of your problems. Or maybe not,
but it is worth a try.
