Which no xfree86 in
ATI driver cannot find XFree86 on the system. User Name. Remember Me? Linux - Software This forum is for Software issues. Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. View Public Profile. View Review Entries. Find More Posts by PCaragounis.
Find More Posts by jschiwal. Posting Rules. Similar Threads. XFree86 4. Main Menu. Login Register. You may want to put dpi fonts ahead of 75dpi fonts if your system normally comes up closer to dots per inch. You may want to remove some font directories completely. Section "Module". If you are going to install NVidia drivers, remove the "dri" line. Sections "InputDevice". You may want to change the keyboard autorepeat rate by adding Option "Autorepeat" " 30". Section "Monitor". Specify the VertRefresh and HorizSync values if the system does not automatically detect the monitor and its values.
Section "Device". You may want to set some of the options available for your selected video driver. A description of the driver parameters is in the man page for your driver. Section "Screen". Add a DefaultDepth statement such as: DefaultDepth In the SubSection for your default depth, add a modes line such as: Modes "x" "x" "x". The first mode listed will normally be the starting resolution. You will only get a gray background with an X-shaped mouse cursor, but it confirms the system is working.
As the root user: move the configuration file to its final location:. This provides an initial screen with an xterm and a clock that is managed by a simple window manager, Tab Window Manager. For details of twm , see the man page. ICE-unix if it does not exist. If this directory is not owned by root , XFree86 delays startup by a few seconds and also appends a warning to the logfile.
This also affects startup of other applications. To improve performance, it is advisable to manually create the directory before XFree86 uses it. It includes the X server, fonts, xterm , a simple window manager twm , various utilities, video output drivers, and various input drivers including the mouse and keyboard.
This allows the xvidtune client to connect from another host. By default non-local connections are not allowed. By default this is only done when an existing configuration file does not contain any ServerLay- out sections or any Screen sections. This can be useful for providing configuration details for things not currently han- dled by the automatic configuration mechanism, such as input devices, font paths, etc.
By default automatic configuration is only used when a configuration file cannot be found. The default is 1. Not all drivers support this. See also the -gamma , -rgamma , and -ggamma options. Use -depth to set the color depth, and use -fbbpp if you really need to force a non-default frame- buffer hardware pixel format. This option currently has some problems on some platforms, but in most cases it is a good way to bootstrap the configuration process.
This option is only available when the server is run as root i. This is the same as the vt option, and is provided for compatibility with the native SCO X server. Legal values are 1, 4, 8, 15, 16, and Not all drivers support all values. You should only set this if you're sure it's necessary; normally the server can deduce the correct value from -depth above.
Useful if you want to run a depth 24 configuration with a 24 bpp framebuffer rather than the possibly default 32 bpp framebuffer or vice versa. Legal values are 1, 8, 16, 24, This value is applied equally to the R, G and B values. Those values can be set independently with the -rgamma , -bgamma , and -ggamma options. See also the -gamma , -rgamma , and -bgamma options. It will normally refuse to load modules with ABI revisions that are newer than the server's. This is because such modules might use interfaces that the server does not have.
When this option is specified, mismatches like this are downgraded from fatal errors to warnings. This option should be used with care. This option is only useful when debugging the server.
Not all platforms support or can use this option. This option is ignored when the ServerLayout section specifies a core keyboard. In the absence of both a ServerLayout section and this option, the first rele- vant InputDevice section is used for the core keyboard.
By default the first ServerLayout section is used. The default may be in a different directory on some platforms. If the n value isn't supplied, each occur- rence of this option increments the log file verbosity level. When the n value is supplied, the log file verbosity level is set to that value. The default log file verbosity level is 3. The default is usually 32 bits per pixel. There is normally little reason to use this option.
0コメント