+ Reply to Thread
Results 1 to 10 of 10

Thread: Debian - 3D Acceleration Module Problem (X1650XT AGP)

  1. #1
    Join Date
    Apr 2008
    Location
    Bristol, England
    Posts
    20

    Default Debian - 3D Acceleration Module Problem (X1650XT AGP)

    I'm have installed Debian Testing onto my secondary machine (Barton 2600+) which has an AGP-based X1650XT. I have installed driver 8.40.4 because (in my experience) later revisions do not work with AGP cards.

    Driver installed well, and now I want to compile and activate the module that enables 3D Acceleration. I go to /usr/src/modules/fglrx/ and run 'sh make.sh' (as superuser), and I get the following error message:

    ATI module generator V 2.0
    ==========================
    initializing...
    ./firegl_public.c: required file is missing in build directory
    computername:/home/username# cd /usr/src/modules/fglrx
    computername:/usr/src/modules/fglrx# sh make.sh
    ATI module generator V 2.0
    ==========================
    initializing...
    cleaning...
    patching 'highmem.h'...
    assuming new VMA API since we do have kernel 2.6.x...
    Assuming default VMAP API
    Assuming default munmap API
    doing Makefile based build for kernel 2.6.x and higher
    make.sh: line 937: cd: 2.6.x: No such file or directory
    make -C /lib/modules/2.6.24-1-686-bigmem/build SUBDIRS=/usr/src/modules/fglrx modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.24-1-686-bigmem'
    CC [M] /usr/src/modules/fglrx/firegl_public.o
    /usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_check_pci’:
    /usr/src/modules/fglrx/firegl_public.c:1857: warning: ‘pci_find_slot’ is deprecated (declared at include/linux/pci.h:493)
    /usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_pci_find_device’:
    /usr/src/modules/fglrx/firegl_public.c:1886: warning: ‘pci_find_device’ is deprecated (declared at include/linux/pci.h:492)
    /usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_vm_test_and_clear_dirty’:
    /usr/src/modules/fglrx/firegl_public.c:2411: error: implicit declaration of function ‘ptep_test_and_clear_dirty’
    /usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_pci_find_slot’:
    /usr/src/modules/fglrx/firegl_public.c:2719: warning: ‘pci_find_slot’ is deprecated (declared at include/linux/pci.h:493)
    /usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_request_irq’:
    /usr/src/modules/fglrx/firegl_public.c:2829: error: ‘SA_SHIRQ’ undeclared (first use in this function)
    /usr/src/modules/fglrx/firegl_public.c:2829: error: (Each undeclared identifier is reported only once
    /usr/src/modules/fglrx/firegl_public.c:2829: error: for each function it appears in.)
    /usr/src/modules/fglrx/firegl_public.c:2829: warning: passing argument 2 of ‘request_irq’ from incompatible pointer type
    /usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_pte_phys_addr_str’:
    /usr/src/modules/fglrx/firegl_public.c:3403: error: implicit declaration of function ‘pte_read’
    /usr/src/modules/fglrx/firegl_public.c:3405: error: implicit declaration of function ‘pte_exec’
    /usr/src/modules/fglrx/firegl_public.c: At top level:
    /usr/src/modules/fglrx/firegl_public.c:5306: error: expected specifier-qualifier-list before ‘kmem_cache_t’
    /usr/src/modules/fglrx/firegl_public.c: In function ‘KAS_SlabCache_Initialize’:
    /usr/src/modules/fglrx/firegl_public.c:5345: error: ‘kasSlabCache_t’ has no member named ‘routine_type’
    /usr/src/modules/fglrx/firegl_public.c:5346: error: ‘kasSlabCache_t’ has no member named ‘lock’
    /usr/src/modules/fglrx/firegl_public.c:5347: error: ‘kasSlabCache_t’ has no member named ‘name’
    /usr/src/modules/fglrx/firegl_public.c:5351: error: ‘kasSlabCache_t’ has no member named ‘cache’
    /usr/src/modules/fglrx/firegl_public.c:5352: error: ‘kasSlabCache_t’ has no member named ‘name’
    /usr/src/modules/fglrx/firegl_public.c:5352: error: too many arguments to function ‘kmem_cache_create’
    /usr/src/modules/fglrx/firegl_public.c: In function ‘KAS_SlabCache_Destroy’:
    /usr/src/modules/fglrx/firegl_public.c:5375: error: ‘kasSlabCache_t’ has no member named ‘cache’
    /usr/src/modules/fglrx/firegl_public.c:5385: error: ‘kasSlabCache_t’ has no member named ‘cache’
    /usr/src/modules/fglrx/firegl_public.c:5387: error: ‘kasSlabCache_t’ has no member named ‘cache’
    /usr/src/modules/fglrx/firegl_public.c: In function ‘KAS_SlabCache_AllocEntry’:
    /usr/src/modules/fglrx/firegl_public.c:5422: error: ‘kasSlabCache_t’ has no member named ‘routine_type’
    /usr/src/modules/fglrx/firegl_public.c:5423: error: ‘kasSlabCache_t’ has no member named ‘lock’
    /usr/src/modules/fglrx/firegl_public.c:5447: error: ‘kasSlabCache_t’ has no member named ‘cache’
    /usr/src/modules/fglrx/firegl_public.c:5450: error: ‘kasSlabCache_t’ has no member named ‘lock’
    /usr/src/modules/fglrx/firegl_public.c:5458: error: ‘kasSlabCache_t’ has no member named ‘cache’
    /usr/src/modules/fglrx/firegl_public.c: In function ‘KAS_SlabCache_FreeEntry’:
    /usr/src/modules/fglrx/firegl_public.c:5486: error: ‘kasSlabCache_t’ has no member named ‘routine_type’
    /usr/src/modules/fglrx/firegl_public.c:5487: error: ‘kasSlabCache_t’ has no member named ‘lock’
    /usr/src/modules/fglrx/firegl_public.c:5499: error: ‘kasSlabCache_t’ has no member named ‘cache’
    /usr/src/modules/fglrx/firegl_public.c:5502: error: ‘kasSlabCache_t’ has no member named ‘lock’
    make[2]: *** [/usr/src/modules/fglrx/firegl_public.o] Error 1
    make[1]: *** [_module_/usr/src/modules/fglrx] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-1-686-bigmem'
    make: *** [kmod_build] Error 2
    build failed with return value 2
    I'm not actually sure what this means tbh. A blind guess tells me I may be missing some dependencies maybe? The same happens when I try to install the same driver in Envy. Ubuntu does not give this error, so it's presumably something I've not set up in Debian.

    Any help is appreciated! It took me mere minutes to set up my GeForce 7900 GTO in my main machine, but installing this has really been stressful. If I can't solve it, I'll have to put Ubuntu back on, which is a shame because I prefer Debian.

    Thanks!
    Last edited by Shakey_Jake33; 04-11-2008 at 10:31 PM.

  2. #2
    Join Date
    Aug 2007
    Posts
    5,495

    Default

    Use my script, that will apply the correct patches up to 2.6.24:

    http://kanotix.com/files/install-fglrx-debian.sh

    sh install-fglrx-debian.sh -v 8.40.4

    (to use google earth you can use -v 8.39.4)

  3. #3
    Join Date
    Mar 2007
    Location
    MN, United States
    Posts
    285

    Default

    Your other option using the latest ATI driver, which works for me using a AGP X1600XT on Debian/Testing. The manual way of fixing this is to extract the ati driver, example:

    Code:
    ati-driver-installer-8-3-x86.x86_64.run --extract ./fglrx
    Then go to:

    Code:
    cd ./fglrx/arch/x86/usr/X11R6/lib
    Then make a copy of libfglrx_gamma.so.1.0 but under a different file name:

    Code:
    cp libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
    Then go back to ./fglrx/ and put in:

    Code:
    ./packages/Debian/ati-packager.sh --buildpkg sid
    Yes even put sid in even when using Debian Testing, works fine and it will build the deb packages.

    Then go back to ./fglrx/ and then install your debs.

    Afterwards just do the usual:

    Code:
    m-a prepare
    m-a a-i fglrx
    Then set up your stuff and you should be good to go.

    Of course you can do the script too but this is the manual way to get it to be able to build on Debian Testing/sid just for reference if you wanted to take that approach instead.

    So give it a shot with the latest once. If it doesn't work just use Kano's script for the older driver which will work too. His script should work with the newest driver too.
    Last edited by Malikith; 04-12-2008 at 02:01 AM.

  4. #4
    Join Date
    Aug 2007
    Posts
    5,495

    Default

    My script works for hardy, lenny or sid as well, it just does require a manually fixed xorg.conf in that case.

  5. #5
    Join Date
    Apr 2008
    Location
    Bristol, England
    Posts
    20

    Default

    Huge thanks for the help guys, works a treat now

    Tried the 8.3 driver using Malikith's way, the basic method worked fine, but I still have no luck with the driver itself. I seem to be unable to use any driver that uses ATI's new naming scheme, and I don't seem to be alone on that. Just a black screen on bootup. A lot of people with AGP cards seem to have the same problem.

    No biggie though, Kano's script with the 8.40.4 driver works great

    Thanks again!

  6. #6
    Join Date
    Mar 2007
    Location
    MN, United States
    Posts
    285

    Default

    Quote Originally Posted by Shakey_Jake33 View Post
    Huge thanks for the help guys, works a treat now

    Tried the 8.3 driver using Malikith's way, the basic method worked fine, but I still have no luck with the driver itself. I seem to be unable to use any driver that uses ATI's new naming scheme, and I don't seem to be alone on that. Just a black screen on bootup. A lot of people with AGP cards seem to have the same problem.

    No biggie though, Kano's script with the 8.40.4 driver works great

    Thanks again!
    Good to see you up and running at least. Kano's script works very well.

  7. #7
    Join Date
    Apr 2008
    Location
    Bristol, England
    Posts
    20

    Default

    Just to let people know, setting the AGP Aperture Size to 128MB in the bios solved by black screen problems with the newer drivers. Seems an unlikely fix, but it's solved it.

  8. #8
    Join Date
    Jan 2008
    Posts
    294

    Default

    Quote Originally Posted by Shakey_Jake33 View Post
    Just to let people know, setting the AGP Aperture Size to 128MB in the bios solved by black screen problems with the newer drivers. Seems an unlikely fix, but it's solved it.
    I have to set my aperture to 512 to get things working. I can get a desktop with 256 but 3D doesn't work and < 256 = black screen.

    It has been posted on here before - I would have suggested it if I had been reading all the posts.

    Does your card have 128 memory? Mine has 512. If it has 256 you may find 256 is the best option, but if you have tested games aswell as desktop then I guess it's OK anyway.

  9. #9
    Join Date
    Apr 2008
    Location
    Bristol, England
    Posts
    20

    Default

    My card has 256MB, I should probably give a higher size a go. For some reason I had it set to the BIOS default of 64, which was unusually silly of me. I gave OpenArena a go and that worked fine, so 3D definitely works.

  10. #10
    Join Date
    Apr 2008
    Location
    Bristol, England
    Posts
    20

    Default

    Sorry for the double post.

    Quick question, am I required to do the 3D Acceleration kernel module compile section with every driver install?

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts