Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Error with fglrx
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Wed Aug 16, 2006 6:36 pm    Post subject: Error with fglrx Reply with quote

Code:
  (WW) fglrx: No matching Device section for instance (BusID PCI:3:0:1) found
  (EE) fglrx(0): ===[R200PreInitDAL]=== DALEnableInstance failed
  (EE) fglrx(0): PreInitDAL failed
  (EE) fglrx(0): R200PreInit failed
  (EE) Screen(s) found, but none have a usable configuration.

I just installed the ati-drivers(latest ~x86 version) and that was the error I got after I ran aticonfig --initial --input=/etc/X11/xorg.conf. I rebooted and when I tried to startx, i got that error.

Here is my xorg.conf:
Code:
Section "Files"
 
 
     #FontPath   "/usr/share/fonts/local/"
     FontPath    "/usr/share/fonts/misc/"
     FontPath    "/usr/share/fonts/Type1/"
     FontPath    "/usr/share/fonts/TTF/"
     FontPath    "/usr/share/fonts/75dpi/"
     FontPath    "/usr/share/fonts/100dpi/"
     FontPath    "/usr/share/fonts/corefonts"
 
 EndSection
 
 # **********************************************************************
 # Module section -- this is an optional section which is used to specify
 # which run-time loadable modules to load when the X server starts up.
 # **********************************************************************
 
 Section "Module"
 
     Load        "dbe"
     Load        "glx"
 #    Load       "ddc"
     Load        "type1"
     Load        "freetype"
     Load        "extmod"
     Load        "synaptics"
 
  Load "dri"
 
 EndSection
 
 
 # **********************************************************************
 # Server flags section.  This contains various server-wide Options.
 # **********************************************************************
 
 Section "ServerFlags"
 
      Option     "AllowMouseOpenFail" "true"
 
 EndSection
 
 # **********************************************************************
 # Input devices
 # **********************************************************************
 
 # **********************************************************************
 # Core keyboard's InputDevice section
 # **********************************************************************
 
 Section "InputDevice"
     Identifier      "Mouse3"
     Driver          "synaptics"
     Option          "SendCoreEvents"        "true"
     Option          "Device"                "/dev/psaux"
     Option          "Protocol"              "auto-dev"
     Option          "HorizScrollDelta"      "0"
     Option          "SHMConfig"             "on"
     # Do you keep moving the mouse while typing? Try this trick.
     #synclient TouchpadOff=1 disable your synaptics touchpad
     #synclient TouchpadOff=0 enable your synaptics touchpad
 EndSection
 
 
 Section "InputDevice"
 
     Identifier  "Keyboard1"
     Driver      "kbd"
 
     Option      "AutoRepeat"    "500 5"
     Option      "XkbModel"      "pc105"
     Option      "XkbLayout"     "us"
 
 EndSection
 
 
 # **********************************************************************
 # Core Pointer's InputDevice section
 # **********************************************************************
 
 Section "InputDevice"
 
 # Identifier and driver
 
     Identifier  "Mouse1"
     Driver      "mouse"
 
     Option      "Device"        "/dev/psaux"
     Option      "Protocol"      "ImPS/2"
     Option "ZAxisMapping" "4 5"
 
 EndSection
 
 Section "InputDevice"
     Identifier  "Mouse2"
     Driver      "mouse"
     Option      "Protocol"      "ImPS/2"
     Option      "Device"        "/dev/input/mice"
     Option      "ZAxisMapping" "4 5"
 EndSection
 
 
 # **********************************************************************
 # Monitor section
 # **********************************************************************
 
 # Any number of monitor sections may be present
 
 Section "Monitor"
 
     Identifier  "Generic Monitor"
     #Option      "DPMS"
 
     VertRefresh 50 - 75        # multisync
     HorizSync   28 - 110
 
     ModeLine "1280x800" 83.91 1280 1312 1624 1656 800 816 824 841
     ModeLine "1600x900" 173.86 1600 1672 2032 2176 900 902 914 940 +hsync +vsync
     Modeline "1280x720" 75 1280 1336 1472 1664 720 725 730 751
     Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
     Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
     ModeLine "1366x768" 88.03 1366 1424 1680 1816 768 770 782 808
     ModeLine "848x480" 31.5 848 864 952 1056 480 481 484 497
     Modeline "720x576" 14.881 720 781 829 960 576 606 610 646 interlace +hsync +vsync
     ModeLine "856x480" 31.7 856 872 960 1064 480 481 484 497
     ModeLine "1024x512" 41.3 1024 1056 1160 1296 512 513 516 531
     ModeLine "960x600" 60 960 968 1048 1264 600 601 603 625 +HSync +VSync
     ModeLine "1088x612" 81.57 1088 1136 1376 1472 612 614 626 652 +hsync +vsync
     ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
     ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
     ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
     ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
     ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
     ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
     ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
     ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
     Modeline "1280x768" 81.59 1280 1280 1384 1688 768 769 774 791
 
 EndSection
 
 # **********************************************************************
 # Graphics device section
 # **********************************************************************
 
 # Any number of graphics device sections may be present
 
 Section "Device"
     Identifier  "VESA"
     Driver      "vesa" # do not remove vesa
 EndSection
 
 
 # **********************************************************************
 # Screen sections.
 # **********************************************************************
 
 Section "Screen"
 
 # The Identifier, Device and Monitor lines must be present
 
     Identifier  "Screen 1"
     Device      "VESA"
     Monitor     "Generic Monitor"
 
 # The favoured Depth and/or Bpp may be specified here
 
     DefaultDepth 24
 
     SubSection "Display"
         Depth           8
         ViewPort        0 0
         Modes           "1024x768" "800x600" "640x480"
     EndSubsection
 
     SubSection "Display"
         Depth           16
         ViewPort        0 0
         Modes           "1024x768" "800x600" "640x480"
     EndSubsection
 
     SubSection "Display"
         Depth           24
         ViewPort        0 0
         Modes           "1024x768" "800x600" "640x480"
     EndSubsection
 
 
 EndSection
 
 
 Section "ServerLayout"
 # The Identifier line must be present
 
     Identifier  "Main Layout"
     Screen 0    "Screen 1"
     InputDevice "Mouse1" "CorePointer"
     InputDevice "Mouse2" "SendCoreEvents"
     InputDevice "Mouse3" "SendCoreEvents"
     InputDevice "Keyboard1" "CoreKeyboard"
 
 EndSection
 
 Section "DRI"
     Mode 0666
 EndSection


