Yess! I found! Strace is the girl's best friend!
r200_dri.so is linked against libexpat.so.1 - while Fedora only provides
libexpat.so.0. That is why libGL.so cannot load r200_dri.so - and
reports missing DR! At the moment, I just symlinked libexpat.so.0 to
libexpat.so.1 - and got my DRI working.
pre-install r200 modprobe -k agpgart
Just one question. Should it be r200 or radeon?
Thanks for the config line, I'll try it.
Sergey
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more
It should be radeon actually. My bad...
I knew! I knew! :)
Well, anyway - this does not explain why libGL cannot find dri while
xfree86.0.log says it is there...
Sergey
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does
Stock drivers never have. You may want to help with the kernel patches
floating around for this?
Well, I don't really know. I am not a big kernel expert. I just say what
I see: when I run standard Fedora X driver - agpgart is loaded without
my intervention. With dri snapshots - I have to load
Hi all
I just took the R200 snapshot and trying to run in on Radeon R250 Lf
(Mobility). First, I encountered the problem with ABI version (6 vs 7)
but after taking XFree86 executable from some well-known place
(mentioned in FAQ) XFree finally took off (first question - would it be
possible to
Well, in my previous mail I was citing the wrong XFree86.0.log. The
right one shows that DRI is actually disabled. And dmesg gives me this:
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 5985 using kernel context 0
Googling around shows
There are new driver snapshots from the trunk (for XFree86 4.3.0) on
http://dri.sourceforge.net/snapshots/ . They were built wihout a glitch
but are yet untested. Please report back success and/or failure.
Great!! Does this include mach64 (which is in bleeding-edge subdir)?
Also, Leif, what
No they aren't supported in DRI. For existing apps, they would probably
Thanks for these very good explanation. My ergo: no use. So, it seems
Mach64 does not have any good usable compression technique.
Cheers,
--
Sergey
signature.asc
Description: This is a digitally signed message part
According to the docs, mach64 implements 4:1 VQ de-compression, but
there's no other info. Rage 128 also has a VQ texture format bit,
according to the register header file. Sega dreamcast used a form of VQ
compression also, I think.
Sorry for my ignorance, are these compression methods
Hi
Just one little XFree-related pro-XML story. Not from DRI, from XKB
life. You know, XKB configuration is generally held in
/usr/X11R6/lib/xkb directory and several subdirectories. All this would
be fine if the format of the files in these directories would be
something good, structured,
Good story. But right there, you point out the main difference between your
example, and the XFree86 config format.
Keep in mind - it is not XF68Config, it is just configuration
repository. The tree of available modeuls/layouts/variants/options. Not
actually chosen one (which is still in
11 matches
Mail list logo
