Kernel 5.0.1 in 64 and 32 bit versions for Puppy Linux

Message

rockedge · #1 Post by **rockedge** » Wed 13 Mar 2019, 15:54

▶—— Linux Kernel 64 bit ——◀

Kernel Release: 5.0.1
Build Date: Mon Mar 11 15:43:45 EDT 2019
Build GCC: 7.3.0
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

Kernel Command Line:
psubdir=Bionic64-v8 pmedia=atahd pfix=fsck net.ifnames=0

https://rockedge.org/kernels

▶—— Linux Kernel 32 bit ——◀

Kernel Release: 5.0.1
Build Date: Mon Mar 11 14:25:37 EDT 2019
Build GCC: 7.3.0
OS Support: GNU/Linux
Architecture: i686
SMP Enabled: Yes
PAE Enabled: Yes

Kernel Command Line:
pdrv=13ec514b-7e2d-43e1-b18e-ed4daceba563 psubdir=/BionicZM-C net.ifnames=0 pmedia=atahd pfix=fsck

https://rockedge.org/kernels

__

PipzDex · #2 Post by **PipzDex** » Fri 12 Jul 2019, 12:58

rockedge wrote:▶—— Linux Kernel 64 bit ——◀

Kernel Release: 5.0.1
Build Date: Mon Mar 11 15:43:45 EDT 2019
Build GCC: 7.3.0
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

Kernel Command Line:
psubdir=Bionic64-v8 pmedia=atahd pfix=fsck net.ifnames=0

https://rockedge.org/kernels

▶—— Linux Kernel 32 bit ——◀

Kernel Release: 5.0.1
Build Date: Mon Mar 11 14:25:37 EDT 2019
Build GCC: 7.3.0
OS Support: GNU/Linux
Architecture: i686
SMP Enabled: Yes
PAE Enabled: Yes

Kernel Command Line:
pdrv=13ec514b-7e2d-43e1-b18e-ed4daceba563 psubdir=/BionicZM-C net.ifnames=0 pmedia=atahd pfix=fsck

https://rockedge.org/kernels

__

Hi Rockedege
I'm using your kernel compilation from Precise 571 to Bionicpup 18 and works pretty well and without crash by de moment ...
Here mi specs...

rockedge · #3 Post by **rockedge** » Sat 13 Jul 2019, 20:19

Hello PipzDex!

glad it is working well and passing that information on. I am using it myself on a Bionic64-v8 system.

bigpup · #4 Post by **bigpup** » Sat 13 Jul 2019, 23:12

First, thank you for this!!

Is this providing anything new, other than support for very new hardware?
Fixing any kernel bugs, maybe?
Providing some new feature?

What is reason for net.ifnames=0?

rockedge · #5 Post by **rockedge** » Mon 15 Jul 2019, 15:48

What is reason for net.ifnames=0?

what it does is ensures that the network devices are counted starting with eth0 and wlan0.....instead of on Bionic where the ethernet device could be named much differently. I use it for testing so I know my Ethernet name and don't need to look it up. It is very optional and most people don't need to use it.

scsijon · #6 Post by **scsijon** » Mon 15 Jul 2019, 23:49

Barry has 5.1.15 out in his Easy Thread and I have 5.1.16 in my Quirky Thud thread If anyones interested.

rockedge · #7 Post by **rockedge** » Tue 16 Jul 2019, 12:24

hello scsijon

thanks for the info...I do have a machine I would like to try this kernel out with

Mike Walsh · #8 Post by **Mike Walsh** » Thu 18 Jul 2019, 13:21

@ rockedge:-

Do I take it the 'kernel-modules-sfs' is in fact the 'z_drv'? Just want clarification on this point, please.....

Mike.

mikeslr · #9 Post by **mikeslr** » Thu 18 Jul 2019, 16:46

Mike Walsh wrote:@ rockedge:-
Do I take it the 'kernel-modules-sfs' is in fact the 'z_drv'? Just want clarification on this point, please.....
Mike.

Yes. You rename it to zdrv_NAME-OF-PUPPYVERSION-NUMBER.sfs, consistent with the name of the zdrv.sfs being replaced; for example zdrv_xenialpup_7.5.sfs.

The real question is "Why isn't it produced with the name zdrv.sfs-kernel_version_number"? kernel_version_number being consistent with that shown by the vmlinuz of the package.

rockedge · #10 Post by **rockedge** » Thu 18 Jul 2019, 16:49

that is correct Mike Walsh

The real question is "Why isn't it produced with the name zdrv.sfs-kernel_version_number"? kernel_version_number being consistent with that shown by the vmlinuz of the package.

it would be great if this was an option in the kernel-kit but for use with other distros like WeeDog (firstrib) it keeps it self explantory what it is...I could see an option switch in the kernel-kit allowing an auto-renaming to fit the Puppy Linux scheme

the change_kernel tool names it for you otherwise

Mike Walsh · #11 Post by **Mike Walsh** » Thu 18 Jul 2019, 17:05

Thanks, guys. Clarification 'assimilated'....

Mike.

Mike Walsh · #12 Post by **Mike Walsh** » Thu 18 Jul 2019, 20:28

@ rockedge:-

Installed into UPupBB 32-bit. Running very smoothly so far.

One very tiny 'glitch' (?) I've noticed, towards the end of the BIOS stuff; immediately before Bionic boots, there's a new line mentioned, which I've not seen before:-

'No IRQ handler for vector (irq-1)'.