For reference I have an ATI Radeon X1600 Pro PCI express 256MB video card.
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
sageman
Guru
Guru


Joined: 04 May 2005
Posts: 363
Location: New Hampshire

PostPosted: Wed Aug 16, 2006 7:31 pm    Post subject: Reply with quote

Well, not sure what aticonfig is suppose to do, but it sure didn't add any entries pertaining to your ATI card in there. There should be a device section using module "fglrx" configured for your card, which there isn't.
_________________
Carlton Stedman
Gentoo Metalheads on Last.fm: http://www.last.fm/group/Gentoo+Metalheads
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Wed Aug 16, 2006 7:50 pm    Post subject: Reply with quote

sageman wrote:
Well, not sure what aticonfig is suppose to do, but it sure didn't add any entries pertaining to your ATI card in there. There should be a device section using module "fglrx" configured for your card, which there isn't.


How should i fix this?
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Wed Aug 16, 2006 11:24 pm    Post subject: Reply with quote

Alright, well, I redid everything, i re-ran aticonfig, checked my kernel, autoloaded the necessary modules and reboot my computer, but I get the same error. Here is my (new) xorg.conf:
Code:
 **********************************************************************
# Module section -- this is an optional section which is used to specify
# which run-time loadable modules to load when the X server starts up.
# **********************************************************************
# **********************************************************************
# Server flags section.  This contains various server-wide Options.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# **********************************************************************
# Screen sections.
# **********************************************************************

Section "ServerLayout"

