dpup-482beta testing
Is this the thread I am supposed to post in?
I am testing dpup-494beta4-2.6.30.5.iso
and it lack the codecs for the mplayer.
I had them in other puppies but packet manager don't find them for this one. The mplayer plug in is lacking too.
Is this not the dpup I am supposed to use. Are there another one that has access to the usual 431codecs?
Hm I guess the D stand for Debian and them maybe are purist and dont' allow codecs that are proprietary? Is that the reason they lacks in rep?
I am testing dpup-494beta4-2.6.30.5.iso
and it lack the codecs for the mplayer.
I had them in other puppies but packet manager don't find them for this one. The mplayer plug in is lacking too.
Is this not the dpup I am supposed to use. Are there another one that has access to the usual 431codecs?
Hm I guess the D stand for Debian and them maybe are purist and dont' allow codecs that are proprietary? Is that the reason they lacks in rep?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Where did you get that one?nooby wrote:Is this the thread I am supposed to post in?
I am testing dpup-494beta4-2.6.30.5.iso
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Not sure. I had it on my usb pin too. I must have used the google search on puppy.
And there I wrote pup nop and a lot of answers and I read and read and then gave up and clicked on a link and installed first with unetbooin on an usb and then when I got upset of Stardust failing to mount usb then I searched for a puppy that could mount usb from internal hdd and this one could and also could do mplayer plug in
but sadly it has Opera instead of Firefox and it take up more of the RAM too.
Stardust let me have 1.5 to 1GB free mem wile NOP let me have only 485 to 190 free.
so what is taking up so much space?
And there I wrote pup nop and a lot of answers and I read and read and then gave up and clicked on a link and installed first with unetbooin on an usb and then when I got upset of Stardust failing to mount usb then I searched for a puppy that could mount usb from internal hdd and this one could and also could do mplayer plug in
but sadly it has Opera instead of Firefox and it take up more of the RAM too.
Stardust let me have 1.5 to 1GB free mem wile NOP let me have only 485 to 190 free.
so what is taking up so much space?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
[quote="nooby"
Stardust let me have 1.5 to 1GB free mem wile NOP let me have only 485 to 190 free.
so what is taking up so much space? [/quote]
hmmm have you tried 2.14X, it should give you about 2GB free ram.
ttuuxxx
Stardust let me have 1.5 to 1GB free mem wile NOP let me have only 485 to 190 free.
so what is taking up so much space? [/quote]
hmmm have you tried 2.14X, it should give you about 2GB free ram.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
I am not used to that numbers series did they not have four files while three and 4 has only three files. I don't remember how one make use of them in a subdirectoru. As I remember something of them need to be root and only one or two files can be a subdirectory. All my puppies are in a sub.
The 214x is that the one with latest kernel from 2009 instead of some kernel from 2008?
Is this the one you have newly taking out and modernized. You gave no link to the thread presenting it. I am very bad at searching.
why do you want me to test it. I want a 431 that works out of the box.
Stardust could not mount an ordinary usv flash mem so can not use that one.
edit
I guess you refer to this one then
http://www.murga-linux.com/puppy/viewtopic.php?t=42553
The 214x is that the one with latest kernel from 2009 instead of some kernel from 2008?
Is this the one you have newly taking out and modernized. You gave no link to the thread presenting it. I am very bad at searching.
why do you want me to test it. I want a 431 that works out of the box.
Stardust could not mount an ordinary usv flash mem so can not use that one.
edit
I guess you refer to this one then
http://www.murga-linux.com/puppy/viewtopic.php?t=42553
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
yes that one, see you found it no problemnooby wrote:I am not used to that numbers series did they not have four files while three and 4 has only three files. I don't remember how one make use of them in a subdirectoru. As I remember something of them need to be root and only one or two files can be a subdirectory. All my puppies are in a sub.
The 214x is that the one with latest kernel from 2009 instead of some kernel from 2008?
Is this the one you have newly taking out and modernized. You gave no link to the thread presenting it. I am very bad at searching.
why do you want me to test it. I want a 431 that works out of the box.
Stardust could not mount an ordinary usv flash mem so can not use that one.
edit
I guess you refer to this one then
http://www.murga-linux.com/puppy/viewtopic.php?t=42553
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
hi never tried grub4dos just burn it to a cdrw and test it live with
puppy pfix=ram
ttuuxxx
puppy pfix=ram
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
But what am I supposed to write in a menu.lst
even if you have not somebody else may have
and does the wmlinux and initrd need to be in root?
or can they me in a subdirectory. Do I have to do a pmedia something.
It tried to boot but got into kernel panic at Usage init.
I try this one
http://www.murga-linux.com/puppy/viewto ... 479#311479
even if you have not somebody else may have
and does the wmlinux and initrd need to be in root?
or can they me in a subdirectory. Do I have to do a pmedia something.
It tried to boot but got into kernel panic at Usage init.
I try this one
http://www.murga-linux.com/puppy/viewto ... 479#311479
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Maybe we should take this over to the 2.14X thread, we are kind of talking about things that aren't related to dpup and well I don't know how gposil feels about taking over his thread I started a link at http://www.murga-linux.com/puppy/viewto ... 034#394034nooby wrote:But what am I supposed to write in a menu.lst
even if you have not somebody else may have
and does the wmlinux and initrd need to be in root?
or can they me in a subdirectory. Do I have to do a pmedia something.
It tried to boot but got into kernel panic at Usage init.
I try this one
http://www.murga-linux.com/puppy/viewto ... 479#311479
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
That is more correct and polite yes.
I try some of the menu.lst examples and see what happen. Almsot two hours now. This one is not as easy as the pup431 series. I failed using it 2008 too.
the easiest menu.lst text worked right away. I guess I test the other one also just in case but write on the thread you linked to
I try some of the menu.lst examples and see what happen. Almsot two hours now. This one is not as easy as the pup431 series. I failed using it 2008 too.
the easiest menu.lst text worked right away. I guess I test the other one also just in case but write on the thread you linked to
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Hi, nooby.
Here's my entry for dpup 484 in grub's menu.lst. It's basically the same for grub4dos or other version.
hd0 is the first disk drive, /mnt/sda in linux lingo
4 is the 5th partition, /mntsda5 in linux lingo
to run any frugal installation of puppy properly from grub, you need:
to create a directory for the puppy, in this case: /dpup484
to launch the linux kernel properly you need to create a sub-directory like
/dpup484/lancement [lancement means launch in French, but the name of this subdirectory doesn't matter, you could call it bebop or rocknroll or salsa
in linux lingo, grub sees this :
1) the drive
2) the partition
3) /mnt/sda5/grunge/vmlinuz and launches it with your chosen parameters
4) /mnt/sda5/grunge/initrd.gz (the linux kernel ramdrive)
Now the ball is in the linux court, grub has finished its work.
So, the last two lines (3 and 4) find the dpup484.sfs file and launch it, and you're now entirely in puppyinux.
I hope I've thoroughly confused you!
Incidentally, concentrating on the use of grub to launch dpup makes it ok to talk about it in the dpup thread, no?
Here's my entry for dpup 484 in grub's menu.lst. It's basically the same for grub4dos or other version.
Code: Select all
title dpup-484
root (hd0,4)
kernel /dpup484/lancement/vmlinuz max_loop=14 pfix=fsck root=/dev/ram0 acpi=-on pfix=copy pmedia=idehd pdev=sda5 psubdir=dpup484 loglevel=3
initrd /dpup484/lancement/initrd.gz
boot
4 is the 5th partition, /mntsda5 in linux lingo
to run any frugal installation of puppy properly from grub, you need:
to create a directory for the puppy, in this case: /dpup484
to launch the linux kernel properly you need to create a sub-directory like
/dpup484/lancement [lancement means launch in French, but the name of this subdirectory doesn't matter, you could call it bebop or rocknroll or salsa
in linux lingo, grub sees this :
1) the drive
2) the partition
3) /mnt/sda5/grunge/vmlinuz and launches it with your chosen parameters
4) /mnt/sda5/grunge/initrd.gz (the linux kernel ramdrive)
Now the ball is in the linux court, grub has finished its work.
So, the last two lines (3 and 4) find the dpup484.sfs file and launch it, and you're now entirely in puppyinux.
I hope I've thoroughly confused you!
Incidentally, concentrating on the use of grub to launch dpup makes it ok to talk about it in the dpup thread, no?
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hi Christian,
oops maybe we derail the thread, strictly it is for reporting bugs and experiences of how it works?
your menu.lst is like this
Could you tell me more about this one: max_loop=14 pfix=fsck
Why does this one need to be on? acpi=-on is it not on by default?
And what does pfix=copy do?
What does loglevel=3 accomplish?
I guess your version boot faster than mine. Mine has to search a lot on its own. I got mine from two sources. Pendrivelinux and the source they got it from.
I just borrowed it. I don't understand it. I just looked around until I found something that worked on my gear.
thanks for sharing the menu.lst that is a good way to learn for me.
To understand why others do things a better way. So do tell me more. [/quote]
oops maybe we derail the thread, strictly it is for reporting bugs and experiences of how it works?
your menu.lst is like this
Mine is like thistitle dpup-484
root (hd0,4)
kernel /dpup484/lancement/vmlinuz max_loop=14 pfix=fsck root=/dev/ram0 acpi=-on pfix=copy pmedia=idehd pdev=sda5 psubdir=dpup484 loglevel=3
initrd /dpup484/lancement/initrd.gz
boot
title dpup-484beta4-2.6.30.5.iso
find --set-root /dpup/vmlinuz
kernel /dpup/vmlinuz psubdir=dpup
initrd /dpup/initrd.gz
boot
Could you tell me more about this one: max_loop=14 pfix=fsck
Why does this one need to be on? acpi=-on is it not on by default?
And what does pfix=copy do?
What does loglevel=3 accomplish?
I guess your version boot faster than mine. Mine has to search a lot on its own. I got mine from two sources. Pendrivelinux and the source they got it from.
I just borrowed it. I don't understand it. I just looked around until I found something that worked on my gear.
thanks for sharing the menu.lst that is a good way to learn for me.
To understand why others do things a better way. So do tell me more. [/quote]
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Hello, again, nooby.
Terribly sorry, my "kernel" line should have looked like this:
Thanks for pointing it out to me.
"pfix=fsck" means to check / defragment the sfs file during the boot process.
"pfix=copy" means copy to ram and restore saves (not really necessary)
You can add the two in the form:
"max_loop=14" means to use as many as 14 loops (or additional sfs files) in the bootmanager. You can have a maximum of 28.
As you can see, I removed acpi=-on. The acpi parameter is for power saving, but this form is wrong. It should be acpi=off if you do not want to activate the power saving feature of your computer. I don't remember why I had put it there. If you don't put it in the boot-up parameters, the computer uses the default from the BIOS.
"loglevel=3" is the degree of information you want the boot process to give you back when it is in activity.
From http://puppylinux.com/download/release-2.11.htm:
For a more complete discussion of the boot parameters in puppy, please see here: http://puppylinux.org/wikka/BootParams
Terribly sorry, my "kernel" line should have looked like this:
Code: Select all
kernel /dpup484/lancement/vmlinuz max_loop=14 pfix=copy,fsck root=/dev/ram0 pmedia=idehd pdev=sda5 psubdir=dpup484 loglevel=3
"pfix=fsck" means to check / defragment the sfs file during the boot process.
"pfix=copy" means copy to ram and restore saves (not really necessary)
You can add the two in the form:
Code: Select all
pfix=copy,fsck
As you can see, I removed acpi=-on. The acpi parameter is for power saving, but this form is wrong. It should be acpi=off if you do not want to activate the power saving feature of your computer. I don't remember why I had put it there. If you don't put it in the boot-up parameters, the computer uses the default from the BIOS.
"loglevel=3" is the degree of information you want the boot process to give you back when it is in activity.
From http://puppylinux.com/download/release-2.11.htm:
I hope this is clearer.This tells the kernel to only report serious errors to the console... [a note from BK for an old version of Puppy]
For a more complete discussion of the boot parameters in puppy, please see here: http://puppylinux.org/wikka/BootParams
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Thanks, now I know more.
I must have donesomething wrong when I tested pulp it got into kernel panic and then this also made dpup to go into kernel panic but both NOP and stardust did survive. So not sure what I made wrong that the first two malfunctioned at same time.
I must have donesomething wrong when I tested pulp it got into kernel panic and then this also made dpup to go into kernel panic but both NOP and stardust did survive. So not sure what I made wrong that the first two malfunctioned at same time.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Hi, nooby.
"kernel panic" may refer to many things, mostly related to hardware compatibility, memory chips or quality of the copy of the files on the disc.
It can also mean that the kernel cannot find the proper next file to load. This file can be a file such as initrd or the puppy sfs or an internal driver the kernel thinks it needs for your hardware.
The fact that one kernel panic causes problems for two puppies makes me believe that your problem is on the disk -- either the disk itself needs checking or the files on it need checking. Probably the two files overlap somehow on the disk sectors.
I would suggest doing the general things as follows:
Boot into one of your working puppies -- or much better, boot this Puppy from its boot CD.
Make sure you have back-ups of all your important files, sfs, etc.
If not, make back-ups before you do the rest (below).
Go to the drive(s) where your sfs files are. For ex.,
cd /mnt/sda1 OR cd /mnt/home
Then, in console, use e2fsck
e2fsck --help
to get general idea of use
Check that all your copies of these files -- linux kernel files and puppy files -- are good. Again, defragment the files if necessary, but maybe making a fresh copy will be faster -- and you will be sure that the copies are good..
If you choose NOT to copy fresh copies of the files, use a command such as
e2fsck -p dpup[proper number].sfs
e2fsck -p dpupsave[your identifier here].2fs
When your files are repaired, check that they are in the proper place (top level of disk, or directory or sub-directory), where they are supposed to be. If not, MOVE them where they are supposed to be.
As to the internal drivers of the kernel, any Puppy kernel usually has a quite complete series of drivers built-in, so unless your hardware is "very-very" uncommon, you should be able to boot into the desktop fluidly.
Which is why I tend to say that the files that you mention have somehow been corrupted, perhaps by shutting down the computer manually in an emergency?
The other possibility would be that you have bad memory chips. This seldom happens, though. You would run a program named "memtest" to check that. There is also, usually, a way to get the BIOS to do this for you at boot.
But start with checking your files on disk with e2fsck first. This is more common.
A final thought: are you using the same savefile for all your puppies? This can be a big problem if the version of the puppies is not the same. I know for a fact that pulp puppy and dpup do not have the same "internals" and they are not of the same kernel version, so the savefile for one will most likely not be good for the other.
I hope this helps. Use care and caution. Remember the above may work or not work. Good luck.
"kernel panic" may refer to many things, mostly related to hardware compatibility, memory chips or quality of the copy of the files on the disc.
It can also mean that the kernel cannot find the proper next file to load. This file can be a file such as initrd or the puppy sfs or an internal driver the kernel thinks it needs for your hardware.
The fact that one kernel panic causes problems for two puppies makes me believe that your problem is on the disk -- either the disk itself needs checking or the files on it need checking. Probably the two files overlap somehow on the disk sectors.
I would suggest doing the general things as follows:
Boot into one of your working puppies -- or much better, boot this Puppy from its boot CD.
Make sure you have back-ups of all your important files, sfs, etc.
If not, make back-ups before you do the rest (below).
Go to the drive(s) where your sfs files are. For ex.,
cd /mnt/sda1 OR cd /mnt/home
Then, in console, use e2fsck
e2fsck --help
to get general idea of use
Check that all your copies of these files -- linux kernel files and puppy files -- are good. Again, defragment the files if necessary, but maybe making a fresh copy will be faster -- and you will be sure that the copies are good..
If you choose NOT to copy fresh copies of the files, use a command such as
e2fsck -p dpup[proper number].sfs
e2fsck -p dpupsave[your identifier here].2fs
When your files are repaired, check that they are in the proper place (top level of disk, or directory or sub-directory), where they are supposed to be. If not, MOVE them where they are supposed to be.
As to the internal drivers of the kernel, any Puppy kernel usually has a quite complete series of drivers built-in, so unless your hardware is "very-very" uncommon, you should be able to boot into the desktop fluidly.
Which is why I tend to say that the files that you mention have somehow been corrupted, perhaps by shutting down the computer manually in an emergency?
The other possibility would be that you have bad memory chips. This seldom happens, though. You would run a program named "memtest" to check that. There is also, usually, a way to get the BIOS to do this for you at boot.
But start with checking your files on disk with e2fsck first. This is more common.
A final thought: are you using the same savefile for all your puppies? This can be a big problem if the version of the puppies is not the same. I know for a fact that pulp puppy and dpup do not have the same "internals" and they are not of the same kernel version, so the savefile for one will most likely not be good for the other.
I hope this helps. Use care and caution. Remember the above may work or not work. Good luck.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
that one could be likely.Which is why I tend to say that the files that you mention have somehow been corrupted, perhaps by shutting down the computer manually in an emergency?
No I give them unique name all of them.
Something odd that I wonder about. I ahve some 4 or 5 puppies now that I have to decide on which one to use.
I am in NOP now and that one uses Opera while me had preferred FF3.6 or at least 3.5.7
Opera works but I am not used to it.
edit
Sorry me misunderstood the message. it says on front 47 meg free or 370 meg free. that is not the RAM memory that is the pupsavefile.
To get how much RAM one have one go into Terminal and write the word
free
and it says how much one have in total and how much free at the moment.
If one write
top
then it tells which process that takes most memory at the moment.
Last edited by nooby on Mon 22 Feb 2010, 14:48, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Hello, again, nooby.
Have you tried this, to reclaim memory ?
http://www.murga-linux.com/puppy/viewto ... h&id=16349
Also, do you use a large enough swap file, or better, a swap partition ?
I know of NOP, but I have never used it, so I cannot help you there.
dpup is rather modest in memory requirements, if I remember correctly.
I am writing this in a modified / upgraded "mywolfe 0.08" and I get this memory usage when I type "free" in console:
and my machine has only one third of the RAM that your machine has... But I have a combination of swap file / swap partition.
As for me I have always preferred opera, I find it faster and more agile than FF, and it uses less memory. I also find it less confusing than FF, But it is a personal choice, of course.
Memory can be calculated in different ways, with or without the buffers, etc. So maybe the memory indication you get is partial.
Also, memory is not the only thing. I'd say to use the Puppy you feel most comfortable with, that looks better in your eyes, or that does the most things you need / like to do?
BFN.
Have you tried this, to reclaim memory ?
http://www.murga-linux.com/puppy/viewto ... h&id=16349
Also, do you use a large enough swap file, or better, a swap partition ?
I know of NOP, but I have never used it, so I cannot help you there.
dpup is rather modest in memory requirements, if I remember correctly.
I am writing this in a modified / upgraded "mywolfe 0.08" and I get this memory usage when I type "free" in console:
Code: Select all
-=-=-=-=-=-
total used free shared buffers
Mem: 1034324 693532 340792 0 43020
Swap: 2574652 0 2574652
Total: 3608976 693532 2915444
-=-=-=-=-=-
As for me I have always preferred opera, I find it faster and more agile than FF, and it uses less memory. I also find it less confusing than FF, But it is a personal choice, of course.
Memory can be calculated in different ways, with or without the buffers, etc. So maybe the memory indication you get is partial.
Also, memory is not the only thing. I'd say to use the Puppy you feel most comfortable with, that looks better in your eyes, or that does the most things you need / like to do?
BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)