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 Sat 25 Oct 2014, 07:40
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 2 of 7 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Author Message
peebee


Joined: 21 Sep 2008
Posts: 1464
Location: Malvern, Worcs, UK

PostPosted: Wed 05 Jan 2011, 14:07    Post_subject:  

sc0ttman wrote:
It boots,.. but should I switch around the symlinks to mksquashfs3 and mksquashfs4?
(So that the default mksquashfs will be mksquashfs4...)


Gosh - no idea - needs an "expert" to answer that.....

I've been making hybrids between recent woof based puppies so haven't run into those sort of issues.....
Back to top
View user's profile Send_private_message Visit_website 
vanchutr

Joined: 05 Aug 2006
Posts: 427

PostPosted: Tue 11 Jan 2011, 09:38    Post_subject:  

1. Aim: Bump kernel 2.6.31.14 in (of) Wary 500 to Puppy 432 (kernel 2.6.30.5)
2. Progress steps
(a). Run (boot) Puppy 432
(b). Copy pup-432.sfs to pup-0432.sfs and open pup-0432.sfs
(c). Copy all in opened pup-0432.sfs in any place (e.g /tmp/sq) (in an ext2 partition)
(d). umount pup-0432.sfs (and you can delete pup-0432.sfs)
(e). Open /tmp/sq and delete these directories: /etc/modules, lib/firware, lib/modules
(f). Open wary_500.sfs and copy these directories: /etc/modules, lib/firware, lib/modules (from wary_500.sfs to /tmp/sq)
(g). Unmount wary_500.sfs
(h). Open terminal (console) at /tmp
(i). Run: mksquashfs sq wary_500.sfs. You will get a "new wary_500.sfs"
(j). Test boot "new wary_500.sfs" with initrd.gz and vmlinuz of wary 500.
*** Some apps will be updated after boot the new wary_500.sfs

Any comments?
Thanks
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1464
Location: Malvern, Worcs, UK

PostPosted: Tue 11 Jan 2011, 14:40    Post_subject: Method #3?  

vanchutr wrote:
Any comments?
Thanks


Hi vanchutr

Looks like this is a "3rd way" or method #3??

Did it work? Did you get a working pup432 with a wary500 kernel?

Are there any advantages over the other 2 methods as you see it?

If I understand correctly you are putting the wary500 kernel into pup432 - but you get a new wary500 so its like method #1? I guess I like method #2 best so far as it maintains the correct puppy identity and it uses built in utilities from the menu - so no install of .pets and no typing into terminals.

Thanks
Peter
Back to top
View user's profile Send_private_message Visit_website 
James C


Joined: 26 Mar 2009
Posts: 5866
Location: Kentucky

PostPosted: Fri 14 Jan 2011, 01:23    Post_subject:  

I just followed the steps in the first post and made a retro Lucid 520 with the 2.6.30.5 kernel. No problems at all....posting from it now.
Really interesting thread....
Lucid-520 2.6.30.5.png
 Description   
 Filesize   67.53 KB
 Viewed   1996 Time(s)

Lucid-520 2.6.30.5.png

Back to top
View user's profile Send_private_message 
vanchutr

Joined: 05 Aug 2006
Posts: 427

PostPosted: Fri 14 Jan 2011, 02:24    Post_subject:  

Thanks to your comments, Peebee (Peter)

Quote:

Looks like this is a "3rd way" or method #3??


It is'nt a third way (it's a trick). I don't care about edit_init..

Quote:

Did it work? Did you get a working pup432 with a wary500 kernel?


I works with all apps installed in old Pupy 432 but with new kernel from Wary 500.

Quote:

Are there any advantages over the other 2 methods as you see it?


No too much. I don't use other apps (scripts). No need to install anything. You can compare with other "methods" with my trick.

Quote:

If I understand correctly you are putting the wary500 kernel into pup432 - but you get a new wary500 so its like method #1? I guess I like method #2 best so far as it maintains the correct puppy identity and it uses built in utilities from the menu - so no install of .pets and no typing into terminals.


Same effects if you test my trick. I test this trick in order: "Don't spare to much time to compile, update a new kernel while you can use a good kernel from your Puppy friends"

Thanks,
Nice days to you
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1464
Location: Malvern, Worcs, UK

PostPosted: Tue 18 Jan 2011, 17:18    Post_subject:  

James C wrote:
I just followed the steps in the first post and made a retro Lucid 520 with the 2.6.30.5 kernel. No problems at all....posting from it now.
Really interesting thread....


Hi James C - useful if you could say which Puppy gave you the 2.6.30.5 kernel - thanks.
Back to top
View user's profile Send_private_message Visit_website 
peebee


Joined: 21 Sep 2008
Posts: 1464
Location: Malvern, Worcs, UK

PostPosted: Tue 18 Jan 2011, 17:30    Post_subject: Fluppy 011 with Wary 500 kernel  

I've put the Wary 500 kernel into Fluppy 011:

Method #1 and Method #3 both worked OK but with Method #2 the XServer would not start (neither Xorg or XVesa) - so there is at least one scenario where Method #2 has problems - Fluppy 011 is not a Woof Puppy as I understand it but is based on Puppy431 but with a kernel that is actually newer than Wary500 so not sure why there might be Xserver problems....also the RemasterPup in Fluppy seems to be a little different than the Lupu520 version.

I've also put the spup055 kernel into lupu520 for my Thinkpad 600E - runs OK in just 196MB ram and gives me wifi capabilities.
Back to top
View user's profile Send_private_message Visit_website 
James C


Joined: 26 Mar 2009
Posts: 5866
Location: Kentucky

PostPosted: Tue 18 Jan 2011, 18:06    Post_subject:  

