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 Thu 23 Nov 2017, 13:00
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
How to switch kernels between Puppy versions
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 8 of 10 [139 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10 Next
Author Message
charlie6


Joined: 30 Jun 2008
Posts: 1175
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Sat 28 Mar 2015, 07:24    Post subject: switch kernels to Puppies with separate zdrv_xxx.sfs  

Hi,

subject: switch kernels to Puppies with separate zdrv_xxx.sfs

Just to know if someone has succedeed in trying to perform jrb's method, detailed in page one this thread, and applying it to later puppies isos coming with separate zdrv_xxx.sfs files, and to puppies having only one main sfs file.

I'm here trying-struggling to switch kernels between puppy_wheezy_3.5.2.11-SCSI.iso which comes with one main sfs file, and, e.g. Pupjibaro_wheezy_JWM_1.0.6_22032015.iso; and getting no-success message like "...kernel panic..." and so on... Crying or Very sad

For sure i'm cutting and trying from reading postsrelevant to this matter; and am still ignorant about how to built a working puppy; so am i asking for help.

Thanks for any answer Smile
Charlie
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11071

PostPosted: Sat 28 Mar 2015, 14:53    Post subject:  

Perhaps its the naming of the zdrv that needs looking at.

I just booted the retro tahr kernel on lucid ok... used the new kernel and named the zdrv to match and placed it next to the main sfs.

There is usually some naming convention needed to match the initrds wants....

Of course this all may fail if the kernel you want does not have the initrd drivers built in since it will be unable to load anything....that requires the matching initrd as well.

mike
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1085
Location: Smithers, BC, Canada

PostPosted: Sun 29 Mar 2015, 00:37    Post subject: Re: switch kernels to Puppies with separate zdrv_xxx.sfs  

charlie6 wrote:
Hi,

subject: switch kernels to Puppies with separate zdrv_xxx.sfs

Just to know if someone has succedeed in trying to perform jrb's method, detailed in page one this thread, and applying it to later puppies isos coming with separate zdrv_xxx.sfs files, and to puppies having only one main sfs file.

I'm here trying-struggling to switch kernels between puppy_wheezy_3.5.2.11-SCSI.iso which comes with one main sfs file, and, e.g. Pupjibaro_wheezy_JWM_1.0.6_22032015.iso; and getting no-success message like "...kernel panic..." and so on... Crying or Very sad

For sure i'm cutting and trying from reading postsrelevant to this matter; and am still ignorant about how to built a working puppy; so am i asking for help.

Thanks for any answer Smile
Charlie


I've built a zdrv with just the kernel and firmware from puppy_wheezy_3.5.2.11.sfs and along with its initrd.gz and vmlinuz have managed to boot Pupjibaro_wheezy_JWM_1.0.6_22032015. I didn't check it too thoroughly but it appears to be working OK. The problem comes when I create a savefile and reboot, X won't start. I don't really have the time to dig deep into this but here's what I did:
1. get the initrd.gz from puppy_wheezy and open it up for editing (click on it). Replace /etc/DISTRO_SPECS with the one from Pupjibaro.
2. place the modified initrd.gz and the vmlinuz from puppy_wheezy in your directory. along with pupjibaro_wheezy_1.0.6.sfs.
3, mount zdrv_wheezy_1.0.6.sfs from Pupjibaro and use it as your guide. Open puppy_wheezy_3.5.2.11.sfs for editing and delete out everything that isn't in zdrv_wheezy_1.0.6.sfs. I also copied in the /boot folder from zdrv_wheezy_1.0.6.sfs, who knows? Now save as zdrv_wheezy_1.0.6.sfs and try rebooting.
Did that make sense? Confused Anyway Good Luck! Hope it works for you.

Cheers, J

PS - If you want I can upload the initrd.gz and zdrv files for you, but like I say, It doesn't want to run from a savefile.
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1175
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Sun 29 Mar 2015, 02:32    Post subject:  

Hi jrb,
many thanks for your answer,

Sorry if I might have been unclear:
My purpose is to use a latest kernel (e.g. 3.17.7 from Pupjibaro, or gfrom Tahr-6.0.2) in puppy_wheezy_3.5.2.11.

I could get a booting wheezy_3.5.2.11 after copying /lib/modules, /lib/firmware, /etc/modules /etc/DISTROSPECS from Pupjibaros main.sfs and zdrv_1.0.6.sfs; along with using Pupjibaros vmlinuz and initrd.gz; BUT with the mouse cursor and keyboard not functionnal nor even recognizes... Crying or Very sad

I haven't edited initrd.gz (don't know if necessary)

