Re: Trouble getting DRI to Work with ATI Rage 128 (solved)
I finally got the stuff working !
It was a matter of AGP support in the kernel...
I didn't understand agpgart.o is NOT sufficient.
You also need AGP chipset support (depending on your chipset). I use Intel
440BX.
Now DRI works fine !
So for DRI + ATI Rage128 you need :
AGP support in the kernel (2.4.0 for me) ie agpgart and your chipset's AGP
support. I compiled that in the kernel (I don't tried compiling as module).
DRM support in the kernel + DRI support for your graphic chipset (I have
ATI Rage 128)
The right XF86Config-4 file. I have :
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
EndSection
Section "Module"
Load "GLcore"
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "pex5"
Load "record"
Load "xie"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"
Option "Buttons" "3"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "MEI"
ModelName "c95"
HorizSync 30.0 - 70.0
VertRefresh 50.0 - 160.0
EndSection
Section "Device"
### Available Driver options are:-
#Option "accel"
#Option "crt_screen"
#Option "composite_sync"
#Option "linear"
#Option "mmio_cache"
#Option "probe_clocks"
#Option "reference_clock"
#Option "shadow_fb"
Identifier "Card0"
Driver "ati"
VendorName "ATI"
BoardName "Rage 128 RF"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 1
EndSubSection
SubSection "Display"
Depth 4
EndSubSection
SubSection "Display"
Depth 8
EndSubSection
SubSection "Display"
Depth 15
EndSubSection
SubSection "Display"
Depth 16
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Beware, with xfree 4.0.2 and ATI Rage 128, you need ati as a driver (r128
don't work anymore).
And it works !!!!
The only point for me now is getting DGA recognized by VMWare...
Thanks to Mike Polniak for is help.
On Sun, 21 Jan 2001 22:38:02 franck wrote:
> Thank you for the advice.
> Is the DRI (Open GL) function working for you ?
>
> I tried again following the advices at the given address (which by the
> way
> has moved to http://avis.lightband.com/david/rage128-howto.html)
>
> I have installed kernel 2.4.0 (not test anymore) because of a note that
> was
> unclear to me (* NOTE: kernel 2.4.0 work only with XFree86 4.02.
> Everything before 2.4.0 (i.e. 2.3-(2.4.0-test)) works with XFree86 4.01.)
>
> DRI still doesn't work...
>
> Here is part of my log file for X :
>
> XFree86 Version 4.0.2 / X Window System
> (protocol Version 11, revision 0, vendor release 6400)
> Release Date: 18 December 2000
> If the server is older than 6-12 months, or if your card is
> newer than the above date, look for a newer version before
> reporting problems. (See http://www.XFree86.Org/FAQ)
> Operating System: Linux 2.2.18 i686 [ELF]
>
> <--- I don't understand that ??
> Module Loader present
> (==) Log file: "/var/log/XFree86.0.log", Time: Sun Jan 21 22:12:56 2001
> (==) Using config file: "/etc/X11/XF86Config-4"
>
> [...]
>
> (--) Chipset ATI Rage 128 RF (AGP) found
> (II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o
> (II) Module r128: vendor="The XFree86 Project"
> compiled for 4.0.2, module version = 4.0.1
>
> [...]
>
> (II) Module xaa: vendor="The XFree86 Project"
> compiled for 4.0.2, module version = 1.0.0
> (--) Depth 24 pixmap format is 32 bpp
> (==) R128(0): Write-combining range (0xe4000000,0x2000000)
> /lib/modules/2.4.0/kernel/drivers/char/drm/r128.o: init_module: Cannot
> allocate memory <--- here is the
> problem...
> /lib/modules/2.4.0/kernel/drivers/char/drm/r128.o: insmod
> /lib/modules/2.4.0/kernel/drivers/char/drm/r128.o failed
> /lib/modules/2.4.0/kernel/drivers/char/drm/r128.o: insmod r128 failed
> [drm] failed to load kernel module "r128"
> (0): [drm] drmOpen failed
>
> <--- yes.......
> (EE) R128(0): DRIScreenInit failed!
> (II) R128(0): Memory manager initialized to (0,0) (1280,6553)
> (II) R128(0): Reserved area from (0,1024) to (1280,1026)
> (II) R128(0): Largest offscreen area available: 1280 x 5527
> (==) R128(0): Backing store disabled
> (==) R128(0): Silken mouse enabled
> (II) R128(0): Using XFree86 Acceleration Architecture (XAA)
> Screen to screen bit blits
> Solid filled rectangles
> 8x8 mono pattern filled rectangles
> Indirect CPU to Screen color expansion
> Solid Lines
> Dashed Lines
> Offscreen Pixmaps
> Setting up tile and stipple cache:
> 32 128x128 slots
> 32 256x256 slots
> 16 512x512 slots
> (II) R128(0): Acceleration enabled
> (II) R128(0): Using hardware cursor (scanline 4104)
> (II) R128(0): Largest offscreen area available: 1280 x 5525
> (II) R128(0): Direct rendering disabled
>
>
> Any help will be much appreciated.
>
> Franck Routier
>
> And remember : "Only Linux makes it possible"(TM)
>
>
> On Sun, 21 Jan 2001 16:33:54 mike polniak wrote:
> > franck wrote:
> > > Hi everybody,
> > >
> > > I'm trying to get XFree 4.0.2 DRI work on my Debian Testing box.
> > > My video card is an ATI Rage Fury (Rage 128 with 32MB).
> > > I run kernel 2.4.0-test11, and installed XFree 4.0.2 from debs (I
> > managed
> > > to find out
> > > I have to use ati and no more r128 out of the list, thanx !).
> >
> > I got my ATI Rage Fury 128 working in XFree4 with the help at:
> > http://www4.ncsu.edu/~distclai/rage128-howto.html.
> > Starting over with this may be easier than trying to debug your
> > current situation.
> > --
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
>
Reply to: