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 28 Nov 2014, 04:36
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
2.17 frugal install problem
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Author Message
ICPUG

Joined: 24 Jul 2005
Posts: 1290
Location: UK

PostPosted: Wed 01 Aug 2007, 20:06    Post subject:  

edoc,

Each of our last mails were written at the same time. I was responding to your one of 31st July at x:53.

I hope that after you deleted the errant pup_216.sfs all was well but I am a little surprised. I thought the 2.16 initrd.gz searched for the pup_216.sfs and the 2.17 initrd.gz searched for the pup_217.sfs! However I am not yet entirely sure of the mechanism for determining the puppy version so I may be wrong. No doubt your next mail will say whether all is OK now or not.

ICPUG
Back to top
View user's profile Send private message 
edoc


Joined: 07 Aug 2005
Posts: 4393
Location: Southeast Georgia, USA

PostPosted: Wed 01 Aug 2007, 22:41    Post subject:  

ICPUG wrote:
edoc,

Each of our last mails were written at the same time. I was responding to your one of 31st July at x:53.

I hope that after you deleted the errant pup_216.sfs all was well but I am a little surprised. I thought the 2.16 initrd.gz searched for the pup_216.sfs and the 2.17 initrd.gz searched for the pup_217.sfs! However I am not yet entirely sure of the mechanism for determining the puppy version so I may be wrong. No doubt your next mail will say whether all is OK now or not.

ICPUG


I had to give up for the moment, this was all happening on my main laptop
and it had been down for two days.

I deleted all of the 2.17 files I could find, tweaked GRUB, then copied back
the four 2.16 Frugal files I had saved to a USB HDD.

I am now back up on 2.16 with the same failed gxine and now my USB
mouse also does not work - good thing I have the touchpad!

Next time I have a chance I will backup the entire laptop contents and
wipe the HDD and do a clean new install -- I did that a few releases ago
and had hoped it would not again be necessary because restoring my
Seamonkey address book, bookmarks, several specialty apps, and some
other things is a real time-consuming nuisance -- I suppose I need to
figure out a way to 'automate' all of that.

Thanks for your assistance and words of encouragement!

_________________
Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Puppy upup Raring 3992 & Lighthouse64-b602
Back to top
View user's profile Send private message Visit poster's website 
tazoc


Joined: 11 Dec 2006
Posts: 1157
Location: Lower Columbia Basin WA US

PostPosted: Thu 02 Aug 2007, 03:09    Post subject: Working 2.17 frugal, full grub, pup_save in subdir  

Well this thread was just what I needed to get my 2.17 frugal/dual boot with LighthousePup working. I'm using full grub and separate pup_save files.
Here's the folder structure:

(hd0,7)/
Code:
pup_215.sfs   (LighthousePup 215 fs)
zdrv_215.sfs
initrd.gz
vmlinuz
pup_save-lhp215Beta4.2fs
pup_217.sfs       (Puppy 2.17 fs)
zdrv_217.sfs

(hd0,7)/boot/pup217
Code:
initrd.gz
vmlinuz
pup_save-217a.2fs

Here are the menu stubs
Code:
title         LighthousePup 215 Beta4 (frugal on hda8)
rootnoverify    (hd0,7)
kernel         (hd0,7)/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda8 PHOME=hda8 loglevel=3 vga=normal
initrd         (hd0,7)/initrd.gz

title         Puppy Linux 2.17 nolzma (frugal on hda8)
rootnoverify    (hd0,7)
kernel         (hd0,7)/boot/pup217/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda8 PHOME=hda8 psubdir=boot/pup217 loglevel=3 vga=normal
initrd         (hd0,7)/boot/pup217/initrd.gz
Results

/etc/PUPSTATE - LighthousePup
Code:
PUPMODE=12
PDEV1='hda8'
DEV1FS='ext3'
PUPSFS='pup_215.sfs'
PUPSAVE='ext3,hda8,/pup_save-lhp215Beta4.2fs'
/etc/PUPSTATE - Puppy 2.17
Code:
PUPMODE=12
PDEV1='hda8'
DEV1FS='ext3'
PUPSFS='ext3,hda8,/pup_217.sfs'
PUPSAVE='ext3,hda8,/boot/pup217/pup_save-217a.2fs'

