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, 07:25
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
4.1.2 Unleashed: custom Puppy won't boot from frugal install
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [16 Posts]   Goto page: 1, 2 Next
Author Message
tronkel


Joined: 30 Sep 2005
Posts: 1104
Location: Vienna Austria

PostPosted: Fri 02 Jan 2009, 19:56    Post subject:  4.1.2 Unleashed: custom Puppy won't boot from frugal install
Subject description: Gives kernel panic
 

I've just been having a go with Unleashed for 4.1.2.

I get a kernel panic every time I try to boot from a frugal install that uses the newly created build copied from isolinux-builds in Unleashed direct to the folder where Puppy looks for the puppy_412.sfs and initrd.gz. Anyone else experienced problems here?

Is it best to have the modules merged to the puppy_412.sfs or to the initrd.gz as offered by the Unleashed script?
Back to top
View user's profile Send private message Visit poster's website AIM Address 
WhoDo


Joined: 11 Jul 2006
Posts: 4441
Location: Lake Macquarie NSW Australia

PostPosted: Fri 02 Jan 2009, 20:15    Post subject: Re: Unleashed problem - 4.1.2  

tronkel wrote:
I've just been having a go with Unleashed for 4.1.2.

I get a kernel panic every time I try to boot from a frugal install that uses the newly created build copied from isolinux-builds in Unleashed direct to the folder that Puppy looks for the puppy_412.sfs and initrd.gz. Anyone else experienced problems here?

Is it best to have the modules merged to the puppy_412.sfs or to the initrd.gz as offered by the Unleashed script?

I thought it was just me, Jack. I've tried with the modules in the pup_412.sfs, a separate zdrv_412.sfs and crammed into the initrd.gz and it doesn't seem to help whichever way.

I tried just updating to the 4.1.2 Unleashed core over an existing 4.1.1 Unleashed install last time, and it won't even mount the AUFS file system and eventually gives an "attempt to kill init - Kernal panic" error. At Barry's suggestion, I'm going to download the whole shebang again, recheck the MD5 sums and start from scratch. He assures me the 4.1.2 Unleashed build works fine. Will let you know how I go.

Cheers

_________________
Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com
Back to top
View user's profile Send private message 
tronkel


Joined: 30 Sep 2005
Posts: 1104
Location: Vienna Austria

PostPosted: Sat 03 Jan 2009, 06:06    Post subject:  

Hi WhoDo

Happy new year to you and yours.

Hope everything is going OK with Puppy 4.2 apart from the problem with Unleashed. I downloaded my Unleashed from Nluug using ftp. The packages dowload failed, leaving about 2 dozen packages missing. I then downloaded the other packages separately, ending up with the correct total number. I wonder if the point where the trip-up occured involves a crucial corrupted package. I'll have a look back at where this was. How was your download?

I had an idea that I wanted to use 4.1.2 to make a special ISO for Asus eeepc users who want a quick and automatic replacement for the OEM Xandros that ships with that model.

Will let u know if I find the solution.

All the best - keep in touch if you need anything

Jack

_________________
Life is too short to spend it in front of a computer
Back to top
View user's profile Send private message Visit poster's website AIM Address 
WhoDo


Joined: 11 Jul 2006
Posts: 4441
Location: Lake Macquarie NSW Australia

PostPosted: Sat 03 Jan 2009, 19:07    Post subject:  

tronkel wrote:
Happy new year to you and yours.

And to you and yours as well, Jack. All is indeed well, apart from the Unleashed problem of course. John Swenson and Glassparrot seem to be having similar issues.

tronkel wrote:
I downloaded my Unleashed from Nluug using ftp. The packages dowload failed, leaving about 2 dozen packages missing. I then downloaded the other packages separately, ending up with the correct total number. I wonder if the point where the trip-up occured involves a crucial corrupted package. I'll have a look back at where this was. How was your download?

I grabbed my 4.1.1 Unleashed from a CD Barry posted me for Christmas, added the fixes from his blog and then updated with the 4.1.2 Core when it was posted at ibiblio. I haven't yet had a chance to go back and download the lot to start from scratch. That's a job for when I'm back in my Puppy "cave" at home, early next week!

I too will keep you posted on my progress, mate.

Cheers,

Warren

_________________
Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com
Back to top
View user's profile Send private message 
tronkel


Joined: 30 Sep 2005
Posts: 1104
Location: Vienna Austria

PostPosted: Sun 04 Jan 2009, 04:56    Post subject:  

