XF86Config won't work correctly

FZJ · 02-28-2003, 07:48 AM

Hi everybody,

I am using RedHat 8 and I want to install the X server. For this, I run xf86config to create the /etc/X11/XF86Config.
But when I type startx, nothing looks like it should.

My graphic device is a ELSA WINNER 1000/T2D. The Chipset says S3 86C775 Trio64V2/DX.

I can select the graphic device as "ELSA WINNER 1000/T2D" or as "S3 86C775 Trio64V2/DX". Both set the driver to "s3". When I type startx, the error message says, that it couldn't find the device - "no screens found".

When I set the device to the "Standard VGA" with "vga" as driver, the startx runs a screen with 320x200 px on the lower part of the screen (the upper remains black), whatever I type in the depth part.

What can be wrong? Has anyone an idea?

loke137 · 02-28-2003, 08:31 AM

Are you using the right frequencies? Are you sure that is your card ( try letting the config detect your card)?

Doalwa · 02-28-2003, 09:59 AM

Hi,

try the following:

su to root , then type

XFree86 -configure

This will start the autodetection. To test if the auto detection worked correctly, type XFree86 -xf86config /root/XF86Config.new

If the x server starts correctly, you should cancel it by pressing ctrl-alt-backspace. Then copy the newly created XF86Config.new file to /etc. I don't know where Red Hat 8 puts the XF86Config file, look it up and overwrite the existing file with your newly created config file. Now simply type startx and the X Server should start. Maybe you'd still have to change certain parameters, like screen resolution , but at least you should get the X server going this way.

Dominik

FZJ · 03-01-2003, 01:26 PM

tried everything. nothing works. even XFree86 -configure or redhat-config-xfree86.

but now i use driver "vesa" for my video card. don't know why

. i saw this one in the autodetection file (which doesn't work).

I put in in my hand-made /etc/X11/XF86config. and now: with this driver i can start now the X.

thanks for your help...

acid_kewpie · 03-01-2003, 01:40 PM

vesa is a VERY basic driver, and doesn't actually use the card properly at all, but instead it shows a picture of an X session inside a framebuffer, which is a long long way from ideal. if you're hapy with it then that's fine, but be aware that it's essentially a crippled lowest-common-denominator kinda affair. a bit like windows rescue mode...