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 Tue 22 Jul 2014, 15:35
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 4 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
Dougal


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

PostPosted: Fri 25 May 2007, 09:17    Post subject:  

BarryK wrote:
Dougal wrote:
Barry, should I remove the "-R" from the remaster script?

Option '-R' works. It is Rock Ridge extensions that keep all file attributes as-is, vital for the multisession CD/DVD.


Oops... I got myself all confused, with the Rock Ridge and Joliet thing... I'll just make sure there's no "-J" there.

_________________
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 
joki

Joined: 21 Oct 2006
Posts: 79

PostPosted: Sat 26 May 2007, 07:36    Post subject: multiple puppy 2.xx versions and 2.16 frugally installed  

i think it would be useful if the 2.16 (frugal) install issues and workarounds could be detailed in a sticky announcement. i needed 2.12 and 2.16 both frugally installed on my win98 c drive (fat hda1). If anyone's interested the only config that worked:

For 2.12 : put vmlinuz and initrd.gz in a folder /pup212
All 2.12's sfs files and pup_save.3fs must remain in the root (presumably 2.16 was going to be able to have the sfs files in a nominated folder too?)
Create batch file to run 2.12:
cd \pup212
loadlin.exe vmlinuz rw init=/etc/init root=/dev/ram0 lang=us initrd=initrd.gz

For 2.16 : put vmlinuz and initrd.gz in root of drive c and all it's sfs files and pup_save.2fs must also be in the root.
Batch file to run 2.16:
cd\
loadlin.exe vmlinuz rw init=/etc/init root=/dev/ram0 initrd=initrd.gz

i have tried passing various combos of PSAVEDIR=/pup216, PDEV1=hda1, PFILE=pup_216.sfs all to no avail.

--

My outstanding questions regarding puppy 2.16:

1. have tried PUPSAVE=ext2,hda1,pup_save.2fs but the loader still asks me to choose which save file to use. i've pup_save.3fs for 2.12, and pup_save.2fs for 2.16 (2.12 doesn't look for the 2fs thankfully)

2. sfs boot manager - why won't it allow you to select sfs's with _puppuversion in the name (eg winexx_212.sfs)? I understand there will be trouble if the wrong devx sfs is selected but some sfs's will work fine on many puppy versions, wine being one. Since puppys earlier than 2.16 require the version in the filename the only option for 'dual puppy frug installs' is to have multiple copies of the sfs files. win98 users could use .bat files to rename as necessary but xp users are stuck with ntlr/grub

I can see things are getting more slick/polished in the 2.16 front-end. this can only help bring more interest Smile , but it would be nice if startup stuff was more retro-friendly and modular...
Back to top
View user's profile Send private message 
bobn9lvu


Joined: 11 Jul 2006
Posts: 173

PostPosted: Sat 26 May 2007, 10:14    Post subject:  

The boot manager DOES allow one to use the Puppy version.
DO NOT UNCHECK the box towards the bottom,
and rename up to 3 sfs with _"VERSION",
or (OO_2.16.sfs) to automagically load em on boot.

Bob Cool

_________________
Puppy Linux - Lift your leg at Redmond. Razz Twisted Evil Razz
Back to top
View user's profile Send private message 
joki

Joined: 21 Oct 2006
Posts: 79

PostPosted: Sat 26 May 2007, 12:57    Post subject:  

bobn9lvu wrote:
The boot manager DOES allow one to use the Puppy version.
DO NOT UNCHECK the box towards the bottom,
and rename up to 3 sfs with _"VERSION",
or (OO_2.16.sfs) to automagically load em on boot.

Bob Cool


this is exactly the problem! i have winexx_212.sfs which i want to use for both puppy 2.12 and 2.16 which are frugally stored on drive c.
2.16 boot manager specifically states that it excludes from selection all sfs files like _nnn.sfs where nnn not equal to 216.
Back to top
View user's profile Send private message 
bobn9lvu


Joined: 11 Jul 2006
Posts: 173

PostPosted: Sat 26 May 2007, 16:12    Post subject:  

joki wrote:
bobn9lvu wrote:
The boot manager DOES allow one to use the Puppy version.
DO NOT UNCHECK the box towards the bottom,
and rename up to 3 sfs with _"VERSION",
or (OO_2.16.sfs) to automagically load em on boot.

Bob Cool


this is exactly the problem! i have winexx_212.sfs which i want to use for both puppy 2.12 and 2.16 which are frugally stored on drive c.
2.16 boot manager specifically states that it excludes from selection all sfs files like _nnn.sfs where nnn not equal to 216.


Well, then do it manually by unchecking the box, and selecting which sfs you want to load, THEN you do NOT have to rename them for each version of Puppy...

Bob Cool

_________________
Puppy Linux - Lift your leg at Redmond. Razz Twisted Evil Razz
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 27 May 2007, 07:44    Post subject:  

'_xxx' SFS files that are not for the current version get totally excluded from the left-pane selection list, so you can't load them. I did that deliberately, as my experience is that if people are given the slightest chance to do something wrong, then someone will -- well, most people will realise that a '_215' SFS may not be intended for say v216. But, I decided to play safe and leave them off the list.
Back to top
View user's profile Send private message Visit poster's website 
bobn9lvu


Joined: 11 Jul 2006
Posts: 173

PostPosted: Sun 27 May 2007, 12:16    Post subject:  

BarryK wrote:
'_xxx' SFS files that are not for the current version get totally excluded from the left-pane selection list, so you can't load them. I did that deliberately, as my experience is that if people are given the slightest chance to do something wrong, then someone will -- well, most people will realise that a '_215' SFS may not be intended for say v216. But, I decided to play safe and leave them off the list.


