Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 29 Aug 2014, 08:08
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Puppy 2.16 install problem(s)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
veronicathecow


Joined: 21 Oct 2006
Posts: 533

PostPosted: Fri 18 May 2007, 03:06    Post subject:  

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
Back to top
View user's profile Send private message 
pupshock

Joined: 23 Mar 2007
Posts: 140

PostPosted: Fri 18 May 2007, 12:22    Post subject:  

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?
Back to top
View user's profile Send private message 
HairyWill


Joined: 26 May 2006
Posts: 2949
Location: Southampton, UK

PostPosted: Fri 18 May 2007, 12:33    Post subject:  

<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:
psubdir=/boot/puppy

http://murga-linux.com/puppy/viewtopic.php?p=115560#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

_________________
Will
contribute: community website, screenshots, puplets, wiki, rss
Back to top
View user's profile Send private message 
Dougal


Joined: 19 Oct 2005
Posts: 2505
Location: Hell more grotesque than any medieval woodcut

PostPosted: Fri 18 May 2007, 14:07    Post subject:  

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)...

_________________
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Fri 18 May 2007, 21:40    Post subject:  

Quote:
psubdir=(hd0,5)

That's wrong. hd0,5 is GRUB notation. Just remove the psubdir parameter.
Back to top
View user's profile Send private message Visit poster's website 
pupshock

Joined: 23 Mar 2007
Posts: 140

PostPosted: Fri 18 May 2007, 22:12    Post subject:  

Thanks for replies.

HairyWill, _without_ the psubdir switch, pup_216.sfs was not found on
(hd0,5) root. Moving all the files to (hd0,0) root and editing menu.lst
to (hd0,0) made no difference.
I moved the files back to (hd0,5) root and wrote psubdir=(hd0,5) to
point the kernel specifically to the root of (hd0,5). I agree it is strange,
but i ran out of ideas. It didnt work either.

Dougal, If it defaults to /boot and not root (there is conflicting
advice here), I'll create /boot, move initrd.gz and pup_216.sfs there,
change menu.lst to:
initrd (hd0,5)/boot/initrd.gz, and
let y'all know what happens without and with psubdir=(hd0,5)/boot
on the kernel line.

I'll be most grateful if anyone can give me a md5sum of
pup_216.sfs, and how to interpret PUPMODE (the wiki is not clear, tho
it may be too much cheap red wine on my part)
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Sat 19 May 2007, 03:16    Post subject:  

Quote:
psubdir=(hd0,5)

Do not do this, it will stuff up booting!!!!!
Puppy reads this parameter, not GRUB!!!!
Puppy expects it to be a path, like 'psubdir=boot/puppy216
however, if you put everything at '/' or '/boot' then psubdir is NOT REQUIRED.

Recommend, put vmlinuz, initrd.gz, pup_216.sfs, zdrv_216.sfs at '/' on hda6 and leave off the psubdir, it should work. This should do it:

rootnoverify (hd0,5)
kernel (hd0,5)/vmlinuz pmedia=idehd root=/dev/ram0
initrd (hd0,5)/initrd.gz
Back to top
View user's profile Send private message Visit poster's website 
pupshock

Joined: 23 Mar 2007
Posts: 140

PostPosted: Sat 19 May 2007, 05:48    Post subject:  

With Barry's dire warning ringing in my ears, i deleted psubdir,
and put everything back on hda6 root as in the very first time.
Predictably, the result was as previously reported:
the 'cannot find' error with PUPMODE=1 PDEV1=
(pup_save deleted for purposes of testing)

I took Dougal's advice and created /boot, and moved
initrd.gz, pup_216.sfs, zdrv_216.sfs inside.
initrd.gz now could not be found, which was solved by writing
initrd (hd0,5)/boot/initrd.gz.
This implies that the default location for initrd.gz is
root, and /boot is not searched automatically.

At this stage, the problem devolves into why the sfs files
cannot be found in either hda6's root or /boot.

