Marko Lukat

I can tell you how **CubicSDR** reacts: if nothing ever touches the device (e.g. no **SoapySDRUtil** query) then I have to add the device (address) and after a re-scan I...

I suspect it's a version mismatch (we had a kernel update recently). Can you find your .ko file and check its version against your current kernel version? ``` $ strings...

In the build log there should be something like this: ``` [ 5 ] Compiling main source... ... 3. SMI kernel module... -- The C compiler identification is GNU 10.2.1...

What kernel have you got and what headers are available under `/usr/src`? The sudo bit is not relevant, it only needs some other part from **SoapySDRUtil**.

And your kernel is at? (`uname -a`)

Thought so. Odd that you won't get v8+ headers which would explain the mismatch. Can you either create a softlink under `/usr/src` or try to update the kernel headers to...

In `/usr/src` run the following: ``` $ sudo ln -s linux-headers-6.1.19-v7+ linux-headers-6.1.19-v8+ ``` That said, it may well be that you need the real headers in case there is a...

Ouch, one last try, remove the link you created and update like this: ``` $ sudo apt install raspberrypi-kernel-headers ``` Which version is reported?

Beats me why only the RPi4 is affected. Should check on my 400. RPi3B is fine (64bit).

For the record, on a RPi400 starting with Pi OS Lite 64bit (from the imager) I never had any issues with upgrading. Headers always matched. I have a feeling that...