eol of linux kernel 3.14

[puppytahruser]

According to this post http://www.murga-linux.com/puppy/viewto ... 7e3#946835 linux kernel 3.14 reach to eol. So is that mean end of tahrpup, as its kernel also 3.14. Need some advise how long we can use tahrpup!!

[puppytahruser]

24 views!! but no reply!!

[watchdog]

It is not so difficult to change kernel in tahr 6.0.6... I'm using the fatdog64-700's kernel 3.18.7 because affection, because it supports using puppy as wifi hotspot, because it is fully 32 bit compatible for chroot jails, and so on. You can also use one of huge-kernels at:

http://distro.ibiblio.org/puppylinux/huge_kernels/

I think that a huge kernel from slacko should also work for tahr.

I change kernel replacing the zdrv.sfs and vmlinuz in the frugal dir.

[puppytahruser]

Thanq WD for your suggestion. how to change kernel in tahrpup?

[puppytahruser]

where i get zdrv.sfs and vmlinuz for kernel 3.16 ? which is supported till 2020.

[watchdog]

You have to choose a kernel compiled for puppy. I do not know about the kernel 3.16. To use the kernel 3.18.7 from fatdog, for example, download:

http://distro.ibiblio.org/fatdog/kernel ... sfs-3.18.7

and

http://distro.ibiblio.org/fatdog/kernel ... nuz-3.18.7

Rename the first as zdrv_tahr_6.0.6.sfs and the second as vmlinuz and replace them in the frugal dir (for the 32 bit version). I think there also is an option to change kernels in quickpet using tahr.

[puppytahruser]

Thank you WD. I will try it as you suggested.

[festus]

In lxpuptahr-15.12.1-pae, I changed kernel from: 3.14.56 to huge-4.1.30-xenial_PAE, by just renamimg the files and then replace them in the frugal dir:
kernel-modules.sfs-4.1.30-xenial_PAE to zdrv_lxtahr_15.12.sfs and
vmlinuz-4.1.30-xenial_PAE to vmlinuz

Everything is running well with the new kernel - 4.1.30

festus

[puppytahruser]

Thank you festus. I found the kernel 3.16 for tahr. replace with the old one. now its working fine.

[Mike Walsh]

Just tried festus's tip for LXTahr 15.12 myself. Now running quite happily with kernel 4.1.30. Thanks for that, mate; I knew there was a way of doing it, but I lost track of the thread from a few years ago where it described how you do all this...

Cheers!


Mike.

[festus]

Just tried festus's tip for LXTahr 15.12 myself. Now running quite happily with kernel 4.1.30. Thanks for that, mate; I knew there was a way of doing it, but I lost track of the thread from a few years ago where it described how you do all this...

Cheers!


Mike.

You're welcome, though I just used watchdog's method, from above.

bliss,
festus

[corvus]

Question, if you change kernel, for example in tahr64 6.0.5, must you also give the following command from a terminal:

Code: Select all

echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/vmlinuz
echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/zdrv_tahr64_6.0.5.sfs

to change the DISTRO_IDSTRING in the new kernel or is it useless?

[festus]

Question, if you change kernel, for example in tahr64 6.0.5, must you also give the following command from a terminal:

Code: Select all

echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/vmlinuz
echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/zdrv_tahr64_6.0.5.sfs

to change the DISTRO_IDSTRING in the new kernel or is it useless?

I forgot to mention that I did run those cmd's using the DISTRO_IDSTRING=
from the /etc/DISTRO_SPECS file.

For lxpuptahr-15.12.1-pae, I ran:

Code: Select all

echo -n t151220170718ZZZZ6.0.5XXXXXXXXXX >> /mnt/home/lxtahr15121/vmlinuz
echo -n t151220170718ZZZZ6.0.5XXXXXXXXXX >> /mnt/home/lxtahr15121/zdrv_lxtahr_15.12.sfs

All is working very well.

festus

[peebee]

Question, if you change kernel, for example in tahr64 6.0.5, must you also give the following command from a terminal:

Code: Select all

echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/vmlinuz
echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/zdrv_tahr64_6.0.5.sfs

to change the DISTRO_IDSTRING in the new kernel or is it useless?

Just to note that this requirement is no longer needed in the latest woof-ce puppies with gyro's new initrd.gz

[watchdog]

Question, if you change kernel, for example in tahr64 6.0.5, must you also give the following command from a terminal:

Code: Select all

echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/vmlinuz
echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/zdrv_tahr64_6.0.5.sfs

to change the DISTRO_IDSTRING in the new kernel or is it useless?

Please explain: what's DISTRO_IDSTRING? I never did this stuff changing kernels and it works. I think the CIA does not need the right idstrings to spy on you

[666philb]

for newer pups in a terminal type

Code: Select all

change_kernels

and follow the instructions.

lots of kernels here http://distro.ibiblio.org/puppylinux/huge_kernels/

note that changing kernels will break any extra drivers you've installed such as the nvidia graphics driver.

[corvus]

Question, if you change kernel, for example in tahr64 6.0.5, must you also give the following command from a terminal:

Code: Select all

echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/vmlinuz
echo -n t151216173205ZZZZ6.0.5XXXXXXXXXX >> /path/to/zdrv_tahr64_6.0.5.sfs

to change the DISTRO_IDSTRING in the new kernel or is it useless?

Just to note that this requirement is no longer needed in the latest woof-ce puppies with gyro's new initrd.gz

Thanks for the information peebee, I thought it was needed for a correct change of the kernel.

Please explain: what's DISTRO_IDSTRING? I never did this stuff changing kernels and it works. I think the CIA does not need the right idstrings to spy on you

I followed the following guidelines:

tahrpup allows easy changing of kernels with a few caveats.

pick a kernel, download, unzip, copy the vmlinuz & zdrv.sfs
over the installed ones and reboot.

CAVEATS:
if you've installed any kernel version dependent drivers,
such as your graphic drivers you won't be able to use the
same savefile so boot with pfix=ram.
even if you haven't installed any drivers, on some setups
you may still need to boot pfix=ram and create a new save.

if you want to use these kernels in any other puppy apart
from tahrpup-6.0, you'll need to rename the zdrv.sfs and do
the following in a terminal...

tail -c32 /path/to/puppy.sfs

this will produce an idstring, for example tahrpup-5.8.4
produces this t141012145113ZZZZ5.8.4XXXXXXXXXX which i'll
use just as an example, you will need to use your own
output.

echo -n t141012145113ZZZZ5.8.4XXXXXXXXXX >> /path/to/vmlinuz
echo -n t141012145113ZZZZ5.8.4XXXXXXXXXX >> /path/to/zdrv.sfs

so the vmlinuz & zdrv.sfs should match the puppy.sfs. you can
use the 'tail' command above to check each one.


happy swapping

available at the following link.

Greetings to all.