Hi,
I am having trouble using Puppy 2.16 as a "somewhat frugal install" following instructions to double-boot with Win2k using http://www.icpug.org.uk/national/linnwi ... innwin.htm
However, before doing the above, I had already started using Puppy 2.16 as a LiveCD, and upon first exit had it create the puppy_save.2fs file in hda2 partition.
Incidentally, at that time, Puppy was only able to recognize the one idehd - hda connected directly to my mobo ( see my post http://www.murga-linux.com/puppy/viewtopic.php?t=19465 ). This has since been fixed "magically" whereby now it can see additional drives.
So my boot partition ( where I have Windows ntldr etc) is hde1, and I followed the instructions in the link above creating a grldr, menu.lst etc.
My menu.lst entry looks like:
title Puppy Linux 2.16
kernel (hd0,0)/boot/puppy.216/vmlinuz root=/dev/ram0 PMEDIA=idehd
initrd (hd0,0)/boot/puppy.216/initrd.gz
boot
When I go through grub, it does find both the above fine, and at the place where it Looks for Puppy_216.sfs file, it ONLY says:
Looking for Puppy in hda1...hda2...hda3...
It then finds the puppy_save.2fs in hda2 and gives an error:
Unable to find Puppy in idehd boot media
PUPSTATE=9 PDEV1=
If I go back and put the LiveCD in, it boots up fine.
I tried looking through documentation( as well as code) for sbin/init and when I run test-eide, it shows me all the drives.
What is causing Puppy to only look in hda1...hda2, and hda3?
Separately, I also tried the humongous initrd.gz ( with the correct ramdisk_size parameter of 93952) as a way to not have to look for the sfs files elsewhere, but get the error:
Error 30: selected item cannot fit in memory
How to set up frugal install to look for puppy_216.sfs file?
My 5 cents
Try to look here:
http://www.murga-linux.com/puppy/viewtopic.php?t=19215
This is where I described how I solved the problem. The only big difference I see in your configuration is that you put the Puppy files in a subfolder, while I put them in the root folder. But this should be an issue only with WinXP_SP2, as far as I know.
Putting them in the root folder anything worked, both for drive C: and D:. The only difference i noticed is that when the pup_save file is in the same drive as Puppy then it is automatically loaded, while if it is on the other drive Puppy asks if I want to use it.
SFS files where correctly loaded in both cases, keeping them (as the pup_save file) on drive D:. The only issue I encountered is that I had to rename them, because the boot loader (after removing the flag forcing to load only _216 files) discarded them not only when they had a name terminating in _xxx (with xxx different from 216 in my case), but also with something named 2.2.0 (es. openoffice-2.2.0.sfs): i simply renamed what I wanted to load (es. web_215.sfs could not be loaded without this trick) and everything worked automatically.
Just fo r a try, put all the files in the root folder.
Hope this helps a bit.
http://www.murga-linux.com/puppy/viewtopic.php?t=19215
This is where I described how I solved the problem. The only big difference I see in your configuration is that you put the Puppy files in a subfolder, while I put them in the root folder. But this should be an issue only with WinXP_SP2, as far as I know.
Putting them in the root folder anything worked, both for drive C: and D:. The only difference i noticed is that when the pup_save file is in the same drive as Puppy then it is automatically loaded, while if it is on the other drive Puppy asks if I want to use it.
SFS files where correctly loaded in both cases, keeping them (as the pup_save file) on drive D:. The only issue I encountered is that I had to rename them, because the boot loader (after removing the flag forcing to load only _216 files) discarded them not only when they had a name terminating in _xxx (with xxx different from 216 in my case), but also with something named 2.2.0 (es. openoffice-2.2.0.sfs): i simply renamed what I wanted to load (es. web_215.sfs could not be loaded without this trick) and everything worked automatically.
Just fo r a try, put all the files in the root folder.
Hope this helps a bit.
[i]campamax[/i]
you need to specify kernel parameter psubdir
http://www.murga-linux.com/puppy/viewto ... 794#123990
http://puppylinux.org/wikka/BootParms
http://www.murga-linux.com/puppy/viewto ... 794#123990
http://puppylinux.org/wikka/BootParms
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
>you need to specify kernel parameter psubdir
yeah, I did that as well.. It didnt make a difference ( anyways I thought the parameter applied to the kernel and not to sfs files)
campamax, I did look at your posts, but wasnt clear from your posting which one was your boot drive ( c: or d:).
In my case the pup_save.2fs file is not on a boot drive and instead on a drive connected to the mobo whereas the boot drive is connected to an Promise IDE PCI controller ( which is where the zdrv_.sfs file is).
2 questions:
a) Is it the case that the driver for the IDE controller is in the zdrv_sfs and so its a chicken and egg problem...that the file is on a drive which needs a driver? ( I dont think so, because doing test-eide does show the drives)
b) Can I simply move pup_save.2fs myself to a different place? Wont that mess up something else?
yeah, I did that as well.. It didnt make a difference ( anyways I thought the parameter applied to the kernel and not to sfs files)
campamax, I did look at your posts, but wasnt clear from your posting which one was your boot drive ( c: or d:).
In my case the pup_save.2fs file is not on a boot drive and instead on a drive connected to the mobo whereas the boot drive is connected to an Promise IDE PCI controller ( which is where the zdrv_.sfs file is).
2 questions:
a) Is it the case that the driver for the IDE controller is in the zdrv_sfs and so its a chicken and egg problem...that the file is on a drive which needs a driver? ( I dont think so, because doing test-eide does show the drives)
b) Can I simply move pup_save.2fs myself to a different place? Wont that mess up something else?
you need to have
pup_216.sfs
zdrv_216.sfs
pup_save.2fs
in the top level directory of the same partition
initrd.gz and vmlinuz should be in the same partition
either in the top level or in /boot
or somewhere else in that partition which is identified by psubdir
pup_216.sfs
zdrv_216.sfs
pup_save.2fs
in the top level directory of the same partition
initrd.gz and vmlinuz should be in the same partition
either in the top level or in /boot
or somewhere else in that partition which is identified by psubdir
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
campamax, I re-read your posts and see you pointed out that Windows is on the C:\. Sorry for saying earlier it wasnt clear to me. I was actually referring to the post. I think I got confused by http://www.murga-linux.com/puppy/viewto ... 317#124317 where it wasnt clear which was the boot partition ( I think its c:)
However, what you say below :
"Note that my Puppy starts from C:, but my PUP_SAVE file is safely on D:, and it works because Puppy looks for it in every accessible drive."
isnt whats working for me. My pup_save file is on a different drive than the pup files. The initrd, vmlinuz and pup_save file is found but not sfs files
HairyWill,
thanks for your reply. Given they are now on different partitions, can pup_save.2fs just be moved to the same partition where the rest are?
However, what you say below :
"Note that my Puppy starts from C:, but my PUP_SAVE file is safely on D:, and it works because Puppy looks for it in every accessible drive."
isnt whats working for me. My pup_save file is on a different drive than the pup files. The initrd, vmlinuz and pup_save file is found but not sfs files
HairyWill,
thanks for your reply. Given they are now on different partitions, can pup_save.2fs just be moved to the same partition where the rest are?
Will, looking at another post of yours on a somewhat similar topic http://www.murga-linux.com/puppy/viewto ... 501#126501 , you say:
But the simplest solution is probably to change the way that your drives are plugged in so that the boot drive is listed in the BIOS as the primary master
Is that what could be happening to me? As I said the boot drive isnt connected to the mobo. It is connected to a separate Promise IDE PCI controller.
But the simplest solution is probably to change the way that your drives are plugged in so that the boot drive is listed in the BIOS as the primary master
Is that what could be happening to me? As I said the boot drive isnt connected to the mobo. It is connected to a separate Promise IDE PCI controller.
yuprajeshh wrote:thanks for your reply. Given they are now on different partitions, can pup_save.2fs just be moved to the same partition where the rest are?
If you haven't got any other working operating system you could boot from CD with pfix=ram and then do the move.
There is no reason to suspect a hardware configuration problem until you have tried booting with all the files in the correct places.
Last edited by HairyWill on Sat 07 Jul 2007, 09:02, edited 1 time in total.
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
As I suspected...
So copying the pup_save.2fs to the same partition as the other files didnt help...
I then reconnected the boot drive to the mobo instead of the PCI controller card, and as expected, it was able to find the pup_216.sfs files etc...
So the issue is definitely that of booting from a drive not connected to the mobo..
Anyone else see an issue like this?
I then reconnected the boot drive to the mobo instead of the PCI controller card, and as expected, it was able to find the pup_216.sfs files etc...
So the issue is definitely that of booting from a drive not connected to the mobo..
Anyone else see an issue like this?
I have no experience with a pci ide controllers but after two minutes reading have a couple of other areas for investigation.So the issue is definitely that of booting from a drive not connected to the mobo..
Anyone else see an issue like this?
Does the BIOS have any settings to enable booting from the pci device?
Are there any switches or jumpers on the controller to determine whether it is bootable?
Do you understand grub drive naming conventions to specify the boot drive properly in menu.lst?
(hd0,0) 1st drive, 1st partition
(hd0,1) 1st drive, 2nd partition
(hd1,0) 2nd drive, 2nd partition
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
>Does the BIOS have any settings to enable booting from the pci device?
>Are there any switches or jumpers on the controller to determine whether it is
bootable?
the BIOS just has an order of which drives to look for as the boot drive, and it does show me drves connected to the PCI controller....I also have Win2k installed, and able to boot that fine ( though something has happened, maybe unrelated, that it bluescreens now with Stop 7f even though I can login safe mode fine)...
as far as grub conventions, as I said the kernel is found fine...its the sfs files alone ( and as far as I know the grub doesnt have anything specific for specifying where the sfs files are)
>Are there any switches or jumpers on the controller to determine whether it is
bootable?
the BIOS just has an order of which drives to look for as the boot drive, and it does show me drves connected to the PCI controller....I also have Win2k installed, and able to boot that fine ( though something has happened, maybe unrelated, that it bluescreens now with Stop 7f even though I can login safe mode fine)...
as far as grub conventions, as I said the kernel is found fine...its the sfs files alone ( and as far as I know the grub doesnt have anything specific for specifying where the sfs files are)
No bother.rajeshh wrote:campamax, I re-read your posts and see you pointed out that Windows is on the C:\. Sorry for saying earlier it wasnt clear to me.
Well, this actually was my first and only experience, so I sincerely do not know how to help you then. Sorry.rajeshh wrote:However, what you say below :
"Note that my Puppy starts from C:, but my PUP_SAVE file is safely on D:, and it works because Puppy looks for it in every accessible drive."
isnt whats working for me. My pup_save file is on a different drive than the pup files. The initrd, vmlinuz and pup_save file is found but not sfs files
[i]campamax[/i]
Rajeshh,
It very much looks like your problem is hardware related and as I am not a hardware expert I am not going to help much. However, I can lend some pointers to get more info.
You might try running with the parameter pfix=debug added to the kernel line. This will give all messages as the bootup process continues, which may give some clues.
I have been looking at the code. The script that runs on startup is located in /initrd/sbin/init once Puppy is loaded.
There are two things to mention. First, the value of PMEDIA has some bearing on where Puppy looks for the Puppy files.
The second is that the command probepart is used to determine which partitions to check for Puppy files. You will see it called up after the comment line in /initrd/sbin/init
#locate all partitions...
Now you say test-ide shows all your disks. I wonder if probepart shows the partitions on your drive connected to the PCI controller. If not, then that could be why the Puppy files are not found.
If this is the case it may be difficult to get round the problem. probepart was written by a Puppy community member. There are already some hacks in the init file to cope with the fact probepart cannot see zip drives. What hacks you would need is a bit of an unknown!
ICPUG
It very much looks like your problem is hardware related and as I am not a hardware expert I am not going to help much. However, I can lend some pointers to get more info.
You might try running with the parameter pfix=debug added to the kernel line. This will give all messages as the bootup process continues, which may give some clues.
I have been looking at the code. The script that runs on startup is located in /initrd/sbin/init once Puppy is loaded.
There are two things to mention. First, the value of PMEDIA has some bearing on where Puppy looks for the Puppy files.
The second is that the command probepart is used to determine which partitions to check for Puppy files. You will see it called up after the comment line in /initrd/sbin/init
#locate all partitions...
Now you say test-ide shows all your disks. I wonder if probepart shows the partitions on your drive connected to the PCI controller. If not, then that could be why the Puppy files are not found.
If this is the case it may be difficult to get round the problem. probepart was written by a Puppy community member. There are already some hacks in the init file to cope with the fact probepart cannot see zip drives. What hacks you would need is a bit of an unknown!
ICPUG
Thanks ICPUG for your tips... It has led me to a series of things that has taken me further..
So i started with your tip of doing probepart, and got the error libcfdisk: cannot open /dev/hde ( the same thing I had posted in the other topic linked in my first post for this topic).
When I googled that message, among other posts I found this one:
http://www.murga-linux.com/puppy/viewto ... 8279#58279
So I unzipped initrd.gz, and added new mknod's for my hde, hde1, hde2, hdf etc...and rebooted..
This time I at least got it to look in all these drives ( going by the message, Looking in hde1..hde2 etc), though it again gave me the same error saying Cannot find puppy in idehd boot media.
I did try the pfix=debug, and it displayed the value of some additional variables like PDEV1, but they were all mostly blank.
Any more suggestions? btw, my /mnt/home/dev_save is off /dev/hda2 ( when I boot off Live-CD)..not sure if that's relevant in any way.
So to summarize again: I have the pup_216.sfs and zdrv_216.sfs in /dev/hde1/ which is what is the boot partition.
TIA
So i started with your tip of doing probepart, and got the error libcfdisk: cannot open /dev/hde ( the same thing I had posted in the other topic linked in my first post for this topic).
When I googled that message, among other posts I found this one:
http://www.murga-linux.com/puppy/viewto ... 8279#58279
So I unzipped initrd.gz, and added new mknod's for my hde, hde1, hde2, hdf etc...and rebooted..
This time I at least got it to look in all these drives ( going by the message, Looking in hde1..hde2 etc), though it again gave me the same error saying Cannot find puppy in idehd boot media.
I did try the pfix=debug, and it displayed the value of some additional variables like PDEV1, but they were all mostly blank.
Any more suggestions? btw, my /mnt/home/dev_save is off /dev/hda2 ( when I boot off Live-CD)..not sure if that's relevant in any way.
So to summarize again: I have the pup_216.sfs and zdrv_216.sfs in /dev/hde1/ which is what is the boot partition.
TIA