With trepidation, (sfs files are now in /boot) i tried
psubdir=/boot. No joy.
psubdir=boot. No joy.
Moved the sfs files to /boot/p216 and tried
psubdir=/p216. No joy.
psubdir=/boot/p216. No joy.
Moved the sfs files to /p216 and tried
psubdir=/p216. No joy.
psubdir=p216. No joy.
Finally, moved initrd.gz as well to /p216 and tried
kernel (hd0,5)/vmlinuz PMEDIA=idehd root=/dev/ram0 psubdir=p216
initrd (hd0,5)/p216/initrd.gz
Again, no joy. kernel loads, initrd loads, then 'cannot find Puppy'.

What am i doing wrong & what to test next?
hda6 is a NTFS partition;
puppy is the 'final' 2.16 from nluug.nl, md5sum correct;
liveCD boots OK;
Puppy 2.15 boots OK with all 4 files in hda6's root
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Sat 19 May 2007, 08:04    Post subject:  

Ah, ntfs.... Boot up a Puppy live-CD, use Pmount to mount the partition hda6 or hda1, whatever you have the Puppy files in, then confirm that all the Puppy files show as lower-case letters.
Back to top
View user's profile Send private message Visit poster's website 
pupshock

Joined: 23 Mar 2007
Posts: 140

PostPosted: Sat 19 May 2007, 09:25    Post subject:  

... renamed the files to lowercase, rebooted,
and sending this from Puppy 2.16.
Yet another leg lifted at Redmond, and
deep gratitude to Barry & all Puppy developers
Back to top
View user's profile Send private message 
pupshock

Joined: 23 Mar 2007
Posts: 140

PostPosted: Sat 19 May 2007, 09:34    Post subject:  

Afternote:
interestingly, the offending files VMLINUZ and INITRD.GZ, were found,
while pup_216.sfs and zdrv_216.sfs were already lowercase,
but were not found. Hmmm ...
... no, no, I've had enough of testing & rebooting...
Back to top
View user's profile Send private message 
tarambuka

Joined: 03 Apr 2007
Posts: 31

PostPosted: Sun 20 May 2007, 16:58    Post subject: Install problems  

Gentlemen, I solved the problem! I just renaimed vmlinus, pup_216 etc. and their extensions in lowercase (in the iso file they are with uppercase) and 2.16 started immediately.
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Sun 20 May 2007, 22:32    Post subject:  

pupshock wrote:
Afternote:
interestingly, the offending files VMLINUZ and INITRD.GZ, were found,
while pup_216.sfs and zdrv_216.sfs were already lowercase,
but were not found. Hmmm ...
... no, no, I've had enough of testing & rebooting...

Yes, I have just mentioned this in another thread. The init script would have found PUP_216.SFS and ZDRV_216.SFS and renamed them lower-case, but it doesn't do so for VMLINUZ and INITRD.GZ -- there is some code in the init script that checks the location of "initrd.gz" (lowercase) and this is probably where things went wrong.

What I will do is get the init script to rename INITRD.GZ to lowercase also, to hopefully eliminate this problem in the future.

You must have been using Windows to put these files in place, and Windows changed them to all upper-case characters. Windows did this because it doesn't care about the case in filenames.
Back to top
View user's profile Send private message Visit poster's website 
pupshock

Joined: 23 Mar 2007
Posts: 140

PostPosted: Mon 21 May 2007, 02:45    Post subject:  

yes, you are right, Barry, it is a a typical set-up for dual-booters
with Frugal installs:
from winXP, get iso, burn with Nero, copy over the files from CD,
take CD out, reboot. It worked for 2.14 and 2.15; but 2.16 threw
a curve ball (I'll look into why 2.14 and 2.15 did not)

Suggest getting the init script to rename all 4 files lowercase,
and subsequently the pup_save.2fs too.
Back to top
View user's profile Send private message 
pupshock

Joined: 23 Mar 2007
Posts: 140

PostPosted: Mon 21 May 2007, 06:13    Post subject:  

report: Puppy files on CD as seen by WinXP
2.14: All files in UPPercase
2.15: All files in LOWercase
2.16: All files in UPPercase
When copied to NTFS, they retain the Case.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0848s ][ Queries: 13 (0.0081s) ][ GZIP on ]