huge-kernels for woof-ce puppies

Core libraries and systems
Message
Author
User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#16 Post by peebee »

Terry H wrote:Hi peebee, Just a question on how to determine if the kernels in your lxpup Huge Kernel archive are 64 bit or 32 bit. You have stated that 64 bit kernels are usable in 32 bit puppies, but they don't appear to be identified as 32 or 64 bit kernels. In particular, is the 4.9.56 kernel 64 bit.
Thanks in advance.
Terry
Ahh - good spot - no 64 bit there at the moment - all 32 bit...

64-bit are at:
http://smokey01.com/peebee/slackocurrent/kernel/
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#17 Post by Sailor Enceladus »

ally wrote:I have been trying to change kernels in xenialpup64 without success (lenovo x230 no hotkey controls - 4.4.35 in fatdog64_710 work fine)
I switched mine to huge-3.14.54-tahr_64.tar.bz2 right off the bat from here:
http://distro.ibiblio.org/puppylinux/huge_kernels/

I didn't create a savefile yet so all I had to do was rename the vmlinuz-3.14.54 to vmlinuz and kernel-modules-3.14.54 to zdrv_xenial_7.0.8.4.sfs to replace over the old ones, then reboot, and it said 3.14.54 and my wifi worked again.

I think if you already created a savefile it's better to type change_kernels in the terminal and use that way to switch kernels, or maybe using that way is the same now.

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#18 Post by belham2 »

Sailor Enceladus wrote:
ally wrote:I have been trying to change kernels in xenialpup64 without success (lenovo x230 no hotkey controls - 4.4.35 in fatdog64_710 work fine)
[b]I switched mine to huge-3.14.54-tahr_64.tar.bz2 right off the bat[/b] from here:
http://distro.ibiblio.org/puppylinux/huge_kernels/

I didn't create a savefile yet so all I had to do was rename the vmlinuz-3.14.54 to vmlinuz and kernel-modules-3.14.54 to zdrv_xenial_7.0.8.4.sfs to replace over the old ones, then reboot, and it said 3.14.54 and my wifi worked again.

I think if you already created a savefile it's better to type change_kernels in the terminal and use that way to switch kernels, or maybe using that way is the same now.

Hi Sailor,

Can I ask why? Do you find the 3.14.54 (54 or did you mean 56?) runs better on your stuff (is it older, like mine, say 7-10 years). I've got two 'frugal' 64-bit Xenials running, one from Battleshooter (with his XFCE), and one built from woof-CE several weeks ago, Sometimes, stuff is really responding slow in Xenials (and other pups) that I have the newer kernels, I noticed especially when things went up to the 4.9.# area, my 'frugal' installs on different computers in the house weren't responding as fast as, say, compared to my 'frugal-install' of Phils old 64-bit Tahr64-6.05., which still runs stuff noticeably quicker.

I am really intrigued that, from what Peebee said today, the 4.4.# series is going to be supported for like 4 or 5 more years.

I wonder if that would provide a good middle ground for someone in my situation? Thing is, I know or think the newer kernels give us access to so much more when installing stuff and compiling (maybe that's a wrong assumption, I don't know), so I wouldn't want to----as they say---cut my hands off to spite my face.

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#19 Post by ally »

confused, what's the difference between a kernel from kernel.org and a huge-kernel?

:)

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

#20 Post by peebee »

ally wrote:confused, what's the difference between a kernel from kernel.org and a huge-kernel?
:)
The source comes from kernel.org....

Kernel-kit in woof-ce compiles that source according to a config, adding aufs and ensuring that vmlinuz has the drivers necessary to boot and packages it as a zdrv .sfs
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#21 Post by ally »

thanks, I understood source.....!

100gig of kernels going up to archive now, few more sources to chase down when it's finished

:)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#22 Post by musher0 »

ally wrote:thanks, I understood source.....!

100gig of kernels going up to archive now, few more sources to chase down when it's finished

:)
Indeed, a huge amount of huge kernels!!! Mind-boggling...
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#23 Post by ally »

just kernels at the mo, hunting ongoing

:)

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

#24 Post by peebee »

64-bit Kernel 4.14.0 - 1st release of the latest LTS kernel.....needs an fdrv....can also be used with 32-bit pups as long as your cpu is 64-bit capable.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

Re: huge-kernels for woof-ce puppies

#25 Post by sheldonisaac »

Hi, please excuse; I did an Internet search for: explain huge kernels
No luck.

