(old)Puppy Linux Discussion Forum

Hi Pemasu,
some more infos about:

charlie6 wrote:...A few minutes before that, i just got successfully driver-nvidia-304.88 on the very same machine+puppy session.

I indeed got a nvidia-304.88-k3.5.2-wheezy.pet + .sfs file compiled , but there is no nvidia driver in xorgwizards drivers choice list ... so...no use !
...

Now i got that nvidia-304.88-k3.5.2-wheezy.pet nvidia driver to work !!
This looks trivial:
In wheezy, the nvidia.ko driver is awaited to be located in:
/lib/modules/3.5.2-dpup/kernel/drivers/video/nvidia/nvidia.ko
BUT either in the pet or in the sfs, it is located in
/lib/modules/3.5.2-dpup/kernel/drivers/video/nvidia.ko
After have installed the pet , just symlinking as follows solves the question: I also noticed to have only 1024x768 depth=16 working resolution using a Samsung Synchromaster 152a display. Forcing xorgwizard to depth=24 causes X to a black screen.
last edited:
using a Samsung Synchromaster 204b display: through the Nvidia Settings menu, and xorgwizard as well, the display resolutions range is wider, and 1280x1024 and depth=24 can be achieved

Charlie

Wrong thread ... again

Still working pretty darn well........

James C,
you are throwing salt to the wound ... Yes, it runs great, I will attest to that. And yet, it is the only of my recent puppies, that I'm not at liberty to give a good run. Because of that "boot failsure" feature. I tried to edit the scripts, broke into initrd, but due to lack of savvy, failed to disable it. On every boot, it sticks a desktop flag on my windows partition. Security aside, that partition happens to be an SSD drive, and I want it to last, I want it to have fewer writes, not more. I don't want it to be burglarized, even if the burglar happens to be pemasu, or even Barry himself.

Pemasu, do you know what exact lines in what exact scripts should I comment out to disable "failsafe", both in dpup Wheezy and upup Raring?

anikin. There are quite many of them. But here is the woof commit:
http://bkhome.org/fossil/woof2.cgi/info/e28eb986ce

With anonymous login, you can go deeper and check the diff of the changes files and see the lines which have been modified in each script.

The pupdesk.flg mechanism can be disabled at woof building state nowadays. Now...when running 3builddistro, the script asks do you want to enable or disable it.

Oh, yes, quite a few. I had a look at them and later versions.
That's too much for me. They make my overwhelmed, little brain swim.
I'm sitting with 3 remastered, non-booting puppies: this one, upup raring and precise-5.7.
Did nothing extraordinary, usual stuff using remasterpup2 script ... no go.
With Barry's raring took a different approach - remastered via unsquashing/squashing and copying over stuff manually from the working tree. That one works. Have a gut feeling, the pupdeskflag is playing tricks on me. Pemasu, please clarify one thing in those scripts. Starting with quicksetup > initrd > init ... pupmode 5, is treated differently. So my question is this: if you disable failsafe in woof at build time, will that also disable failsafe for pupmode-5? Just desperately trying to understand how it works.

Thank you in advance.

Anikin. If the failsafe is dropped, only that feature is not in use. It just means that if you boot the black screen when X is starting and you have to press power button, then next time there is no automatic xorgiward in console state waiting for you. It will boot to the same black screen again.

The pupdesk.flg mechanism is only for preventing that. Nothing else.

I was looking at the situation with pBurn in Dpup Wheezy and there are a few issues.

The dependency check of pBurn 3.7.18 reports that dvd+rw-tools is missing. The official Debian .deb of dvd+rw-tools-7.1 is installed but it seems pBurn does not see it.

I compiled dvd+rw-tools-7.1 from source in Dpup Wheezy and I notice some of the files are different from the .deb package. Anyway, pBurn recognises it and the dependency check reports "OK".

I then looked at upgrading to the latest pBurn (4.0.4).

Am I correct in thinking that Dpup Wheezy has gtkdialog-0.8.4-r514 already installed? There is a gtkdialog file in /usr/sbin which I think is this binary, BUT there also is a symlink named gtkdialog in /usr/bin which links to gtkdialog4 in /usr/bin

I think you have to delete this symlink otherwise it over-rides the newer gtkdialog in /usr/sbin

