Every time a new kernel is downloade d and installed. fresh drivers have to be compiled against the new kernel using the same gcc compiler that had been used to create the new kernel.
Previously this had been just a case of running a script. However recently I just get 'make' errors.
I have gone back to kernel 5.15.0-133-generic without success.
Does ayone else use these cards?
Alan
No but I've been around the loop with out-of-tree drivers, now I only buy tuner cards with in-tree drivers ...
The claimed kernel range for the driver, suggests the build should be working. Yet your "make" evidence is, there is a mismatch on the parameters in one of the headers.
I tried to follow the build recipe, but I'm not sure git was pulling the correct set of files. I ended up with one source giving me a much larger tarball, than what git was giving me.
I own a different brand of tuner cards, and this is my situation:
1) Linux does not have the firmware file. A hobbyist provides the file, via his own web site.2) On Windows, the catalog server at Microsoft, does not have the driver. You had better not lose the driver on the CD in the box.
And the available chipsets for TV tuning, mean that there could be software changes depending on what year you bought a card.
As I understand this process, it is supposed to be compiling against the kernel headers, which you download when kernels are installed. It might mean the kernel range is not accurate, and the driver needs to be reissued when the delta is corrected by the developer. I don't think you are supposed to be grabbing arbitrary headers from the repo tree.
*******What have you decided, is the correct location and recipe for the build ? Which web page are you using ? The word "fork" comes up, when I am examining the various sites. Maybe only one of the sites claims "regular maintenance", but that is not evident.
Paul
+1. It's quite possible that the card has a chip on it that's supported by in-tree drivers, and the vendor drivers are just an unnecessary pile of trouble. Always better to make it work with in-tree (or at best DKMS) drivers, rather than messing with trying to build some vendor driver dump.
Theo
Surprisingly, my TBS6280 worked pretty well in Windows 7.
It turned out that I needed the full kernel source, the headers were insufficient. I don't recall this being an issue in the past. Dementia onset probably. :(
Alan
I doubt it...
I had a program which worked well to control the keyboard led lighting suddenly stop working when I upgraded from Linux Mint 21.3 to 22.0. It took a 400MB linux firmware update a month later before it started working again.
Shouldn't you have always used the full kernel source? :)
Have something to add? Share your thoughts — no account required.
Ask the community — no account required