LINUX.ORG.RU

Проблема с установкой драйвера Radeon 9000


0

0

Cистема на базе NForce2 (Epox 8RDA+), Mandrake 9.1 Хотел поставить драйвер с http://www.schneider-digital.de/html/download_ati.html, ставлю rpm -Uhv --force fglrx-glc22-4.3.0-2.9.8.i586.rpm. Выдает вот что:

*** Trying to install a precompiled kernel module. *** WARNING *** Tailored kernel module for fglrx not present in your system. You must go to /lib/modules/fglrx/build_mod subdir and execute './make.sh' to build a fully customed kernel module. Afterwards go to /lib/modules/fglrx and run './make_install.sh' in order to install the module into your kernel's module repository. (see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated OpenGL will not work and 2D graphics will lack performance.

failed. *** Found kernel module build environment, generating kernel module now. ATI module generator V 2.0 ========================== probing for VMA API version... cleaning... patching 'highmem.h'... patching 'drmP.h'... patching file drmP.h Hunk #1 FAILED at 255. Hunk #2 FAILED at 266. 2 out of 2 hunks FAILED -- saving rejects to file drmP.h.rej compiling 'agpgart_be.c'... compiling 'agp3.c'... compiling 'i7505-agp.c'... compiling 'firegl_public.c'... linking of fglrx kernel module... duplicating results into driver repository... done. ============================== - creating symlink - recreating module dependency list - trying a sample load of the kernel module Warning: loading /lib/modules/2.4.21-0.13mdk/kernel/drivers/char/drm/fglrx.o will taint the kernel: non-GPL license - Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY See http://www.tux.org/lkml/#export-tainted for information about tainted modules Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg failed. Installed: qt3 (gcc 3.2) based control panel application === ATI display drivers successfully installed please run 'fglrxconfig' now ===

В общем, как откомпилить все таки этот fglrx?


Ну и что не нравится? Ну ругается немного, но драйвер-то компилирует. Остается прогнать fglrxconfig и переправить BusID:PCI:1:0:1 на BusID:PCI:1:0:0. Если нет dri, то придется еще и перегрузится.

StepDV
()

Прогонял я fglrxconfig. У меня по умолчанию стояло BusID:PCI:2:0:0, в таком варианте лог иксов выдает (окончание лога):

(II) Loading extension ATIFGLRXDRI (II) fglrx(0): doing DRIScreenInit drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed [drm] failed to load kernel module "agpgart" drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmGetBusid returned '' (II) fglrx(0): [drm] loaded kernel module for "fglrx" driver (II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:2:0:0" (II) fglrx(0): [drm] added 8192 byte SAREA at 0xe483c000 (II) fglrx(0): [drm] mapped SAREA 0xe483c000 to 0x40014000 (II) fglrx(0): [drm] framebuffer handle = 0xe0000000 (II) fglrx(0): [drm] added 1 reserved context for kernel (II) fglrx(0): DRIScreenInit done (II) fglrx(0): Kernel Module Version Information: (II) fglrx(0): Name: fglrx (II) fglrx(0): Version: 2.9.8 (II) fglrx(0): Date: Apr 15 2003 (II) fglrx(0): Desc: ATI Fire GL DRM kernel module (II) fglrx(0): Kernel Module version matches driver. (II) fglrx(0): Kernel Module Build Time Information: (II) fglrx(0): Build-Kernel UTS_RELEASE: 2.4.21-0.13mdk (II) fglrx(0): Build-Kernel MODVERSIONS: yes (II) fglrx(0): Build-Kernel __SMP__: no (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000 (II) fglrx(0): [drm] register handle = 0xec020000 (EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV" (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

Похоже он AGP не может найти. Может это быть из-за чипсета NForce2?

filolog
() автор топика

Похоже на то. Тогда lspci и ищем в списке agp. Кстати, а как скомпилирован agpgart? Для атишных карт он однозначно должен быть вынесен в модуль.

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