SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running slack current with 2.6.10 as my kernel and I have an ATI 9200 SE radeon for the vid card. Everything seems to be going and I can modprobe the fglrx and everything, does anyone know what I am missing or can someone offer suggestions?
what? whats the problem? you said 'everything seems to be going...' i assume you meant to add 'fine' in there.
whats the problem your having? what error messages (if the case)? what did you do to produce the message? etc etc
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:2:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0xf8871000
(II) fglrx(0): [drm] mapped SAREA 0xf8871000 to 0xb7ced000
(II) fglrx(0): [drm] framebuffer handle = 0xd0000000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.10.19
(II) fglrx(0): Date: Feb 9 2005
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.10
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0xe5000000
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOMEM"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xf8871000 at 0xb7ced000
(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: 0xd0000000 FBMappedSize: 0x08000000
(II) fglrx(0): FBMM initialized for area (0,0)-(1600,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1600,1200) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) fglrx(0): Using hardware cursor (scanline 1200)
(II) fglrx(0): Largest offscreen area available: 1600 x 6988
(**) Option "dpms"
(**) fglrx(0): DPMS enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled
(**) fglrx(0): Video overlay enabled on CRTC1
oops. Sorry its late and I am tired :-). The problem lies in the fact that my glxgears returns at best 266 FPS and games like tuxracer run with laaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaag. Hehe.
so you have isntalled it without errors and it is working? so the questions is about the performance... i dunno, check the site (for the drivers and the game) make sure everything is met, read the faq about either the game or the drivers for performance issues like this.. sorry i cant help with it, i was just trying to get you to post more info so whoever could help would know what your asking.
afterall, 266fps is pretty good, no? your eyes cant even recognize that much
266 is quite frankly shit, unfortunately. Like I said, everything seems to be good, the module loads, no errors, just that 3d acceleration won't turn on!!!!!!!!!! LOL. The tables have turned eh? In any event, thanks for catching my errors, I appreciate it.
I have tried everything that I have read and everything that I can think of to get these drivers to work, and the conclusion that I have arrived at is that tomorrow I am going to buy a Nvidia card. Thanks for the help those guys, too bad this one couldn't work eh.
Before you give up entirely, may I make a suggestion?
Firstly, you will not get FireGL working properly if you have AGPGART compiled into the kernel. It *must* be a module. If it isn't a module, you will never get DRI working with FireGL, because FireGL uses its own internal AGP driver and needs to be able to replace the kernel module with its own.
Secondly, why on earth would you download a binary driver from linuxpackages.net? It's kernel-specific, and quite likely system-specific. Much better to download the driver from ati.com and install that. It's a graphical installer, and it will compile and insert the driver into your kernel for you. It's really a lot like a Windows installer.... open it, choose the install type, click next, next, and you're done.
Once you've done that, run fglrxconfig, and you're off to the races. There's no special steps required. Have AGP set as a module in the kernel, run the ATI installer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.