By the way, Beryl, Compiz? Is it possible to install them for usage with mach64-device? Am I insane?
By the way, Beryl, Compiz? Is it possible to install them for usage with mach64-device? Am I insane?
http://ubuntu4us.wordpress.com - New World Computer Religion... Ubuntu with Us! Join Us!
I've made a bit of progress.. but have some more issues
I had to delete a bunch of references to config.h in a few files, and replace ati_agpgart with one I found in this thread to get mesa to compile.
Then when I restarted, xserver freaked out. (had to switch to vesa in xorg.conf)
I finally reinstalled the xorg ati driver and got it back.
got these errors in Xorg.O.log
without link to libGLcore.so in home/felix/src/snapshots/inst/HEAD/lib/dri
shows direct rendering enabled
......
(**) Option "dpms"
(**) ATI(0): DPMS enabled
(WW) ATI(0): Option "UseInternalAGPGART" is not used
(II) ATI(0): X context handle = 0x1
(II) ATI(0): [drm] installed DRM signal handler
(II) ATI(0): [DRI] installation complete
(II) ATI(0): [drm] Added 128 16384 byte DMA buffers
(II) ATI(0): [drm] Mapped 128 DMA buffers at 0xb688b000
(II) ATI(0): [drm] Installed interrupt handler, using IRQ 11
(II) ATI(0): Direct rendering enabled
(==) RandR enabled
......
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(EE) AIGLX error: dlopen of /home/felix/src/snapshots/inst/HEAD/lib/dri/mach64_dri.so failed (/home/felix/src/snapshots/inst/HEAD/lib/dri/mach64_dri.so: cannot open shared object file: No such file or directory)
(EE) GLX-DRI: reverting to software rendering
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.2
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
GLcore compiled for 7.0.0, everything else in xorg compiled for 7.2.0 ex.
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.1
with link to libGLcore.so in home/felix/src/snapshots/inst/HEAD/lib/dri
shows direct rendering enabled
(II) ATI(0): Direct rendering enabled
but gives a different message farther on
(EE) AIGLX error: Calling driver entry point failed(EE) GLX-DRI: reverting to software rendering
I'm going to reinstall xorg, by the way, as running glxinfo crashes it, possibly because libGLcore.so is compiled for xorg version 7.0.0 not 7.2.0. Not sure how that happened.
Any ideas?
Reinstalled xorg
the following is from glxinfo which no longer crashes xorg
Mach64 DRI driver expected DRM version 2.0.x but got version 1.0.0
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
display: :0 screen: 0
direct rendering: No
This error message is still in the xorg log...
(EE) AIGLX error: Calling driver entry point failed(EE) GLX-DRI: reverting to software rendering
Next I'm following the instructions on
http://dri.freedesktop.org/wiki/Buil...0bb2e088e2e86e
and see what happens.
I'm hoping rebuilding DRM might get rid of the version conflict.
The adventure continues...
After following the instructions in my previous post I get this
(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
(II) ATI(0): Direct rendering disabled
So I have version 2.0.0, but version 1.0 or greater is needed...hmmm...anyone see the problem with this?
So when I have version 1.0 it tells me I need version 2.0.0,
When I have version 2.0.0 it tells me I need greater than version 1.0.
Not quite banging my head on a wall yet, but getting close
still no luck...has anyone seen this?
I wasn't successful in activating the DRI, but I did manage to compile on a somewhat clean install, heres exactly what i did :
00. sudo apt-get install linux-686 linux-headers-2.6-686 build-essential
*. you might want to reboot
01. "uname -r" to see your kernel version
02. cd /usr/src/linux-headers-"what ever you got with uname -r"/include/linux
03. sudo ln -s autoconf.h config.h
04. cd /usr/src
05. mkdir mach64_dri
06. cd mach64_dri
To date their hasn't been new daily snapshots for months since the devs are lazy and have too much faith in their git server - which I could never clone from
07. sudo wget http://dri.freedesktop.org/snapshots...x.i386.tar.bz2
08. sudo wget http://dri.freedesktop.org/snapshots...x.i386.tar.bz2
09. sudo tar xjvf common-20060403-linux.i386.tar.bz2
10. sudo tar xjvf mach64-20060403-linux.i386.tar.bz2
11. get Ally_S' ati_pcigart.zip:
http://ubuntuforums.org/attachment.p...7&d=1162424703
Posted at: http://ubuntuforums.org/showthread.php?t=7200&page=7
12. extract ati_pcigart.c to /usr/src/mach64*/drm/linux-core/
Back in xterm:
13. nano /usr/src/mach64*/drm/linux-core/drm_stub.c
14. comment out line 51: add "//" to tell the compiler to ignore that line.
15. sudo /usr/src/common-20060403-linux.i386/install.sh
16. sudo /usr/src/mach64-20060403-linux.i386/install.sh
17. sudo /etc/init.d/gdm restart
So that what I did, more or less, supposedly at that point things should have worked and this should have been verified with glxinf | grep 'direct', unfortunately for me it didn't
Were did I go wrong ?
P.S: By my little comment you must have gathered I wasn't successful cloning with git so I used this method, I tried with three different machines, so its either my router which has no firewall, or my ISP which is evil...
P.S.S: Can anyone recommend a dist (live will be perfect) that comes with recent mach64 drivers and x.org already build ? just don't suggest some old dist cause I require a very recent build of alsa...
Edit: obviously lsmod shows mach64 module loaded...
Last edited by RamiK(*_-_*)RamiK; July 20th, 2007 at 06:08 AM. Reason: errors
I have installed new kernel 2.6.20.16 and lose direct acceleration. Was trying to reinstall old driver and kill ati driver at all.... Now I have the same problem as Minime... Old driver doen't work...
Here is a part of install log for mach64 driver:
WARNING: /home/worker/TMP/mach64-20060403-linux.i386/drm/linux-core/drm.o - Section mismatch: reference to .exit.text:drm_exit from __ksymtab between '__ksymtab_drm_exit' (at offset 0x58) and '__ksymtab_drm_init'
WARNING: /home/worker/TMP/mach64-20060403-linux.i386/drm/linux-core/drm.o - Section mismatch: reference to .exit.text:drm_cleanup_pci from __ksymtab between '__ksymtab_drm_cleanup_pci' (at offset 0x68) and '__ksymtab_drm_poll'
And dmesg said that cannot find any ati driver....
I am going to try second Audiophil way of installing, but I am frustrated a little bit.
http://ubuntu4us.wordpress.com - New World Computer Religion... Ubuntu with Us! Join Us!
You say the new kernel gives trouble ? I didn't even try the drivers WITHOUT it, so maybe that's why I failed...
What exactly should I be looking for ? and where (logs) ?
Been getting loads of crap trying to install this. Now glxinfo just kills X.
Sorry I can't help Old Pink, I haven't had much luck my self...
Isn't a clean install an option ? it took me 45mins to install xubuntu using the alternative cd and a cml box install, and that was on a Intel Pentium 200mhz MMX with 65mb RAM ...
On a brighter note, I was finally able to git clone git://anongit.freedesktop.org/git/mesa/drm,
so I've compiled it on Gusty (beta), but still no luck with the dri...
Also I noticed the i915 module doesn't compile and that breaks the make process, so I've deleted the i915 source code files, went through all the files, including the make files, making sure to remove any references to i915, compiled and cp *.ko /lib/modules/$KERNEL/kernel/drivers/char/drm.
So except for the i915 part its all the same as it is found in the Readme...
I suppose I could also "dummied" the i915 source files by putting empty files by the same name to replace them so the make won't break, maybe adding some odd includes, or linking the files to one of the headers, but I prefer the "ugly" hack method ...
I'm still unsuccessful at activating the dri, but with the double buffer and the updated xorg i got from gusty, I'm able to get some improvements to the point I'm now able to watch youtube quality .flv's
I haven't tried to compile xorg and I'm not planning to in the near future, the git alone isn't likely to succeed on my loosy connection (for a lack of a better term to describe the results of a selective isp, without resorting to obscenity) let alone the dependencies...
I hope this helps you with your card cause I think I'm waiting until gusty to see if the devs are going too compile the module on their own, before I attempt to do it myself...
Bookmarks