Hi Warren,

I just downloaded the packages-4 folder to try to establish if there was anything strange going on there.

It all download OK this time from ibiblio this time. albeit slowly. Unfortunately still no go with boot-up from the ISO though.

How many files does your Unleashed packages folder contain?
Mine ended up with 619 but ibiblio seemed to download 1238 in total - exactly twice that number. I wonder if Barry's original upload of Unleashed to ibiblio got corrupted. If this is the case some all all of the mirrors could also have been affected - dunno.

Only 619 files actually appeared in the packages folder though just as previously. How very strange!!

Will do more research and let you know what I find.

_________________
Life is too short to spend it in front of a computer
Back to top
View user's profile Send private message Visit poster's website AIM Address 
WhoDo


Joined: 11 Jul 2006
Posts: 4441
Location: Lake Macquarie NSW Australia

PostPosted: Sun 04 Jan 2009, 19:16    Post subject:  

tronkel wrote:
How many files does your Unleashed packages folder contain?

I downloaded 638 packages from Pet_Packages_4 on ibiblio. Total 858Mb when unpacked. Directory shows 627 items but I did get rid of a couple of extraneous packages. I also did a comparison check against the included packages list for Puppy 4.12 and got a complete match.

tronkel wrote:
Will do more research and let you know what I find.

In the meantime I have downloaded a complete clean Unleashed and tried to build a new pup with only the default selections. No go; same errors - here is what I see when I try to run the build after it fails to mount the layered file system:
Code:
bootinit.log -
mount: mounting /dev/sr0 on /mnt/data failed
mount: mounting /dev/sr0 on /mnt/data failed
mount: mounting /dev/loop0 on /pup_ro2 failed
mount: mounting unionfs on /pup_new failed

kernel log -
(4) EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
(6) kjournald starting. Commit interval 5 seconds
(6) EXT3 fs on sda5, internal journal
(6) EXT3 fs: mounted file system with ordered data mode

Pausing for 60 seconds ....

Performing a 'switch root' to the layered file system ... Kernel panic - not syncing: Attempted to kill init!


Here is what Barry suggested when I PM'd him earlier about the problem:
BarryK wrote:
You could do a test build from my "pristine" 4.1.2 then compare what you have inside boot/initrd-tree0 with what you have inside your initrd-tree0.
- do you have the same modules?
- do the dependency files look ok? (like /lib/modules/2.6.25.x/modules.dep)
- what changes have you made to the 'init' script compared with mine?
- is your 'createpuppy' script different from mine?


Needless to say the failure to build from Barry's pristine 4.1.2 tarball makes those steps redundant.

Next I think I'll try using the Puppy 4.1.1 0rootfs_skeleton_411 package to see if it builds with that. Reports elsewhere indicate 4.1.1 Unleashed builds without issues. I'll keep in touch.

Update:
I used the Puppy-4.1.1 Unleashed core, added the packages including my updates and was able to successfully create a Puppy 4.2alpha ... at last! Shocked

The problem seems to be in the /boot/initrd0 section of the 4.1.2 Unleashed tree. I didn't bother to do a compare on the two directories - I don't have time for that. I'll just manually add the 4.1.2 patches from the entries in Barry's blog, then produce an alpha for uploading sometime this week.

_________________
Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com
Back to top
View user's profile Send private message 
tronkel


Joined: 30 Sep 2005
Posts: 1104
Location: Vienna Austria

PostPosted: Mon 05 Jan 2009, 12:31    Post subject:  

Here's another approach that seems to work.

Use the normal 4.1.2 Unleashed core, but replace the whole of the Unleashed boot folder in 4.1.2 Unleashed core with the one from 4.1.1. Unleashed core.

Then simply open boot/initrd-tree0/PUPPYVERSION in a text editor and change it from 411 to 412 and save the file.

This has built what I think is Puppy 4.1.2

The fault of course has not been established as such. Maybe when Barry gets back, he could re-visit the boot tree and establish where the fault is.

In the meantime, this should put the 4.2 build back on track.

_________________
Life is too short to spend it in front of a computer

Last edited by tronkel on Mon 05 Jan 2009, 14:31; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website AIM Address 
MagicZaurus

Joined: 05 Jan 2009
Posts: 88

PostPosted: Mon 05 Jan 2009, 13:41    Post subject:  

Hi Tronkel & WhoDo!

Just to let you know that I had similar problems in building from Unleashed 4.1.2 yesterday. I thought I'm doing something wrong as I just started to play around with it the last 2 days.

