| View previous topic :: View next topic |
| Author |
Message |
redbeardmcg
Apprentice
Joined: 12 Mar 2006
Posts: 171
Location: Suburbia Massachusetts
|
 Posted: Tue Mar 14, 2006 3:07 am Post subject: i will call you god if you help me get ati working |
 |
|
Ok, so ive tried 4 different distributions, and 3 different versions of the ati driver over the past 2 years and I have never gotten it to work. The fglrx module is loading fine (which is good because I have never gotten this far before) but I am getting errors, and fglrxinfo reports mesa 
| Code: | redbeardmcg@piston ~ $ fglrxinfo
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.2.1) |
| Code: | redbeardmcg@piston ~ $ lsmod
Module Size Used by
fglrx 451980 0
agpgart 30160 1 fglrx |
| Code: | redbeardmcg@piston ~ $ cat /var/log/Xorg.0.log|grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Specified desktop setup not supported: 8
(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): ********************************************* *
redbeardmcg@piston ~ $ cat /var/log/Xorg.0.log|grep EE
Current Operating System: Linux piston 2.6.15-gentoo-r1 #8 SMP PREEMPT Mon Mar 13 21:51:27 UTC 2006 i686
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"
(EE) fglrx(0): cannot init AGP |
Any and all help is greatly appreciated!
Thanks,
Ryan |
|
| Back to top |
|
 |
