kernel-firmware missing after latest kernel update to 4.4.199
 

Somehow the updated kernel-firmware package got lost in the recent update to 4.4.199.

There was patches/packages/linux-4.4.190/kernel-firmware-20190821_c0fb3d9-noarch-1.txz before, but there's no kernel-firmware package anymore in the linux-4.4.199 directory.

Be careful when you use automatic tools for updating because you might accidentally downgrade to Slackware 14.2's stock kernel-firmware-20160628git-noarch-1 then.

Can we get a recent kernel-firmware package again, please? :-)

Edit: tonight's update re-delivered the kernel-firmware packge

You'll find it (and later updates) here: http://slackware.uk/cumulative/slack...slackware64/a/
Or, if you've got a 32bit system: http://slackware.uk/cumulative/slack...t/slackware/a/

Whole thing is down.

https://downforeveryoneorjustme.com/....slackware.com

So, I'm thinking I'll defer moving from 4.4.190 for a day or two while this sorts itself out.

Plenty of mirrors out there working: slackware.osousl.org, slackware.uk, slackware.nl...

have tried several - all I've found so far suggest replacing

installed: kernel-firmware-20190821_c0fb3d9-noarch-1
with kernel-firmware-20160628git-noarch-1


I'll wait a bit

The OP is using 14.2 not -current.

And the firmware does seem to be lost in the aether.

The firmware package does not depend on 32/64 bit or the kernel version, so feel free to use e.g. the -current one. They are copied onto hardware devices, not code to be run by the CPU.

The link provided is "cumulative". It includes files for 14.1, 14.2 & current. The 14.2 firmware-kernel patch is there.

Running without new firmware file
 

This morning I updated without the new firmware file and everything seems to be running fine. Is this OK or should I be expecting problems?

That just doesn't make sense to me. Not the "cumulative" part, but that 14.1, 14.2 & current would be placed in the same directory. That seems like a recipe for disaster.

These repositories are intended for people wanting to install an old version of a software not found anymore on another mirror for a specific need, not to be used to keep updated a system, let alone using an automated tool like slackpkg.

Why is that? The great thing with the cumulative repo is that you can find older versions, e.g if a new upgrade breaks something. Say that you're running 14.2 and the recent python-2.7.17 update creates havoc. But where to find the previous version? Thanks to the cumulative repo you can easily downgrade to 2.7.16 and then, with a fully functional system, patiently work out what happened.
You're not supposed to make it your default repo (then, I admit, disaster will be around the corner).

That cumulative -current directory does not have python-2.7.16-x86_64-1_slack14.2.txz which was compiled on 14.2 against the libc of 14.2, and was in /patches. Instead, it has python-2.7.16-x86_64-1.txz compiled on what was -current at that time, against the libc which was current on -current then.

But it's different with the firmware packages, as they are not compiled at all.

This was what I was thinking, which can lead to breaks.