Puppy Linux Discussion Forum

[MU]

I'm currently adding compiz to Muppy.
I looked at Tigerpup to see how it works.
I really like the cfmanager coming from wNOP2, that runs after xorgwizard.

For Muppy, I modified it.

Here is my patched version, it includes the ATI/Nvidia-drivers.
ftp://ks301128.kimsufi.com/Muppy0084/Alpha-test/07special/developer-patches/

Mark
------------------------------------------------------
readme.txt:
these drivers are taken from tigerpup.
I added the XORG72.tar.gz so that you can restore OpenGL, it has:

./usr
./usr/X11R7
./usr/X11R7/lib
./usr/X11R7/lib/libglut.so.3.7.1
./usr/X11R7/lib/libGLw.so
./usr/X11R7/lib/libGL.so.1
./usr/X11R7/lib/libglut.so
./usr/X11R7/lib/README-opengl.txt
./usr/X11R7/lib/libGL.so
./usr/X11R7/lib/libGLU.so
./usr/X11R7/lib/libglut.so.3
./usr/X11R7/lib/libGLU.so.1
./usr/X11R7/lib/libGLw.so.1.0.0
./usr/X11R7/lib/libGL.so.1.2
./usr/X11R7/lib/libGLw.so.1
./usr/X11R7/lib/libGLU.so.1.3.060502
./usr/X11R7/lib/xorg
./usr/X11R7/lib/xorg/modules
./usr/X11R7/lib/xorg/modules/extensions
./usr/X11R7/lib/xorg/modules/extensions/libGLcore.so
./usr/X11R7/lib/xorg/modules/extensions/libglx.so
./usr/X11R7/lib/xorg/modules/extensions/README-glcore.txt


The Ati/nvidia packages now have shorter names for easier updates.
They are no longer in /tmp, so that you can use them more than once.They are now in:
/usr/lib/graficsdrivers/
I changed the way they are packed and extracted, to reduce the need of temporary space.

I took out some files, and added them in the SFS itself, to save space:
./usr/X11R7/lib
./usr/X11R7/lib/libGLcore.so.96.43.01
./usr/X11R7/lib/libGLcore.so.100.14.19
./usr/X11R7/lib/xorg
./usr/X11R7/lib/xorg/modules
./usr/X11R7/lib/xorg/modules/dri
./usr/X11R7/lib/xorg/modules/dri/fglrx_dri.so
./usr/X11R7/lib/xorg/modules/drivers
./usr/X11R7/lib/xorg/modules/glesx.so

I modified the /usr/sbin/cfwizard correspondingly.
It also will extract the XORG72.tar.gz when it runs.
So this restores Puppys original drivers.
If the user then chooses ATI/Nvidia, those packages are extracted.

I also replaced text like "use XFCE in wNOP2" with more neutral strings (use no compiz, use standard desktop).


-----------------
On my system, xorgwizard gets wrong info and creates a corrupt xorg.conf, when fglrx_drv.so is installed.
Also if I want to use the freeRadeon-driver.
So I patched xorgwizard like this (on mine around line 312):


#autoprobe...
#MU- fglrx crashes xorgwizard! so remove it...
rm -f /tmp/fglrx_drv.so
mv /usr/X11R7/lib/xorg/modules/drivers/fglrx_drv.so /tmp/fglrx_drv.so
rm -f /usr/X11R7/lib/xorg/modules/drivers/fglrx_drv.so
#MU-end
Xorg -configure > /tmp/xorgprobe.txt 2>&1

#MU-restore fglrx
if [ -f /tmp/fglrx_drv.so ];then
mv /tmp/fglrx_drv.so /usr/X11R7/lib/xorg/modules/drivers/fglrx_drv.so
fi
#MU-end

Mark Ulrich, July 2008

[mysticmarks]

are you basing muppy on dingo w/ compiz?

[MU]

No, muppy(008.3) was initially based on Puppy 3.
Muppy 008.4 is a updated version, but the scripts are rewritten in many parts, and most base libraries were replaced with newer ones from Slackware 12.1 and Gnomeslackbuild.

So to say it is based on Puppy 3 would be a wrong indication, as it meanwhile has replaced most of it.
It should be compatible in most parts with Puppy 3 and 4.
The Compiz I used is the one made for Puppy 3 by wow.

Mark

[tombh]

Hi MU,

I'm glad my cfwizard script has been useful for you. Thanks for keeping a record of your changes.

tom

[wow]

I have a request:

- An option to force the proprietary nVidia/ATI driver

Some gpus (like my igpu nVidia GeForce 7050) are not automatically detected (it uses the "vesa" driver by default, and "unknown" as BoardName in xorg.conf).

[MU]

can't you force the propriatary drivers in the manual setup?

Mark

[wow]

Not really, it just says something like "you're using the vesa driver, your card is unsupported and compiz won't be loaded" (can't remember I'm not at home now) I'll give you some screenshots later. The same happens with wNOP and MUppy, I can install/setup the driver manually but maybe other users can't.

[tombh]

Ah yes, this is something that has already been discussed on the wNOP thread as a bug, it is something I plan to fix for the next release. To fix it, not only does the option to run the cfwizard manually need to be given under all circumstances, but the code also needs to take responsibility for the

[wow]

This is the only one message that I got with cfwizard (wNOP and MUppy):

[Click to read some lines from my xorg.conf file]
(As you can see the user can't do nothing more, if I choose <Retry Xorgwizard> it'll drop me to this message over and over again)



@MU and tombh: I'm sorry, what I really meant to say is that I wanted something like this in the "generic vesa..." dialog:

But now that I've seen the code (cfwizard - muppy084), I've noted that it's simplier to edit and comment out these lines: