bon, ben tu n’es plus trés loin…
j’ai trouvé quelques pistes interressantes: ca peut venir de la manière dont est configuré ton agp.
sur odin.prohosting.com/wedge01/gent … kernelopts
il est précisé que la config de ton noyau devait contenir les éléments suivants:
Loadable module support -> Enable loadable module support: ENABLED
Loadable module support -> Module unloading: ENABLED
Loadable module support -> Automatic kernel module loading: ENABLED
The above 3 options will generally be enabled in most kernels anyway, but since it wouldn't be possible to load any modules without them, they are required to use the ATI drivers.
Processor type and features -> MTRR (Memory Type Range Register) support: ENABLED
MTRR support should always be enabled - if not, the driver may run very slowly, if it runs at all
Character Devices -> /dev/agpgart (AGP Support): ENABLED OR MODULE (if you don't compile this as a module, you'll have to set "UseInternalAGPGART" to "no" in your XF86Config file)
This option enables AGP support in the kernel, which is usually a good thing to have :)
Character Devices -> (pick the correct AGP chipset option from the list, depending on your motherboard): ENABLED OR MODULE
Examples:
Motherboard: nVidia nForce2 based ---- NVIDIA nForce/nForce2 chipset support
Motherboard: VIA KT266/333/400 based ---- VIA chipset support
NB: compiling this option as a module is only possible in 2.6 kernels.
NB: AMD64 users: you must also select the AMD Opteron/Athlon64 on-CPU GART support option in addition to those described above.
Character Devices -> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support): DISABLED
This option is not required, and will almost certainly prevent the driver from working if enabled.
NB: in 2.6 kernels, the final 3 settings can be found in the "Device Drivers" section of the kernel configuration.
bon, mais sinon, avant de recommencer une compil de noyau, plusieurs choses:
essayes un ‘modprobe via_agp’ si tu es en chipset via, et un modprobe autrechose (mais je ne connais plus le nom du module, il faut le retrouver dans l’aide de la config noyau) si c’est autrechose comme agp.
APRES, tu essayes ton fglrx …
Sinon, juste aprés une tentative d’insertion du module fglrx, si tu pouvais récupèrer les derniers lignes de dmesg, par exemple ‘dmesg | tail’ ca aiderait à diagnostiquer…
finalement, un petit guide de troubleshooting:
odin.prohosting.com/wedge01/gent … 4_nomodule