Maybe I will try the way with the core from Unleashed 4.1.1.

Good luck for 4.2.
Back to top
View user's profile Send private message 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Thu 08 Jan 2009, 01:40    Post subject:  

Huh. Here's my guess: In the past, I have had a working initrd-tree/ directory, but after copying it to another computer it became goofed up. Everything looked fine, but the device files in initrd-tree/dev/* were somehow wrong.

I suspect that that is what has happened here.

So try deleting the boot/initrd-tree0/dev directory from the 4.12 unleashed and replacing it with the one from 4.11, and see how that works.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
MagicZaurus

Joined: 05 Jan 2009
Posts: 88

PostPosted: Fri 09 Jan 2009, 14:13    Post subject:  

I managed to built a working version from Unleashed 4.1.2 now.

After downloading the core and packages I did the following 2 things.

1) Copy 'depmod' from puppy-unleashed-4.1.1/boot to puppy-unleashed/boot.

2) Copy puppy-unleashed-4.1.1/boot/initrd-tree0/dev to puppy-unleashed/boot/initrd-tree0/dev.

After that I just used the ./createpuppy and no problems or errors observed.

Cheers

MagicZaurus
Back to top
View user's profile Send private message 
glassparrot


Joined: 01 Jun 2008
Posts: 285
Location: Durango, Colorado - USA

PostPosted: Sat 10 Jan 2009, 14:01    Post subject:  

Worked like a charm! Very Happy Thanks, Magiczaurus. I think Barry should cut you in on the company! Wink
Back to top
View user's profile Send private message Visit poster's website Yahoo Messenger MSN Messenger 
WhoDo


Joined: 11 Jul 2006
Posts: 4441
Location: Lake Macquarie NSW Australia

PostPosted: Sat 10 Jan 2009, 18:19    Post subject:  

glassparrot wrote:
Worked like a charm! Very Happy Thanks, Magiczaurus. I think Barry should cut you in on the company! Wink

Maybe, but the suggestion to replace the /boot/initrd-tree0/dev directory came from Pizzasgood not MagicZaurus, who still did the testing and reporting. Thanks to both guys for a working solution! Cool

_________________
Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com
Back to top
View user's profile Send private message 
MagicZaurus

Joined: 05 Jan 2009
Posts: 88

PostPosted: Sun 11 Jan 2009, 00:47    Post subject:  

Not so much kudos for me, I just picked up the suggestion from 2 other guys and put them together and tried it. The problem with 'depmod' was mentioned in another thread. That's how a good community works, also in real life, everybody contributes his part.

I just started to 'play' with Puppy Linux about 10 days ago and it's great. Really a great job done by Barry and very good to learn about the internals of Linux.
Back to top
View user's profile Send private message 
beer-man

Joined: 26 Feb 2009
Posts: 2

PostPosted: Thu 26 Feb 2009, 13:04    Post subject:  

I've tried six was to sunday and still cannot get unleashed to create a working iso. I've tried everything I've seen posted and still get kernel panic when switching root.

I did find that if I have my flash drive (load with puppy) plugged in it boots /switches to that some how.

I don't have lots of linux experence, but have played with it though out my 19 years in the computer career.

my goal is to try to strip down puppy to just boot into rdesktop and connect to a terminal server.

thanks
Back to top
View user's profile Send private message 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Fri 27 Feb 2009, 17:25    Post subject:  

Instead of trying everything, try only doing the two things MagicZaurus listed: replacing the /boot/initrd-tree0/dev directory and adding the depmod program. You may want to move the packages directory out of the unleashed tree, delete the unleashed tree, grab a fresh unmodified copy, put the packages directory back, and then make those modifications, just to make sure it's clean.

Also, be sure that you're modifying the initrd-tree0 directory, NOT the initrd-tree directory. In fact, you may want to delete the initrd-tree directory just to make sure the changes are being incorporated. When you do that, also remove the initrd.gz file form isolinux-builds/. That way you can make sure it's being rebuild freshly.

When Unleashed is running, chose only the defaults initially, to make sure it's working.

Also, check that you're actually running the same kernel version as that of the Puppy you're trying to build, as not doing so can cause issues.

And make sure that the official copy of that version of Puppy also boots - preferably you would be doing the building from that very version of Puppy to ensure maximum compatibility.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 2 [16 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
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.0935s ][ Queries: 12 (0.0043s) ][ GZIP on ]