Bog standard installer, here, and 5.10.3. No problems. I don't do the -K option, though. I'm also using 460.27.04. I was on 455.45.01. Are you who're having problems using the huge kernel or the generic one? (I'm using huge.)

1 members found this post helpful.

Just another me to!
5.10.4 built and running no problemo.
John

1 members found this post helpful.

At the risk of jinxing it... 8 hours plus, no lockups...

yet.

1 members found this post helpful.

I have built 5.10.4 and Bluetooth is still broken. I don't have this problem with 5.4.xx or 5.9.xx. Even the icon disappear in the taskbar.

Attached Thumbnails

   

FWIW, the zfs-2.0.1-staging branch is updated for 5.10 compat as well. It may not help for your 5.10 production needs *now*, but a zfs-2.0.1 will happen soon(tm).

5.10.4 also locks up, so I guess it was just biding it's time to bite me.

*sigh* I give up, back to 5.9.

1 members found this post helpful.

Hasn't been a problem here. 5.10.4 is running as advertised.

Me too, I only did 5.10.4 because it had some Bluetooth fixes in the changelog. I will wait until someone else confirm working bluetooth in the 5.10.X.

Could be something hardware specific I suppose, or maybe something environmental/situational, such as whether one is using compositing or not, evdev or libinput driver for input devices, and so on.

I could not get the zfs 2.0.0 to compile without editing the configure script. Something about the mktemp needing 6 X's in linux. I reported this and it will be fixed in 2.0.1. Also the zfs-zstd module would not load for me on either 5.4 or 4.4. So I went back to 0.8.6. I am using the long term support kernel 5.4.x

Is there any chance of Slackware 14.2 jumping to kernel 5.4? or will it stay on 4.4 forever? It would be nice to update with slackpkg instead of compiling and manually installing it.

1 members found this post helpful.

5.10.4 is running as advertised too, thanks

1 members found this post helpful.

5.10.4 running smoothly here on laptop and desktop (all Intel).
FWIW, have built and run 5.10.x starting with the RC's without any issues.

2 members found this post helpful.

It wouldn't be 14.2 any more if that happened. Everything would have to be recompiled against the new kernel headers.
Edit since people are quibbling: there are some things you would need to recompile against the new headers, for instance the compiler and libraries. Realistically a distribution would need to recompile everything against the new kernel. You don't need to recompile with a new minor version number so any 4.4.x kernel is not a problem for 14.2.
Since the version numbers for Slackware are notoriously ad hoc whether or not it wouldn't be 14.2 would be something only Patrick could say, my argument would be a kernel revision is too much to claim it's the same thing.

1 members found this post helpful.

? Slint that I maintain currently ships linux 5.4.75 (compiled with a genuine gcc 5.5 from Slackware 14.2), with no issue so far and no user complaint. I consider upgrading to 5.10.n when dust will have settled a bit.

1 members found this post helpful.

IIRC every LTS_to_be-kernel had similar problems on lower end of the revision count, this is actually a good sign in the long run?