DRI problem on ATI Rage LT Pro 133

[daemon]

I have installed 3DCC, drm,dri modules, opengl libs, but acceleration didn't work. 3DCC says "DRI-Status: DRI is NOT active, the demo should run slow (< 10 fps)" and demo runs at 4fps. What is wrong? What i made incorrect?
SYSINFO in 3DCC says
"Your /var/log/Xorg.0.log reports you have this card:

(--) PCI:*(1:0:0) ATI Technologies Inc 3D Rage LT Pro AGP-133 rev 220, Mem @ 0xfd000000/24, 0xfc100000/12, I/O @ 0x2000/8

Your current Xserver uses this standard-driver:
ati

DRI IS active."

Here are my config and log files.

[tempestuous]

Unfortunately your "LT" model is not supported by the mach64 3D driver
http://www.murga-linux.com/puppy/viewto ... 8949#48949

[daemon]

Yes, i've read this

Cards earlier than the ATI 3D Rage Pro don't have a triangle setup engine and are not supported. This includes VT chips, ATI 3D Rage, ATI 3D Rage II/II+/IIc, and ATI 3D Rage LT. Supported cards include ATI 3D Rage Pro, ATI 3D Rage LT Pro, ATI 3D Rage XL or XC, and ATI 3D Rage Mobility.

and this

Your /var/log/Xorg.0.log reports you have this card:

(--) PCI:*(1:0:0) ATI Technologies Inc 3D Rage LT Pro AGP-133 rev 220, Mem @ 0xfd000000/24, 0xfc100000/12, I/O @ 0x2000/8

So it seems to be supported....
But does not work...

Yes, and one more thing: driver LOADS and WORKS, so video playback is faster(and sopports hw scaling), then using "vesa" driver.
I think, if it will be unsupported, driver vill not load at all (when i try "r128" X fails to start.).

[MU]

from the log:

Code: Select all

(WW) ATI(0): DRI static buffer allocation failed -- need at least 7680 kB video memory

(II) ATI(0): Direct rendering disabled

Try to reduce the colordepth to get more memory.

in xorg.conf, replace:

Code: Select all

    DefaultDepth 24
    #Gamma 0.7
    Subsection "Display"
        Depth       24
        Modes       "1024x768,800x600,640x480"
    EndSubsection

with:

Code: Select all

    DefaultDepth 16
    #Gamma 0.7
    Subsection "Display"
        Depth       16
        Modes       "1024x768,800x600,640x480"
    EndSubsection

Mark

[daemon]

Yes, you were right, 800x600x16 fixed this memory issue. But now it says:

Code: Select all

(==) ATI(0): Write-combining range (0xfd000000,0x400000)
(II) ATI(0): [drm] SAREA 2200+1208: 3408
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "mach64"
(II) ATI(0): [drm] drmOpen failed
(EE) ATI(0): [dri] DRIScreenInit Failed
(II) ATI(0): Largest offscreen areas (with overlaps):
(II) ATI(0): 	800 x 2020 rectangle at 0,600
(II) ATI(0): 	640 x 2021 rectangle at 0,600
(II) ATI(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
	Offscreen Pixmaps
	Setting up tile and stipple cache:
		32 128x128 slots
		14 256x256 slots
(==) ATI(0): Backing store disabled
(==) ATI(0): Silken mouse enabled
(II) ATI(0): Direct rendering disabled
(**) RandR enabled

I think i have to create device /dev/dri/card0 but i dont know what i should say to mknod. Any ideas?

[MU]

no, those messages are typical even for a working setup I think.

Please type "lsmod" and post the result here.
Some people reported problems with the AGP-port detection, what was the reason, that the Kernel-module could not be loaded.

We must clarify this first.

Mark

[tempestuous]

Try this -

mknod /dev/dri/card0 c 226 0

... but as Mark says, there's probably more to the problem.

[daemon]

lsmod gives such result:

Code: Select all

Module                  Size  Used by
ppp_async              11408  1 
crc_ccitt               1968  1 ppp_async
ppp_generic            27460  5 ppp_async
slhc                    7056  1 ppp_generic
bnep                   11536  2 
hci_usb                14668  3 
rfcomm                 33644  4 
l2cap                  19924  11 bnep,rfcomm
bluetooth              43876  8 bnep,hci_usb,rfcomm,l2cap
snd_mixer_oss          17328  0 
lp                     12520  0 
parport_pc             32100  1 
parport                35080  2 lp,parport_pc
pcnet32                32452  0 
mii                     5680  1 pcnet32
snd_ymfpci             59360  0 
gameport               14904  1 snd_ymfpci
snd_ac97_codec         90448  1 snd_ymfpci
snd_ac97_bus            2128  1 snd_ac97_codec
snd_pcm                77592  2 snd_ymfpci,snd_ac97_codec
snd_opl3_lib           10448  1 snd_ymfpci
snd_timer              23540  3 snd_ymfpci,snd_pcm,snd_opl3_lib
snd_hwdep               9076  1 snd_opl3_lib
snd_page_alloc         10008  2 snd_ymfpci,snd_pcm
snd_mpu401_uart         8112  1 snd_ymfpci
snd_rawmidi            24064  1 snd_mpu401_uart
snd_seq_device          7996  2 snd_opl3_lib,snd_rawmidi
snd                    51396  10 snd_mixer_oss,snd_ymfpci,snd_ac97_codec,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               9408  1 snd
i2c_piix4               8380  0 
i2c_core               21408  1 i2c_piix4
intel_agp              22668  1 
agpgart                34608  1 intel_agp
usb_storage            83904  3 
fuse                   44388  0 
unionfs                77696  1 
nls_iso8859_1           3984  1 
nls_cp437               5648  1 
sr_mod                 17412  0 
ide_cd                 40100  0 
cdrom                  39424  2 sr_mod,ide_cd
ehci_hcd               30200  0 
uhci_hcd               23356  0 
usbcore               126116  5 hci_usb,usb_storage,ehci_hcd,uhci_hcd
yenta_socket           27516  4 
rsrc_nonstatic         12912  1 yenta_socket

so agp seems to be ok.

mknod /dev/dri/card0 c 226 0

didn't help. After X restart device just disappears...

[MU]

yes, agp looks fine.

I'm running out of ideas.
Just as a last resort:
please attach again your current /var/log/Xorg.0.log

Also try to run
modprobe mach64

and
modinfo mach64

Then post the results here.
If I don't answer, I will have no idea how to proceed

Mark

[daemon]

DAMN, I AM FOOL!!!!
there is simply no such module!!!
But i wonder where i can get march64 module for puppy 212.
I attach my log, but it seems to be useless
there is no march64.ko in drm-kernelmodules.pup????[/code]

[tempestuous]

No you're not a fool. Puppy does not contain the mach64 module, and it is not part of Mark's 3DCC. It's here
http://dotpups.de/tests/mach64-DRM-k2.6.18.1.tar.gz

Go ahead and test it if you like, but the mach64 driver is a problem, I don't think it will work in Puppy 2.12/2.13.
Read about forum member Roger's testing of this driver here http://www.murga-linux.com/puppy/viewto ... 1566#81566

The mach64 driver does work in earlier versions of Puppy: definitely in versions 1.0.4-1.0.9, and maybe 2.0 & 2.01.
http://www.murga-linux.com/puppy/viewtopic.php?t=13627

[MU]

why did I did not add it to the kernelmodules?
Don't remember. Did we never get a positive result maybe?
I have another version slightly different in size here, I'll attach it.
Extract to:
/lib/modules/2.6.18.1/kernel/drivers/char/drm/
then run:
depmod
modprobe mach64

Please keep us informed, if one module loads without error, and if yes, which.
Mark

[daemon]

it says "-1 unknown symbol in module"
i think i need correct drm.ko

2 tempestuous: i have downloaded package, it says version missmatch (lost that log, will try again and attach log)

here it is:

Code: Select all

(EE) ATI(0): [dri] ATIDRIScreenInit failed because of a version mismatch.
[dri] mach64.o kernel module version is 2.0.0, but version 1.0 or greater is needed.
[dri] Disabling DRI.

and full log.

An one more question: what performans may i expect from this card? is it worth time getting it to work? (this is laptop, native screen size is 1024x768, in 800x600 it looks "not very good", and in 1024x768 dri fails because not enough memory, even in 16bit)