![Sad :(](./images/smilies/icon_sad.gif)
ASUS P5K
Samsung DVD Burner
4 gig of ram
This concerns Kernelmodules.Question. I have read that packages installed should be installed on the same kernel version that they were compiled with, for best compatibility.
Thanks for the link. I have a problem however. I have put a description of it to the above cited thread. Rgds ZGP152MU wrote:Muppybackup requires a patched initrd.gz, so it cannot be installed as a pet.
There is just a version with reduced functionality for other Puppys:
http://www.murga-linux.com/puppy/viewto ... 368#222368
But that can not backupp/restore at startup, just backup the running system.
Mark
No puppy 406 and now 410 didn't have that issue. I could boot the CD and do the Puppy Installer. Not at the same speed as the native installs, but still good performance. So now I know when extracting, the hda1 will have some 2GB. At this point it is I have 2.1GB and the last file is zmsy_84.sfsMU wrote:is Puppy also so slow?
Of course it takes a while to copy 2 gig of data.
And qemu is slow.
But that now looks really extreme.
I have not enough experience with qemu, but as it emulates a whole computer I would think, that there is a driver issue.
Nor K&Ubuntu and Suse 10.3 with their 700MB CD's extracted to some 2GB as well had this issue. I think it took less then an hour to do the respective full installs.MU wrote:Normal drives sometimes can be made faster using "hdparm".
That can set up DMA modes.
So maybe qemus drives cannot use DMA, and so run in a very slow defaultmode.
Mark
So I wanted to open a console to execute the grubconfig, but the system didn't move. (frozen or too slow), so I pulled the (virtual) plug.Béèm wrote:In order for the 'report' not being too big I copied the link here of what reported already.
As I left the PC running while I was asleep, I don't know when exactly the copy process stopped and if it did.
I have now 21h running and 2120MB copied and there seems not to be more movement. The last file being copied is the zmsy_084.sfs, so therefor I suppose the copying is done.
As the install script disappeared, I don't have further indications, but I think the only to do still is the grubconfig, which I can do by hand.
Also I see there are 374 processes of which one running. Normal?
After that, the big bang (boot)
I didn't understand there was some distinction there, between kernelmodules and some other kind of modules (loadable modules?). In fact I thought that modules were just the linux name for drivers. I guess I am far from understanding the jargon, or the implications here. I don't know what "3rd party drivers" means either. Where this came up was when I was trying to get scramdisk to work with Puppy 4.1, which I have failed at so far.This concerns Kernelmodules.
For example, you could not use wifi drivers (that use Kernelmodules) from Slackware.
Got finally the rc update and grubconfig and install is complete after 2:15MU wrote:.Béèm wrote:I see a cp process now. that should be the one to watch then
yes.
No joy to boot from the hda1 full install of the mini sys.Béèm wrote:Got finally the rc update and grubconfig and install is complete after 2:15MU wrote:.Béèm wrote:I see a cp process now. that should be the one to watch then
yes.
Success finaly.Béèm wrote:No joy to boot from the hda1 full install of the mini sys.Béèm wrote:Got finally the rc update and grubconfig and install is complete after 2:15MU wrote:.
yes.
Like yesterday for the live, after selecting to boot from hda1 in grub, I get a black screen.
Don't know how to diagnose.