Don't have a clue what it means, though there's no degradation in performance. Just thought I'd better mention it, that's all.

Thanks!

(Edit:- Apparently, it is kernel-related, but the general consensus of opinion seems to be that it doesn't affect overall functionality, and is nothing to be concerned about.....if this DuckDuckGo search page is anything to go by:-

https://duckduckgo.com/?q=No+IRQ+handle ... =h_&ia=web (Have to copy'n'paste that one; the forum software doesn't like the URL, I'm afraid.)

One guy on a Manjaro thread refers to it as a 'watchdog function'... (??!?)

Heaven above knows.)

Mike.

Gobbi · #13 Post by **Gobbi** » Thu 18 Jul 2019, 20:48

Thank you rockedge for the 32 bit 5.0.1 kernel . It's the first time a 32 bit Pup works quite well on my NUC . I have both network and sound recognized and working on BionicPup 32 .
Pmcputemp doesn't find the temp sensors and also , I can not see them in Hardinfo . Good to see that PupSysInfo got them though .
Booted from a USB partition using Grub4Dos . I just used the main files and pfix=ram on the kernel line .

Mike Walsh · #14 Post by **Mike Walsh** » Thu 18 Jul 2019, 21:00

@ Gobbi:-

I don't think that's kernel-related; it's more to do with the way pmcputemp is coded.

Have a look at ozsouth's 're-worked' 0.63a packages for this:-

http://www.murga-linux.com/puppy/viewto ... 76#1008276

.....and the following post. AMDs don't seem to be as 'vulnerable' to this quirk as Intels do. But those should, I think, fix it for you. They did for me when installing Puppy to a mate's old Dell desktop.

Make sure to uninstall pmcputemp first if you installed it yourself.

Mike.

Gobbi · #15 Post by **Gobbi** » Thu 18 Jul 2019, 21:04

Mike Walsh , thank's for the tip

I'll give it a try

Mike Walsh · #16 Post by **Mike Walsh** » Thu 18 Jul 2019, 21:47

Gobbi wrote:Mike Walsh , thank's for the tip
I'll give it a try

No worries, mate. It worked on my mate's old Dell desktop.....Pentium Dual-Core-powered (so you know it's kinda Vista-era vintage). Ozsouth uses a much newer Intel (one of the 'Cores', I believe), so I couldn't say how many Intel CPUs there are that don't 'play nice' with it.

If you find it works OK, could you let us know on the original pmcputemp thread, please?

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

Thanks.

Mike.

Mike Walsh · #17 Post by **Mike Walsh** » Fri 19 Jul 2019, 16:48

PipzDex wrote:Hi Rockedege
I'm using your kernel compilation from Precise 571 to Bionicpup 18 and works pretty well and without crash by de moment ...
Here mi specs... </snip>

>>>----------------------->>

rockedge wrote:glad it is working well and passing that information on. I am using it myself on a Bionic64-v8 system.

Hang about, hang about.....hold on; whoa! What's all this about 'Precisepup 7.5'...(huh??) And how on earth does a kernel, presumably compiled against glibc 2.27, run with 'only' glibc 2.15...? You've completely lost me here.

Care to elaborate, either of you? Please??

Mike.

nic007 · #18 Post by **nic007** » Sat 20 Jul 2019, 06:01

I don't think glibc play as much a role with kernel swopping (if any). Generally, kernel has to do with hardware and glibc with software. I tried one of peebees new kernels on Precise 571 a time ago and it worked nicely apart from that it took about 5 minutes to boot up. This was probably due to the system trying to load an appropriate driver for the old laptop's keyboard or a keymapping problem. Eventually the system settled on something that did work.

PipzDex · #19 Post by **PipzDex** » Sun 23 Feb 2020, 21:45

Mike Walsh wrote:
PipzDex wrote:Hi Rockedege
I'm using your kernel compilation from Precise 571 to Bionicpup 18 and works pretty well and without crash by de moment ...
Here mi specs... </snip>
>>>----------------------->>

rockedge wrote:glad it is working well and passing that information on. I am using it myself on a Bionic64-v8 system.

Hang about, hang about.....hold on; whoa! What's all this about 'Precisepup 7.5'...(huh??) And how on earth does a kernel, presumably compiled against glibc 2.27, run with 'only' glibc 2.15...? You've completely lost me here.

Care to elaborate, either of you? Please??

Mike.

HI Mike
sorry for the delay
precisepup 7.5 was an old personal proyect, not for share because was a test... And finally I discarded it because I finish with a size of 650 mb only the main sfs ... it was a mix between precise and xenial, that's why the name precisepup 7.5 and the reason to send to trash...

by the way.. ROCKEDGE

i modify "a little" your zdrv 5.0.1 32b with some lib and a firmware to be functional with some hardware of 64b

the main system still be precise 5.7.1 32b

i'm working now with a laptop acer aspire 5 intel core 5 64b and no matter the version of kernel 32b the simply no detect the wireless driver...

but with de modification i made on your zdrv i don't have any problem about that...

if you wanna check the file i paste the url
i hope work en another pc or laptops
cheers

https://drive.google.com/file/d/1_SkYYv ... sp=sharing

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Kernel 5.0.1 in 64 and 32 bit versions for Puppy Linux

Kernel 5.0.1 in 64 and 32 bit versions for Puppy Linux

Re: Kernel 5.0.1 in 64 and 32 bit versions for Puppy Linux