Cheers, Charlie
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11071

PostPosted: Sun 29 Mar 2015, 09:45    Post subject:  

Quote:
I haven't edited initrd.gz (don't know if necessary)

those kernels you mention appear to have initrd drivers built in.

Again with the save could be a naming convention.... I assume save files are not using any weird tagging system.

Cannot think of another reason off hand ... only things i find are driver related eg matching alsa and nfs ..scripts are scripts.

Again probably of no connection but recent 3 kernels will not find the puppy files on a P3 machine EVEN THOUGH from the initrd I can mount drives and see them with ls from the initrd console. Cannot fathom that one either.

Kernel devs do move things around in /proc, /sys and /dev ..if any script or binary is relying on that then it will be affected (explains the alsa and NFS ...expected behaviour)

mike
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1085
Location: Smithers, BC, Canada

PostPosted: Sun 29 Mar 2015, 11:33    Post subject:  

charlie6 wrote:
Hi jrb,

Sorry if I might have been unclear:
My purpose is to use a latest kernel (e.g. 3.17.7 from Pupjibaro, or gfrom Tahr-6.0.2) in puppy_wheezy_3.5.2.11.

Cheers, Charlie


I'm glad that's what you want. Very Happy Turns out it's really easy.
1. Place initrd.gz, vmlinuz and zdrv_wheezy_1.0.6.sfs from Pupjibaro in your folder. Rename "zdrv_wheezy_1.0.6.sfs" to "adrv_wheezy_1.0.6.sfs".
2. Place "puppy_wheezy_3.5.2.11.sfs" in the folder and rename it to "pupjibaro_wheezy_1.0.6.sfs".

Reboot and its a done deal. Works with savefile and gives me my favorite resolution which puppy_wheezy never did. Posting from it right now.

Cheers, J
wheezy1.jpg
 Description   
 Filesize   16.04 KB
 Viewed   1057 Time(s)

wheezy1.jpg

Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1085
Location: Smithers, BC, Canada

PostPosted: Sun 29 Mar 2015, 12:09    Post subject:  

The above technique worked so well and was so easy, I just tried it on Racy-5.5. Posting from it now. Very Happy
racy1.jpg
 Description   
 Filesize   24.06 KB
 Viewed   1043 Time(s)

racy1.jpg

Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1175
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Mon 30 Mar 2015, 14:12    Post subject:  

@J and @mike,
Hi Smile ,

@J,
Shocked wow ! that so easy ! thanks a lot for that tip !

Success here on applying what you described in yout post !

Having had some reading in BK's literature about PuppyLinux, would the adrv_xxx.sfs have precedence on zdrv_xxx.sfs, and therefore the drivers in the main.sfs are ignored during the bootup, wouldn't it?

@mike,
good to know a bit more about recent kernels

Again many thanks for your time !
Bets regards,
Charlie
Back to top
View user's profile Send private message 
jrb


Joined: 11 Dec 2007
Posts: 1085
Location: Smithers, BC, Canada

PostPosted: Mon 30 Mar 2015, 14:32    Post subject:  

charlie6 wrote:
Having had some reading in BK's literature about PuppyLinux, would the adrv_xxx.sfs have precedence on zdrv_xxx.sfs, and therefore the drivers in the main.sfs are ignored during the bootup, wouldn't it?


Yes, in Puppy the adrv.sfs loads first, then the puppy.sfs and then the zdrv.sfs. The first loaded takes precedence over the later ones and so on. By loading the kernel first it covered over any conflicts in the puppy.sfs. I was surprised that it named the savefile properly but /etc/DISTROSPECS seems to have been carried over from the initrd.gz and specified the correct name.

I'm very glad you posted this topic Cool , it wouldn't have occurred to me otherwise.
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11071

PostPosted: Mon 30 Mar 2015, 15:09    Post subject:  

The drivers in the main would be ignored as they are in a different folder under the version number.

firmware and other stuff like module configs and bootmanagers on the other hand may be affected by the upsidown layering of standard puppies... adrv was added to do at least one layer properly i believe Smile

distrospecs copied from initrd does ring a bell.

