Page 1 of 5

Puppy 2.16 install problem(s)

Posted: Wed 16 May 2007, 00:04
by bobn9lvu
I installed Puppy both ways, Full HD, and Frugal install...

With a frugal install, the Grub menu.lst has the wrong boot parameters to boot into ram.

I had to rewrite the menu.
From;
title Puppy Linux 2.16 (on /dev/hdc1)
root (hd0,0)
kernel /vmlinuz root=/dev/hdc1 ro vga=normal

NOTE, I changed the vmlinuz path from the original which was ( /boot/vmlinuz)
and incorrect, as file does not exist. It is at ( /boot/puppy216/vmlinuz),
TO (/vmlinuz) as there was a copy here as well,
and I deleted the /boot/puppy216/vmlinuz file + residing dir..

I then rewrote the entry;

title Puppy Linux 2.16 (on /dev/hdc1)
root (hd0,0)
kernel /vmlinuz root=/dev/ram0 loglevel=3 PMEDIA=idehd ro vga=normal
initrd /initrd.gz

and made sure there was a copy of the initrd file in the root dir of hdc1


Guess what, IT WORKS!!! BUT I still cannot get OO to display,
even though it is in the correct dir (/mnt/home) and I used the util,
rebooted, and ran fixmenus from consol...

With FULL install I cannot get the Nvidia display to work under xorg unless,
I test the mode, then select generic driver...
The sound and ethernet must be manually forced to configure,
even though under live cd boot ALL is found automagically... :shock:

Also the sfs installer unpacks all the files to the root dir " not good " :shock:




Bob

Re: Puppy 2.16 install problem(s)

Posted: Wed 16 May 2007, 00:38
by WhoDo
bobn9lvu wrote:Also the sfs installer unpacks all the files to the root dir " not good " :shock:
I have had this problem with the sfs installer before, too. I don't know why it does that occasionally, but that is why you can't run Open Office. It sounds like the installer for the FULL install to hard drive has tried to run on your Frugal install or something.

With a Frugal install you shouldn't need to run any installer - just reboot, run fixmenus and refresh your window manager.

Hope that helps

Posted: Wed 16 May 2007, 00:39
by Kal
Thanks, Bob

Works for me on boot up.

Good Luck, Kal

Posted: Wed 16 May 2007, 01:17
by BarryK
Guess what, IT WORKS!!! BUT I still cannot get OO to display,
even though it is in the correct dir (/mnt/home) and I used the util,
rebooted, and ran fixmenus from consol...
You do not need to run fixmenus in 2.16.
When you ran the SFS Boot Manager, did you untick the checkbox, the one that says it will ignore your choices if left ticked?

Note, I have only tested my OO SFS on ibiblio, I cannot say anything about any other OO SFS file.

Posted: Wed 16 May 2007, 01:26
by bobn9lvu
Ok, I did select OO, and unchecked the box (for 2.16 sfs only), rebooted, and nothing shows up.....
Will RE dl from your site, and re-try...

Bob

BTW do you know why the hardware recognition problems that are happening on a full hd install,
but does work, and finds all hardware on a frugal install, and cd live boot???

UPDATE::::
I could ONLY get the OO icons to display on the menus after I manually
ran an OO application, and went through the pre-setup/registration in OO.
Now all icons are SHOWING in the menus... :roll: Go Figure :!: :!:

Posted: Wed 16 May 2007, 01:42
by Newcrest
I am unable to boot 216 as well. I am running a frugal install on an external usb HDD.
It says searching for Puppy and goes through all available disk partitions including the correct one. It then says it cannot find Puppy on "usbhd" boot media and PDEV1=

I tried specifying PDEV1=SDB1 but did not help. Also I have found that PDEV1 does not seem to work in 215CE either. Even though I have it specified, it still gets ignored and a search of HD partitions takes place. However, 215 continues on and boots.

Thanks.

