LINUX.ORG.RU

Ну как настроить АТИ-драйвера (Slackware10, kernel 2.6.9, Xorg 6.7.0)


0

0

Делаю так:
rpm2tgz fglrx-4.3.0-3.14.6.i386.rpm

installpkg fglrx-4.3.0-3.14.6.i386.tgz

Installing package fglrx-4.3.0-3.14.6.i386...
PACKAGE DESCRIPTION:

cd /lib/modules/fglrx/build_mod/

sh make.sh

ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
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.9/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-2.6.7'
Building modules, stage 2.
MODPOST
*** Warning: "pci_find_class" [/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko] undefined!
*** Warning: "remap_page_range" [/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko] undefined!
make[1]: Leaving directory `/usr/src/linux-2.6.7'
build succeeded with return value 0
duplicating results into driver repository...
done.
==============================
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
==============================

cd ..

- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
failed.

cd /etc/X11

fglrxconfig

==============================================================================
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.






==============================================================================
Mouse
==============================================================================

Specify the mouse port type. Choose one from the following list:

1. Serial Port
2. PS/2 or USB with PS/2 protocol
3. Inport Bus

Enter the number for your port type: [2] 2







Specify the mouse model. Choose one from the following list:

1. PS/2 Mouse (X11 generic ps/2 mouse driver)
2. PS/2 Wheel Mouse (X11 generic ps/2 wheel mouse driver)
3. Microsoft Intellimouse (PS2)
4. Microsoft IntelliMouse Explorer (PS2)
5. Kensington ThinkingMouse (PS2)
6. Logitech MouseManPlus (PS2)
7. Alps Glidepoint PS/2 Touchpad
8. Genius NetMouse
9. Genius NetScroll

Enter the number for your mouse model: [2] 2


If your mouse has only two buttons, it is recommended that you enable
Emulate3Buttons.

Do you want to enable Emulate3Buttons (y/n)? [n] n

Now give the full device name that the mouse is connected to, for example
/dev/tty00 or /dev/mouse or /dev/psaux (includes IBM Laptops).

Mouse device: [/dev/mouse] /dev/psaux



★★★★★

==============================================================================
Keyboard
==============================================================================

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] 1






Please select the layout corresponding to your keyboard

1. U.S. English
2. U.S. English w/ISO9995-3
3. Belgian
4. Bulgarian
5. Canadian
6. Czechoslovakian
7. German
8. Swiss German
9. Danish
10. Spanish
11. Finnish
12. French
13. Swiss French
14. United Kingdom
15. Hungarian
16. Italian
17. Japanese
18. Norwegian

Press [Enter] for the next page or
enter the number for your keyboard layout country: 1






==============================================================================
FireGL Display Settings
==============================================================================

Quad Buffer Stereo ("Active Stereo"):

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
==============================================================================

Do you want to enable TV out (y/n)? [n] n






==============================================================================
FireGL Screen Layout
==============================================================================

------------------------------------------------------------------------------
| 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] 1






==============================================================================
Single Head selected
==============================================================================





UVV ★★★★★
() автор топика
Ответ на: комментарий от UVV

==============================================================================
Monitor Settings
==============================================================================

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): [1] 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

Enter your choice: [1] 3






==============================================================================
Display Modes
==============================================================================

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:

"640x480" 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: 1

Select your modes from the following list:

1 "640x480"
2 "800x600"
3 "1024x768"
4 "1152x864"
5 "1280x960"
6 "1280x1024"
7 "1400x1050"
8 "1600x1200"
9 "1792x1344"

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

UVV ★★★★★
() автор топика
Ответ на: комментарий от UVV

==============================================================================
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] 1






==============================================================================
Application Profiles
==============================================================================

Please select application specific profile:

1. Default
2. Individual Configuration of Capabilities
3. Maya
4. SOFTIMAGE|XSI
5. SOFTIMAGE|3D
6. Houdini 4.0
7. Houdini 5.0
8. Houdini 5.5

Enter the number for your profile: [1] 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] 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):
/sbin/insmod agpgart
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

UVV ★★★★★
() автор топика
Ответ на: комментарий от UVV

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)

Which storage method do you want to use? [0] 0






==============================================================================
Finish
==============================================================================

I am going to write the XF86Config-4 file now. Make sure you don't accidently
overwrite a previously configured one.

Shall I write it to '/etc/X11/XF86Config-4' (y/n)? y

cp XF86Config-4 xorg.conf

glxinfo

name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_SGI_make_current_read, GLX_SGIS_multisample
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
GLX_ATI_render_texture
GLX extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.4 Mesa 5.0.2)
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 1 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 1 0 None
0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 1 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 1 0 None
0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 1 0 None

из /var/log/Xorg.0.log
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"

В ядре включен agpgart для 875 чипсета модулем!
DRI for XFree86 отключен.

UVV ★★★★★
() автор топика
Ответ на: комментарий от UVV

agpgart перед стартом Х загружен ? #lsmod

может быть кроме общего agpgart должен ещё модуль для твоего чипсета?
у меня с VIA lsmod:
#####################
fglrx 242300 7
via_agp 6464 1
agpgart 28200 2 via_agp
######################

попробуй загрузить "руками" fglrx.ko

#modprobe fglrx

или

#insmod /гдеЛежит/fglrx

а потом cтартуй Х

anonymous
()
Ответ на: комментарий от UVV


ну значит точно не хватает модуля для чипсета.

anonymous
()
Ответ на: комментарий от UVV

Какая видюха?

Обнови ядро(pci_find_class - проблемы с "старых" ядрах)

P.S. не обязательно было постить весь свой вывод.

Deleted
()

Так ты вот это
==============================
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
==============================
после того как модули собрались, выполнил? Если нет, то что ты грузить пытаешься?

anonymous
()
Ответ на: комментарий от Deleted

Неужели ядро 2.6.9 настолько старое?

UVV ★★★★★
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.