(old)Puppy Linux Discussion Forum

I put the slax 6 kernel on puppy 4.12. Works nicely though those analogue modems can be a problem as puppy has some script jiggling to implement the drivers...ie such a modem is detected (or not...it always wants to load slmodem cos there is an Intel sound card!!!!), that unpacks driver, binary, init script, firmware ...in theory a change of kernel should not affect this but its one to watch out for (new kernel may not include needed driver for example). Or in my case I have a router so quietly ignore any potential issues as I cannot test it

Also watch for kernel changes... eg splitting up the usbhid drivers forced a major hack in the initrd. Plus /sys and /proc locations get moved around so may upset scripts.

top tips from top tip land

mike

Ya Lucid is a fantastic pup. Only problem is that I can't record from the Audio Line-In on my iMac because the kernel doesn't support it. The kernel in Precise 5.7 does so I think I will play around and see if I can get 5.2.8 working with the Precise 5.7 kernel.

jrb wrote:


Open Edit-SFS from the Utility menu.

1. Extract lupu-511.sfs from lupu-511.iso. Click on the .iso and when it opens in rox drag lupu-511.sfs to the edit-sfs window.

2. When the edit window opens up delete /etc/modules/, /lib/modules/ and /lib/firmware/.

3. Click on wary-060.iso. Click on wary-060.sfs to mount it. Drag /etc/modules/, /lib/modules/ and /lib/firmware/ from wary-060.sfs into the edit window and copy them in. (Make sure they end up in the right place!)

Build the new lupu-511.sfs.

In my case, I am trying to upgrade the kernel in puppy 528 with the one in precise 5.7.1.

I am stuck on step 3. I have the precise iso on my desktop, I click on it to open but when I click on the puppy_precise_5.7.1.sfs file, it doesn't mount. I get a failed mounting or unmounting error. What am I doing wrong?

I am stuck on step 3. I have the precise iso on my desktop, I click on it to open but when I click on the puppy_precise_5.7.1.sfs file, it doesn't mount. I get a failed mounting or unmounting error. What am I doing wrong?

change in squashfs version/format at a guess...its not generally backward compatible.

My technique is usually to build a tree of the files then make an sfs of it in the target version... that way it can be tested and tweaked assuming you get puppy to load it at boot. (set in boot manager then point to new kernel/initrd in boot menu at a guess)

mike

It may be not the squashfs version, but the type of squashfs compression ( gz or xz ) .

The kernel should support squashfs xz compressed since version 2.6.38 .

Lupu default kernel is version 2.6.33.2 and THD I think 2.6.37.6 -- both would not support xz-squash .

http://www.murga-linux.com/puppy/viewtopic.php?t=67123

Would this be useful for kernel switching ?

Luci to Racy : the whole process runs fine, I enjoy that !
the only problem is the save file : saved in lucisave, but not found at reboot by Racy, sorry Lucid.
AaaaH, just the little thing that is wrong. Could you help ? Merci.

One hour later : I Change savefilename from lucisave to racysave in sda2 and that is ok ! i will confirm at shutdown . Nice, very nice.
And the distro reboots on the racysave. I added the necessary flasplayer, you tube shows me the movies with the sound. Racy has provided the adequate drivers. But all that is wonderfull.

If you dont want to run frugal install, type puppy pdev1=sdb1 (or other) to run distro from yr usb stick.

FYI Lucid couldnt connect wireless on my computer. Racy does.

FYI Lucid couldnt connect wireless on my computer. Racy does.

It did not have a suitable driver you mean.. its relatively easy to build them . Replacing a whole kernel for the sake of one driver is part of linux madness ...

But who cares

mike

Wireless driver : can you tell us more about that ? I have been searching for ... years (3, 4 years).
Very happy that switching kernels solve the problem. But you are right, it's not the easiest way, sure.

Hi pelo...

sorry not aimed at you really...
for you it should have been a case of you posting your wifi card details and a driver being built for you....but thats really out of the scope of this thread.
But perhaps if you encounter a similar problem in the future then you may find an easier path..

Driver sources are usually found at the manufacturers site if they support linux well.. eg ralink...then a devx file and kernel sources for the particular puppy..... it actually takes more time to gather the files than actually build the driver... and if you are not confident there should be someone around who is able to help you here.

regards

mike

Here above i thank you for frugal install of a Luci-005 ( iso remasterized with Racy 5.3).

I want to go one step forward by using the second method with lupu 528 (spanish nite flux box) installed on USB stick.
Unfortunately i have no more wireless connection and sound than with the original Lupu.
Kernel 3.0.25 well installed. But no kernel modules listed in hardinfo hardware info
Distro spec are lupu's ones.
FYI intel chipset 1048086 not recognized by 915 resolution : could this explain that ?
Strange : sda3 is mounted (my HD linux partition). I am still with frugal install ?
2nd info : pupsave size : 1MB ?!!! solved by using pet pupsaveconfig 2.2.2

Distro now works fine with wireless and sound. I have only burn the iso on the usb stick via puppy univeral installer. All is fine, even the savefiles ( reboot well loads the pupsave found in the USB stick.
Kernel is 3.0.25 (Racy 5.3).
Ah, the creator has issued a nite fluxbox based on Precise... zut !
But now, i know how to proceed.

I want puppy 3.01 with the kernel from 4.1.2.

I copied the 301 files, except the pup_301.sfs and the zdrv_301.sfs, to the puppy301 folder on partition 2.

I copied the pup_412.sfs into the same folder and renamed it to pup_301.sfs.

Amended the menu.lst to suit.

Tried to boot but get a message saying that pup_301.sfs cannot be found.

Looked inside the renamed pup_301.sfs and amended, in two files, 412 to 301.

Rebooted but get the same message. What do I need to do?

There's much more to it than that; read jrb's initial post closely.
(I wouldn't try that combo anyway; too many differences.)

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

Dewbie wrote:(I wouldn't try that combo anyway; too many differences.)

Is there anywhere I could read up on what would need to be done?

Mercedes350se wrote:

Dewbie wrote:(I wouldn't try that combo anyway; too many differences.)

Is there anywhere I could read up on what would need to be done?

Don't know anything about puppy 3 because I have never used it. I will explain the steps to you as simple as possible but first do the following and let me know the results:
1) Download editsfs.pet and install it on puppy 3. Are you able to install it and make it run from the menu?
2) Whilst in puppy 3, click on puppy 412.sfs file and see if it mounts?
That's all for now, let me know

EDIT: Forget about the above and let's do it on puppy 412 which I am more familiar with:
1) Boot Puppy 412 and install the editsfs.pet. Restart JWM and you should see Editsfs in the menu.
2) Run editsfs. Drag and drop the Puppy 3.sfs file to editsfs and click OK. The next screen will ask you for the location of the conversion which should be in a linux partition or Ramdisk About 1GB should be available to be safe. Choose the location for the conversion (I had a save file with about 1GB free space to use so I selected /root) and click ok.
3) Editsfs will now open the puppy 3.sfs file to edit. There will also be a window which says build, this you select AFTER you had done your editing so leave it open. With the puppy 3.sfs file open, delete the following folders: modules in etc (/etc/modules) ; modules firmware and network folders in lib. Leave sfs open for further editing..
4) Click file on your desktop to open your running filesystem of puppy 412. Click back arrow to get to /. Now copy the above named folders found in the same locations in puppy 412 from 412 to puppy 3.sfs edit file. Make sure it goes to the same locations ie: /etc/modules to /etc/modules and the lib folders to lib. Editing of the puppy 3.sfs is now finished so click build in the window. Editsfs will now rebuild the puppy3.sfs file and place the edited file in the location you have chosen when finished.
5) Your puppy 3.sfs. File now has a 412 kernel. Now rename this file to pup_412xxx.sfs. Xxx being the string you want to attach like pup_412hybrid.sfs For frugal install, place this file together with vmlimuz and initrd of puppy 412 in partition you want to boot from, edit menu1st and see if it works. Good luck

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?

nic007 wrote:1) Download editsfs.pet and install it on puppy 3. Are you able to install it and make it run from the menu?
2) Whilst in puppy 3, click on puppy 412.sfs file and see if it mounts?
That's all for now, let me know
............
Why don't you try switching puppy 412 kernel with something later like a Wary Puppy?

The pet installs and seems to run - a window opens and asks for a path to be input or a file to be dragged and dropped..

Putting in the path to the 412.sfs and selecting ramdisk - I have plenty of RAM - I get the message to the effect that the filesystem is 3.1 but only 2.x and 3.0 is supported.
The puppy 412.sfs will not mount by clicking on it either using puppy 3.

I have 5.2.8 installed - do not like it all that much though - but it will not mount either 301 or 412 .sfs'.

It is beginning to look as though I will have to get to like my 4.1.2 install. The reason why I wanted to switch kernels is that I really like 3.01 but it does not support SATA drives which I hope to use in this machine build.

Mercedes350se wrote:

nic007 wrote:1) Download editsfs.pet and install it on puppy 3. Are you able to install it and make it run from the menu?
2) Whilst in puppy 3, click on puppy 412.sfs file and see if it mounts?
That's all for now, let me know
............
Why don't you try switching puppy 412 kernel with something later like a Wary Puppy?

The pet installs and seems to run - a window opens and asks for a path to be input or a file to be dragged and dropped..

Putting in the path to the 412.sfs and selecting ramdisk - I have plenty of RAM - I get the message to the effect that the filesystem is 3.1 but only 2.x and 3.0 is supported.
The puppy 412.sfs will not mount by clicking on it either using puppy 3.

I have 5.2.8 installed - do not like it all that much though - but it will not mount either 301 or 412 .sfs'.

It is beginning to look as though I will have to get to like my 4.1.2 install. The reason why I wanted to switch kernels is that I really like 3.01 but it does not support SATA drives which I hope to use in this machine build.

Hi, check my above edited post and good luck. Puppy 5 uses squash file system 4 and puppies before Puppy 431 uses squash file system 3 so an sfs file need to be converted either way depending on using an older or newer puppy.

swapping the initrd is not really such a good idea.. and indeed that would cause problems as the init boot script would not work well with puppy 3 plus it uses cpio not rootfs...these initrds are not as portable as they appear.

The better way would be to edit the 3.01 initrd and replace the modules in /lib.... with the ones from puppy 4.12 initrd.

Also rather than edit the whole puppy filesystem why not make an sfs of the new kernel modules from 4 only making sure the sfs is built using puppy 3 for sfs compatibility. It can then be loaded (no bootmanager crap in 3 i think...just match the name) and remastered in later on.

The only other problem that comes to mind is in kernel 2.6.25 and newer ssb is needed for uhci or ohci...ie usb 1 which is crap but you have to live with it so if ssb is not loaded additionally in the initrd usb1 won't work....this of course conflicts with such as the broadcom sta wifi driver. (one reason I went to a slax kernel plus that also give SMP and SATA with EIDE support)

breasts

mike