SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I downloaded the schneider-digital drivers and followed everything in the readme.
the screens are setup fin in my xf86config-4 file, but i am having problems with my agp it seems.
After adding the modprobes to /etc/rc.d/rc/modules
and rebooting I can't startx again.
I had to use "modprobe agpgart agp_try_unsupported=1" to make the agpgart module load.
Output from logfile:
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOMEM"
(EE) fglrx(0): cannot init AGP
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signal 11. Server aborting
If you are using Slackware 9.0, then you need to edit /etc/X11/XF86Config. The file xf86config-4 is used in Mandrake and probably others, but not Slack. You may get away with renaming the file.
You may like to know that X is started from various window managers (if you have /etc/inittab set to
# Default runlevel. (Do not set to 0 or 6)
if set as above, then /etc/rc.d/rc.4 is called, which can be modified to start gnome or kde etc as required.
if set to
# Default runlevel. (Do not set to 0 or 6)
then you will boot to the command line. Even if you prefer a gui to load automatically, this is very useful at times, eg for running scripts for video card drivers, eg the nvidia driver, and very likely the ATI ones as well, although I am not familiar with the setup process for ATI cards.
If it is not, why then is the logfile telling me this:
XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20 i686 [ELF]
Build Date: 01 March 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Tue Sep 9 18:23:34 2003
(==) Using config file: "/etc/X11/XF86Config-4"
It was using the original xf86config file until i installed new vid drivers, now it is using xf86config-4.
But lets assume I'm wrong. How would I go about editing the xf86config file to get me into X with the agpsupport?
OK. XFree86 4.3.0 (or 4.anything for that matter), the version that is included with Slack 9, will use XF86Config-4 if it finds it. If it does not find it, then it will use XF86Config. Since there is only one version of X included in Slack 9, there was no reason to name the file XF86Config-4. If you do have two files, however, and one of them is named XF86Config-4, then it will use this one and ignore the other. Just because Slack 9's XFree86 will use XF86Config, does not mean it can't use XF86Config-4.