Regression in newer (non-Slackware) kernels
 

This doesn't affect Slackware provided kernels, but may affect those who roll their own...

I run slarm64 (an ARM64 version of Slackware) on a Pi 400. It uses cutting edge kernels, currently up at 6.5. A few upgrades ago, my dvb dongle stopped working. While chasing the problem, I found this: https://lore.kernel.org/stable/20230...d-d6bc@gregkh/

It looks like it affects 130 devices, so if you've been having issues with your own kernels, have a look at the list in this thread!

--
Pete

It was in the slackware-current kernel for a week, too, when it was 6.1.52. https://www.linuxquestions.org/quest...ml#post6452632

Thanks for the pointer! I would have missed that because the kernel updates come so thick and fast that these days, I only do every 5th one (45,50,55...)! :)

On ARM, the kernel updates don't come so often, so it caught me out!

--
Pete

Funny that.

I've just set up a nice, tidy & well-behaved Slarm64 on 6.1.52, and it works fine, and my video issues are solved. Now I know the slarm64 guys check for upstream patches for kernels they build. It's unusual, because the previous update was 6.1.48 and they're close together. I gather the RazPi 4B is involved?

Reading between the lines a bit, it looks like NVidia was doing something the kernel devs didn't like, and they took steps to restrict it. Unfortunately, they caught quite a few DVB devices in the net at the same time.

As far as I can tell, it looks like only DVB devices are affected - not even all of them. It shouldn't have any impact on plain video, or video players.

I am prepared to be shown wrong about this! ;)

--
Pete

Thanks for the info. And don't worry, it won't be me proving anyone wrong. I've everything singing & dancing nicely. I suppose Nvidia were trying to get rid of that notice about 'tainting the kernel.' My guess is that that one isn't over yet. That was simply round 1.