So you are saying, that in order for a person to use the same sfs file in
different versions of puppy, you have to have a copy renamed for each of the
puppy versions...
Hmmmm, it would take up a LOT of needed space..

Could you add a checkbox in the mount utility to negate this feature??
Or provide some way ( different util version) to negate this feature??


Thanks !

Bob Cool

_________________
Puppy Linux - Lift your leg at Redmond. Razz Twisted Evil Razz
Back to top
View user's profile Send private message 
HairyWill


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

PostPosted: Sun 27 May 2007, 13:28    Post subject:  

try commenting out line 82 of /usr/sbin/bootmanager

My personal opinion is that users running multiple puppy versions should really be knowledgeable enough to manage this themselves or should invest the disk space needed to create multiple sfs file versions.

Open source allows any one to configure anything the way they wish if they invest the time in learning how. It is much better to guarantee a working solution to those that do not wish to learn how to configure things themselves.

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


Joined: 11 Jul 2006
Posts: 173

PostPosted: Sun 27 May 2007, 14:21    Post subject:  

Agreed, AND I do have LOTS of drive space, but the way I asked the question,
was more of a learning curve/experience. Wink

I am happy with 2.16 and OO with manually added specific programs... Very Happy

Bob

_________________
Puppy Linux - Lift your leg at Redmond. Razz Twisted Evil Razz
Back to top
View user's profile Send private message 
joki

Joined: 21 Oct 2006
Posts: 79

PostPosted: Sun 27 May 2007, 14:42    Post subject:  

BarryK wrote:
'_xxx' SFS files that are not for the current version get totally excluded from the left-pane selection list, so you can't load them. I did that deliberately, as my experience is that if people are given the slightest chance to do something wrong, then someone will -- well, most people will realise that a '_215' SFS may not be intended for say v216. But, I decided to play safe and leave them off the list.


fair point.
dialog could allow the selection of _214, _212 etc files after some warning/confirmation.

there's now a trend for creating sfs files without the _xxx in the filename - may cause problems in the future as they will be listed in future puppy version's boot manager dialog.

tricky one. maybe a hidden file in the sfs could let the sfs manager know if it's 'generic' enough for any puppy version.

or if it's just the system sfs's like devx and zdrv you're worried about, specifically exclude those from selection. ie, ensure devx and zdrv sfs always have the puppy version on them and for the list of known 'system' sfs's the _xxx is required.
Back to top
View user's profile Send private message 
Leachim

Joined: 27 May 2007
Posts: 229

PostPosted: Sun 27 May 2007, 19:15    Post subject: initrd.gz  

I had similar problems about "Puppy not found".

The reason is simply that V2.16 insists that the initial ramdisk file is called "initrd.gz" - in V2.15 I could rename it to an arbitrary name (and change the boot configuration file accordingly) and everything continued to work fine. (This has nothing to do with filename capitalization.)

Is there any specific reason for this strict behaviour?

Anyway I would appreciate more detailed error messages, e.g.
Code:
"/initrd.gz" not found on "/dev/sda1"

But despite of my criticism: Puppy is great and I like it! Very Happy
Back to top
View user's profile Send private message 
Lobster
Official Crustacean


Joined: 04 May 2005
Posts: 15117
Location: Paradox Realm

PostPosted: Sun 03 Jun 2007, 04:28    Post subject: Bug of missing driver (REM for Barry)
Subject description: . . . and its solution
 

This problem was solved in 2.12 and yet in 2.16 the driver was ommitted?

- anyway here s the solution Smile

http://www.murga-linux.com/puppy/viewtopic.php?p=117150#117150

_________________
Puppy WIKI
Back to top
View user's profile Send private message Visit poster's website 
edoc


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

PostPosted: Thu 07 Jun 2007, 19:57    Post subject: 2.16 broke Seamonkey, html, gxine, email
Subject description: calendar, chat, calc, paint, dillo work OK
 

2.16 broke Seamonkey, html, gxine, email

calendar, chat, calc, paint, dillo work OK.

/tmp/xerrs.log shows:

/usr/lib/mozilla/mozilla-bin: line 35: /usr/lib/mozilla/seamonkey-bin: No such file or directory
/usr/lib/mozilla/mozilla-bin: line 35: exec: /usr/lib/mozilla/seamonkey-bin: cannot execute: No such file or directory

I am anxiously seeking a solution else I will have to very reluctantly roll back to 2.14 -- what may have caused this odd anomaly and how might it be resolved, please?

We are in the middle of selling our home and E-mail and Internet access are critical.

Help?

_________________
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 
GuestToo
Puppy Master

Joined: 04 May 2005
Posts: 4078

PostPosted: Thu 07 Jun 2007, 21:05    Post subject:  

if you have a frugal install, copy the missing seamonkey-bin file from /initrd/pup_ro2/usr/lib/mozilla/ to /usr/lib/mozilla/

if you have a full install, boot the Puppy cd maybe using the pfix=ram option, mount the partition, and copy the missing seamonkey-bin file from /usr/lib/mozilla/ to the mounted partition

there may be other missing files
Back to top
View user's profile Send private message 
edoc


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

PostPosted: Thu 07 Jun 2007, 21:35    Post subject:  

GuestToo wrote:
if you have a frugal install, copy the missing seamonkey-bin file from /initrd/pup_ro2/usr/lib/mozilla/ to /usr/lib/mozilla/

if you have a full install, boot the Puppy cd maybe using the pfix=ram option, mount the partition, and copy the missing seamonkey-bin file from /usr/lib/mozilla/ to the mounted partition

there may be other missing files


Thanks, did the copy, will reboot.

Any idea why this would have happened?

_________________
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 
Display posts from previous:   Sort by:   
Page 4 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.1084s ][ Queries: 13 (0.0122s) ][ GZIP on ]