If I do not delete the symlink, the new pBurn reports gtkdialog as too old but if I delete the symlink the dependency check reports gtkdialog "OK". This also affects the latest pMusic if you try to install that.

Also, the new pBurn needs cdrtools-3 which I have compiled from source in Dpup Wheezy. If it is available as a Debian package I couldn't find it.

I am attaching these packages in case anyone wants to TEST them. Install at your own risk. The cdrtools-3 package does seem to work with pBurn 4.0.4 but does over-write some existing files so it may be affecting other programs. May be perfectly OK though. Reports welcome.

With Datafilehost you need the small grey "DOWNLOAD" button.

cdrtools-3.01a16 Wheezy .PET
download = http://www.datafilehost.com/d/7674c28e
md5sum = 8604344b2265430afa9f43d38138cf48

cdrtools_DEV-3.01a16 Wheezy .PET
download = http://www.datafilehost.com/d/2aaa195e
md5sum = 95b45b23e72b56a76750bdc71dce0ed5

Hi OscarTalks,

OscarTalks wrote:...Am I correct in thinking that Dpup Wheezy has gtkdialog-0.8.4-r514 already installed?...

...The dependency check of pBurn 3.7.18 reports that ... There is a gtkdialog file in /usr/sbin which I think is this binary, BUT there also is a symlink named gtkdialog in /usr/bin which links to gtkdialog4 .... This also affects the latest pMusic if you try to install that.

That gtkdialog issue has been fixed in later Pburn's as also PMusic versions. Just download both latest !
That gtkdialog's symlink issue has already been reported as fa as i right remenber ... just browse across the forum member Zigbert's Pburns and PMusics threads to learn more about it.
Hope this helps
Charlie

Hi,
calcurse-3.1.4 organizer compiled for wheezy
(calcurse is a text-based calendar and scheduling application.)
here: http://www.murga-linux.com/puppy/viewto ... 476#721476
runs also on raring-3.9.9.X
Enjoy !, charlie

a few backgrounds.

Hi, futwerk.

I hope you are well.

picture au13 is quite different, I like the concept. It tries to delimit where the default Puppy icons are, perhaps ?

However, any way to change the very sad grey background to a more joyful color ?

Best regards.

musher0

Hi, Musher0, here are a couple of varitions of au13. Enjoy.

Hello,
Here's a little pet for people who prefer to keep java and flash player out of pupsave, and use only when needed. The script adds links in /tmp/lib. The pet has permanent links from /usr/lib/mozilla/plugins to /tmp/lib. The script in /root/my-applications must be edited to give the correct paths to libnpjp2.so and libflashplayer.so on your system.
Hope someone finds this useful.

P.S. Many thanks to Zigbert for http://murga-linux.com/puppy/viewtopic.php?t=38608

Since this question is not specific to Wheezy, I moved it to Beginners section of the forum http://murga-linux.com/puppy/viewtopic.php?p=726601

futwerk wrote:Hi, Musher0, here are a couple of varitions of au13. Enjoy.

Thanks!

new background.

new background.

Hello,
Still love Wheezy! I just remastered with /etc and /root customized to my settings. My intention was to run it in ram, as a frugal install on HD with no savefile, for more secure online banking. But when I boot with pfix=ram, I get the keyboard, country and xorg wizards and my customizations are overwritten.
I have this from arseh at http://www.murga-linux.com/puppy/viewtopic.php?t=89970 (Slacko)

Is there any practical way to remove [the quick setup menu] from the start, while it can remain as a program that can be used for times that it can be needed?
Or - I can delete the quickstart file from the system.

and from MochiMoppel:

Expand the main Puppy file (unsquashfs puppy_whatever.sfs) . In the resulting squashfs-root directory go to squashfs-root /var/local and create an empty file delayedrun_firstboot_flag. Repack the main file with mksquashfs squashfs-root puppy_whatever.sfs. That's it.

But I don't find a delayedrun_firstboot_flag file in Wheezy. Can someone tell me how Wheezy detects whether or not it's a first boot? Or another method to avoid the startup wizards?

Thanks
Wheezy 3.5.2.7, frugal installs on Lenovo S12 netbook

hi pemasu

we over at the community edition
are trying to make a woof debian base puppy
since you are the expert
could you give me any advice
about making an up to date
woof wheezy
also would you allow us to take a look at your project
and possibly use some of your ideas

any help would be appreciated

thanks

wanderer