LighthousePup 215 Beta4, based on Puppy 215CE doesn't look for a pup_save in subfolders, it uses the one in /. That's why I put Lighthouse in the / folder and 2.17 in a subdir, not the other way around. Puppy 2.17 finds both pup_save files and prompts me during bootup whether to use:
0 - none
1 - /pup_save-lhp215Beta4.2fs on hda8
2 - /boot/pup217/pup_save-217a.2fs on hda8
From the PUPSTATE above you can see which option I chose.
Can load and share SFS modules in both systems. With Lighthouse the filename must end with _215.sfs. (Edit 2 Aug) With Puppy 2.17 the filename cannot end with '_nnn.sfs' unless nnn=217. www.murga-linux.com/puppy/viewtopic.php?t=17338&start=45

To share SFS files without copying, I create a symlink <whatever>_217.sfs to <whatever>_215.sfs (Edit 2 Aug) (Of course, some SFS modules will not work as well in versions for which they were not designed. But this will enable testing and design for multiple versions. I'm doing exactly that right now with K3b/GIMP/pgs graphics SFS development pgs_K3b-12.17-01_215.sfs 115M, which is missing some libs needed for 2.17 but version -02 to be available in a couple of days is tested with Puppy 2.17) www.lhpup.org/download.htm
-TazOC

_________________
lhpup.org Lighthouse 64 6.02

Last edited by tazoc on Thu 02 Aug 2007, 20:10; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
ICPUG

Joined: 24 Jul 2005
Posts: 1290
Location: UK

PostPosted: Thu 02 Aug 2007, 19:28    Post subject:  

Well done tazoc.

Thanks for posting your results back. This shows how to dual boot two Puppies (where one is 2.17). You have also confirmed what Leon found that Puppy 2.17 will now find a Pupsave in the subdirectory denoted by psubdir. Great news.

ICPUG
Back to top
View user's profile Send private message 
edoc


Joined: 07 Aug 2005
Posts: 4393
Location: Southeast Georgia, USA

PostPosted: Thu 02 Aug 2007, 19:51    Post subject:  

ICPUG wrote:
Well done tazoc.
Thanks for posting your results back. This shows how to dual boot two Puppies (where one is 2.17). You have also confirmed what Leon found that Puppy 2.17 will now find a Pupsave in the subdirectory denoted by psubdir. Great news.
ICPUG


I have printed his post and am downloading the tmxxine Puppy as I type this.

The children want me to load GamePup somewhere though I think TeenPup is
likely to promote a little more productivity! Smile

Am looking at ChurchPup as it would be neat to have a version deliberately
designed to facilitate Bible study and application.

Now if only I could find a version of Puppy that will run on the old Panasonic
CF-41 MKiii laptop here with 16MB of RAM (32MB if I spend $40. on a 16M
memory card) - that would be really cool!.

Now tell me, can the billionnaire Bill Gates and his chronically defective
and bloated MS versions of windows do all this? Yeah, right. Great marketing
and poor product ... oh yeah, I remember that product, magic elixir!

Thanks ICPUG and tazoc and Barry, et al!

_________________
Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Puppy upup Raring 3992 & Lighthouse64-b602
Back to top
View user's profile Send private message Visit poster's website 
tazoc


Joined: 11 Dec 2006
Posts: 1157
Location: Lower Columbia Basin WA US

PostPosted: Thu 02 Aug 2007, 20:13    Post subject:  

ICPUG wrote:
Well done tazoc.

Thanks for posting your results back. This shows how to dual boot two Puppies (where one is 2.17). You have also confirmed what Leon found that Puppy 2.17 will now find a Pupsave in the subdirectory denoted by psubdir. Great news.

ICPUG
Thank you everyone I'd been struggling with this psubdir= usage for several days until I came upon this thread! I guess avoiding the leading and trailing /'s helped?

Also note my edits today re: SFS modules at end of my prev post.
-TazOC

_________________
lhpup.org Lighthouse 64 6.02
Back to top
View user's profile Send private message Visit poster's website 
edoc


Joined: 07 Aug 2005
Posts: 4393
Location: Southeast Georgia, USA

PostPosted: Tue 07 Aug 2007, 00:01    Post subject:  

tazoc wrote:
ICPUG wrote:
Well done tazoc.

Thanks for posting your results back. This shows how to dual boot two Puppies (where one is 2.17). You have also confirmed what Leon found that Puppy 2.17 will now find a Pupsave in the subdirectory denoted by psubdir. Great news.

ICPUG
Thank you everyone I'd been struggling with this psubdir= usage for several days until I came upon this thread! I guess avoiding the leading and trailing /'s helped?

Also note my edits today re: SFS modules at end of my prev post.
-TazOC


I have been trying to get TEENpup (Puppy 2.14) and TXXINE-Prism (Puppy 2.17)
to play nicely together ... errr ... dual boot.

Because of an odd problem I had clearing out the old install I ended up doing a WIPE
of my laptop HDD and a FULL install of TEENpup.

Then I did a FRUGAL install of TMXXINE-Prism and have been tinkering with the
file locations and GRUB -- and tried to emulate TAZOC's folder structure.

TMXXINE-Prism is struggling to boot.

Anyone see anything obviously UGLY in my GRUB code?

EDIT: I commented-out this line in the code for the Frugal TMXXINE-Prism boot:
PDEV1=hda1 PHOME=hda1 psubdir=boot/prism loglevel=3 vga=normal

# Linux bootable partition config begins

title TEENpup 2.0.0 Puppy Linux (Full on /dev/hda1)
root (hd0,0)
kernel /vmlinuz root=/dev/hda1 ro vga=normal

title TMXXINE-Prism Puppy Linux (frugal on /dev/hda1)
rootnoverify (hd0,0)
kernel (hd0,0)/boot/prism/vmlinuz root=/dev/ram0 PMEDIA=idehd
# PDEV1=hda1 PHOME=hda1 psubdir=boot/prism loglevel=3 vga=normal
initrd (hd0,0)/boot/prism/initrd.gz

# Linux bootable partition config ends

_________________
Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Puppy upup Raring 3992 & Lighthouse64-b602
Back to top
View user's profile Send private message Visit poster's website 
rcrsn51


Joined: 05 Sep 2006
Posts: 9261
Location: Stratford, Ontario

PostPosted: Tue 07 Aug 2007, 11:04    Post subject:  

A menu.lst file can only be analyzed if you also specify where the core Puppy files are located. Also, the GRUB and Puppy error messages would be helpful.
Back to top
View user's profile Send private message 
edoc


Joined: 07 Aug 2005
Posts: 4393
Location: Southeast Georgia, USA

PostPosted: Tue 07 Aug 2007, 13:39    Post subject:  

rcrsn51 wrote:
A menu.lst file can only be analyzed if you also specify where the core Puppy files are located. Also, the GRUB and Puppy error messages would be helpful.


Sorry, thought I was clear when I wrote that I had followed TAZOC's folder structure ...

Here's my folder structure:

(hd0,0)/
pup_214.sfs (TEENpup 214)
zdrv_214.sfs (TEENpup 214)
initrd.gz (TEENpup 214)
vmlinuz (TEENpup 214)
pup_save-teenpup.2fs (TEENpup 214)
pup_217.sfs (TMXXINE-Prism Puppy 2.17 fs)
zdrv_217.sfs (TMXXINE-Prism Puppy 2.17 fs)
idehd (TMXXINE-Prism Puppy 2.17 fs)

(hd0,0)/boot/prism/
initrd.gz (TMXXINE-Prism Puppy 2.17 fs)
vmlinuz (TMXXINE-Prism Puppy 2.17 fs)
pup_save-tmxxineprism1.2fs


TEENpup generates an error re. cat: /etc/TZ no such file or directory - that is
now worked around automatically in the boot - no user intervention required.

The TMXXINE-Prism is much more messy ...

Here's the relevant part of the boot results:

Looking for Puppy in hda1 ... Done
pup_save-teenpup.2fs found Done

ERROR, cannot find Puppy on 'idehd' boot media.
PUPMODE=15 PDEV1=hda1
Exited to initial-ramdisk (initramfs) commandline ...
(the Linux-guru can now debug, 'e3' edition is available)
/bin/sh: can't access tty; job control turned off

_________________
Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Puppy upup Raring 3992 & Lighthouse64-b602
Back to top
View user's profile Send private message Visit poster's website 
rcrsn51


Joined: 05 Sep 2006
Posts: 9261
Location: Stratford, Ontario

PostPosted: Tue 07 Aug 2007, 14:30    Post subject:  

You have sfs files for both Teenpup (2.14) and Prism Puppy (2.17) in /. It looks like Puppy is finding and using Teenpup which doesn't match the kernel files off which it booted . Since Teenpup is a full install, try deleting/renaming its files.
Back to top
View user's profile Send private message 
edoc


Joined: 07 Aug 2005
Posts: 4393
Location: Southeast Georgia, USA

PostPosted: Tue 07 Aug 2007, 14:55    Post subject:  

rcrsn51 wrote:
You have sfs files for both Teenpup (2.14) and Prism Puppy (2.17) in /. It looks like Puppy is finding and using Teenpup which doesn't match the kernel files off which it booted . Since Teenpup is a full install, try deleting/renaming its files.


What can I delete or rename and still have TEENpup run, please?

If I rename am I just changing the .sfs to something else or is Puppy looking for ".sfs"
OR "pup_" and if found is loading the first one it finds ?

_________________
Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Puppy upup Raring 3992 & Lighthouse64-b602
Back to top
View user's profile Send private message Visit poster's website 
rcrsn51


Joined: 05 Sep 2006
Posts: 9261
Location: Stratford, Ontario

PostPosted: Tue 07 Aug 2007, 15:14    Post subject:  

Unless I'm mistaken, when you do a full install, the contents of the sfs files are extracted to your hard drive and you don't need them at all. You just need the vmlinuz file to get started.
Back to top
View user's profile Send private message 
edoc


Joined: 07 Aug 2005
Posts: 4393
Location: Southeast Georgia, USA

PostPosted: Tue 07 Aug 2007, 15:55    Post subject:  

rcrsn51 wrote:
Unless I'm mistaken, when you do a full install, the contents of the sfs files are extracted to your hard drive and you don't need them at all. You just need the vmlinuz file to get started.


Does it need the pup_save or may I rename that as well?

I renamed everything else and it came up OK but TMXXINE-Prism still fails due to the TEENpup pup_save being picked up.

_________________
Thanks! David
Home page: http://nevils-station.com
Don't google Search! http://duckduckgo.com
Puppy upup Raring 3992 & Lighthouse64-b602
Back to top
View user's profile Send private message Visit poster's website 
rcrsn51


Joined: 05 Sep 2006
Posts: 9261
Location: Stratford, Ontario

PostPosted: Tue 07 Aug 2007, 18:13    Post subject:  

Be brave. You have the answer to your own question.
Back to top
View user's profile Send private message 
tazoc


Joined: 11 Dec 2006
Posts: 1157
Location: Lower Columbia Basin WA US

PostPosted: Tue 07 Aug 2007, 21:07    Post subject:  

Quote:
# Linux bootable partition config begins

title TEENpup 2.0.0 Puppy Linux (Full on /dev/hda1)
root (hd0,0)
kernel /vmlinuz root=/dev/hda1 ro vga=normal

title TMXXINE-Prism Puppy Linux (frugal on /dev/hda1)
rootnoverify (hd0,0)
kernel (hd0,0)/boot/prism/vmlinuz root=/dev/ram0 PMEDIA=idehd
# PDEV1=hda1 PHOME=hda1 psubdir=boot/prism loglevel=3 vga=normal
initrd (hd0,0)/boot/prism/initrd.gz

# Linux bootable partition config ends

edoc,
When you commented out
# PDEV1=hda1 PHOME=hda1 psubdir=boot/prism loglevel=3
did that also comment out 'psubdir=boot/prism' ?
(The line commented out was part of the previous 'kernel ...' line.
Maybe try:
Note: 'kernel ... 3' is all on same line:
Code:
title TMXXINE-Prism Puppy Linux (frugal on /dev/hda1)
rootnoverify (hd0,0)
kernel (hd0,0)/boot/prism/vmlinuz root=/dev/ram0 PMEDIA=idehd psubdir=boot/prism loglevel=3
# PDEV1=hda1 PHOME=hda1 vga=normal
initrd (hd0,0)/boot/prism/initrd.gz
Need to have the 'psubdir=boot/prism' on the kernel line or else it will 'not find Puppy.'
-TazOC

_________________
lhpup.org Lighthouse 64 6.02
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 2 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 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.1187s ][ Queries: 13 (0.0179s) ][ GZIP on ]