mike
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1175
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Tue 31 Mar 2015, 00:50    Post subject:  

Hi mike,
mikeb wrote:
...
firmware and other stuff like module configs and bootmanagers on the other hand may be affected by the upsidown layering of standard puppies... adrv was added to do at least one layer properly i believe Smile


mikeb wrote:
...
distrospecs copied from initrd does ring a bell.


Then, are there some mysfunctioning to be awaited Question Confused
Cheers,
Charlie
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11071

PostPosted: Tue 31 Mar 2015, 02:02    Post subject:  

Quote:
Then, are there some mysfunctioning to be awaited

in your case sounds like its fine... just mentioned the reasons why this may not work out and ways to fix really for others....

sorry to confuse Smile

mike
Back to top
View user's profile Send private message 
CatDude


Joined: 03 Jan 2007
Posts: 1563
Location: UK

PostPosted: Wed 15 Apr 2015, 15:31    Post subject:  

Hi

Reading through this thread i see no mention regarding compiling in these new frankenpup's, which leaves me asking a few questions.

Those questions are:
Does one need to make any changes to the devx, and if so, then what would those changes be Question

Also, am i correct in assuming that one would have to use the kernel sources from the donor Puppy Question

Maybe i'm not thinking this through properly, but i just had to ask.

CatDude
.

_________________

Back to top
View user's profile Send private message 
Pelo

Joined: 10 Sep 2011
Posts: 12591
Location: Mer méditerrannée (1 kms°)

PostPosted: Tue 28 Apr 2015, 11:46    Post subject: Help in français for french forum  

translated french traduction française tarhpup procedure
_________________
Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.
Back to top
View user's profile Send private message Yahoo Messenger 
mikeslr


Joined: 16 Jun 2008
Posts: 2017
Location: 500 seconds from Sol

PostPosted: Mon 22 Jun 2015, 20:26    Post subject: How to get a FrankenPup to point to the right repos?
Subject description: Problem with naming
 

Hi All,

Picking up on CatDude's above inquiry, I would think that the Pup version which provided the vmlinuz & zdrv is the one whose devx would be used in compiling. I've refrained from referring to it as "donor". I have a problem conceptualizing which of the two Pups should bear that name. Both are donating something.

As I see it, the END-PUP, in Charlie6's situation, is pretty much Pupjibaro_wheezy_1.0.6 wearing puppy_wheezy_3.5.2.11's clothing.

Maybe referring to them as "the base pup" --in the above case Pupjibaro-- and the outfitter --wheezy-- would be easier to remember.

I suspect that the employment of a more modular design in Puppy builds since this tread first started is the reason jrb's last technique became possible.

The following seem to be logical conclusions. Just some thoughts. The "real world" isn't always logical. Please feel free to "flesh-out" or correct any:

(a) The zdrv_xxx.sfs from Wheezy_3.5.2.11 serves no useful purpose: firmware is being provided by Pupjibaro's zdrv. If so, Wheezy's firmware/zdrv.sfs can be discarded.

(b) If the ISO's of either or both Pups being used to build an END-PUP lacks a zdrv, simply remaster to create it/them before combining the desired parts. I've used the term "simply" because in this instance all that would be required is to boot a Pup to which no changes were made, and accept all defaults except to select having a zdrv.

(c) A remaster of the END-PUP, should be able to "convert" its current "adrv" into the remastered Pup's zdrv if the unused zdrv was discarded.

More Important than my ramblings above:

Employing the terminology I used above, I just "outfitted" azami's Vividpup 4.0.1 PAE, http://murga-linux.com/puppy/viewtopic.php?p=847738#847738 with tahrpup 6.0.2's applications. Working my way thru the menu to see what works, and for any problems, everything I tried seemed to work, although there were occasional references to tahrpup, such as to a tahrpup SaveFile when, in fact, it had correctly created a vivid_SaveFile.
A significant problem, however, is that although this is essentially a vividpup, ppm points to tahrpup's repo, and ubuntu's trusty tahr repos rather than VividVervet and VividPup's repos. What's a simple way to correct this?

Perhaps better --as many apps created for TrustyTahr/Tahrpup may function in Vivid Vervet/VividPup, and vice-versa-- didn't RSH/LazyPuppy create an app making it easy to add repositories?

mikesLr
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 8 of 10 [139 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
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.1085s ][ Queries: 14 (0.0127s) ][ GZIP on ]