# The Identifier line must be present
        Identifier     "Main Layout"
        Screen      0  "aticonfig-Screen[0]" 0 0
        InputDevice    "Mouse1" "CorePointer"
        InputDevice    "Mouse2" "SendCoreEvents"
        InputDevice    "Mouse3" "SendCoreEvents"
        InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

    #FontPath   "/usr/share/fonts/local/"
        FontPath     "/usr/share/fonts/misc/"
        FontPath     "/usr/share/fonts/Type1/"
        FontPath     "/usr/share/fonts/TTF/"
        FontPath     "/usr/share/fonts/75dpi/"
        FontPath     "/usr/share/fonts/100dpi/"
        FontPath     "/usr/share/fonts/corefonts"
EndSection

Section "Module"
        Load  "dbe"
        Load  "glx"
#       Load  "ddc"
        Load  "type1"
        Load  "freetype"
        Load  "extmod"
        Load  "synaptics"
        Load  "dri"
EndSection

Section "ServerFlags"
        Option      "AllowMouseOpenFail" "true"
EndSection

Section "InputDevice"

    #synclient TouchpadOff=1 disable your synaptics touchpad
    #synclient TouchpadOff=0 enable your synaptics touchpad
        Identifier  "Mouse3"
        Driver      "synaptics"
        Option      "SendCoreEvents" "true"
        Option      "Device" "/dev/psaux"
        Option      "Protocol" "auto-dev"
        Option      "HorizScrollDelta" "0"
        Option      "SHMConfig" "on"
    # Do you keep moving the mouse while typing? Try this trick.
EndSection

Section "InputDevice"
        Identifier  "Keyboard1"
        Driver      "kbd"
        Option      "AutoRepeat" "500 5"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us"
EndSection

Section "InputDevice"

# Identifier and driver
        Identifier  "Mouse1"
        Driver      "mouse"
        Option      "Device" "/dev/psaux"
        Option      "Protocol" "ImPS/2"
        Option      "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
        Identifier  "Mouse2"
        Driver      "mouse"
        Option      "Protocol" "ImPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
EndSection

Section "Monitor"

    #Option      "DPMS"
        # multisync
        Identifier   "Generic Monitor"
        HorizSync    28.0 - 110.0
        VertRefresh  50.0 - 75.0
        ModeLine     "1280x800" 83.9 1280 1312 1624 1656 800 816 824 841
        ModeLine     "1600x900" 173.9 1600 1672 2032 2176 900 902 914 940 +hsync +vsync
        ModeLine     "1280x720" 75.0 1280 1336 1472 1664 720 725 730 751
        ModeLine     "1920x1080" 172.8 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
        ModeLine     "1920x1200" 193.2 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
        ModeLine     "1366x768" 88.0 1366 1424 1680 1816 768 770 782 808
        ModeLine     "848x480" 31.5 848 864 952 1056 480 481 484 497
        ModeLine     "720x576" 14.9 720 781 829 960 576 606 610 646 +hsync +vsync interlace
        ModeLine     "856x480" 31.7 856 872 960 1064 480 481 484 497
        ModeLine     "1024x512" 41.3 1024 1056 1160 1296 512 513 516 531
        ModeLine     "960x600" 60.0 960 968 1048 1264 600 601 603 625 +hsync +vsync
        ModeLine     "1088x612" 81.6 1088 1136 1376 1472 612 614 626 652 +hsync +vsync
        ModeLine     "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
        ModeLine     "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
        ModeLine     "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
        ModeLine     "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
        ModeLine     "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
        ModeLine     "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
        ModeLine     "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
        ModeLine     "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
        ModeLine     "1280x768" 81.6 1280 1280 1384 1688 768 769 774 791
EndSection

Section "Monitor"
        Identifier   "aticonfig-Monitor[0]"
        Option      "VendorName" "ATI Proprietary Driver"
        Option      "ModelName" "Generic Autodetecting Monitor"
        Option      "DPMS" "true"
EndSection

Section "Device"

 # do not remove vesa
        Identifier  "VESA"
        Driver      "vesa"
EndSection

Section "Device"
        Identifier  "aticonfig-Device[0]"
        Driver      "fglrx"
EndSection

Section "Screen"

# The Identifier, Device and Monitor lines must be present
# The favoured Depth and/or Bpp may be specified here
        Identifier "Screen 1"
        Device     "VESA"
        Monitor    "Generic Monitor"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     8
                Modes    "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     16
                Modes    "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

