Download Failure
Posted: Sat 24 Nov 2012, 22:07
Delete or ignore this message. Seems that its working now for some reason.
READ-ONLY Archive
https://oldforum.puppylinux.com/
I didn't use grub2 myself and never tested that. But rcrsn51 uses grub2 and it shouldn't be problem.spandey wrote:Yes Linux mint 13 is using Grub2.
1,2,3 is all right, 4 is odd because it should be looking at /Fatdog/fd64save.ext4.I looked at error message and there are bunch of them, like:
1. can't stat /lib
2. aufs/kernel-modules/lib missing
3. HDIO_SET_DMA failed
4. can't find savefile /fd64save.ext4 in partitions.....
That is very all right, I do this all the time tooFor frugal install I just copied the contents of the ISO, to /Fatdog directory. Hope that's alright ?
Nah, this means that the savefile name or path should not contain a space or a colon. The colon in the savefile parameter itself is all right.spandey wrote:Just going thru Fatdog help documents and found something interesting under boot options:
savefile parameter has colon!!!Note 1: parameters are case sensitive. Most of them are in lower case, so if you specify them in upper case (capital letters), it won't work. Also remember that all parameters cannot include space or colon.
smokey01, spandey's line is all right. He doesn't use "direct" but he uses "ram" which means he is using the RAM layer (in other puppies, this is called PUPMODE=13).smokey01 wrote:spandey you appear to have omitted the word "direct" eg:
Yes, fatdog sfs loader just mounts the sfs. It doesn't do anything extra. This is a design decision - different SFS serves different purposes and may have different activation mechanisms; and the sfs loader doesn't try to guess what they are. You will to manually do what is required - e.g. "depmod" for extra modules, or "modprobe", or start-up services, or refresh menus, etc. (openbox menus btw is automatically updated, lxpanel isn't).smokey01 wrote:When using the fatdog sfs loader it loads/mounts the sfs but VirtualBox or for that matter, wine, neither works. The reason being, some modules need to be loaded so a reboot or a modprobe of the modules is required.
Yes, because shino's sfs has the smarts.I then tried shino's SFS-load-on-the-Fly and it worked fine without a reboot as it obviously loads the required modules.
Yes because shino's loader was the default sfs loader for Fatdog 500, and even for early betas of 600.After I had installed shino's SFS-load-on-the-Fly I notice it had clobbered the fatdog sfs loader because the desktop entries have the same name although the file names are different. It's easy enough to rename one so they can co-exist.
Yes, it probably will. Early in 600 beta we have Shino's SFS loader in the ISO, and we run into some obscure problems. Turns out that it was the interaction between shino's loader with Fatdog's layering system; we were forced to take it out.1. Will using shino's SFS-load-on-the-Fly cause any problems with fatdog?
Not at the moment, but I will consider that. Where is this pinstall.sh located? Is this supported by Shino's SFS loader too? We have to consider the effect when multiple SFS-es have pinstall.sh-es; we have to ensure that when one SFS is loaded, only its own pinstall.sh will be executed and not pinstall.sh from previously loaded SFS; thus the pinstall.sh must also be written carefully. Unlike pets, where the pinstall.sh is executed only once and then deleted (thus one pet's pinstall.sh is unlikely to affect other pets), this isn't true with SFS where its pinstall.sh will live forever.2. Is it possible to use a pinstall.sh in the fatdog sfs loader to load the required modules?
Thanks. I usually download Vbox and install it from the official website myself, but I do appreciate this isn't always possible for others (especially live session users).I will place the VirtualBox-4.2.4-fd64_600.sfs here:
http://www.smokey01.com/software/Fatdog64-600/
Yeah that might work providing VB is called from the menu entry.01micko wrote:smokey01
You could put a wrapper script in the sfs called from the DOTdesktop file that checks if the modules are loaded, if not loads them then runs virtual box. Would overcome your problem I think.
No I don't. I was testing spandey's savefile argument in regular GRUB.jamesbond wrote: But rcrsn51 uses grub2 and it shouldn't be problem.
It does. I just tested it with your Virtualbox sfs. The SFS already have the right files in /etc/init.d; that will start the vbox services which will load the modules after your reboot.smokey01 wrote:jamesbond further investigation has revealed a reboot after loading the sfs with the fatdog loader does not fix the problem, even with a savefile.
Code: Select all
#!/bin/sh
! modinfo vboxdrv && depmod
! lsmod | grep -q vboxdrv && /etc/rc.d/rc.vboxdrv start
VirtualBox
Oops I thought you did test it with grub2. Sorryrcrsn51 wrote:No I don't. I was testing spandey's savefile argument in regular GRUB.
Code: Select all
cat /proc/cmdline
Your fix is a lot more elegant than mine. I took Mick's advice and made a wrapper which checks to see if each module had been loaded, if not it loads them. The script also starts with a depmod.jamesbond wrote:It does. I just tested it with your Virtualbox sfs. The SFS already have the right files in /etc/init.d; that will start the vbox services which will load the modules after your reboot.smokey01 wrote:jamesbond further investigation has revealed a reboot after loading the sfs with the fatdog loader does not fix the problem, even with a savefile.
The only missing thing is that you need to "depmod" after the SFS is loaded, and this needs to be done only once.
If you want to run this from a live session, you just need to "depmod" and then start the /etc/init.d/vboxdrv services ("/etc/init.d/vboxdrv start") or use the Service Manager. Like 01micko says, you can modify the VBox desktop button to point to your wrapper script to test for conditions launching the real VirtualBox, like this one:
should do the trick.Code: Select all
#!/bin/sh ! modinfo vboxdrv && depmod ! lsmod | grep -q vboxdrv && /etc/rc.d/rc.vboxdrv start VirtualBox
That's probably why they recommend that you not hand-edit the Grub2 config file.spandey wrote:There are some unprintable characters before word savefile. Hence entire savefile argument has become meaningless. Looks like they came up while copying and pasting Grub2 entries in the editor. A very good lesson for future !!!!
It's all there in http://puppylinux.org/wikka/Grub2. Anyway I am repeating it again.For the benefit of other Fatdog-Grub2 users, could you please post your 40-custom file along with some instructions on how you used it in Mint? Where do you put the file? What update command do you run? etc.
Code: Select all
menuentry "Lucid Puppy 5.2.8" {
search --no-floppy --fs-uuid --set=root 672878ac-c0ca-453b-bc38-0de03ec38f63
linux /Luppuold/vmlinuz pmedia=atahd psubdir=Luppuold pfix=fsck
initrd /Luppuold/initrd.gz
}
menuentry "Precise 5.4.1" {
search --no-floppy --fs-uuid --set=root 672878ac-c0ca-453b-bc38-0de03ec38f63
linux /Precise/vmlinuz pmedia=atahd psubdir=Precise pfix=fsck
initrd /Precise/initrd.gz
}
menuentry "Fatdog 600" {
search --no-floppy --fs-uuid --set=root 672878ac-c0ca-453b-bc38-0de03ec38f63
linux /Fatdog/vmlinuz savefile='ram:device:sda5:/Fatdog/fd64save.ext4'
initrd /Fatdog/initrd
}
Code: Select all
#!/bin/sh
cat <<EOF
if [ -f \$prefix/custom.cfg ]; then
source \$prefix/custom.cfg;
fi
EOF
Code: Select all
menuentry "Fatdog64 610" {
insmod part_msdos
insmod ext2
set root='(dev/sda,msdos2)'
search --no-floppy --fs-uuid --set=root 6fbee58b-cd48-4819-8d2b-ed06d7f00eea
linux /fatdog610/vmlinuz root=UUID=6fbee58b-cd48-4819-8d2b-ed06d7f00eea savefile=direct:device:sda2:/fatdog610/fd64save.ext4
initrd /fatdog610/initrd
}
Code: Select all
menuentry "Fatdog64 600 No Save" {
insmod part_msdos
insmod ext2
set root='(dev/sda,msdos2)'
search --no-floppy --fs-uuid --set=root 6fbee58b-cd48-4819-8d2b-ed06d7f00eea
linux /fatdog600/vmlinuz root=UUID=6fbee58b-cd48-4819-8d2b-ed06d7f00eea savefile=none
initrd /fatdog600/initrd
}
Code: Select all
blkid
Code: Select all
sudo update-grub
Code: Select all
lspci > /root/lspci.txt
dmesg > /root/dmesg.txt
Thank you, bug confirmed, I will look at it.gcmartin wrote:Xdesktop is then exited and text terminal (console) continues with message that a fatdog ...sfs is being created. Immediately the system progresses with another message, then and within 15 seconds, the PC powers down without every saving of anything to the Live media.
Procedure is correct.Could someone confirm the procedure