LinuxQuestions.org - DVB bug in recent kernels

- slarm64 (https://www.linuxquestions.org/questions/slarm64-132/)

- - DVB bug in recent kernels (https://www.linuxquestions.org/questions/slarm64-132/dvb-bug-in-recent-kernels-4175729154/)

DVB bug in recent kernels

This may affect other modules as well....

A while back, my DVB Pi-hat (Sony cxd2880) stopped working. I found this in dmesg:

Code:

dmesg | grep cxd2880

[    3.628383] failing symbol_get of non-GPLONLY symbol cxd2880_attach.

[    3.628412] DVB: Unable to find symbol cxd2880_attach()

[    3.628419] cxd2880_spi: cxd2880_spi_probe: cxd2880_attach failed

Googling for it, I found this:

https://lore.kernel.org/stable/20230...d-d6bc@gregkh/

I think its been around longer than they realise, but at least they are now aware. There is a list of devices affected in that thread - about 130 of them!

Just a "heads up" for anyone having a similar issue.

The only solution at present is to revert to a (much) earlier kernel...

--
Pete

Quote:

Originally Posted by pchristy

The only solution at present is to revert to a (much) earlier kernel...

Do you know how early?

That last on that I *know* is OK is 6.1.50.

However the other thread over on the main slackware forum indicates that it was fixed in the later 6.1.5X (after 6.1.52) series, which I find puzzling. If it was fixed there, why not in the others?

I *think* its only DVB devices that are affected, but since it also affects NVidia drivers - or something they were trying to do - who knows?

--
Pete

Quote:

Originally Posted by pchristy (Post 6455362)

I think I read something about that (Nvidia). It seems they didn't like their modules being treated as 'tainted' so had some trickery of importing them into other stuff to 'clean them up.' But once the kernel heads caught on, they closed that door, and rightly so. Nvidia modules are big and messy. I had one old nvidia card ever on a 32bit box, and that cured me of deciding "AMD or Nvidia?" The card was good but reinstalling the modules was a pain.