Announcement

Collapse
No announcement yet.

Slamd64 (64 Bit slackware) and ATI Radeon (catalyst) driver problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    ljones
    Junior Member

  • ljones
    replied
    Originally posted by ArTourter View Post
    From your dmesg dump:


    This is the same error as on Slackware 32bit. The requirements for the AMD kernel module have changed in 9.1 and above, without any mention in the changelog: it now requires PCI_MSI enabled in the kernel and this is not the case in the standard Slackware kernel (or Slamd64). You will need to recompile your kernel with this turned on for the newer fglrx to work. Otherwise you have to go back to 8.12 or prior.

    Slackware-current with 2.6.28.8 has now PSI_MSI enabled by default in the kernel and so does Slamd64-current. However I haven't tried fglrx in -current yet (do not want to upgrade to kde4 just yet).

    Hope this is helpful
    Yep looks like I'll have to compile a kernel. I checked the normal slackware current version (it is currently 2.6.28.8 as you say) however the slamd64 kernel current appears to be different (example here - ftp://ftp.gtlib.gatech.edu/pub/slamd...t/slackware/a/ ), they are using 2.6.28.7 . I tried installing this on the offchance that PSI_MSI would be enabled, but no luck, installing the newer kernel made no difference, no accelration.

    Guess its time to download a kernel and compile it !

    EDIT
    Now things might have worked -- after reinstalling the drivers at the command line and typing aticonfig --initial things may be working (plus reboot). Glxinfo now says "yes" to direct rendering; glxgears gives me around 521 FPS, while fgl_glxgears comes in at just a little more, around 644 FPS. Though I have no idea if those numbers are bad, good or about normal!

    As for KDE 4 I see its packages are in current, however I have no idea which packages to install! (I don't think *everything* KDE 4 in slackware needs is in the KDE/ directory).

    Should anyone need it btw after installing the new kernel bits 'n' pieces (from here - ftp://ftp.gtlib.gatech.edu/pub/slamd...t/slackware/a/ ) and installing these files :


    kernel-firmware-2.6.28.7-noarch_slamd64-1.tgz
    kernel-generic-2.6.28.7-x86_64_slamd64-1.tgz
    kernel-huge-2.6.28.7-x86_64_slamd64-1.tgz
    kernel-modules-2.6.28.7-x86_64_slamd64-1.tgz
    kernel-source-2.6.28.7-noarch_slamd64-1.tgz


    I also adjusted my lilo.conf (and and ran lilo) to point at /boot/vmlinuz-huge-2.6.28.7

    Here's the X server log after doing the above:
    http://www.pastebin.ca/1369730

    And the output of dmesg:
    http://www.pastebin.ca/1369732

    uname -r reports 2.6.28.7

    If this is all working now I must type it all out as a sequence of steps so I can follow it through! And the system didn't restart if I exited X !

    ljones
    ljones
    Junior Member
    Last edited by ljones; 23 March 2009, 07:36 PM.

    Leave a comment:

  • ArTourter
    Junior Member

  • ArTourter
    replied
    From your dmesg dump:
    fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
    fglrx: Unknown symbol pci_disable_msi
    fglrx: Unknown symbol pci_enable_msi
    This is the same error as on Slackware 32bit. The requirements for the AMD kernel module have changed in 9.1 and above, without any mention in the changelog: it now requires PCI_MSI enabled in the kernel and this is not the case in the standard Slackware kernel (or Slamd64). You will need to recompile your kernel with this turned on for the newer fglrx to work. Otherwise you have to go back to 8.12 or prior.

    Slackware-current with 2.6.28.8 has now PCI_MSI enabled by default in the kernel and so does Slamd64-current. However I haven't tried fglrx in -current yet (do not want to upgrade to kde4 just yet).

    Hope this is helpful
    ArTourter
    Junior Member
    Last edited by ArTourter; 23 March 2009, 07:04 PM.

    Leave a comment:

  • ljones
    Junior Member

  • ljones
    replied
    Y'learn something new every day . I had never heard of a pastebin before!

    Anyways, here is the output of dmesg and the X log file;

    First of all, dmesg;
    http://www.pastebin.ca/1369456

    And then the X server's log;
    http://www.pastebin.ca/1369457

    hope this helps!

    ljones

    Leave a comment:

  • bridgman
    AMD Linux

  • bridgman
    replied
    Go to www.pastebin.ca or any of the other locations -- I think there are pastebin sites around the world). That site will let you paste in a big block of text, then when you save will give you a link to the resulting page.

    Leave a comment:

  • ljones
    Junior Member

  • ljones
    replied
    How do I pastebin? I tried to put my log and dmesg in seperate posts here, but they are too big x.x

    I could always try zipping them and uuencoding them, would that work?

    ljones
    ljones
    Junior Member
    Last edited by ljones; 23 March 2009, 01:53 PM.

    Leave a comment:

  • bridgman
    AMD Linux

  • bridgman
    replied
    It's wierd, I'm not finding them either. Even if the discussion was on IRC rather than Phoronix it would have shown up in the logs. I found *this* thread easily enough

    Ah well... can you pls pastebin your entire log as well as dmesg output and maybe we'll find a clue there.

    Leave a comment:

  • ljones
    Junior Member

  • ljones
    replied
    Originally posted by bridgman View Post
    The kernel driver isn't starting up so you have no acceleration. The driver is saying that it can't find the X server version, which I don't remember seeing before.

    Someone else was trying to get slamd working here a couple of days ago, let's see if we can find those posts.
    Maybe my X server is too old? Though it is the one that slamd64 comes with. Wonder where those other posts are, I've not come across 'em yet.



    ljones

    Leave a comment:

  • bridgman
    AMD Linux

  • bridgman
    replied
    The kernel driver isn't starting up so you have no acceleration. The driver is saying that it can't find the X server version, which I don't remember seeing before.

    Someone else was trying to get slamd working here a couple of days ago, let's see if we can find those posts.

    Leave a comment:

  • ljones
    Junior Member

  • ljones
    replied
    !

    Output of /var/log/Xorg.0.log

    Code:
    (==) fglrx(0): NoDRI = NO
    (II) Loading sub module "fglrxdrm"
    (II) LoadModule: "fglrxdrm"
    (II) Reloading /usr/lib64/xorg/modules/linux//libfglrxdrm.so
    (==) fglrx(0): Capabilities: 0x00000000
    (==) fglrx(0): CapabilitiesEx: 0x00000000
    (==) fglrx(0): cpuFlags: 0x4000001f
    (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
    (WW) fglrx(0): No DRM connection for driver fglrx.
    (II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
    (==) fglrx(0): UseFastTLS=0
    (==) fglrx(0): BlockSignalsOnLock=1
    (II) fglrx(0): Direct rendering disabled
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC?  No, I don't.
    (II) resource ranges after preInit:
    	[0] 0	0	0xfbb00000 - 0xfbbfffff (0x100000) MX[B]
    	[1] 0	0	0xfbcf0000 - 0xfbcfffff (0x10000) MX[B]
    	[2] 0	0	0xd0000000 - 0xdfffffff (0x10000000) MX[B]
    	[3] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
    	[4] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
    	[5] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
    	[6] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
    	[7] -1	0	0xfbff0000 - 0xfbffffff (0x10000) MX[B]
    	[8] -1	0	0xfaff0000 - 0xfaffffff (0x10000) MX[B]
    	[9] -1	0	0xfbeff000 - 0xfbefffff (0x1000) MX[B]
    	[10] -1	0	0xfbdfec00 - 0xfbdfec7f (0x80) MX[B]
    	[11] -1	0	0xfbdff000 - 0xfbdff07f (0x80) MX[B]
    	[12] -1	0	0xfbdff400 - 0xfbdff47f (0x80) MX[B]
    	[13] -1	0	0xfbdff800 - 0xfbdfffff (0x800) MX[B]
    	[14] -1	0	0xfbce8000 - 0xfbcebfff (0x4000) MX[B]
    	[15] -1	0	0xfbaf9000 - 0xfbaf9fff (0x1000) MX[B]
    	[16] -1	0	0xfbaf4000 - 0xfbaf7fff (0x4000) MX[B]
    	[17] -1	0	0xfbafa800 - 0xfbafa8ff (0x100) MX[B]
    	[18] -1	0	0xfbafb000 - 0xfbafbfff (0x1000) MX[B]
    	[19] -1	0	0xfbafc000 - 0xfbafcfff (0x1000) MX[B]
    	[20] -1	0	0xfbaff000 - 0xfbaff0ff (0x100) MX[B]
    	[21] -1	0	0xfbafd000 - 0xfbafdfff (0x1000) MX[B]
    	[22] -1	0	0xfbafe000 - 0xfbafefff (0x1000) MX[B]
    	[23] -1	0	0xfbaff800 - 0xfbaffbff (0x400) MX[B]
    	[24] -1	0	0xfbb00000 - 0xfbbfffff (0x100000) MX[B](B)
    	[25] -1	0	0xfbcf0000 - 0xfbcfffff (0x10000) MX[B](B)
    	[26] -1	0	0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
    	[27] 0	0	0x000a0000 - 0x000affff (0x10000) MS[B](OprU)
    	[28] 0	0	0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU)
    	[29] 0	0	0x000b8000 - 0x000bffff (0x8000) MS[B](OprU)
    	[30] 0	0	0x0000d000 - 0x0000d0ff (0x100) IX[B]
    	[31] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
    	[32] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
    	[33] -1	0	0x0000e800 - 0x0000e8ff (0x100) IX[B]
    	[34] -1	0	0x0000ff00 - 0x0000ff0f (0x10) IX[B]
    	[35] -1	0	0x000001f0 - 0x000001f0 (0x1) IX[B]
    	[36] -1	0	0x000001f0 - 0x000001f7 (0x8) IX[B]
    	[37] -1	0	0x000001f0 - 0x000001f0 (0x1) IX[B]
    	[38] -1	0	0x000001f0 - 0x000001f7 (0x8) IX[B]
    	[39] -1	0	0x00008000 - 0x0000800f (0x10) IX[B]
    	[40] -1	0	0x00009000 - 0x00009003 (0x4) IX[B]
    	[41] -1	0	0x0000a000 - 0x0000a007 (0x8) IX[B]
    	[42] -1	0	0x0000b000 - 0x0000b003 (0x4) IX[B]
    	[43] -1	0	0x0000c000 - 0x0000c007 (0x8) IX[B]
    	[44] -1	0	0x0000d000 - 0x0000d0ff (0x100) IX[B](B)
    	[45] 0	0	0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
    	[46] 0	0	0x000003c0 - 0x000003df (0x20) IS[B](OprU)
    (II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
    (WW) fglrx(0): could not detect X server version (query_status=-1)
    (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized. 
    (WW) fglrx(0): ***********************************************
    (WW) fglrx(0): * DRI initialization failed!                  *
    (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
    (WW) fglrx(0): * 2D acceleraton available (MMIO)             *
    (WW) fglrx(0): * no 3D acceleration available                *
    (WW) fglrx(0): ********************************************* *
    (II) fglrx(0): FBADPhys: 0x0 FBMappedSize: 0x10000000
    (==) fglrx(0): Write-combining range (0xd0000000,0x10000000)
    (II) fglrx(0): FBMM initialized for area (0,0)-(1728,8191)
    (II) fglrx(0): FBMM auto alloc for area (0,0)-(1728,1680) (front color buffer - assumption)
    (II) fglrx(0): Largest offscreen area available: 1728 x 6511
    (NI) fglrx(0): ASIC Family ID/Name:75/RS780 
    
    (NI) fglrx(0): ASIC Rev ID/Name:19/Not RV6xx family Device 
    
    (NI) fglrx(0): ASIC Device ID/Name:0X9610/Not RV6xx family Device 
    
    (NI) fglrx(0): CPLIB is initialized.
     
    (==) fglrx(0): Backing store disabled
    Ok, I'm stumped - I've installed the drivers but I just cannot get 3d to work properly. XFCE's compositing effects work and are fast if the windows are small, but slow down if they are larger. Windows are *really* slow if I turn off XFCE's compisiting effects!



    Anyone know what is going on?!

    ljones

    Leave a comment:

  • ljones
    Junior Member

  • ljones
    replied
    Ok, I'm going to try to reinstall everything, start from scratch. I just looked in my /var/log/Xorg.0.log file and saw this:

    Code:
    fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
    fglrx(0): could not detect X server version (query_status=1)
    fglrx(0): atiddxDriScreenInit failed. GPS not been initalised.
    Thinking something has got messed up somewhere .....

    ljones

    Leave a comment:

Working...
X