***Newbie Alert***

I just installed Fedora Core 4 on a PIII/1GHz with 512 RAM and a ATI Radeon
7200 video card. I used the "Install Everything" option and then changed
inittab to start at runlevel 3. I have installed nothing else and have not
touched any configuration files.

The problem is that I can type "startx", go into KDE, and logoff again -
getting a perfectly good text mode screen with which I may continue to work
without any problems. However, if I then type startx again - I can reenter
KDE without any problem, but after logging out the _second_ time, the
previous character text is disrupted, "ckear" doesn't help, and if I press
to many keyes or <ENTER>s, I eventually get incomprehensible reverse color
characters in an assortment of foreign languages. I can type "startx" again
and get a perfectly good KDE session, but the problem repeats itslef upon
logging out from KDE.

I should point out that the same problem occurs with gnome.

I'd appreciate any help.

Cheers,
Lavie

can u not use alt+ F1 , alt +F7 to change between gui and text console, why are u typing startx every time?.

Well, am I not allowed to? Is this a known limitation?

And if KDE stays up - even in the background, isn't it supposed to be a phenomenal memory hog?

And extra info - this is a plain vanilla FC4 installation - with the default KDE 3.4.0-6.

And yes - I know it's an embarrasment not compiling your own kernel - but I am a newbie...


Any ideas?

Lavie

Also - in out-of-the-box RH9.0 (my previous installation), there was no such problem...

I also just tried the ALT-F1, etc, to get into text mode from within gnome. I get the same problem there, too. When I get the text logon prompt, the cursor is 2 lines below where it should be. Each time I type a line of anything, the cursor _doubles_ the number of lines it is below where it should be - first 2 lines, then 4, then 8, etc.

Any ideas?

Lavie

I have a i815e chipset, and apparently that is the root of all the problems.

I found a relevant thread here:

forums.fedoraforum.org/showthread.php?t=59129

The immediate remedy is to install the FC3 version of the libvgahw.a file.


FYI

Lavie