(old)Puppy Linux Discussion Forum

G_Pup is a Barebones (fat free), SMP enabled, Puppy 4.1.2. Thanks to MU for the SMP kernel, and Pizzasgood for the SM crash fix, multiple monitor fix and petget path fix.

Note: For the lock icon to work install, xlockmore-5.20.1patched.pet
For wallpaper setter to work install, gpicview-0.1.9.pet

g_pup-1.2.iso
md5sum
Kernel_src to compile modules is here.
For devx use puppy 4.1.2 devx.

OK I am running low on HD space so this may explain my difficulties.

Booted up OK and I then tried to install the nvidia drivers
after rebooting I was unable to use xorg and had to revert to xvesa.

Defeated the purpose for me as I wanted to set up SecondLife

Be interested how others get on and if they notice any speed increase on multi processors?
Thanks wolf-pup, sorry was unable to devote more time to testing dues to system deficiencies . . .

the Nvidia drivers might have to be recompiled for the new Kernel.
What driver did you use?
Mark

lobster, i haven't tried this one yet but have also just remastered a puppy with smp-kernel.

my first impressions:
- everything seems to run a little more 'fluently' but as i use an actual laptop (sure multicore) i didn't really have speed-deficits with puppy ...
- using dir2sfs is much faster

i will test with some encoding and report back.

cheers
aragon

Does G Pup have a GUI? I have not been able to get any Puppy's to run on my computer. It is a Dell PowerEdge 2300. It was used as a server and has 6 hard drives. I can run Slackware on it fine. I have Wolvix running on it right now and I really like it but I have all these Puppy CD's (probably more than 40 because I'm either nuts or addicted) lying around and it just bugs me that I can't get any of the versions to work.

What are the applications included, if any?

Thanks.

BuddhaDog wrote:Does G Pup have a GUI?

Yes, has Xorg and Xvesa.

MU wrote:the Nvidia drivers might have to be recompiled for the new Kernel.
What driver did you use?
Mark

NVIDIA-177.82-k2.6.25.16.pet

Found out that USB booting seems to work in the puplet using the fatmbr, have not tried in reg puppy 4.1.2.

downloading it now.

hopefully should make a nice base for 0.4.

well, i guess the next thing to do is test it.

- J-Bob

deleted

g_pup updated to 1.1, fixed modules not loading when installed and removed the extra SCSI modules to save space.

For some reaason, the wallpaper setter won't work.
And I have conky set to run on startup, but after a few times it won't run on startup anymore.

Hi Lobster:

Did you ever get Nvidia working with G_Pup 1.1. I haven't had any luck with either the latest pet or building with the download from Nvidia's site. If you did get it working could you give a hint as to how you got it working? The pet installs without any problem and the driver downloaded from nvidia's website builds successfully but both approaches leave me unable to start X. See my note to Wolf Pup below to see what I have tried so far.

Hi Wolf Pup:

When I build the nvidia driver using the file downloaded from nvidia's site it appears to complete successfully, however when I:
Googling and referring to nvidia user forums, seems to indicate two possible causes.

One is that the gcc used to build the kernel is different from the one used to build the driver. I am using the devx_412.sfs which appears to have gcc 4.2.2. Is this the same gcc used to build the kernel?

A second possible cause is that the kernel sources used during the build are incorrect. I am using the
kernel-src-2.6.25.15-patched-puppy4.1.sfs as my kernel source. Would you know if this is correct? If it is not correct, do you know where I can get the correct sources?

Any help or direction would be much appreciated.

Thanks.

bdika

wosifat wrote:For some reaason, the wallpaper setter won't work.

The problem is in the file "/usr/local/apps/Wallpaper/AppRun". Since none of the image viewers it looks for are present, the "View" menu ends up with no menuitems. Gtkdialog3 doesn't like this and aborts.

Fix: sorry, haven't made a "fixed" version of "/usr/local/apps/Wallpaper/AppRun".

Very crude work around: Install one of the viewers it is looking for, namely "gpicview". Use the wallpaper setter. Then uninstall "gpicview".

gyro

In menu, "Desktop->JWM configuration->Application launch buttons in tray", does not work.
The problem is in file "/usr/local/jwmconfig2/panel-buttons". It uses the program "bc", which is not present.

Very crude work around: Install "bc". Use "Application launch buttons in tray". Uninstall "bc".

gyro

So how good if gpicview? Should I really uninstall it after running the wallpaper selector?

For the lock icon to work install, xlockmore-5.20.1patched.pet

gyro wrote:In menu, "Desktop->JWM configuration->Application launch buttons in tray", does not work.
The problem is in file "/usr/local/jwmconfig2/panel-buttons". It uses the program "bc", which is not present.

Very crude work around: Install "bc". Use "Application launch buttons in tray". Uninstall "bc".

Too lazy to go through "/usr/local/jwmconfig2/panel-buttons" replacing every call to "bc". Besides there could be other scripts that use "bc" in the same way. So I wrote a very small bash script that reads an arithmetic expression from stdin and writes the result to stdout just like "bc -l". It uses bash's inbuilt maths capabilities.

I have attached "bc.gz", which contains only the script "bc". Copy the file "bc.gz" to /root/my-applications/bin, (or any other place on the path). Click on it and then click on "Yes".

gyro

To return the wallpaper setter to full functionality, it is necessary to install either "fotox" or "gpicview".

The wallpaper setter could be made to work, but without it's "View" menu functioning.
This could be done my modifying the file "/usr/local/apps/Wallpaper/AppRun" so that it doesn't crash.
Or the wallpaper setter can be fooled into thinking it has either "fotox" or "gpicview" available.

I have no need of either "fotox" or "gpicview" in the puppy I intend to build on this base. I do want to have the wallpaper setter available, but I can happily live without the "View" menu.

So, I have added the following script as "/root/my-applications/bin/fotox":This script does nothing, but convinces the wallpaper setter that "fotox" is installed, so it works rather than crashing. If "View->Fotox" is clicked, nothing happens.

NOTE: If ever the real "fotox" is installed it does so into "/usr/bin", ("# which fotox" in normal Puppy412). It will always be found in the path before this bogus "fotox". So, in the wallpaper setter, clicking "View->Fotox" would then work.

gyro

G_pup updated to 1.2, fixed SMP not working in USB boot.