3D-Dri-Kernelmodules for most Graficscards
Thanks for the help
I followed your instructions the cvs part went fine I think
but when I went to compile I get this error message
Makefile:170: *** Cannot find a kernel config file. Stop.
ok I'm new to this thing called linux and really have no
idea where I would find this? any clues pointers ect
would be great!
but when I went to compile I get this error message
Makefile:170: *** Cannot find a kernel config file. Stop.
ok I'm new to this thing called linux and really have no
idea where I would find this? any clues pointers ect
would be great!
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
You need the full kernel source tree, patched and configured to match the kernel you are running.
Bombayrockers has this, of course, since he built this kernel, and I see that MU has asked for the exact setup details also.
It's worth pointing out that for versions of Puppy other than 1.0.4 through 1.0.7 with the "standard" 2.4.29 kernel that many add-on driver packages presently available for download will be incompatible.
Bombayrockers has this, of course, since he built this kernel, and I see that MU has asked for the exact setup details also.
It's worth pointing out that for versions of Puppy other than 1.0.4 through 1.0.7 with the "standard" 2.4.29 kernel that many add-on driver packages presently available for download will be incompatible.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I removed the Option "EnableAGPDMA" "true" from the xorg.conf file, and glxgears performance improved slightly, from 520FPS to 550FPS.
Since this option appears to offer no benefit, I will ask MU to remove reference to it.
And I forgot to mention that with Puppy's 2.4 kernel these drivers only support the CLE266 "Unichrome" graphics chipset, not the CN400 "Unichrome Pro" chipset found on the Epia SP8000E and SP13000.
A 2.6 kernel is needed for the Unichrome Pro.
Since this option appears to offer no benefit, I will ask MU to remove reference to it.
And I forgot to mention that with Puppy's 2.4 kernel these drivers only support the CLE266 "Unichrome" graphics chipset, not the CN400 "Unichrome Pro" chipset found on the Epia SP8000E and SP13000.
A 2.6 kernel is needed for the Unichrome Pro.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Here is the xine-Dotpup (4.5 MB):
http://dotpups.de/dotpups/Multimedia/xine-unichrome.pup
You can run it from the Dotpups-menu, or like described in the readme:
This Xine package does not overwrite Puppy's Gxine.
The only shared location is /usr/lib/win32 for extra codecs, but I
don't think the files supplied by Gxine in this location (cook.so &
sipr.so.6.0) are necessary for Xine.
The "magic" file that makes MPEG2 acceleration work is /usr/local/lib/
xine/plugins/1.1.1/xineplug_vo_out_xxmc.so, but this plugin won't work
until the XvMC wrapper library (libXvMCW.so) links the plugin to
libviaXvMC.so in the VIA DRI package.
Instructions are quite simple -
Launch Xine from the command line with "xine". The preferences are set
up for xxmc video output. Audio output can be changed to ALSA if ALSA
is installed.
DVD's can be played from the command line, fullscreen, without playbar,
as such -
xine -V xxmc -f -I dvd://VTS_01_2.VOB
To use it in mozilla, execute "run-xine" once, it copies the necessary plugin (this is done automatically, if you run it from the Dotpups-menu).
As /lib/mozilla is a symbolic link, I could not add it directly to the dotpup with my wizard.
Mark
(Ps: I also updated the unicrome-dotpup, just removed the "EnableAGPDMA" from readme and xorg.conf-example)
http://dotpups.de/dotpups/Multimedia/xine-unichrome.pup
You can run it from the Dotpups-menu, or like described in the readme:
This Xine package does not overwrite Puppy's Gxine.
The only shared location is /usr/lib/win32 for extra codecs, but I
don't think the files supplied by Gxine in this location (cook.so &
sipr.so.6.0) are necessary for Xine.
The "magic" file that makes MPEG2 acceleration work is /usr/local/lib/
xine/plugins/1.1.1/xineplug_vo_out_xxmc.so, but this plugin won't work
until the XvMC wrapper library (libXvMCW.so) links the plugin to
libviaXvMC.so in the VIA DRI package.
Instructions are quite simple -
Launch Xine from the command line with "xine". The preferences are set
up for xxmc video output. Audio output can be changed to ALSA if ALSA
is installed.
DVD's can be played from the command line, fullscreen, without playbar,
as such -
xine -V xxmc -f -I dvd://VTS_01_2.VOB
To use it in mozilla, execute "run-xine" once, it copies the necessary plugin (this is done automatically, if you run it from the Dotpups-menu).
As /lib/mozilla is a symbolic link, I could not add it directly to the dotpup with my wizard.
Mark
(Ps: I also updated the unicrome-dotpup, just removed the "EnableAGPDMA" from readme and xorg.conf-example)
Last edited by MU on Fri 27 Jan 2006, 06:35, edited 2 times in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Mark,
Quick turnaround, thanks a million.
I'm confused about the Mozilla problem ... I created a /usr/lib/mozilla/plugins path ... should this path have been /usr/lib/mozilla-1.8b1.5/plugins instead?
And just a small point, it's not "gxine", I used a different frontend "xine-ui" which launches as "xine".
Quick turnaround, thanks a million.
I'm confused about the Mozilla problem ... I created a /usr/lib/mozilla/plugins path ... should this path have been /usr/lib/mozilla-1.8b1.5/plugins instead?
And just a small point, it's not "gxine", I used a different frontend "xine-ui" which launches as "xine".
No.tempestuous wrote:I'm confused about the Mozilla problem ... I created a /usr/lib/mozilla/plugins path ... should this path have been /usr/lib/mozilla-1.8b1.5/plugins instead?
/lib/mozilla-1.8b1.5/plugins is unique for Puppy 107.
So the current solution is more flexible.
When you run it from the Dotpups-menu (or "run-xine" in a shell), the plugin is copied to /lib/mozilla/plugins ; that will work with any puppy.
I just cannot extract the .tar.gz in the Dotpup there directly, that would break the symlink.
Corrected.tempestuous wrote:And just a small point, it's not "gxine", I used a different frontend "xine-ui" which launches as "xine".
Mark
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
just finding this . . .MU wrote:Lobster, what Driver is used in your xorg.conf?
If it is "via":
install the dotpup.
And install http://noforum.de/dotpups/X11R6addons/d ... ndrake.pup
In a console type:
/usr/local/install-DRI/install-DRI via
Restart X.
Run "glxinfo" to test if it works(it should say "DRI: yes").
As you can play Descent2 I assume your /etc/X11/xorg.conf includes these 2 lines in Section "Module":These are important for 3D.Code: Select all
Load "dri" Load "glx"
There also is a "savage"-Kernelmodule, load it with:
/usr/local/install-DRI/install-DRI savage if via does not work.
But my download-site has no "dri-savage.pup" for X.org 6.8.x.
Please try the via first. If it does not work, I could create a X.org 6.9 -Savage Dotpup.
Mark
thanks Mark
there is a# /usr/local/install-DRI/install-DRI via
bash: /usr/local/install-DRI/install-DRI: No such file or directory
#
/usr/local/dri-via-mandrake
created by the dotpup but it is empty?
completely confusing myself will have to calm down a bit . . .
Lobster, did you install this one, too?
http://dotpups.de/dotpups/XServer/DRI-Kernelmodules.pup
http://dotpups.de/dotpups/XServer/DRI-Kernelmodules.pup
Re: 3D-Dri-Kernelmodules for most Graficscards
Hi,
I tried to install the drivers on my notebook, that has a "ATI Rage Mobility P/M" chip. A "mach64" variant as far as i understand.
So I installed everything needed to get DRI working, but one thing seems to be missing:
Regards,
Roger
I tried to install the drivers on my notebook, that has a "ATI Rage Mobility P/M" chip. A "mach64" variant as far as i understand.
So I installed everything needed to get DRI working, but one thing seems to be missing:
Any chance you could provide a "dri" .pup for the mach64?MU wrote: You also will need a "dri"-file especially for your graficscard, get it from here:
http://noforum.de/dotpups/X11R6addons/
Mark
Regards,
Roger
There is no DRI-Driver for mach64 neither in my X.org on Mandrake9.2 (selfcompiled), nor on my X.org 6.8.2 in Puppy.
I just saw a file here:
http://dri.freedesktop.org/snapshots/
( http://dri.freedesktop.org/wiki/Download )
But this is for X.org 6.9 RC, that worked unstable with my Ati Radeon.
If anyone finds a mach64_dri.o module in
/usr/X11R6/lib/modules/DRI
for example in Vector-Linux, please inform me.
Then I could upload it, too.
Mark
I just saw a file here:
http://dri.freedesktop.org/snapshots/
( http://dri.freedesktop.org/wiki/Download )
But this is for X.org 6.9 RC, that worked unstable with my Ati Radeon.
If anyone finds a mach64_dri.o module in
/usr/X11R6/lib/modules/DRI
for example in Vector-Linux, please inform me.
Then I could upload it, too.
Mark
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I just installed the mach64 DRI modules that MU mentioned (they're similar to the package I previously assembled for VIA Unichrome) then packaged and sent them to him. So it may be a relatively easy to install this package and have DRI for mach64 ... but ... the information here - http://www.geekounet.org/powerbook/driplusxv.html
implies that a special variant of Xorg needs to be compiled to get the ati xorg module that supports these DRI modules.
Anyway, it wouldn't hurt to try these mach64 modules once MU puts them on his download site.
And here is some very detailed information about how to set up your xorg.conf for mach64 with DRI - http://www.retinalburn.net/linux/dri_status.html
implies that a special variant of Xorg needs to be compiled to get the ati xorg module that supports these DRI modules.
Anyway, it wouldn't hurt to try these mach64 modules once MU puts them on his download site.
And here is some very detailed information about how to set up your xorg.conf for mach64 with DRI - http://www.retinalburn.net/linux/dri_status.html
Ok, forATI Mach64 try this:
Install with Pupget Xorg-openGL.
install:
http://dotpups.de/dotpups/XServer/DRI-Kernelmodules.pup
install:
http://noforum.de/dotpups/X11R6addons/dri-mach64.pup
install:
http://noforum.de/dotpups/X11R6addons/xorg-mach64.pup
IMPORTANT:
rename
/usr/X11R6/lib/modules/driver/ati_drv.o to
/usr/X11R6/lib/modules/driver/ati_drv.o-backup
and
/usr/X11R6/lib/modules/driver/atimisc_drv.o to
/usr/X11R6/lib/modules/driver/atimisc_drv.o-backup
If you don't, the new .so -modules will not be used.
Now be shure, that /etc/X11/xorg.conf contains these lines in Section "Module":
And the existing line with the driver must use ati:
Now load the Kernel-module, run
/usr/local/install-DRI/install-DRI mach64
and restart X (you later should add this comand to /etc/rc.d/rc.local so that it is done after every reboot, if everything works).
Run "glxinfo" to test, if DRI works, the result should contain a line "dri: yes".
If you get "no", you might need to upgrade libGL.so, but first please tell us the results.
If your X does not start with the new drivers, rename the "-backup" files to their original filenames.
Run these 2 commands in the black commandline-screen:
mv /usr/X11R6/lib/modules/driver/ati_drv.o-backup /usr/X11R6/lib/modules/driver/ati_drv.o
mv /usr/X11R6/lib/modules/driver/atimisc_drv.o-backup /usr/X11R6/lib/modules/driver/atimisc_drv.o
Then X should start, and you can remove the new Dotpups with Pupget.
Mark
Install with Pupget Xorg-openGL.
install:
http://dotpups.de/dotpups/XServer/DRI-Kernelmodules.pup
install:
http://noforum.de/dotpups/X11R6addons/dri-mach64.pup
install:
http://noforum.de/dotpups/X11R6addons/xorg-mach64.pup
IMPORTANT:
rename
/usr/X11R6/lib/modules/driver/ati_drv.o to
/usr/X11R6/lib/modules/driver/ati_drv.o-backup
and
/usr/X11R6/lib/modules/driver/atimisc_drv.o to
/usr/X11R6/lib/modules/driver/atimisc_drv.o-backup
If you don't, the new .so -modules will not be used.
Now be shure, that /etc/X11/xorg.conf contains these lines in Section "Module":
Code: Select all
Load "dri"
Load "glx"
Code: Select all
Driver "ati"
/usr/local/install-DRI/install-DRI mach64
and restart X (you later should add this comand to /etc/rc.d/rc.local so that it is done after every reboot, if everything works).
Run "glxinfo" to test, if DRI works, the result should contain a line "dri: yes".
If you get "no", you might need to upgrade libGL.so, but first please tell us the results.
If your X does not start with the new drivers, rename the "-backup" files to their original filenames.
Run these 2 commands in the black commandline-screen:
mv /usr/X11R6/lib/modules/driver/ati_drv.o-backup /usr/X11R6/lib/modules/driver/ati_drv.o
mv /usr/X11R6/lib/modules/driver/atimisc_drv.o-backup /usr/X11R6/lib/modules/driver/atimisc_drv.o
Then X should start, and you can remove the new Dotpups with Pupget.
Mark
Hi,
thanks a lot for your help. Unfortunately, I haven't got it working yet.
X won't restart when everything is installed as you described it.
The command
/usr/local/install-DRI/install-DRI mach64
succeeds, but gives a warning about some unresoved symbol.
X only comes back to life with the original modules.
Any further thoughts?
Regards,
Roger
thanks a lot for your help. Unfortunately, I haven't got it working yet.
X won't restart when everything is installed as you described it.
The command
/usr/local/install-DRI/install-DRI mach64
succeeds, but gives a warning about some unresoved symbol.
X only comes back to life with the original modules.
Any further thoughts?
Regards,
Roger
There also is a mach64 -kernelmodule in the Kernel-modules-Dotpup.
Install it again, to overwrite the new module used for testing.
That might solve the unresolved symbols.
But then we still would need working Xorg-modules - I have no idea how to get them.
Maybe someone using vector-linux or Slakware has them.
It is odd, sometimes modules from other distros may even work better than modules compiled in Puppy.
Just trial and error in such a case
Greets, Mark
Install it again, to overwrite the new module used for testing.
That might solve the unresolved symbols.
But then we still would need working Xorg-modules - I have no idea how to get them.
Maybe someone using vector-linux or Slakware has them.
It is odd, sometimes modules from other distros may even work better than modules compiled in Puppy.
Just trial and error in such a case
Greets, Mark
OK, looks like I'm stuck here.
Used a more recent libdri.a, no more comlaints ablout that. But still - no DRI.
From the X log:
(WW) ATI(0): Failed to set up write-combining range (0x40000000,0x800000)
(II) ATI(0): [drm] SAREA 2200+1208: 3408
(WW) ATI(0): Direct rendering has been disabled.
(EE) ATI(0): [dri] DRIScreenInit Failed(II)
...
ATI(0): Direct rendering disabled
No idea what that's all about. Anybody?
Regards,
Roger
Used a more recent libdri.a, no more comlaints ablout that. But still - no DRI.
From the X log:
(WW) ATI(0): Failed to set up write-combining range (0x40000000,0x800000)
(II) ATI(0): [drm] SAREA 2200+1208: 3408
(WW) ATI(0): Direct rendering has been disabled.
(EE) ATI(0): [dri] DRIScreenInit Failed(II)
...
ATI(0): Direct rendering disabled
No idea what that's all about. Anybody?
Regards,
Roger
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
My VIA Unichrome DRI package contains updated libGL files compiled from CVS source at http://dri.freedesktop.org. Maybe this is what you need? Certainly DRI could not be enabled with the Unichrome driver without these files. To save you the trouble of downloading the Unichrome package and extracting the files you need, I have just now packaged these files separately. The package also contains updated libdrm files which might also help. Uncompress this package from /MU wrote:Run "glxinfo" to test, if DRI works, the result should contain a line "dri: yes".
If you get "no", you might need to upgrade libGL.so
EDIT: libGL-for-DRI.tar.gz removed. Get it from http://www.murga-linux.com/puppy/viewtopic.php?p=83603
Last edited by tempestuous on Tue 12 Dec 2006, 08:27, edited 2 times in total.
Thanks a lot! Nice to get some help from someone just around ... the globe
It still does not what it should. No complaints anymore in the X log, I could even get around that "write-combining range" error, but glxinfo still tells me that dri is not enabled.
I managed to get it running in my gentoo playgroud somehow, but I could not recognize much of an improvement. glxgears gave me roundabout the same results as without dri.
GL is working anyway, so I guess I'll leave it with that, it's obviously running reasonable fast.
Many thanks for all that help!
Regards,
Roger
It still does not what it should. No complaints anymore in the X log, I could even get around that "write-combining range" error, but glxinfo still tells me that dri is not enabled.
I managed to get it running in my gentoo playgroud somehow, but I could not recognize much of an improvement. glxgears gave me roundabout the same results as without dri.
GL is working anyway, so I guess I'll leave it with that, it's obviously running reasonable fast.
Many thanks for all that help!
Regards,
Roger