kfiaciarka
Veteran
Joined: 20 May 2005
Posts: 1498
Location: Dobre Miasto, Poland
|
|
| Back to top |
|
|
redbeardmcg
Apprentice
Joined: 12 Mar 2006
Posts: 171
Location: Suburbia Massachusetts
|
| Posted: Tue Mar 14, 2006 3:28 am Post subject: |
|
|
Ok, I loaded up via_agp and those errors went away but now I am having some new ones.
| Code: | fglrxinfo
libGL error: failed to open DRM: Operation not permitted
libGL error: reverting to (slow) indirect rendering
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.2.1) |
| Code: | cat /var/log/Xorg.0.log|grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Specified desktop setup not supported: 8 |
Here is my xorg.conf
| Code: | Section "ServerLayout"
Identifier "Simple Layout"
Screen 0 "aticonfig Screen 0" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
EndSection
Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
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" "pc101"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
# Mouse-speed setting for PS/2 mouse.
Option "Emulate3Buttons"
EndSection
Section "Monitor"
Identifier "rosewill"
HorizSync 31.5 - 79.0
VertRefresh 55.0 - 85.0
EndSection
Section "Monitor"
Identifier "aticonfig Monitor 0"
EndSection
Section "Device"
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
Identifier "9200"
Driver "ati"
EndSection
Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "9200"
Monitor "rosewill"
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 "ATI Graphics Adapter 0"
Monitor "aticonfig Monitor 0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection |
any ideas?
Thanks again.... really |
|
| Back to top |
|
|
redbeardmcg
Apprentice
Joined: 12 Mar 2006
Posts: 171
Location: Suburbia Massachusetts
|
| Posted: Tue Mar 14, 2006 3:42 am Post subject: update |
|
|
I have long suspected this was a problem with my hardware ( i have followed numerouse tutorials to a T) and I just found this:
http://www.rage3d.com/board/showthread.php?t=33831753
Seems to be a bios problem... I am going to attempt the fix.. Ill let you know if it works incase others are having the same problem |
|
| Back to top |
|
|
redbeardmcg
Apprentice
Joined: 12 Mar 2006
Posts: 171
Location: Suburbia Massachusetts
|
| Posted: Tue Mar 14, 2006 3:56 am Post subject: |
|
|
No luck, looks like mtrr is fine
| Code: | cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
reg01: base=0xf0000000 (3840MB), size= 128MB: write-combining, count=2
reg02: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=5 |
Anyone? |
|
| Back to top |
|
|
kfiaciarka
Veteran
Joined: 20 May 2005
Posts: 1498
Location: Dobre Miasto, Poland
|
| Posted: Tue Mar 14, 2006 9:17 pm Post subject: |
|
|
| Post emerge --info and hardware settings. |
|
| Back to top |
|
|
The Ennead
Apprentice
Joined: 31 Jan 2003
Posts: 157
Location: Red Half Of Manchester, UK
|
| Posted: Wed Mar 15, 2006 11:55 pm Post subject: |
|
|
Tbh m8 i'm probably not going to be a lot of help since I gave up with ATI and went Nvidia purely because of the problems with their crap drivers which if it hadn't been for Wedge's faq i'd have probably shot myself over. That guy deserves about a thousand free pints in any country he visits for writing that faq 
Anyway, a couple of things i've noticed in your post (which I came across whilst looking for something else) remind me of similar errors that I had. The first was the mtrr thing which you seem ok with but going back to rage3d and i'm wondering if also you may possibly have another problem which I spoke about in this mtrr thread http://www.rage3d.com/board/showthread.php?t=33736241&highlight=mtrr Scroll down to the Last post by Aiki_}{_Ghost (my ET clan tag at the time) and there's a bit where it says
| Quote: | Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "no"
Option "ForceGenericCPU" "no"
# BusID "PCI:2:0:0" # vendor=1002, device=4e4a
ChipID 0x4e48
Screen 0
EndSection |
That ChipID thing was something I used to con the drivers into thinkng my 9800xt was a 9800pro. It was literally the only way I could get it to work because ati drivers just wouldn't support the XT for Lord knows how many releases. I can't remember now how I went about finding out which ID number to use, it's 2 years back since I had the problem, but searching for ChipID and ATI might give you some leads.
The other thing is the "xf86_ENODEV" error you're getting. I also had that error and it was due to some kind of problem with agpgart.
| Quote: | X Fails to Load on Systems with Linux Kernel Version 2.6.x
This information applies to the following system configurations:
* Linux kernel version 2.6.x
* Any ATI Linux driver
A blank screen may appear momentarily when X starts to load. The following error message (or similar) may appear on the text console or in /var/log/XFree86.0.log:
(EE) fglrx(0): [agp] unable to acquire AGP, error ""xf86_ENODEV"
This is not a problem with the display driver.
Version 2.6 kernels require a second kernel module in addition to agpgart, which should be named similar to the manufacturer of your motherboard AGP chipset. This error message should occur if the other agp module is not loaded.
This issue can be worked around as follows:
1. First make sure that agpgart is loading properly.
2. To find out which AGP controller your motherboard uses, issue the following command: lspci | grep AGP
3. To find a list of AGP related kernel modules installed on your machine, issue the following command and look for a module (*.ko file) that suits your AGP Controller: ls /lib/modules/`uname -r`/kernel/drivers/char/agp
4. Use the modprobe command (as root) to load the module. For example: On a motherboard using a VIA® AGP Controller, you would load the via-agp.ko using modprobe as follows (notice that the trailing .ko is omitted): modprobe via-agp
Check the modprobe manpage for more information on loading kernel modules.
5. To verify that the AGP module is already loaded, run lsmod as root. With the X server running and the connection established, the usage count of this module must be greater than zero.
If you cannot find a suitable agp module for your motherboard, then you may want to upgrade to the latest version of the Linux kernel, or check your motherboard manufacturer's website for more information. |
Hope it's at least some help. GL  |
|
| Back to top |
|
|
zaai
Apprentice
Joined: 24 Jul 2004
Posts: 175
|
| Posted: Wed May 10, 2006 12:35 am Post subject: |
|
|
| redbeardmcg wrote: | Ok, I loaded up via_agp and those errors went away but now I am having some new ones.
| Code: | fglrxinfo
libGL error: failed to open DRM: Operation not permitted
libGL error: reverting to (slow) indirect rendering
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.2.1) |
|
This is a permission problem in your xorg.conf. Make sure that the following is enabled:
| Code: | Section "DRI"
Mode 0666
EndSection |
_________________
* most bugs can be reduced to either dependency or state *
Athlon64 X2 4800+ on Asus M2N SLI deluxe with 4GB Dual channel
video nVidia GForce 7300 GS 512MB (snail); xorg-7.2
kernel 2.6.24-gentoo-r3 |
|
| Back to top |
|
|
|
Kernel & Hardware