What are they, and why would I use them? (And while we're at it, how to use them)

Thanks a lot.
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#26 Post by musher0 »

HI Sheldon.

Thje expression "huge kernel" was coined by Puppy's new top dog, Micheal Amadio,
aka 01micko, a few years ago. It's "huge" in the sense that it brings together in an
archive the kernel proper plus several other essential elements, as explained by
peebee above:
http://murga-linux.com/puppy/viewtopic. ... ost#972043

It's a Puppy "feature". Other distros do not do that, at least not like we do it.

IHTH.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

#27 Post by sheldonisaac »

musher0 wrote:HI Sheldon.

Thje expression "huge kernel" was coined by Puppy's new top dog, Micheal Amadio,
aka 01micko, a few years ago. It's "huge" in the sense that it brings together in an
archive the kernel proper plus several other essential elements, as explained by
peebee above:
http://murga-linux.com/puppy/viewtopic. ... ost#972043

It's a Puppy "feature". Other distros do not do that, at least not like we do it.

IHTH.
OK, thank you. Do ordinary users like me need concern ourselves with these packages?
(I had used Puppys like 214X (by ttuuxx), Lucid by playdayz and now rerwin, some slackos, and recently tahr, and now will be using your Xenial as my everyday OS)
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#28 Post by musher0 »

Nope! :D
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
mikeslr
Posts: 3890
Joined: Mon 16 Jun 2008, 21:20
Location: 500 seconds from Sol

Couple of Questions

#29 Post by mikeslr »

Hi All,

I noticed that some of the packages appearing @ http://archive.org/download/Puppy_Linux_Kernels have a "pfs" ending, such as 000-kernel-3.13.0-24-generic.sfs.pfs. What are they? How are they used?

peebee has kindly made 64-bit Kernel 4.14.0 available. Link a couple of posts above this one. I note that 4.14 has been designated as being Long Term Support, and is one of the first kernels for which patches against the meltdown and spectre vulnerabilities are being developed. Taking into consideration that an fdrv.sfs is required (which peebee has also made available) and that not all Puppies are "fdrv aware", can these be used in Puppies other than LxPup?

mikesLr

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#30 Post by ally »

russian version of sfs from puppyrus-a repos

they can just be renamed .sfs

:)

edit: dedicated page for huge kernels here: http://archive.org/details/Puppy_Linux_Huge-Kernels

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

Re: Couple of Questions

#31 Post by peebee »

mikeslr wrote:Taking into consideration that an fdrv.sfs is required (which peebee has also made available) and that not all Puppies are "fdrv aware", can these be used in Puppies other than LxPup?

mikesLr
Hi Mike

Short answer=yes. Longer answer - if fdrv is not automatically loaded by init (only likely in very old pups) then you could try explicitly loading it as an .sfs assuming that it isn't needed on the very first boot to get a basic system running.....as always in pupland - try it and see :wink:

Otherwise the zdrv and fdrv would need to be "combined"....

Cheers
peebee
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
mikeslr
Posts: 3890
Joined: Mon 16 Jun 2008, 21:20
Location: 500 seconds from Sol

#32 Post by mikeslr »

Thanks peebee,

Probably could have used your first suggestion, but your second method worked fine with Xenialpup64.

Ally, changing the "pfs" ending to "sfs" does, in fact, enable their contents to be viewed and perhaps used with non-Russian-built Puppies. However, I have some doubts about the later. An examination of the included files revealed several with suffixes I'm not familiar with from my dissection of other Puppies and applications.

I didn't test, nor expend the time which would have been necessary to ascertain how those files functioned within their system.

mikesLr

ozsouth
Posts: 858
Joined: Fri 01 Jan 2010, 22:08
Location: S.E Australia

#33 Post by ozsouth »

I've made a 64bit Slacko compatible 4.9.94 kernel via Puppy kernel-kit, with the cutdown firmware option. Is Spectre/Meltdown mitigated.
Adding needed firmware to (or using another) fdrv will be helpful. Uses performance cpu governor by default (max speed).
Have swapped it into Slacko64 6.9.9.9 and LxpupSc64 18.03. Works ok in both. As usual, use at own risk.

Kernel: http://archive.org/download/Puppy_Linux ... 64.tar.bz2
md5: a84bf520693321ffa78062fe9335097e huge-4.9.94-s64.tar.bz2

Sources: https://archive.org/download/Puppy_Linu ... 94-s64.sfs
md5: 25c7d6be2f67188d98b7e2f3e339f94b output/kernel_sources-4.9.94-s64.sfs

Thanks to ally for mirroring.
.
Last edited by ozsouth on Wed 02 May 2018, 00:03, edited 3 times in total.

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#34 Post by ally »


musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

Re: Couple of Questions

#35 Post by musher0 »

peebee wrote:
mikeslr wrote:Taking into consideration that an fdrv.sfs is required (which peebee has also made available) and that not all Puppies are "fdrv aware", can these be used in Puppies other than LxPup?

mikesLr
Hi Mike

Short answer=yes. Longer answer - if fdrv is not automatically loaded by init (only likely in very old pups) then you could try explicitly loading it as an .sfs assuming that it isn't needed on the very first boot to get a basic system running.....as always in pupland - try it and see :wink:

Otherwise the zdrv and fdrv would need to be "combined"....

Cheers
peebee
Hello, peebee, mikeslr and all.

It used to be (around the time of jrb's Puppy 4.12 / 4.21) that Puppy
would load automatically any sfs with its version number in it. (E.g.
something like openoffice_4.12.sfs, gimp_4.12.sfs, etc.) Has that capacity
been removed from the init in new Puppies?

(This is a real question, not a rhetorical one: if that capacity is still there,
it could be put to good use. Also, if this capacity is still present, combining
the fdrv with the zdrv would not be necessary.)

In any case, one could still load this fdrv sfs through sfs_load, no?

BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Post Reply