(old)Puppy Linux Discussion Forum

WhoDo wrote:Could it [Remaster Express] be run on RAM-challenged machines IF they have sufficient SWAP? I don't like telling users of Puppy that they can't remaster with less than 1Gb of physical RAM, which is what it seems we're looking at here.

No, I don't want to tell them that. Let me see what I do want to tell them. How about this, prominently displayed at the stage where the estimated sizes are figured and the "Proceed to Step Three" button is displayed? (Feel free to suggest any improvements in the language!)
________

Warning: the remastering process may use a large amount of your computer's memory, possibly three or four times the size of the new pup-420.sfs main file that will be created. If your computer does not have that much RAM available, you will need a swap partition that can be used for additional memory. If you do not already have a Linux swap partition (typically located on a hard drive), you will need to use one of the partition managers under the System menu to create one.

If you are not sure your computer has enough memory, it would be a very good idea to run HardInfo (under the System menu), scroll down to the "Memory" section, and use it to keep track of how much "free memory" and "virtual memory" (swap space) you have available, especially during Steps Three and Four. If you run out of both "free memory" and "virtual memory" during remastering, Remaster Express may stop working. If it does, open Pprocess (also under the System Menu); select the "wish /usr/sbin/remax" process; and click "End Process." If all else fails, rebooting Puppy will shut down Remaster Express and restore your free memory.
________

