LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-12-2004, 08:02 AM   #1
sinistre
LQ Newbie
 
Registered: May 2004
Posts: 8

Rep: Reputation: 0
agpgart, fglrx, radeon 9800


I'm using Slackware 10 with all the upgrades (with slackgrade). Unfortunately I need to use propriatary graphic drivers from ATI. Everything works - but I don't get acceleration on 3D graphics. Has anyone else had a similar problem and solved it? Or anybody have any ideas? Would be appreciated!

Quote:
root@duramater:~# startx

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/duramater:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.26 i686 [ELF]
Current Operating System: Linux duramater 2.6.9 #3 Wed Nov 17 02:21:54 CET 2004 i686
Build Date: 05 June 2004
Before reporting problems, check ...
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 11 22:49:59 2004
(==) Using config file: "/etc/X11/xorg.conf"

(WW) fglrx: No matching Device section for instance (BusID PCI:3:0:1) found
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOMEM"
(EE) fglrx(0): cannot init AGP
(WW) fglrx(0): Failed to set up write-combining range (0xa0000000,0x8000000)


==> /var/adm/messages <==
Dec 11 22:49:26 duramater udev[9798]: removing device node '/dev/vcc/7'
Dec 11 22:49:26 duramater udev[9812]: removing device node '/dev/vcc/a7'
Dec 11 22:49:59 duramater udev[9844]: configured rule in '/etc/udev/rules.d/udev.rules' at line 99 applied, added symlink '%k'
Dec 11 22:49:59 duramater udev[9844]: configured rule in '/etc/udev/rules.d/udev.rules' at line 99 applied, 'vcs7' becomes 'vcc/%n'
Dec 11 22:49:59 duramater udev[9844]: creating device node '/dev/vcc/7'
Dec 11 22:49:59 duramater udev[9851]: configured rule in '/etc/udev/rules.d/udev.rules' at line 101 applied, added symlink '%k'
Dec 11 22:49:59 duramater udev[9851]: configured rule in '/etc/udev/rules.d/udev.rules' at line 101 applied, 'vcsa7' becomes 'vcc/a%n'
Dec 11 22:49:59 duramater udev[9851]: creating device node '/dev/vcc/a7'
Dec 11 22:50:00 duramater kernel: Fire GL built-in AGP-support
Dec 11 22:50:00 duramater kernel: Based on agpgart interface v0.99 (c) Jeff Hartmann
Dec 11 22:50:00 duramater kernel: agpgart: Maximum main memory to use for agp memory: 816M
Dec 11 22:50:00 duramater kernel: agpgart: AGP aperture is 512M @ 0x80000000
Dec 11 22:50:00 duramater kernel: Power management callback for AGP chipset installed
Dec 11 22:50:00 duramater kernel: [fglrx] AGP detected, AgpState = 0x00000000 (hardware caps of chipset)

==> /var/adm/syslog <==
Dec 11 22:50:00 duramater kernel: mtrr: 0xa0000000,0x8000000 overlaps existing 0xa0000000,0x200000
Dec 11 22:50:00 duramater kernel: [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)
Dec 11 22:50:00 duramater kernel: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
Dec 11 22:50:00 duramater kernel: agpgart: Detected nVidia nForce2 chipset
Dec 11 22:50:00 duramater kernel: agpgart: Bridge device is in AGP v3 mode
Dec 11 22:50:00 duramater kernel: [fglrx:firegl_unlock] *ERROR* Process 9831 using kernel context 0
Dec 11 22:50:00 duramater kernel: mtrr: 0xa0000000,0x8000000 overlaps existing 0xa0000000,0x200000
 
Old 12-12-2004, 09:06 AM   #2
objorkum
Member
 
Registered: Aug 2003
Location: Norway
Distribution: Slackware 10.0
Posts: 231

Rep: Reputation: 30
When you ran "fglrxconfig", did you choose to use the built-in AGP or the external?
 
Old 12-12-2004, 09:53 AM   #3
sinistre
LQ Newbie
 
Registered: May 2004
Posts: 8

Original Poster
Rep: Reputation: 0
This is what my xorg.conf looks like.
Quote:
Section "Device"
Identifier "Card0"
Driver "fglrx"
VendorName "ATI Technologies Inc"
BoardName "RV350 AP [Radeon 9600]"
BusID "PCI:3:0:0" # vendor=1002, device=4150
Option "no_accel" "no"
Option "no_dri" "no"
Option "mtrr" "on"
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
EndSection
Changing "option "useinternalagpgart"" to no gives the following output in syslog:

Quote:
Dec 12 18:20:44 duramater kernel: mtrr: 0xa0000000,0x8000000 overlaps existing 0xa0000000,0x200000
Dec 12 18:20:44 duramater kernel: [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)
Dec 12 18:20:44 duramater kernel: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
Dec 12 18:20:44 duramater kernel: [fglrx:firegl_unlock] *ERROR* Process 3322 using kernel context 0
Dec 12 18:20:44 duramater kernel: mtrr: 0xa0000000,0x8000000 overlaps existing 0xa0000000,0x200000

Last edited by sinistre; 12-12-2004 at 11:26 AM.
 
Old 12-12-2004, 11:43 AM   #4
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 52
is your agp-module loaded when you start X ?
use " lsmod " to check....

egag
 
Old 12-12-2004, 12:24 PM   #5
sinistre
LQ Newbie
 
Registered: May 2004
Posts: 8

Original Poster
Rep: Reputation: 0
It's hard coded into the kernel.
 
Old 12-12-2004, 04:52 PM   #6
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 52
well...i wonder if it can work that way.
maybe i'm wrong but i thought agp should be modular.....

egag
 
Old 12-14-2004, 08:44 AM   #7
sinistre
LQ Newbie
 
Registered: May 2004
Posts: 8

Original Poster
Rep: Reputation: 0
Ok now I only get this:

[drm] failed to load kernel module "fglrx"
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): Failed to set up write-combining range (0xa0000000,0x8000000)

Guess the agpgart module should be modular... Thanks. Apparently things won't work anyway since the ati drivers isn't compatible with this latest version of X. Now things will work when the drivers are upgraded... or when I downgrade X.

Thanks.
 
Old 12-14-2004, 09:13 AM   #8
Slovak
Member
 
Registered: Oct 2004
Location: North Olmsted, Oh
Distribution: Slackware 10
Posts: 206

Rep: Reputation: 30
When you compiled the kernel, make sure that you did this....
And enable the following options:

* /dev/agpgart under ``character devices''
* MTRR (Memory Type Range Register) under ``processor type and features''

Then disable:

* Direct Rendering Manager (XFree86 DRI support) under ``character devices''
* Kernel debugging under ``Kernel hacking''
Those steps are a must for successful ATI drivers, and even at that it has been known to be a hit or miss success story for folks, I for one am on the miss list, but I know plenty of folks that have awsome 3D with the above compiled in.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Explanation please: ATI Drivers - fglrx and agpgart statguy Linux - Hardware 1 03-24-2005 10:53 AM
fglrx 3D acceleration failes due to DRM/DRI/AGPGART problems in Slackware 10, 2.6.8 DaneM Linux - Hardware 1 10-20-2004 01:33 AM
Radeon 9600 agpgart/fglrx and gerneral 3D questions jawaking00 Linux - Hardware 1 03-10-2004 11:32 AM
modprobe agpgart and fglrx ?? ludeKing Slackware 2 09-07-2003 08:10 PM
DRI not initializing on Radeon 9800 with fglrx Jawoota Linux - Hardware 0 07-23-2003 02:14 PM


All times are GMT -5. The time now is 07:20 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration