Puppeee 4.3X

[jemimah]

I've been told it doesn't work at all in 7 (dunno about Vista). I updated the instructions to tell Win7 users to use Unetbootin.

[aarf]

http://puppeee.com/web/blog/puppeee-10-released/

wasnt puppeee going to distrowatch?

[jemimah]

I think so. I have to do the paperwork first and tell Barry.

I'm not sure if I have enough megabytes left on my aircard (evil AT&T will cut you off if you go over the limit) to do the upload to ibibio so I need to wait until Monday.

[simon1482]

hi, (not sure if this is a puppy question or a puppee question) My firefox 3.6.3 cache file is growing bigger and bigger and eating up all my save file. The firefox limit is set to 50Mb, but it's gone well past that. I've read about linking the cache to a /tmp folder, but it would be nice to keep some cache of commonly used sites. Is there a way to limit the cache file size?

Also, firefox is asking me to update to version 3.8. Should I do it, or will it break puppeee things?

[lemmy999]

Apologies for cross-posting this one but I thought I might have a better chance of sorting this problem out here rather than in Beginners Help.

First thing I have to say is- great distro Jemimah!! I am hoping to use this as my main distro on my 1000H. But thats after I sort out the following problem

I have installed puppeee in a frugal install on sda5. Grub is now properly configured and tries to boot puppeee.At some point I get the following error message

eee-504.sfs not found.Dropping out of initial-ramdisk console...
/bin/sh: can't access tty: job control turned off

This also happened with RC8. Any thoughts?

[jemimah]

hi, (not sure if this is a puppy question or a puppee question) My firefox 3.6.3 cache file is growing bigger and bigger and eating up all my save file. The firefox limit is set to 50Mb, but it's gone well past that. I've read about linking the cache to a /tmp folder, but it would be nice to keep some cache of commonly used sites. Is there a way to limit the cache file size?

Also, firefox is asking me to update to version 3.8. Should I do it, or will it break puppeee things?

I'm not sure about the cache question. Updating may or may not work. I've had issues in the past. I will make a Firefox 3.8 SFS this week.

[jemimah]

Apologies for cross-posting this one but I thought I might have a better chance of sorting this problem out here rather than in Beginners Help.

First thing I have to say is- great distro Jemimah!! I am hoping to use this as my main distro on my 1000H. But thats after I sort out the following problem

I have installed puppeee in a frugal install on sda5. Grub is now properly configured and tries to boot puppeee.At some point I get the following error message

eee-504.sfs not found.Dropping out of initial-ramdisk console...
/bin/sh: can't access tty: job control turned off

This also happened with RC8. Any thoughts?

Can you post your grub configuration?

[lemmy999]

Code: Select all

title Puppy Linux 504 frugal
rootnoverify (hd0,4)
kernel /puppy504/vmlinuz pmedia=atahd psubdir=puppy504 nousbwait=1
initrd /puppy504/initrd.gz

This is the grub config produced when I did the frugal install.

[jemimah]

Code: Select all

title Puppy Linux 504 frugal 
rootnoverify (hd0,4) 
kernel /puppy504/vmlinuz
initrd /puppy504/initrd.gz

If that works, you can add the other parameters back one at a time and see which is causing the problem. My guess is that you don't want pmedia.

[sandungas]

psubdir=XXXXX is mandatory if you want to boot from a subfolder

***You can make non-permanent changes in grub lines by pressing "E" in the grub selector window***
e= edit/ edit line
d=delete line
b=boot

Try to do some changes this way... is fast and is not dangerous

[jemimah]

It's not mandatory. The init script searches all drives one directory deep by default. Adding additional parameters only serves to speed things up.

[lemmy999]

Yay!!!! Your suggestion was spot-on Jemimah!!

Next task is to get Skype and NFS working.

Thanks.

[simon1482]

I'm not sure about the cache question. Updating may or may not work. I've had issues in the past. I will make a Firefox 3.8 SFS this week.

Thanks heasp, that would be great! Actually, the new version is 3.6.8 (not 3.. Sorry about that.

[songzi]

Just upgraded a previous Puppeee RC version to Puppeee 1.0 on this Eee PC 900. Everything works fine. Lots of thanks for Jemimah's work!!

[sandungas]

In this one http://puppeee.com/files/misc/bootinst.bat .... and the one included in V1 (different, but both has the same code lines) there are 2 spaces between -maf ...&... %DISK%:

Code: Select all

\boot\syslinux\syslinux.exe -maf  %DISK%:

Maybe this 2 spaces are the culpit of the broken installer in vista/7 ?¿?¿

I been looking at some different booinst.bat you did because im sure at least one of them dont creates this (hidden) ldlinux.sys file in the root of the device
At least the one included in RC2 creates the file in this subfolder \boot\syslinux\ldlinux.sys using this command line:

Code: Select all

\boot\syslinux\syslinux.exe -maf -d \boot\syslinux %DISK%:

Maybe this file is needed inside this path in vista/7 ?¿?¿
I have no idea about syslinux, but it seems that the -d modifyer is needed to set the folder where this ldlinux.sys file is created

Take a look at this bug report from other distro as an example where a bad syntaxis of -d modifyer, the root is used to create the file
https://fedorahosted.org/liveusb-creator/ticket/167

[jemimah]

Well, the new Syslinux version has a lot of improvements - I will research the problem for the next version of Puppeee.

[lemmy999]

I'm seeing Puppeee not finding the eeesave file file so I have to set it up on every boot. I have tried using different partitions but nothing helps.

[sandungas]

The alternative for SYSLINUX is GRUB4DOS, i was looking a bit about it because maybe is more compatible for the bootloader chainloading, but im too newbie with both
With compatibility i mean that seems more easy to chainload grub--->grub4dos because one is based on the other

Im chainloading grub (legacy)---> syslinux
Grub is able to pass the modifyers to syslinux without problem (i.e. ramboot=1)

I have puppeee installed frugal in a subfolder of an SD card
And booting puppeee from grub ("puppeee ramboot" is my default option in grub)
I have another line in grub for a "puppeee normal boot" (i use this when i need to change something)
When i turn on the eeepc, what boots is puppeee ramboot, i do not need to press the ESC key to enter in syslinux
But still i have the option to press ESC and enter in syslinux to use the configured boot modes (savefile repair ones are always usefull).. or i can boot a "clean" puppeee for repair purposes

As i have puppeee in a subfolder inside the SD card... i had to modify syslinux.cfg to point to this subfolder

For this kind of boot psubdir=XXX is needed (if im not wrong... i did a lot of tests and did not work without it, but i will test again)

----------------------

Im having some problems when loading .sfs files ---> http://www.murga-linux.com/puppy/viewto ... 452#440452
It seems that are loaded from root of the device

I have an internal 250GB HDD with XP, debian, swap & a 200GB fat partition
And i was testing hibernation to this "shared" swap (shared between debian & puppeee) and it works O.K. and i can return from hibernation in around... 15 seconds (my grub has a delay of 5 seconds)
Now im thinking in making a dedicated swap only for puppeee hibernation (not shared & hidden for the other operative systems)
The further experiment is to make a swap partition in the SD card an "hibernate to SD" (work in progress and under discussion)
This idea is the only solution to completly disable the internal HDD and keep hibernation working

And i have some doubts if the "dual" boot alternative between ramboot & normal & return from hibernation can cause a distorsion in space-time and generate a black hole
When booting in ramboot i see the message "updating layered filesystem" but... the filesystem was updated before when i booted "normal" (i boot normal i.e. for adding a new .sfs in bootmanager... then i turn off saving session)
I dont understand this error yet, and im not sure what fails, but sometimes i see .sfs not detected... or sometimes i see this message persistent in all boots

--------------------------------------------------

All this wall of text is more a concept idea of how we can boot puppeee than a question... im not sure wich is the best way to boot it, im just experimenting but there are a lot of options availables
I will paste my syslinux.cfg & my menu.lst with an explain of all modifyers used later on
Im still having some problems, but this freedom is great

Sorry for the wall of text maybe offtopic, but i think that the amount of possiblityes to boot puppeee deserves a talk, there are some clarifying old messages in this thread talking about hibernation, chainloading, fast boots/shutdowns etc... and all this needs to be resumed

[sandungas]

For this kind of boot psubdir=XXX is needed (if im not wrong... i did a lot of tests and did not work without it, but i will test again)

More tests...

Well... it seems that only is needed for booting puppeee in ramboot from a subfolder (both grub & syslinux fails to boot without it)

As a example... this grub config does not work

Code: Select all

root (hd1,0)
kernel /PuppEee/vmlinuz ramboot=1
initrd /PuppEee/initrd.gz

It generates this error (same in grub & syslinux) in the boot messages, when loading .sfs

loading personal file
Copying files to ram xxxxx.sfs...
The superblock could not be read or does not desbribe a correct ext2 filesystem...
loading eee-504 ---------------------done
setting up the layered filesystem ----done
performing a switch_root.... kernel panic


this is fixed by using psubdir=XXXXX
As another example... it needs to be this way in grub

Code: Select all

root (hd1,0)
kernel /PuppEee/vmlinuz psubdir=PuppEee ramboot=1
initrd /PuppEee/initrd.gz

This is the only way i found to boot in ramboot from a subfolder


----------------

Edit... well maybe this happens only with frugal installs ? or is related with removable media ? i have no idea

[sandungas]

I'm seeing Puppeee not finding the eeesave file file so I have to set it up on every boot. I have tried using different partitions but nothing helps.

Did you tryed this ?
pdev=/dev/sda5
Or this
pdev1=sda5