How to switch kernels between Puppy versions

How to do things, solutions, recipes, tutorials
Post Reply
Message
Author
User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#91 Post by peebee »

Wognath wrote: wl is not in the wary kernel.
Don't know if it helps - but wl is available for Wary5.5 at:

http://www.murga-linux.com/puppy/viewto ... 360#609360

wl works fine for all latest Puppies and latest kernels up to and including 3.10....for me
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

Wognath
Posts: 423
Joined: Sun 19 Apr 2009, 17:23

#92 Post by Wognath »

@mikeb,
I've tried a few more things with this, and I'm none the wiser. ssb is not blacklisted. I have removed from the old savefile everything that I thought related to networking, but I still get

Code: Select all

failed to raise interface wlan0
failed command was : ifconfig wlan0 up
Error returned was ifconfig: SIOCSIFFLAGS:  No such file or directory
@peebee
Thanks. I found your awesome collection of wl pets and used several while I was fooling around with different kernels. My wireless connects with b43 in later kernels, but apparently something in the original 431 savefile is interfering, whether b43 or wl.

Ok, back to making tamales :P

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#93 Post by peebee »

Wognath wrote: but I still get

Code: Select all

failed to raise interface wlan0
failed command was : ifconfig wlan0 up
Error returned was ifconfig: SIOCSIFFLAGS:  No such file or directory
Hi Wognath

That error usually means firmware can't be found - and the firmware loading mechanism did change between Puppy editions and kernels - if you look in dmesg there may be missing firmware error messages?

You will need to make sure that the firmware is present and is located in the correct place.

Cheers
peebee
Last edited by peebee on Mon 23 Dec 2013, 16:21, edited 1 time in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#94 Post by mikeb »

With kernel changes come mysteries beyond our comprehension.... saying from ancient greece....

mike

Wognath
Posts: 423
Joined: Sun 19 Apr 2009, 17:23

#95 Post by Wognath »

the firmware loading mechanism did change between Puppy editions and kernels - if you look in dmesg there may be missing firmware error messages?
peebee, you hit the nail on the head. dmesg output includes

Code: Select all

b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
In Wary, this file is in /lib/modules/all-firmware/b43/lib/firmware/b43. Creating a symlink to that folder in /lib/firmware solves the problem and allows wireless to connect! I still don't understand what it is about the savefile that causes puppy to look in the wrong place...
With kernel changes come mysteries beyond our comprehension
Thanks to both of you for the help.

Pelo

SFS load on the fly

#96 Post by Pelo »

"But as the poster has pointed out, there are major differences between puppy series 3 and 4 so will be very surprised if the kernel switch will work in this instance. Why don't you try switching puppy 412 kernel with something later like a Wary Puppy?"
At home, the process fails with puppies series 3 and 4
I use SFS load on the fly , and load the SFS of the old Puppy, all the applications become available inside the installed recent Puppy.
Is that forbidden ?
What does 'underdog' mean in Boot options (PF3) ? is it similar as load on the fly ?

Mercedes350se
Posts: 790
Joined: Wed 16 Apr 2008, 11:28

#97 Post by Mercedes350se »

I finally downloaded James C's .iso (link on the previous page) and burnt it to CD. It seems to work well - I haven't spent a lot of time on it though - it is very cold here in the control room!

Mark_C
Posts: 44
Joined: Sat 28 Aug 2010, 16:36

#98 Post by Mark_C »

I wanted to use lxpup14 but its kernel is to old to work for my network card.
So I used unicornpup which does work with my network card and followed the directions in the first post.
Everything was looking good on boot until it tried to start x which it couldn't do, I ran xorgwizard and it finds the right resolution but x still doesn't start.

Now both lxpup 14 and unicornpup boot no problem and x starts without a problem in their original form.
I even tried deleting etc/x11 and replacing it with the one from unicorn but still x doesn't start.
Hoping someone has an idea what the problem could be.


Mark

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#99 Post by mikeb »

Well not sure how matched xorg and the kernel need to be when kernel mode setting is used. Intel video?

What network card.... ? Might be a driver built for the older kernel around. mountains and Mohammad stuff...

mike

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#100 Post by peebee »

Mark_C wrote:I wanted to use lxpup14 but its kernel is to old to work for my network card.
So I used unicornpup which does work with my network card and followed the directions in the first post.
Everything was looking good on boot until it tried to start x which it couldn't do, I ran xorgwizard and it finds the right resolution but x still doesn't start.

Now both lxpup 14 and unicornpup boot no problem and x starts without a problem in their original form.
I even tried deleting etc/x11 and replacing it with the one from unicorn but still x doesn't start.
Hoping someone has an idea what the problem could be.


Mark
Maybe try LxPupUnicorn15.02:
http://lx-pup.weebly.com/upup-unicorn.html
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

Mark_C
Posts: 44
Joined: Sat 28 Aug 2010, 16:36

#101 Post by Mark_C »

Yes it is intel video.
I believe the network card is Atheros AR9565
It uses ath9k in slacko 5.7.0 but ath9k doesn't do any thing for it in lxpup14

Mark_C
Posts: 44
Joined: Sat 28 Aug 2010, 16:36

#102 Post by Mark_C »

peebee wrote:
Mark_C wrote:I wanted to use lxpup14 but its kernel is to old to work for my network card.
So I used unicornpup which does work with my network card and followed the directions in the first post.
Everything was looking good on boot until it tried to start x which it couldn't do, I ran xorgwizard and it finds the right resolution but x still doesn't start.

Now both lxpup 14 and unicornpup boot no problem and x starts without a problem in their original form.
I even tried deleting etc/x11 and replacing it with the one from unicorn but still x doesn't start.
Hoping someone has an idea what the problem could be.


Mark
Maybe try LxPupUnicorn15.02:
http://lx-pup.weebly.com/upup-unicorn.html
Does that version use the gslapt package manager?

User avatar
8Geee
Posts: 2181
Joined: Mon 12 May 2008, 11:29
Location: N.E. USA

Sticky this please

#103 Post by 8Geee »

I just started reading this thread, and am very surprized this is not a sticky. Considering the current 2015 state of all things Puppy, I'll ask for this thrread to be made sticky.

TIA
Linux user #498913 "Some people need to reimagine their thinking."
"Zuckerberg: a large city inhabited by mentally challenged people."

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#104 Post by peebee »

Mark_C wrote: Maybe try LxPupUnicorn15.02:
http://lx-pup.weebly.com/upup-unicorn.html

Does that version use the gslapt package manager?
Sorry - no.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

Mark_C
Posts: 44
Joined: Sat 28 Aug 2010, 16:36

#105 Post by Mark_C »

peebee wrote:
Mark_C wrote: Maybe try LxPupUnicorn15.02:
http://lx-pup.weebly.com/upup-unicorn.html

Does that version use the gslapt package manager?
Sorry - no.
I decided to try again using slacko 5.7.0 pae and it worked this time, posting from it now.
I have been curious about this version he made it seems pretty innovative.
Thank you for your replies.

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

switch kernels to Puppies with separate zdrv_xxx.sfs

#106 Post by charlie6 »

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... :cry:

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 :)
Charlie

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#107 Post by mikeb »

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

User avatar
jrb
Posts: 1536
Joined: Tue 11 Dec 2007, 19:56
Location: Smithers, BC, Canada

Re: switch kernels to Puppies with separate zdrv_xxx.sfs

#108 Post by jrb »

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... :cry:

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 :)
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? :? 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.

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#109 Post by charlie6 »

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... :cry:

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

Cheers, Charlie

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#110 Post by mikeb »

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

Post Reply