Section "Screen"
        Identifier "aticonfig-Screen[0]"
        Device     "aticonfig-Device[0]"
        Monitor    "aticonfig-Monitor[0]"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection

Section "DRI"
        Mode         0666
EndSection

_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
sageman
Guru
Guru


Joined: 04 May 2005
Posts: 363
Location: New Hampshire

PostPosted: Thu Aug 17, 2006 12:05 pm    Post subject: Reply with quote

Does your video card have two monitor inputs on it? If so, try plugging your monitor into the other input. Any luck?

At least your Xorg looks like it has the right device and module now!
_________________
Carlton Stedman
Gentoo Metalheads on Last.fm: http://www.last.fm/group/Gentoo+Metalheads
Back to top
View user's profile Send private message
PaulBain
Apprentice
Apprentice


Joined: 14 Jun 2005
Posts: 159
Location: Coventry, UK

PostPosted: Thu Aug 17, 2006 1:47 pm    Post subject: Reply with quote

The only way I got direct rendering to work for me, was to compile support for my agpgart into my kernel which stopped problems with it loading.
This worked with a radeon 9200 and 9800 pro.

I also noticed fglrx is nowhere in your config file, is VESA the same thing?

Hope it helps.

Here is my xorg config:
Code:

Section "DRI"
    Mode 0666
EndSection

Section "ServerLayout"

# "SendCoreEvents".
        Identifier     "Simple Layout"
        Screen      0  "aticonfig-Screen[0]" 0 0
        InputDevice    "Mouse1" "CorePointer"
        InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# The module search path.  The default path is shown here.
        FontPath     "/usr/share/fonts/misc"
        FontPath     "/usr/share/fonts/75dpi"
        FontPath     "/usr/share/fonts/100dpi"
        FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"

        Load  "dbe"     # Double buffer extension
        SubSection "extmod"
        Option      "omit xfree86-dga"   # don't initialise the DGA extension
        EndSubSection
        Load  "freetype"
        Load  "dri"
        Load  "glx"
EndSection

Section "InputDevice"

        Identifier  "Keyboard1"
        Driver      "kbd"
        Option      "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
        Option      "XkbRules" "xorg"
        Option      "XkbModel" "microsoft"
        Option      "XkbLayout" "gb"
EndSection

Section "InputDevice"

        Identifier  "Mouse1"
        Driver      "mouse"
        Option      "Protocol" "Auto"   # Auto detect
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5 6 7"
        Option      "Emulate3Buttons"
EndSection

Section "Monitor"

        Identifier   "DELL"
        HorizSync    31.5 - 79.0
        VertRefresh  50.0 - 100.0
        Option      "VendorName" "ATI Proprietary Driver"
EndSection

Section "Monitor"
        Identifier   "aticonfig-Monitor[0]"
        Option      "VendorName" "ATI Proprietary Driver"
        Option      "ModelName" "Generic Autodetecting Monitor"
        Option      "DPMS" "true"
EndSection

Section "Device"

        Identifier  "Standard VGA"
        Driver      "vga"
        VendorName  "Unknown"
        BoardName   "Unknown"
EndSection

Section "Device"

        # unsupported card
    #VideoRam    131072
    # Insert Clocks lines here if appropriate
        Identifier  "RADEON"
        Driver      "fglrx"
        Option      "UseInternalAGPGART" "no"
        Option      "AGPFastWrite" "1"
        Option      "VideoOverlay" "on"
EndSection

Section "Device"
        Identifier  "aticonfig-Device[0]"
        Driver      "fglrx"
        Option      "UseInternalAGPGART" "no"
        Option      "VideoOverlay" "on"
EndSection

Section "Screen"
        Identifier "Screen 1"
        Device     "RADEON"
        Monitor    "DELL"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     8
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     16
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

Section "Screen"
        Identifier "aticonfig-Screen[0]"
        Device     "aticonfig-Device[0]"
        Monitor    "aticonfig-Monitor[0]"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     8
        Option      "UseInternalAGPGART" "no"
        Option      "AGPFastWrite" "1"
        Option      "VideoOverlay" "on"
EndSection

Section "Device"
        Identifier  "aticonfig-Device[0]"
        Driver      "fglrx"
        Option      "UseInternalAGPGART" "no"
        Option      "VideoOverlay" "on"
EndSection

Section "Screen"
        Identifier "Screen 1"
        Device     "RADEON"
        Monitor    "DELL"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     8
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     16
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

Section "Screen"
        Identifier "aticonfig-Screen[0]"
        Device     "aticonfig-Device[0]"
        Monitor    "aticonfig-Monitor[0]"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     8
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     16
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Thu Aug 17, 2006 2:41 pm    Post subject: Reply with quote

My video card only has 1 monitor output and as far as I know, /dev/agpgart is "ENABLED" in my kernel, Ill build it as a module and then see how it goes.

Edit: It should be noted though that I have a PCIe card, but I read on wedge's Radeon ATI FAQ that many people couldn't get them working with PCIe cards unless agp support was working as well.
Edit 2: A closer look at my Vid card shows it has VGA and DVI out, I am using VGA now. Also, I compiled /dev/agpgart support as a modules and I added it to my modules.autoload.d, but when I try to load "agpgart" it says it has cant and fails to load it.
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
PaulBain
Apprentice
Apprentice


Joined: 14 Jun 2005
Posts: 159
Location: Coventry, UK

PostPosted: Thu Aug 17, 2006 3:23 pm    Post subject: Reply with quote

What is the output of fglrxinfo?

I found compiling support worked best rather than module.

Do you know why id dosent say fglrx under driver but says VESA ?

Thanks

Paul
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Thu Aug 17, 2006 3:25 pm    Post subject: Reply with quote

PaulBain wrote:
What is the output of fglrxinfo?

I found compiling support worked best rather than module.

Do you know why id dosent say fglrx under driver but says VESA ?

Thanks

Paul


fglrxinfo:
Code:
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
display: :0.0  screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.2)


As for why it says VESA, I dont really know. :?
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
PaulBain
Apprentice
Apprentice


Joined: 14 Jun 2005
Posts: 159
Location: Coventry, UK

PostPosted: Thu Aug 17, 2006 4:58 pm    Post subject: Reply with quote

Cool, looks like DRI isnt working properly, have you recompiled agpgart back into the kernel?

Have you done:
Code:

modprobe fglrx
eselect opengl set ati
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Thu Aug 17, 2006 5:02 pm    Post subject: Reply with quote

PaulBain wrote:
Cool, looks like DRI isnt working properly, have you recompiled agpgart back into the kernel?

Have you done:
Code:

modprobe fglrx
eselect opengl set ati


agpgart is compiled as a module in the kernel, but won't load for some reason.

Edit:
Code:
modprobe fglrx

gives this error:
Code:

WARNING: Error inserting agpgart (/lib/modules/2.6.17-reiser4-r1-nosmp/kernel/drivers/char/agp/agpgart.ko): Invalid module format

_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
bdm
Guru
Guru


Joined: 20 Jan 2006
Posts: 305
Location: Canada, Barrie, Ontario

PostPosted: Thu Aug 17, 2006 5:22 pm    Post subject: Reply with quote

Could you please post the output of dmesg?

I found this from the ATI FAQ that may be useful to you:
wrote:
Question 4.7: When I try to run "modprobe fglrx" it doesn't work
There are a number of possible causes for this. The first thing to do is to get the error message given when you try to load the module. If the output from modprobe doesn't tell you anything, check the last few lines of "dmesg" output just after you've run it. There will usually be a better description of the error there.

Check that your /usr/src/linux symlink is pointing to the set of kernel sources that you are currently using. If the link isn't correct, the module will be generated for the wrong kernel and modprobe won't be able to find it. To update the link, use the following command: ln -sf /usr/src/linux-2.x.y /usr/src/linux

If modprobe cannot find the module even after checking the /usr/src/linux symlink is correct, the problem is usually that the compilation of the module has failed. The ati-drivers ebuilds will complete successfully even if the module fails to compile, so it is easy to miss this problem. Re-run the emerge, and watch carefully for errors in the compilation process, particularly if you are using a heavily patched kernel (see Q2.2).

If modprobe fails with an "Invalid module format message", and the dmesg output contains lines similar to this: "fglrx: version magic '2.6.1-gentoo-r1 SMP preempt K7 gcc-3.3' should be '2.6.1-gentoo-r1 SMP preempt K7 gcc-3.2'" then it usually means that you have compiled the drivers with a different gcc version than you compiled the kernel with. To fix this, just recompile the drivers with the same gcc version as the kernel (the second one in the message above), or recompile both driver and kernel with the same version. This error may also be caused in other ways. For example, if you have compiled a kernel with 4k stacks support, but are still using the fglrx module from a normal 8k stacks kernel, you will get a message similar to that above, except that the difference between the two versions will be that one mentions "4KSTACKS" while the other does not. In this case, the solution is to remerge the drivers and load the newly compiled module.

If the "dmesg" output mentions "unresolved symbols", it's possible that the kernel version you're using has had some patches applied to it that aren't compatible with the drivers (Q2.2). The easiest thing to do is try a different kernel version. If you can create a patch for the drivers that fixes the problem, submit it to bugs.gentoo.org so that it can be included in future releases of the ebuild.

If the "dmesg" output says something similar to "the fglrx module must be loaded before any other DRM module", then it probably means that you still have DRM support in your kernel, which has been loaded before the fglrx module and is preventing it from working properly. Another indication of this problem is an "Operation not permitted" error from modprobe. See Q2.1 for more information on the DRM settings in the kernel.

If the error is "No device found", it means the driver does not support your card. If you have an older card, there's not much you can do except try the opensource "radeon" driver. If you have a new card, it's possible that the driver simply hasn't been updated with the necessary information to allow it to recognise your device. It can be made to work with a little extra effort. See Q4.41 and fglrx_binary_edit.
Back to top
View user's profile Send private message
hookooekoo
Apprentice
Apprentice


Joined: 02 May 2004
Posts: 196

PostPosted: Thu Aug 17, 2006 5:46 pm    Post subject: Reply with quote

Sorry wrong thread.

Last edited by hookooekoo on Thu Aug 17, 2006 6:14 pm; edited 2 times in total
Back to top
View user's profile Send private message
bdm
Guru
Guru


Joined: 20 Jan 2006
Posts: 305
Location: Canada, Barrie, Ontario

PostPosted: Thu Aug 17, 2006 5:48 pm    Post subject: Reply with quote

hookooekoo wrote:
Very Helpful bdm

Code:
ittomlt ~ # dmesg |grep "no device"
lp: driver loaded but no devices found


Now what are my options? use the radeon driver that works horrid?

or

Code:
If the error is "No device found", it means the driver does not support your card. If you have an older card, there's not much you can do except try the opensource "radeon" driver. If you have a new card, it's possible that the driver simply hasn't been updated with the necessary information to allow it to recognise your device. It can be made to work with a little extra effort. See Q4.41 and fglrx_binary_edit.


Now off to see if I can make the second option work :)


Not to be rude or anything. But could you post that in your thread please? It might interfere with the original posters. ;)
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Thu Aug 17, 2006 5:56 pm    Post subject: Reply with quote

Code:
dmesg
 (level, low) -> IRQ 16
[4294721.031000] PCI: Setting latency timer of device 0000:00:10.2 to 64
[4294721.343000] intel8x0_measure_ac97_clock: measured 50741 usecs
[4294721.343000] intel8x0: clocking to 46838
[4294757.967000] EXT3 FS on dm-0, internal journal
[4294758.556000] agpgart: exports duplicate symbol agp_bridge (owned by kernel)
[4294758.672000] agpgart: exports duplicate symbol agp_bridge (owned by kernel)
[4294758.739000] agpgart: exports duplicate symbol agp_bridge (owned by kernel)
[4294758.786000] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[4294758.788000] [fglrx] Maximum main memory to use for locked dma buffers: 427 MBytes.
[4294758.788000] [fglrx] module loaded - fglrx 8.27.10 [Jul 27 2006] on minor 0
[4294759.417000] kjournald starting.  Commit interval 5 seconds
[4294759.417000] EXT3 FS on sda1, internal journal
[4294759.417000] EXT3-fs: mounted filesystem with ordered data mode.
[4294759.774000] Adding 1048568k swap on /dev/VolGroup00/LogVol01.  Priority:-1 extents:1 across:1048568k
[4294779.783000] Bridge firewalling registered
[4294816.503000] fbsplash: console 1 using theme 'default'
[4294816.509000] fbsplash: switched splash state to 'on' on console 1
[4294816.582000] fbsplash: console 2 using theme 'default'
[4294816.588000] fbsplash: switched splash state to 'on' on console 2
[4294816.611000] fbsplash: console 3 using theme 'default'
[4294816.684000] fbsplash: switched splash state to 'on' on console 3
[4294816.760000] fbsplash: console 4 using theme 'default'
[4294816.766000] fbsplash: switched splash state to 'on' on console 4
[4294816.771000] fbsplash: console 11 using theme 'default'
[4294816.777000] fbsplash: switched splash state to 'on' on console 11
[4294915.524000] NET: Registered protocol family 10
[4294915.524000] lo: Disabled Privacy Extensions
[4294915.524000] IPv6 over IPv4 tunneling driver
[4294926.065000] eth0: no IPv6 routers present
[4301532.619000] agpgart: exports duplicate symbol agp_bridge (owned by kernel)
[4301606.366000] agpgart: exports duplicate symbol agp_bridge (owned by kernel)
[4304632.508000] agpgart: exports duplicate symbol agp_bridge (owned by kernel)


Thats the relevant part of its output. Also, my symlink is pointing to the correct kernel.

Code:
ls -l /usr/src/linux
lrwxrwxrwx 1 root root 23 2006-08-16 03:48 /usr/src/linux -> linux-2.6.17-reiser4-r1

Code:
uname -r
2.6.17-reiser4-r1-nosmp

_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
hookooekoo
Apprentice
Apprentice


Joined: 02 May 2004
Posts: 196

PostPosted: Thu Aug 17, 2006 6:13 pm    Post subject: Reply with quote

You are correct bdm, i thought I was in my thread.
Back to top
View user's profile Send private message
PaulBain
Apprentice
Apprentice


Joined: 14 Jun 2005
Posts: 159
Location: Coventry, UK

PostPosted: Thu Aug 17, 2006 9:09 pm    Post subject: Reply with quote

Sorry, I havnt been very clear, I had problems loading the agpgart module for via from autoload modules, so I compiled everything directly into the kernel (<*> not <M>), and then worked, (leaving the autoload for fglrx in).

I know the guide says to use the module but it never worked for me!

Also, it is important to note, every time you compile your kernel, you must recompile ati-drivers and if you have ati-drivers-extras do them aswell.
I made that mistake so many times I wrote a script to do it

Code:

#!/bin/bash

mount /boot
cd /usr/src/linux

make && make modules modules_install install
umount /boot
emerge ati-drivers

# uncomment following line if needed:
#emerge ati-drivers-extras

Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Thu Aug 17, 2006 9:20 pm    Post subject: Reply with quote

PaulBain wrote:
Sorry, I havnt been very clear, I had problems loading the agpgart module for via from autoload modules, so I compiled everything directly into the kernel (<*> not <M>), and then worked, (leaving the autoload for fglrx in).

I know the guide says to use the module but it never worked for me!

Also, it is important to note, every time you compile your kernel, you must recompile ati-drivers and if you have ati-drivers-extras do them aswell.
I made that mistake so many times I wrote a script to do it

Code:

#!/bin/bash

mount /boot
cd /usr/src/linux

make && make modules modules_install install
umount /boot
emerge ati-drivers

# uncomment following line if needed:
#emerge ati-drivers-extras



Alright, il build everything into the kernel, (nvidia_agp and agpgart), also, ill do the same for PCIe support, and autload fglrx at boot, right?
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
PaulBain
Apprentice
Apprentice


Joined: 14 Jun 2005
Posts: 159
Location: Coventry, UK

PostPosted: Thu Aug 17, 2006 9:28 pm    Post subject: Reply with quote

Sounds good to me, it seemed to stop my problem, just hope it does for you 2!

Paul
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Thu Aug 17, 2006 9:52 pm    Post subject: Reply with quote

:( Doesn't want to work still. Everything has the * instead of M but glxinfo still shows Mesa. I did re-emerge ati-drivers after I rebuilt the kernel, so I dont know whats wrong.

Edit: I've tried a lot and it should work by now, if anyone has anything that they know that I haven't done, please let me know so I can try this out, i really want 3d acceleration, ive been working on this for weeks!

Edit 2:
I just noticed that it looks for a PCI dvice with teh ID 3:0:1, lspci shows my video card as 3:0:0
Code:
03:00.0 VGA compatible controller: ATI Technologies Inc RV530 [Radeon X1600]
03:00.1 Display controller: ATI Technologies Inc RV530 [Radeon X1600] (Secondary)

Is this the source of my errors, and can I fix this somehow?
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Fri Aug 18, 2006 10:12 pm    Post subject: Reply with quote

I just read that the 8.28 drivers will have more support for X1x00 Cards, ill have to wait till then, anyone know when they are coming out?
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
VincenzoVega
n00b
n00b


Joined: 15 Aug 2006
Posts: 42
Location: The land of mills and wooden shoes

PostPosted: Fri Aug 18, 2006 11:48 pm    Post subject: Reply with quote

Varean wrote:
I just read that the 8.28 drivers will have more support for X1x00 Cards, ill have to wait till then, anyone know when they are coming out?

You can already download them @ the Ati site.
8.28.8 to be exact.

This is the link to the ATI Driver Installer :
https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.28.8.run

I hope it gets into portage soon 8)
Back to top
View user's profile Send private message
Varean
Guru
Guru


Joined: 03 Jul 2005
Posts: 436
Location: California, USA

PostPosted: Sat Aug 19, 2006 3:49 am    Post subject: Reply with quote

VincenzoVega wrote:
Varean wrote:
I just read that the 8.28 drivers will have more support for X1x00 Cards, ill have to wait till then, anyone know when they are coming out?

You can already download them @ the Ati site.
8.28.8 to be exact.

This is the link to the ATI Driver Installer :
https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.28.8.run

I hope it gets into portage soon 8)


Looks promising, Ill give it a shot.

Edit: I get the same PreInitDALEnable failed error, not much more support for the X1x00 cards I guess. :lol:
_________________
Registered Linux User #387568
Back to top
View user's profile Send private message
hookooekoo
Apprentice
Apprentice


Joined: 02 May 2004
Posts: 196

PostPosted: Tue Aug 29, 2006 4:53 pm    Post subject: Reply with quote

I tried installing the new driver, but got the following error.

Code:
ittomlt ~ # cat /usr/share/fglrx/fglrx-install.log
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
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
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.17-gentoo-r4/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-2.6.17-gentoo-r4'
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:447: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function `firegl_stub_open':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:570: warning: assignment discards qualifiers from pointer target type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: At top level:
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2246: warning: 'deferred_flush' defined but not used
  LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
  Building modules, stage 2.
  MODPOST
  CC      /lib/modules/fglrx/build_mod/2.6.x/fglrx.mod.o
  LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
make[1]: Leaving directory `/usr/src/linux-2.6.17-gentoo-r4'
build succeeded with return value 0
duplicating results into driver repository...
done.
==============================
- recreating module dependency list
- trying a sample load of the kernel modules
failed.
[Error] Kernel Module : Failed to install compiled kernel module - please consult readme.


Anyone successfully installed this? Any idea what I need to do to fix this? I tried to consult the readme but it didn't exist.
Back to top
View user's profile Send private message
PaulBain
Apprentice
Apprentice


Joined: 14 Jun 2005
Posts: 159
Location: Coventry, UK

PostPosted: Tue Aug 29, 2006 7:29 pm    Post subject: Reply with quote

Are you using the newest version, and was it masked with ~x86 ?
I have had problems before with that sort of thing and just had to wait until it was stable.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum