Puppy 2.12: 3D-Control-Center V2.00
Puppy 2.12: 3D-Control-Center V2.00
This is a slightly modified version for Puppy 2.12
Details about the program (and older versions):
http://www.murga-linux.com/puppy/viewtopic.php?t=10834
Download:
http://dotpups.de/dotpups/3D-Control-Center/getdir.pup (20 kb)
http://dotpups.de/dotpups/3D-Control-Ce ... st04MU.pup (18 kb)
http://dotpups.de/dotpups/3D-Control-Ce ... d-2.13.pup (74 kb)
It requires an active internet-connection, to be able to download additional files required for your graficscard.
I did not test it intesively, so please report all bugs you find.
But t should work, as I just had to change some version-numbers.
Nvidia-users
there is an own installer for you:
http://www.murga-linux.com/puppy/viewtopic.php?t=14438
Mark
Details about the program (and older versions):
http://www.murga-linux.com/puppy/viewtopic.php?t=10834
Download:
http://dotpups.de/dotpups/3D-Control-Center/getdir.pup (20 kb)
http://dotpups.de/dotpups/3D-Control-Ce ... st04MU.pup (18 kb)
http://dotpups.de/dotpups/3D-Control-Ce ... d-2.13.pup (74 kb)
It requires an active internet-connection, to be able to download additional files required for your graficscard.
I did not test it intesively, so please report all bugs you find.
But t should work, as I just had to change some version-numbers.
Nvidia-users
there is an own installer for you:
http://www.murga-linux.com/puppy/viewtopic.php?t=14438
Mark
Last edited by MU on Sat 13 Jan 2007, 17:32, edited 5 times in total.
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
Did you do that yet, or am I just being glitchy? It's to late/early for me to go digging around for error messages, so lets just say I'm getting higher framerates with the vesa driver than with the fglrx driver without DRI. 25 vs 14, to be exactThis version does not support the propriatary ATI-driver, I will compile the required kernel-module tomorrow.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
Re: Puppy 2.12: 3D-Control-Center V2.00
Hey Mark, thanks for that! Much appreciated.MU wrote: I did not test it intesively, so please report all bugs you find.
But t should work, as I just had to change some version-numbers.
Mark
I have installed too, but like Pizzasgood I'm getting some strange activity.
Even though I loaded the i810 DRI - correct for my hardware - when I try your Demo it says that
Only trouble is I still get frame rates >20fps, according to the Demo screen!DRI-Status: DRI is NOT active, the demo should run slow (< 10 fps)
I absolutely LOVE the window shadows, though. What do I have to change to get that to load at startup?
Vista, eat your heart out!
Cheers
Sorry, I had uploaded the old dotpup by accident
I updated it with a new one now.
I did not yet compile the ATI propriatary driver, hope I can do it today.
-------------
exec $CURRENTWM
Look with an editor at
/usr/local/3DCC/resource/run-shaows
for other parameters to display shadows different, try
xcompmgr --help
for details.
Mark
I updated it with a new one now.
I did not yet compile the ATI propriatary driver, hope I can do it today.
-------------
You can add such 2 lines to /root/.xinitrc, beforeI absolutely LOVE the window shadows, though. What do I have to change to get that to load at startup?
exec $CURRENTWM
Code: Select all
killall xcompmgr
xcompmgr -c -l -14 -t -14 -r 15 -o .7 2>/dev/null&
/usr/local/3DCC/resource/run-shaows
for other parameters to display shadows different, try
xcompmgr --help
for details.
Mark
Re: Puppy 2.12: 3D-Control-Center V2.00
Hi Mark. Sorry, but no change even though I downloaded all the dotpups again, reinstalled and rebooted. Same error as above.WhoDo wrote: Even though I loaded the i810 DRI - correct for my hardware - when I try your Demo it says thatOnly trouble is I still get frame rates >20fps, according to the Demo screen!DRI-Status: DRI is NOT active, the demo should run slow (< 10 fps)
Cheers
whodoo, please send me your /var/log/Xorg.0.log as attachment.
----------------
I uploaded the ATI-propriatary driver dotpup, you can install it from within the 3DCC (DRI-Graficscard-drivers -> ATI-fglrx).
This was nasty
First the Kernelmodule failed to compile, but this helped me:
http://www.gentooforum.de/thread.php?threadid=11378
I hope, the dotpup works, at least it did then in a new Test-Muppy.
I also could compile the newer driver, but made no dotpup, as I cannot test it.
The new driver no longer supports cards older than Radeon 9500.
Mark
----------------
I uploaded the ATI-propriatary driver dotpup, you can install it from within the 3DCC (DRI-Graficscard-drivers -> ATI-fglrx).
This was nasty
First the Kernelmodule failed to compile, but this helped me:
http://www.gentooforum.de/thread.php?threadid=11378
Then I got strange errors from libGL that are reported in many forums, but a re-installation with the Ati-installer fixed it./usr/src/linux/include/linux/mm.h
insert after the "include" lines:
#define VM_SHM 0x00000000
I hope, the dotpup works, at least it did then in a new Test-Muppy.
I also could compile the newer driver, but made no dotpup, as I cannot test it.
The new driver no longer supports cards older than Radeon 9500.
Mark
Here it is, Mark. After reading the file I also tried the i915 driver as well, but the same result.MU wrote:whodoo, please send me your /var/log/Xorg.0.log as attachment.
Cheers
Update: Hmmm. Board won't let me add an attachment with .log, .sav or .txt extension ... something is amiss. I have changed extension to .gz but file is still raw text.
- Attachments
-
- Xorg.0.log.gz
- (61.02 KiB) Downloaded 954 times
2146: (II) I810(0): direct rendering: Disabled
But no hint, why.
I miss entries concerning DRM , loading a Kernel-Module.
Do you have these files?:
/lib/modules/2.6.18.1/kernel/drivers/char/drm/drm.ko
and
/lib/modules/2.6.18.1/kernel/drivers/char/drm/i810.ko
/lib/modules/2.6.18.1/kernel/drivers/char/drm/i915.ko
In the logs I was sent in the past I find none for intel-chips.
If someone with working accelleration (even on other Pupyversions) might post his log, we might get a hint by comparing them...
For example my Ati-fglrx-driver has such lines in the log, that show that it tries to use the Kernelmodule:
Mark
But no hint, why.
I miss entries concerning DRM , loading a Kernel-Module.
Do you have these files?:
/lib/modules/2.6.18.1/kernel/drivers/char/drm/drm.ko
and
/lib/modules/2.6.18.1/kernel/drivers/char/drm/i810.ko
/lib/modules/2.6.18.1/kernel/drivers/char/drm/i915.ko
In the logs I was sent in the past I find none for intel-chips.
If someone with working accelleration (even on other Pupyversions) might post his log, we might get a hint by comparing them...
For example my Ati-fglrx-driver has such lines in the log, that show that it tries to use the Kernelmodule:
I think, also with Intel something concerning DRM should be reported, but as it is not, the drm.ko might not have been found.(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [drm] mapped SAREA 0x2000 to 0xb6f4d000
(II) fglrx(0): [drm] framebuffer handle = 0x3000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.28.8
(II) fglrx(0): Date: Aug 17 2006
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
Mark
Yes, there is a unichrome-driver for xorg:
http://dotpups.de/3DCC/2.12/
The Kernel-dotpup contains a via.ko-module.
You can choose unichrome in the 3DCC.
I could not test it myself though, so no guarantee.
Please look first in xorg.conf, what Puppys xorgwizard entered as
Driver "xxx"
If xxx is vesa, you might have to replace it with
Driver "via"
/usr/X11R7/lib/xorg/modules/drivers/
has no unichrome, so I assume it is via.
The via-module then automatically should load
/usr/X11R7/lib/xorg/modules/dri/unichrome_dri.so
This file is installed by 3DCC from the dotpup DRI-unichrome_dri.so.pup.
Try and please report if it works or not.
Mark
http://dotpups.de/3DCC/2.12/
The Kernel-dotpup contains a via.ko-module.
You can choose unichrome in the 3DCC.
I could not test it myself though, so no guarantee.
Please look first in xorg.conf, what Puppys xorgwizard entered as
Driver "xxx"
If xxx is vesa, you might have to replace it with
Driver "via"
/usr/X11R7/lib/xorg/modules/drivers/
has no unichrome, so I assume it is via.
The via-module then automatically should load
/usr/X11R7/lib/xorg/modules/dri/unichrome_dri.so
This file is installed by 3DCC from the dotpup DRI-unichrome_dri.so.pup.
Try and please report if it works or not.
Mark
That fixed it for the VIA unichrome drivers as well. Thanks Mark.Ah, found it.
Please delete:
/root/dotpups-downloads/DRM-Kernelmodules-Puppy.pup
Then again in 3DCC, install the Kernelmodules.
I had packaged them in a wrong folder Embarassed Embarassed
They went to /modules/
instead of
/lib/modules/
You can delete /modules/
Mark
mach64
Hi,
just tried it on my notebook with mach64 - no success.
The 3d demo runs but tells me dri is not anbaled, i get about 7 fps.
From the xorg log:
(==) ATI(0): Write-combining range (0x40000000,0x800000)
(II) ATI(0): [drm] SAREA 2200+1208: 3408
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "mach64"
(II) ATI(0): [drm] drmOpen failed
(EE) ATI(0): [dri] DRIScreenInit Failed
I managed to get drm/dri running (with lots of help from you) on puppy 1.08 - but that was xorg 6
Any ideas?
just tried it on my notebook with mach64 - no success.
The 3d demo runs but tells me dri is not anbaled, i get about 7 fps.
From the xorg log:
(==) ATI(0): Write-combining range (0x40000000,0x800000)
(II) ATI(0): [drm] SAREA 2200+1208: 3408
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "mach64"
(II) ATI(0): [drm] drmOpen failed
(EE) ATI(0): [dri] DRIScreenInit Failed
I managed to get drm/dri running (with lots of help from you) on puppy 1.08 - but that was xorg 6
Any ideas?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
mach64 is a problem. Even after compiling the kernel module, the 2D mach64 drivers (ati_drv.o & atimisc_drv.o) have their DRI plugin code disabled for security reasons ... well this was the case with Xorg 6.8.1 & 6.8.2. This can be fixed, but it involves a complete recompile of Xorg7 with the configuration file modified.
I tried to compile this older Kernel-module this morning.
http://dri.freedesktop.org/snapshots/ma ... 86.tar.bz2
Got an error, and commented a function for tests in drm/linux-core/ati_pcigart.c
86-89
Then it compiled, but a modprobe mach64 results in:
FATAL: Error inserting mach64 (/lib/modules/2.6.18.1/kernel/drivers/char/drm/mach64.ko): Unknown symbol in module, or unknown parameter (see dmesg)
No idea
Mark
http://dri.freedesktop.org/snapshots/ma ... 86.tar.bz2
Got an error, and commented a function for tests in drm/linux-core/ati_pcigart.c
86-89
Code: Select all
// for (i = 0; i < ATI_PCIGART_TABLE_PAGES; i++, page++) {
// __put_page(page);
// ClearPageReserved(page);
// }
FATAL: Error inserting mach64 (/lib/modules/2.6.18.1/kernel/drivers/char/drm/mach64.ko): Unknown symbol in module, or unknown parameter (see dmesg)
No idea
Mark
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
message from tempestous:
---------
Mark,
You're right, the mach64 DRM source from http://dri.freedesktop.org/snapshots/ will not compile, but I just downloaded the latest DRM source using git, and this compiles the mach64 module OK.
So I have just uploaded the mach64 module to you.
When I ran this build command -
make DRM_MODULES="mach64"
the drm.ko module also compiled. It might be important that this version goes with the mach64 module, so I sent you both.
Regarding the 2D mach64 driver: I'm not sure what configuration options were used in Puppy's Xorg7.0, but I just downloaded the Xorg7.0 source and its default configuration (xorg.cf) has the mach64 DRI option disabled. Line 252 has this -
#define BuildDevelDRIDrivers NO
The "DevelDRIDrivers" are ffb mach64 and unichrome
So I have changed this line to "YES" and I will send you the new mach64 2D driver hopefully in a day or 2.
-----------
Kernelmodule:
http://dotpups.de/tests/mach64-DRM-k2.6.18.1.tar.gz
---------
Mark,
You're right, the mach64 DRM source from http://dri.freedesktop.org/snapshots/ will not compile, but I just downloaded the latest DRM source using git, and this compiles the mach64 module OK.
So I have just uploaded the mach64 module to you.
When I ran this build command -
make DRM_MODULES="mach64"
the drm.ko module also compiled. It might be important that this version goes with the mach64 module, so I sent you both.
Regarding the 2D mach64 driver: I'm not sure what configuration options were used in Puppy's Xorg7.0, but I just downloaded the Xorg7.0 source and its default configuration (xorg.cf) has the mach64 DRI option disabled. Line 252 has this -
#define BuildDevelDRIDrivers NO
The "DevelDRIDrivers" are ffb mach64 and unichrome
So I have changed this line to "YES" and I will send you the new mach64 2D driver hopefully in a day or 2.
-----------
Kernelmodule:
http://dotpups.de/tests/mach64-DRM-k2.6.18.1.tar.gz
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Roger, I suggest you try this new mach64 kernel module. Uncompress the package from your uppermost directory, then run "depmod". Your xorg.conf needs to contain - Load "dri"
Now restart X. Check that "lsmod" lists the mach64 module. If not, load it manually then restart X again.
If 3D still doesn't work, it means that the standard mach64 (ati) 2D Xorg7.0 driver is not DRI-aware. I am trying to compile a revised 2D driver at the moment.
Now restart X. Check that "lsmod" lists the mach64 module. If not, load it manually then restart X again.
If 3D still doesn't work, it means that the standard mach64 (ati) 2D Xorg7.0 driver is not DRI-aware. I am trying to compile a revised 2D driver at the moment.