peebee wrote:
James C wrote:
I just followed the steps in the first post and made a retro Lucid 520 with the 2.6.30.5 kernel. No problems at all....posting from it now.
Really interesting thread....


Hi James C - useful if you could say which Puppy gave you the 2.6.30.5 kernel - thanks.


I used the kernel from ttuuxxx's latest 4.32..... it had more drivers so the resulting 5.20 ended up at 138 mb.
Back to top
View user's profile Send_private_message 
sc0ttman


Joined: 16 Sep 2009
Posts: 2385
Location: UK

PostPosted: Sat 22 Jan 2011, 13:09    Post_subject:  

James C, peebee and vanchutr,

Did you follow the steps which include replacing DISTRO_SPECS in the initrd.gz file?

Or did you simply rename your new sfs to that of the original kernel puppy?

Using the remasterpup method, I cannot get my new iso to find any puppy/wary .sfs if I edit the DISTRO_SPECS in initrd.gz.
I must always rename it to the filename of the kernel puppies sfs file, and not edit DISTRO_SPECS

_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1464
Location: Malvern, Worcs, UK

PostPosted: Sat 22 Jan 2011, 14:07    Post_subject:  

sc0ttman wrote:
James C, peebee and vanchutr,

Did you follow the steps which include replacing DISTRO_SPECS in the initrd.gz file?


Hi sc0ttman

No - I didn't do this step

Quote:
Or did you simply rename your new sfs to that of the original kernel puppy?


this is what I did for methods 1 & 3

Quote:
Using the remasterpup method, I cannot get my new iso to find any puppy/wary .sfs if I edit the DISTRO_SPECS in initrd.gz.
I must always rename it to the filename of the kernel puppies sfs file, and not edit DISTRO_SPECS


Using method 2 remasterpup it didn't seem that any changes to DISTRO_SPECS were needed either in the /etc version or elsewhere.

Cheers
Peter
Back to top
View user's profile Send_private_message Visit_website 
James C


Joined: 26 Mar 2009
Posts: 5866
Location: Kentucky

PostPosted: Sat 22 Jan 2011, 14:14    Post_subject:  

sc0ttman wrote:
James C, peebee and vanchutr,

Did you follow the steps which include replacing DISTRO_SPECS in the initrd.gz file?

Or did you simply rename your new sfs to that of the original kernel puppy?


I did replace DISTRO_SPECS in the initrd.gz and did not rename the sfs. Burned a cd and worked fine. Smile
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1464
Location: Malvern, Worcs, UK

PostPosted: Sat 19 Feb 2011, 05:37    Post_subject: Success report: Fluppy013 on Wary510  

Success report:

Just to report that I've put the wary504 kernel into fluppy013 and it works well on my HP550 laptop - gives me agere modem support (from wary) and hibernate to ram (from fluppy) both of which are very useful when away from home. Frisbee is also good at finding wireless connections if these are available.

I used Method #1 but a wrinkle is that as wary504 comes in 2 parts with a zdrv .sfs then the sfs edit is a bit simpler (no need to copy /lib/firmware as this is in the wary zdrv file).

A point of interest (maybe) is that the previous version of wary (wary503) which Barry implemented with his simple .sfs names wouldn't work for me - so lets hope he's droppped this idea.

[edit]wary510 is now out and Barry has reverted to a single .sfs with the original "version" names - fluppy013 with the wary510 k2.6.32.28 kernel works great using Method#1. [/edit]

Cheers
Peter
screenie.png
 Description   
 Filesize   167.81 KB
 Viewed   802 Time(s)

screenie.png

Back to top
View user's profile Send_private_message Visit_website 
peebee


Joined: 21 Sep 2008
Posts: 1464
Location: Malvern, Worcs, UK

PostPosted: Wed 05 Oct 2011, 15:12    Post_subject:  

Just to report that I was able to switch the kernels for both

lupu528

and slacko4.99.7

today to use the kernel from wary5.1.103 using method #1

so that my Agere HDA modem could be used in both these puppies

See screen shot attached.

Cheers
Peter
screen.png
 Description   
 Filesize   147 KB
 Viewed   1220 Time(s)

screen.png


_________________
LxPup-14.10 = Puppy + LXDE
Back to top
View user's profile Send_private_message Visit_website 
ozsouth

Joined: 01 Jan 2010
Posts: 143
Location: S.E Australia

PostPosted: Mon 16 Jan 2012, 04:31    Post_subject: LuRa52  

Using basically method 1, I've inserted Racy 522's 3.0.7 PAE kernel into Lupu 528.
Extra steps:- I also inserted Racy's /etc/DISTRO_SPECS, and via ISOMaster, replaced Racy's .sfs with renamed, edited one from Lupu, creating LuRa52.iso
Can now access over 3Gb ram, with Lupu's stability & familiarity.

*** NOTE:- if you try opening .sfs files in ROX with the new iso, you'll get a version error. Can still open them in Edit-SFS. ***
LuRa52.jpg
Description 
jpg

 Download 
Filename  LuRa52.jpg 
Filesize  32.27 KB 
Downloaded  442 Time(s) 
Back to top
View user's profile Send_private_message 
ozsouth

Joined: 01 Jan 2010
Posts: 143
Location: S.E Australia

PostPosted: Thu 19 Jan 2012, 08:06    Post_subject: LuSl  

Inserting Slacko-531-PAE-HIGHMEM's 2.6.39.4 kernel into Lucid 529, using same method as previous post, is even better. SFS's now openable via ROX.
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 2 of 7 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » House Training » HOWTO ( Solutions )
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0943s ][ Queries: 12 (0.0114s) ][ GZIP on ]