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.
Hi, i'm new here and not too linux savy so I figured i'd ask about this.
I have a Radeon 9200 saphire, slackware 10 with the 2.4.26 kernel, running XFree86 4.4.0 just compiled and seems to be working fine... but when I go to install the ATI graphics drivers, it won't work properly.
I'm assuming that it's a problem with XFree86 because ATI doesn't appear to have support for version 4.4.0, but it could be something stupid like I have a config file in the wrong place.... I noticed several howtos to get it working under the 2.6.7 kernel so I may just compile that and get it working then... but if someone could help me get it working under 2.4 it would be great.
I have gotten it working under both the 2.4.x and 2.6.x kernels, but I couldn't get it to work with the slackware "out of the box" kernel. After I recompiled my kernel, the ATI driver would compile and work fine.
I've just installed slackware 10. This is what I did to get my Radeon 9800 working.
1. download the ati drivers, make sure you get the xfree 4.3 ones.
2. open terminal.
4. cd into directory containing the drivers you just downloaded
5. rpm2tgz fglrx****.rpm
6. installpkg fglrx****.tgz
7. cd /lib/modules/fglrx/build_mod
8. sh make.sh
9. cd ..
10. sh make_install.sh
12. rename /etc/X11/XF86Config-4 to xorg.conf (backup your xorg.conf first)
13. reboot or restart x server
14. open terminal
15. glxinfo it should say near the top direct rendering YES. (which means hardware opengl working)
or may be the problem when u made fglrxconfig u didnt choose the right options
here is what i choose :
ATI - FIRE GL - BE THE CREATOR
This program will create the ATI "XF86Config-4" file
- based on your selections - for the below listed boardtypes...
- ATI Radeon 8500 / 9100
- ATI FireGL 8700 / 8800 / E1
- ATI FireGL T2
- ATI Radeon 9000
- ATI Radeon 9200
- ATI Radeon 9500
- ATI Radeon 9600
- ATI Radeon 9700
- ATI Radeon 9800
- ATI FireGL Z1 / X1 / X2
- ATI Mobility M9
- ATI Mobility FireGL 9000
- ATI Mobility M9PLUS
The "XF86Config-4" file usually resides in /etc/X11.
Press [Enter] to continue, press 'q'&[Enter] or [Ctrl]+'c' to abort.
Please select one of the following keyboard types that is the better
description of your keyboard. If nothing really matches,
choose 1 (Generic 101-key PC)
1. Generic 101-key PC
2. Generic 102-key (Intl) PC
3. Generic 104-key PC
4. Generic 105-key (Intl) PC
5. Dell 101-key PC
6. Everex STEPnote
7. Keytronic FlexPro
8. Microsoft Natural
9. Northgate OmniKey 101
10. Winbook Model XP5
11. Japanese 106-key
12. PC-98xx Series
Enter a number to choose the keyboard type:  1
Please select the layout corresponding to your keyboard
1. U.S. English
2. U.S. English w/ISO9995-3
8. Swiss German
13. Swiss French
14. United Kingdom
Press [Enter] for the next page or
enter the number for your keyboard layout country: 1
This driver does support Quad Buffer Stereo ("Active Stereo")
in combination with a CRT monitor (refresh rate abt. 100 to 120 Hz)
and the appropiate stereo viewing subsystem hardware. This can be
e.g. a shutter glasses system (infrared or wired) or an active
polarisation device paired with passive stereo polarization glasses.
Do you want to enable "Quad Buffer Stereo" (y/n)? [n] n
TV out Configuration
| Maximum resolution for OpenGL operation |
| - R200 chip family (Radeon 8500-9100 Pro, FireGL 8700/8800/E1): |
| 2048x2048 |
| - R300 chip family (Radeon 9500-9700 Pro, FireGL T2/Z1/X1/X2): |
| 2560x2560 |
Choose configuration from the list below
1. Single Head (1 screen, second dark)
2. Laptop Mode (Ability to toggle between internal / external screen)
3. Clone Mode (2 screens - same content)
4. Big Desktop (2 screens - one framebuffer)
5. Dual Head (2 screens - two drivers)
Enter the number for your configuration:  1
Single Head selected
Now we want to set the specifications of the monitor(s). The two critical
parameters are the vertical refresh rate, which is the rate at which the
the whole screen is refreshed, and most importantly the horizontal sync rate,
which is the rate at which scanlines are displayed.
The valid range for horizontal sync and vertical sync should be documented
in the manual of your monitor. If in doubt, check the monitor database
/usr/X11R6/lib/X11/doc/Monitors to see if your monitor is there.
Press [Enter] to continue, press 'q'&[Enter] or [Ctrl]+'c' to abort.
You must indicate the horizontal sync range of your monitor. You can either
select one of the predefined ranges below that correspond to industry-
standard monitor types, or give a specific range.
It is VERY IMPORTANT that you do not specify a monitor type with a horizontal
sync range that is beyond the capabilities of your monitor. If in doubt,
choose a conservative setting.
hsync in kHz; monitor type with characteristic modes
1. 31.5 ; up to 640x480 @ 60 Hz (VGA)
2. 31.5 - 37.9; up to 800x600 @ 60 Hz (SVGA)
3. 31.5 - 48.4; up to 1024x768 @ 60 Hz (XGA)
4. 31.5 - 60.0; up to 1024x768 @ 75 Hz (XGA)
5. 31.5 - 68.7; up to 1024x768 @ 85 Hz (XGA)
6. 31.5 - 80.5; up to 1280x1024 @ 75 Hz (SXGA)
7. 31.5 - 91.1; up to 1280x1024 @ 85 Hz (SXGA)
8. Enter your own horizontal sync range
Enter your choice (1-8):  5
You must indicate the vertical sync range of your monitor. You can either
select one of the predefined ranges below or give a specific range.
1. 20 - 60 (e.g. slow scan flat panels with DVI cable)
2. 50 - 70 (VGA)
3. 60 - 75
4. 60 - 85
5. 60 - 100
6. Specify your own vertical sync range
Please list the digits and characters for the modes that you want to use.
For example, '632' selects "1280x1024" "1024x768" "800x600", with
the default mode of "1280x1024".
Which modes do you want? 3
The default resolution that the server will start-up with will be the first
listed mode that can be supported by the monitor and card.
Currently it is set to:
"1024x768" for 24-bit
Modes that cannot be supported due to monitor or clock constraints will
be automatically skipped by the server.
1. Change the modes for 24-bit (24-bit color)
2. The modes are OK, continue.
Enter your choice: 2
You can have a virtual screen (desktop), which is screen area that is larger
than the physical screen and which is panned by moving the mouse to the edge
of the screen. The largest resolution in the modelist is used for any of the
listed resolution with less dimensions. Each color depth can have a
differently-sized virtual screen. Virtual screens resolutions are set
for each color depth separately.
Note: This grafics adapter will always select the maximum
x and y resolution as the default virtual desktop resolution.
This complies with general X11 specifications. see "man XF86Config".
Do you want to use a virtual desktop where the dimensions are bigger
than your maximum x and y screen resolution? (y/n) [n] n
Direct Rendering Interface Restrictions
Please specify which restriction sheme you want to implement:
1. no restrictions - any user has access to the OpenGL ICD
2. limited to group 'users' - only group members can access the OpenGL ICD
3. limited to group 'root' - only group members can access the OpenGL ICD
4. limited to group 'video' - only group members can access the OpenGL ICD
5. limited to group 'dri' - only group members can access the OpenGL ICD
Enter the number for your default user restrictions:  1
Advanced Graphics Features Settings
Do you want to initialize xfree86-dga (y/n)? [n] y
Do you want to export pseudo color visuals (y/n)? [n] n
Do you want to synchronize buffer swaps
with the vertical sync signal (y/n)? [n] y
Full Scene Anti Aliasing (FSAA)
Please select multi sample visuals you want to share:
1 = All (Visuals for 2,4 and 6 Samples per Pixel)
2 = Visuals for 2 Samples per Pixel
4 = Visuals for 4 Samples per Pixel
6 = Visuals for 6 Samples per Pixel
Please enter:  1
Do you want to force multi sample visuals
for every OpenGL application? (y/n)? [n] n
Disable FSAA Gamma (y/n)? [n] n
Customize FSAA Multi Sample Position (y/n)? [n] n
Advanced OS Settings
External AGPGART module:
It is possible (but not recommended) to turn off the usage of
built-in agp support of the provided fglrx kernel module and
use the external AGP GART module (agpgart.o) of the Linux kernel.
If you want to use the external module then ensure that it loads
prior to the drivers full startup. In order to manually load the
external agpgart module execute this on the commandline (as root):
or alternatively configure your system to auto load the module.
Do you want to use the external AGP GART module (y/n)? [n] y
AGP Locked User Pages
The grafics driver is able to read and write textures and bitmaps trough AGP
mapped and locked views of the main memory for the application's mem space.
Performing those mapping task depends on several successfull interaction steps
with the Linux kernel. A failure in this process might lead to some messages
in the kernel log. If these kernel functions are failing silently or in case
of other heavy incompatibility (e.g. a new kernel memory manger) then there
is a high chance that the system will hang as soon as the graphics adpater
wants to read from assumed but nor really mapped memory location.
If you do see that the advanced fgl_glxgears application halts your session
whilst the simple glxgears does run nicely then please disable this feature.
If you do see lots of notifications about failed kernel calls for mem locking
then please disable this feature and re-check the kernel message log.
Do you want to enable "AGP Locked User Pages" (y/n)? [y] y
TLS Method: *** this only applys to the FireGL workstation boards ***
The grafics driver supports two different methods of thread local storage.
The first method is fast but might immediately abort when used with
WineX, VM emulators or some other advanced programming tools.
The second method is up to 10% slower in a few rendering cases
but does nicely cope with any sort of exotic software.
For more details on this topic, please see the readme.
If not totally sure about your needs, then please select "0 - default".
0 - default (FireGL workstation boards: fast)
1 - fast operation (only for standard gnu C/C++ OpenGL applications)
2 - compatible operation (for WineX, VM emulators and some profilers)
trying to setup the drivers again. not working so swell.
root@freedom:/lib/modules/fglrx/build_mod# sh make.sh
ATI module generator V 2.0
skipping patch for 'drmP.h', not needed
skipping patch for 'drm_os_linux.h', not needed
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.7/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make: Entering directory `/usr/src/linux-2.6.7'
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agp3.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/nvidia-agp.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agpgart_be.o
/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c: In function `agp_generic_alloc_page':
/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c:1405: error: structure has no member named `count'
/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c: In function `ali_alloc_page':
/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c:4416: error: structure has no member named `count'
make: *** [/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.o] Error 1
make: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make: Leaving directory `/usr/src/linux-2.6.7'
make: *** [kmod_build] Error 2
build succeeded with return value 0
duplicating results into driver repository...
cp: cannot stat `fglrx.ko': No such file or directory
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
it isnt finding agpgart? or something? lol, i'm so used to freebsd, so still trying to get the hang of this.