Yes please.James C wrote:I went ahead and uploaded pup 301-k-2.6.25.16.iso .......if interested I'll supply the link.
How to switch kernels between Puppy versions
-
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
http://www.smokey01.com/JamesC/vintage/ ... .25.16.isoMercedes350se wrote:Yes please.James C wrote:I went ahead and uploaded pup 301-k-2.6.25.16.iso .......if interested I'll supply the link.
http://www.smokey01.com/JamesC/vintage/ ... 5.16%20md5
As I noted, Pmount doesn't work and I honestly didn't try to fix it. Everything else appeared fine in some quick testing.
-
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
For the sake of discussion, "What is in the puppyversion file for 3.01retro - is it 301 or 301retro or ... ?"James C wrote:EDIT:
Almost forgot...... while the sfs is unsquashed edit /etc/puppyversion/ to "412" instead of "301". This version shows as 412 but its still 301 just with the newer kernel..... posting from it now.
Thank you for the upload info.
Someone?nic007 wrote:Okay. Switched the puppy 5390 kernel to puppy 412 and then converted to 4sfs. Everything works fine except for the timezone, date and time. Wouldn't accept/save the customized correct settings, keep on changing after every reboot. Any ideas to fix it? Settings appear to be incorrect in the base file.
Still looking for an answer to this. If I change the timezone at bootup the screen flickers and the correct time appears. Is there a script that can run at start-up to set the clock correct automatically? I'm at GMT +2. Thanks
Polarpup now rides a Racy 5.3
- Attachments
-
- kernel.jpg
- (63.33 KiB) Downloaded 346 times
Last edited by Pelo on Wed 07 May 2014, 21:01, edited 3 times in total.
I couldn't resist any longer and tried jrb's kernel transplant method on pup-431bcm4312v3, which is approaching its 4th anniversary on my Lenovo S12. All goes well except that if I keep the savefile by renaming pupsave.2fs to warysave.2fs, I can't establish a wireless connection (Failed command: ifconfig wlan0 up). Wary and hybrid with no savefile connect immediately using b43. 431 used wl. In the end, I started over with a new savefile, which was probably a good thing anyway, and have had no further problems.
Can someone explain how something in my savefile would prevent the drivers in the new kernel from working properly?
P.S. The reason for kernel change was lack of a driver for my particular SD card reader in the 2.6.30.5 kernel; also gained the ability to mount late-model sfs files.
Can someone explain how something in my savefile would prevent the drivers in the new kernel from working properly?
P.S. The reason for kernel change was lack of a driver for my particular SD card reader in the 2.6.30.5 kernel; also gained the ability to mount late-model sfs files.
mikeb,
All the later pups connect my broadcom wireless with b43, but jrb used wl in his custom 431. wl is not in the wary kernel. So where in the savefile is the wl module specified? I tried deleting the /etc/network-wizard folder. When I run the wizard and load b43, why doesn't that override whatever is in the savefile?
Yeah, I forgot to mention my indigestionpatching the kernel caused indigestion
All the later pups connect my broadcom wireless with b43, but jrb used wl in his custom 431. wl is not in the wary kernel. So where in the savefile is the wl module specified? I tried deleting the /etc/network-wizard folder. When I run the wizard and load b43, why doesn't that override whatever is in the savefile?
Don't know if it helps - but wl is available for Wary5.5 at:Wognath wrote: wl is not in the wary kernel.
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
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
@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
@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
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
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
Hi WognathWognath wrote: but I still getCode: Select all
failed to raise interface wlan0 failed command was : ifconfig wlan0 up Error returned was ifconfig: SIOCSIFFLAGS: No such file or directory
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.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
peebee, you hit the nail on the head. dmesg output includesthe firmware loading mechanism did change between Puppy editions and kernels - if you look in dmesg there may be missing firmware error messages?
Code: Select all
b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
Thanks to both of you for the help.With kernel changes come mysteries beyond our comprehension
SFS load on the fly
"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 ?
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 ?
-
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
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
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: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
http://lx-pup.weebly.com/upup-unicorn.html
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64