ATi driver big problem

Discussion in 'Linux, BSD and Other OS's' started by Willz, Dec 12, 2006.

  1. Willz

    Willz MiCrO$oFt $uK$ :D

    Likes Received:
    36
    Trophy Points:
    48
    Hi, this is really driving me up the wall now, its making me think they must be a problem with my graphics card.

    I followed all the instructions from the link to installing ATi drivers from the getting more from K/ubuntu thread, and when it says to check if it works using that flgrxinfo command, i get this, instead of ATi Techonologies:

    display: :0.0 screen: 0
    OpenGL vendor string: Mesa project: Mesa Home Page
    OpenGL renderer string: Mesa GLX Indirect
    OpenGL version string: 1.2 (1.5 Mesa 6.4.1)

    What going on? how come is the drivers not working now?

    edit** Also tried the following command: sudo modprobe fglrx, and i got:

    FATAL: Could not open '/lib/modules/2.6.15-27-k7/volatile/fglrx.ko': No such file or directory

    sudo rmmod radeon:

    ERROR: Module radeon does not exist in /proc/modules


    root@C0A8080A:/home/will# sudo rmmod ati-agp
    ERROR: Module ati_agp does not exist in /proc/modules


    also, seems some stuff is missing in the xorg.conf file, i did not delete it aswell.

    Code:
    # /etc/X11/xorg.conf (xorg X Window System server configuration file)
    #
    # This file was generated by dexconf, the Debian X Configuration tool, using
    # values from the debconf database.
    #
    # Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
    # (Type "man /etc/X11/xorg.conf" at the shell prompt.)
    #
    # This file is automatically updated on xserver-xorg package upgrades *only*
    # if it has not been modified since the last upgrade of the xserver-xorg
    # package.
    #
    # If you have edited this file but would like it to be automatically updated
    # again, run the following command:
    #   sudo dpkg-reconfigure -phigh xserver-xorg
    
    Section "ServerLayout"
    	Identifier     "Default Layout"
    	Screen      0  "aticonfig-Screen[0]" 0 0
    	InputDevice    "Generic Keyboard"
    	InputDevice    "Configured Mouse"
    	InputDevice    "stylus" "SendCoreEvents"
    	InputDevice    "cursor" "SendCoreEvents"
    	InputDevice    "eraser" "SendCoreEvents"
    EndSection
    
    Section "Files"
    
    	# path to defoma fonts
    	FontPath     "/usr/share/X11/fonts/misc"
    	FontPath     "/usr/share/X11/fonts/cyrillic"
    	FontPath     "/usr/share/X11/fonts/100dpi/:unscaled"
    	FontPath     "/usr/share/X11/fonts/75dpi/:unscaled"
    	FontPath     "/usr/share/X11/fonts/Type1"
    	FontPath     "/usr/share/X11/fonts/100dpi"
    	FontPath     "/usr/share/X11/fonts/75dpi"
    	FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
    EndSection
    
    Section "Module"
    	Load  "i2c"
    	Load  "bitmap"
    	Load  "ddc"
    	Load  "dri"
    	Load  "extmod"
    	Load  "freetype"
    	Load  "glx"
    	Load  "int10"
    	Load  "type1"
    	Load  "vbe"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Generic Keyboard"
    	Driver      "kbd"
    	Option	    "CoreKeyboard"
    	Option	    "XkbRules" "xorg"
    	Option	    "XkbModel" "pc105"
    	Option	    "XkbLayout" "gb"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Configured Mouse"
    	Driver      "mouse"
    	Option	    "CorePointer"
    	Option	    "Device" "/dev/input/mice"
    	Option	    "Protocol" "ExplorerPS/2"
    	Option	    "ZAxisMapping" "4 5"
    	Option	    "Emulate3Buttons" "true"
    EndSection
    
    Section "InputDevice"
    
                                                          # /dev/input/event
                                                          # for USB
    	Identifier  "stylus"
    	Driver      "wacom"
    	Option	    "Device" "/dev/wacom"          # Change to 
    	Option	    "Type" "stylus"
    	Option	    "ForceDevice" "ISDV4"               # Tablet PC ONLY
    EndSection
    
    Section "InputDevice"
    
                                                          # /dev/input/event
                                                          # for USB
    	Identifier  "eraser"
    	Driver      "wacom"
    	Option	    "Device" "/dev/wacom"          # Change to 
    	Option	    "Type" "eraser"
    	Option	    "ForceDevice" "ISDV4"               # Tablet PC ONLY
    EndSection
    
    Section "InputDevice"
    
                                                          # /dev/input/event
                                                          # for USB
    	Identifier  "cursor"
    	Driver      "wacom"
    	Option	    "Device" "/dev/wacom"          # Change to 
    	Option	    "Type" "cursor"
    	Option	    "ForceDevice" "ISDV4"               # Tablet PC ONLY
    EndSection
    
    Section "Monitor"
    	Identifier   "aticonfig-Monitor[0]"
    	Option	    "VendorName" "ATI Proprietary Driver"
    	Option	    "ModelName" "Generic Autodetecting Monitor"
    	Option	    "DPMS" "true"
    EndSection
    
    Section "Device"
    	Identifier  "aticonfig-Device[0]"
    	Driver      "fglrx"
    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 
    I go to display, and get this error:
    the module display could not be loaded.
     
  2. sabashuali

    sabashuali Ani Ma'amin

    Likes Received:
    6
    Trophy Points:
    38
    I am having a bit of a problem as well. I am running Debian (Sid) with Kernel image- 2.6.16-18, I think....

    I have downloaded the automated driver from the ATI(AMD) site and followed their instructions.
    At the end of the process, I get a message the there were errors but I do not get any indication that the driver has not been installed.
    This is the output of the install log file -
    I am not sure what readme it is talking about... but I suppose I will have to go back to the site and see....

    I am running, as far as I know the latest kernel module so I am not sure what's the meaning of the log.... :dry:
     

Share This Page