Posted: Wed 16 May 2007, 03:17
by BarryK
Newcrest wrote:I am unable to boot 216 as well. I am running a frugal install on an external usb HDD.
It says searching for Puppy and goes through all available disk partitions including the correct one. It then says it cannot find Puppy on "usbhd" boot media and PDEV1=

I tried specifying PDEV1=SDB1 but did not help. Also I have found that PDEV1 does not seem to work in 215CE either. Even though I have it specified, it still gets ignored and a search of HD partitions takes place. However, 215 continues on and boots.

Thanks.
Do not put 'sdb1' in capitals.

Posted: Wed 16 May 2007, 03:31
by Newcrest
BarryK wrote:
Newcrest wrote:I am unable to boot 216 as well. I am running a frugal install on an external usb HDD.
It says searching for Puppy and goes through all available disk partitions including the correct one. It then says it cannot find Puppy on "usbhd" boot media and PDEV1=

I tried specifying PDEV1=SDB1 but did not help. Also I have found that PDEV1 does not seem to work in 215CE either. Even though I have it specified, it still gets ignored and a search of HD partitions takes place. However, 215 continues on and boots.

Thanks.
Do not put 'sdb1' in capitals.
Sorry, I only used capitals in the forum post. I have it correct in the boot parameters: PDEV1=sdb1

Any advice as to why 216 does not boot?
ERROR: cannot find Puppy on 'usbhd' boot media.
PUPMODE=1 PDEV1=

Puppy 214 and 215ce boot ok with the same parameters.
Are there any parameters that need to be changed for 216? I tried looking but could not find any mention to use something different.

Posted: Wed 16 May 2007, 06:05
by BarryK
For frugal and full internal hd install fix, see this post:
http://www.murga-linux.com/puppy/viewto ... 711#116711

manual frugal install 216 fails

Posted: Thu 17 May 2007, 16:22
by stroom
Newcrest wrote: "I am unable to boot 216 as well. I am running a frugal install on an external usb HDD.
It says searching for Puppy and goes through all available disk partitions including the correct one. It then says it cannot find Puppy on "usbhd" boot media and PDEV1= "

I have exactly same problem as newcrest with manual frugal install.
puppy214 works fine, puppy216 doesn't with similar grub entries:

title Puppy Linux 2.16 (frugal on /dev/hda4)
root (hd0,3)
kernel /puppy216/vmlinuz root=/dev/ram0 PMEDIA=idehd ro vga=normal
initrd /puppy216/initrd.gz

title Puppy Linux 2.14 (frugal on /dev/hda4)
root (hd0,3)
kernel /puppy214/vmlinuz root=/dev/ram0 PMEDIA=idehd ro vga=normal
initrd /puppy214/initrd.gz

sfs files are in /
vmlinuz and initrd.gz in the respective /puppy21x directories

Since I have installed ubuntu on the same partition I cannot put the vmlinuz in /

Any idea to solve this?

Posted: Thu 17 May 2007, 16:38
by HairyWill
try the kernel parameter

Code: Select all

psubdir=/puppy216
as described here
http://murga-linux.com/puppy/viewtopic. ... 560#115560

Posted: Thu 17 May 2007, 20:24
by stroom
HairyWill wrote:try the kernel parameter

Code: Select all

psubdir=/puppy216
as described here
http://murga-linux.com/puppy/viewtopic. ... 560#115560
That did the trick, thanks.
I had read the post but since the files in the subdirectory (kernel and initrd) were found and running, and it appeared that it could not find the pup_216.sfs file which is in the /, I did not expect this to be the problem
Anyway, this was not needed in puppy214. Is this a feature or a bug?

Posted: Thu 17 May 2007, 21:20
by veronicathecow
Hi, I've installed 2.16 (Final) via a hand built frugal (the installer failed to give a correct grub entry) I renamed the 2.15 sfs for OO and others (pgs and also web) but no joy in getting any .sfs extra goodies to load even though the I choose them from the sfs installer (It only showed up on the second reboot) (I unticked the load all box)
Cheers
Tony

Posted: Thu 17 May 2007, 21:38
by veronicathecow
Hi also I have timed Puppy boot at 1m 2secs (PClinux takes 1m 5sec)
Of that it takes 15 seconds for post on my machine. From Checking version update to the end of Rclocal takes 22 seconds. If backgrounding can be sorted for those items then the actual booting of Puppy would drop from 47 seconds to 25!.
Must get back to work!

P.S. Puppy frugal still loads apps so much faster (Approx twice speed of Pclinux)
Cheers
Tony

Posted: Thu 17 May 2007, 21:52
by bobn9lvu
Run any OO ap manually, and fill out the registration pre-install ect., exit the program, and reboot windows manager, your menu items will be there...

Bob

Posted: Fri 18 May 2007, 07:06
by veronicathecow
Hi bobn9lvu, thanks for info but how do I open openoffice if I am using a frugal install where files are tucked away in a .sfs file (It's a pain not being able to search for three letter words in the forum)
cheers
Tony

Posted: Fri 18 May 2007, 16:22
by pupshock
Unable to install Puppy2.16 to internal HD on both my computers.
Gone back to 2.14 on my laptop and 2.15 on my desktop.
The liveCD boots a wonderful 2.16 on both computers with pfix=ram.

Desktop:
vmlinuz, initrd.gz, pup_216.sfs, zdrv_216.sfs, pup_save.2fs copied
to the root of hda6, 2.15 files deleted.

Desktop dual-boots using Grub4DOS, the Puppy part of menu.lst is:
title Puppy Linux 2.16
rootnoverify (hd0,5)
kernel (hd0,5)/vmlinuz PMEDIA=idehd root=/dev/ram0 psubdir=(hd0,5)
initrd (hd0,5)/initrd.gz
boot

I get
ERROR: cannot find Puppy on idehd boot media
PUPMODE=9 PDEV1=
Moving the files to the root of hda1 and replacing
(hd0,5) with (hd0,0) gives the same error.
Removing PMEDIA and/or psubdir switches give the same error.
Deleting pup_save.sfs gives kernel panic.

Laptop:
the universal installer cannot see hda1, which is a ext3 boot partition
containing Puppy2.14 where i want to put 2.16.
It does see hda3 which contains DSL : )

Any ideas?

Posted: Fri 18 May 2007, 16:33
by HairyWill
<edit=this section not applicable to pupshock>
2.16 only looks for the kernel in / or /boot, if you have it anywhere else then you have to include the kernel parameter psubdir=xxxxxxxx, in your case

Code: Select all

psubdir=/boot/puppy
http://murga-linux.com/puppy/viewtopic. ... 560#115560
http://puppylinux.org/wikka/BootParms
It is in Barry's blog somewhere
</edit>

Pupshock,
You don't need psubdir if vmlinuz and initrd.gz are in the root of the partition

Posted: Fri 18 May 2007, 18:07
by Dougal
pupshock wrote:ERROR: cannot find Puppy on idehd boot media
PUPMODE=9 PDEV1=
Moving the files to the root of hda1 and replacing
(hd0,5) with (hd0,0) gives the same error.
PUPMODE 9 means it found your pup_save but not pup_216.sfs.

In 2.16 Barry added the "psubdir" parameter, which tells it where to look for initrd and pup_216.sfs.
psubdir defaults to "boot", so you need the sfs and initrd to be in the directory /boot on that partition (as opposed to the past, when you had the sfs on the root of the partition).

Your problem is that psubdir was (for some strange reason) set to (hd0,5)...

Posted: Sat 19 May 2007, 01:40
by BarryK
psubdir=(hd0,5)
That's wrong. hd0,5 is GRUB notation. Just remove the psubdir parameter.