By the way, one of the users who reported the problems to me (eegad, in this thread: http://www.murga-linux.com/puppy/viewto ... 6&start=15) said he tried a newer version of mksquashfs posted by vanchutr in the same thread, and he was able to use it (unlike the older version) to burn a CD with Remaster Express. I'm not quite sure why the difference, because the newer version used up about as much free memory as the older one when I tried it--but I'm attaching the newer version here in case you'd like to take a look.

post deleted.

More involved than I thought - not just an edit of the init script

Can someone try this cups and see what the cpu usage is?
http://www.puppylinux.asia/tpp/ttuuxxx/ ... i386-3.pet
ttuuxxx
name: puppy
password: linux
you'll probably have to type it twice

1Gb RAM is not enough for me for remasterpup2...Does you new program fix it ?

Can someone try this cups and see what the cpu usage is?
http://www.puppylinux.asia/tpp/ttuuxxx/ ... i386-3.pet
ttuuxxx

Fresh CD boot RC4, ran CUSP... initializes...

RAN PET.. "Failed to connect".... this was after restart X....

Two machines. Assume necessary to restart x?

Minnesota wrote:

Can someone try this cups and see what the cpu usage is?
http://www.puppylinux.asia/tpp/ttuuxxx/ ... i386-3.pet
ttuuxxx

Fresh CD boot RC4, ran CUSP... initializes...

RAN PET.. "Failed to connect".... this was after restart X....

Two machines. Assume necessary to restart x?

na you shouldn't have to restart after installing it, ok how about this patch that pizzasgood offered, It was included in the last one you tried, but that was on beta3, maybe just reboot on your live cd, with
puppy fix=ram
and then install this small patch with the current cups installed. Not the beta 3 just the one which came with the cd
I'm thinking maybe beta 3 isn't working correctly so we'll try the current one, the current one works for you right? but you just have high cpu resource usage right ?
thanks for the help
ttuuxxx

capoverde wrote:Also, with XOrg the keyboard shorcut to open a terminal inside a directory (<'>) doesn't work -- not that it matters much, but this is an old unsolved issue, most probably a tricky one since all other shortcuts seem to work.

Actually, it does work. But it uses the backquote, not the normal quote ( ` vs ' ). On a US keyboard it's the same key as the tilde, left of the 1 and below the Esc.

`f00 wrote:Obviously, xorg.conf switched over to new vidcard at boot - same issue as noted with xorg (when dealing with vidcard with more than one vga out, as many aftermarket vidcards have as a standard), namely the line in xorg.conf, section server layout

Code: Select all

#   Screen      1  "Screen1" RightOf "Screen0"

must be commented out to keep the maus-pointer from disappearing 'offscreen' .. even though there is only one monitor on this card, xorg seems perhaps to be interpreting the card's two vga outs as 'screens' even if there is no display connected to the 2nd vga out.

Earilier in this thread I supplied WhoDo with a further modified /usr/sbin/xorgwizard that will automatically comment out any screen lines besides Screen0, in addition to the other modifications it has had since 4.1.2.

Hey WhoDo
A couple of months back I posted a gimp package I compiled In the Software section, Today one user asked me how come you can't acquire from a scanner in gimp using xsane, well I read up on it and basically first you need a system link from xsane bin to the usr/lib/gimp/2.0/plugins etc, so I tried it and it worked on Dpup, but dpup isn't puppy, when I tried it on 4.2 rc4 no go, Then I started thinking it must be Xsane, so I compiled the latest version and sure enough it didn't compile with gimp support, because I didn't have the devs installed at the time. So I install the gimp devs and recompiled it and poof it worked.
Below is the latest xsane with gimp support its 4kb larger then the repo pet, but its also a couple versions newer.

also if you wanted a 5.5MB gimp for the repo this one compiled without patching things and changing glib.dbus etc like other gimps on the forum.
http://www.puppylinux.asia/tpp/ttuuxxx/ ... oc-nsl.pet

ttuuxxx

Whodo

First I want to say NO OFFENSE to anybody.....ok ttuuxxx?

I tried to use icewm's freememapplet in jwm...picture below...the "M" only shows half or it won't be like that in 4.2 final if using this? Or could be only me?

Thanks

trio wrote:Whodo

First I want to say NO OFFENSE to anybody.....ok ttuuxxx?

I tried to use icewm's freememapplet in jwm...picture below...the "M" only shows half or it won't be like that in 4.2 final if using this? Or could be only me?

Thanks

Hey bro, nice of you... but no need to be politically correct... ttuuxx has thick skin....

linuxcbon wrote:1Gb RAM is not enough for me for remasterpup2...Does you[r] new program fix it ?

You've tried remasterpup2 and it didn't work because you had "only" 1 GB RAM? Ugh! Well, eegad said he has 1 GB RAM too, and he reported that the newer version of mksquashfs (attached above, i.e., on page 27 of this thread) did work for him with Remaster Express (presumably it would work with remasterpup2 too).

Untar the tarball, rename /usr/sbin/mksquashfs as "mksquashfs.old" or something ("mksquashfs.ancien" in French), copy the new mksquashfs to /usr/sbin, and give it a try (preferably while running HardInfo to see what's happening to your computer's memory). If it doesn't work, please let me know what happens instead.

Ok, I've been thinking & testing how is the easiest workaround for the bcm43xx module problem, and I found one..very easy..want to test?

1. boot fresh (no pup_save)
2. install this pet below
3. reboot (you'll be asked to make pup_save file, please make one)
4. on this second boot, then you go to network wizard..and bcm43xx won't be there.......

Hopefully Whodo already fix this for final..

thanks

.

MinHundHettePerro wrote:

trio wrote:Whodo

First I want to say NO OFFENSE to anybody.....ok ttuuxxx?

I tried to use icewm's freememapplet in jwm...picture below...the "M" only shows half or it won't be like that in 4.2 final if using this? Or could be only me?

Thanks

Not only you, me too in IceWM!

Cheers/
MHHP

I'm working on it
Really the numbers are way more important than the letters, m=mb g=gb etc, But i'm working on it as we speak:) It never used to do that, Its something new, I wonder why ?
ttuuxxx

.

ttuuxxx

Boot RC4 new from CD.. should be same as pfix=ram?
a. click on cups-patch-v1.pet
FAILED TO CONNECT with either link, from System or from Setup menu
b. restart menu
same results
c. restart x
same results
Boot RC4 new from CD
a cups-8462-i386-3.pet
b Any combination of system menu, restart menu, restart x, setup menu....all yield
FAILED TO CONNECT

Boot RC4 new from CD..
a. click on cups-patch-v1.pet
Finally read message for need to REBOOT
Put in stick, saved to stick
reboot from CD assumed picked up saved data from stick
b. FAILED TO CONNECT

Not having any luck with this....

Sorry guys that Gimp/Xsane package was missing a updated lib, its now updated but its 145kb bigger, libtiff.so.5 I had to include, so since probably WhoDo doesn't have a extra 145kb compressed, probably just use it as a repo item.
here's the link to the updated package that includes the latest libtiff
http://www.murga-linux.com/puppy/viewto ... h&id=16574
url

Minnesota wrote:ttuuxxx

you have to boot clean on puppy 4.2
you need the cd in the drive and reboot, when the first screen comes up tye
puppy pfix=ram
that will ignore anything you have saved on hard disk and boot 100% in ram.
then try the patch please
ttuuxxx

you could also unplug your hard drive if you really want to make sure
and have the patch saved on usb etc or download it again from here.

NO hard drive.. test bed has mobile disk, and I pull the drive.. so Booting from CD clean!!!

Greg

add:

In a few cases I have pressed RESET.. but I assume Puppy is loading from scratch and will not pick up anything in OLD memory... I know this is not true with the old video as I can see last image a sometimes.. but I assume regular memory is reset????

My Medium has a second 320GB HDD connected to a e-sata connector in a bay. So the HDD is connected external.

the 4.20RC4 don't recognize this HDD.
The first sata HDD is recognized fortunately.

I tried upup-015 and to my surprise and pleasure this external HDD was recognized.

I looked at the kernel version and saw 2.6.29.rc7.
Could this be the reason for the support of the external HDD?
Will this support be there soon in 4.2x?