download firmware from here dvb-demod-m88ds3103.fw
rename from dvb-demod-m88ds3103.fw to dvb-demod-m88ds3103b.fw and copy to /lib/firmware
this works on current kernels...
Tried this on las RPi OS build (5.10.17 kernel) and frontend not attached
download firmware from here dvb-demod-m88ds3103.fw
rename from dvb-demod-m88ds3103.fw to dvb-demod-m88ds3103b.fw and copy to /lib/firmware
this works on current kernels...
Tried this on las RPi OS build (5.10.17 kernel) and frontend not attached
After that I got the same message but with different number
[ 268.971808] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:76: Failed to set clock: 600000 (-12)
[ 268.980421] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:175: Error occurred setting a new frequency (600000)
[ 268.991268] cpufreq: __target_index: Failed to change cpu frequency: -22
so it worked with that number
Display Morecrazycat Running on Ubuntu and probably on Raspbian. I just deleted the old drivers (I noticed it's in the install.sh script).
Code[ 5.419590] dvb_core: disagrees about version of symbol vb2_vmalloc_memops [ 5.419592] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22) Usually that means that the drivers (modules) were built for a different linux kernel. ->>>> sudo rm -rf /lib/modules/$(uname -r)/kernel/drivers/media/*
I think we can focus on the bugs. What should I do?
(Signal differences from the same source between hd star and android box with 2 tuners)
EPG Grab errors:
Thanks to this I got frontend with crazy cat drivers in the last Ubuntu Server version for rbpi3. The problem now is that it only finds 2 channels, and I get flooded with this message while the device is connected.
It's working with the crazycat driver. But there are some bugs like continuity errors, problems with EPG and signal.
I tried the LibreELEC unofficial version with DVB drivers from here with crazycat drivers but didn't work.
Maybe you say that because of the img that is supposed to work with it but the link gives a 404 error.
I have never read this thread from beginning to end, but I think if you do, you will find there is a solution to m88ds3103b and some folks with m88ds3103b reporting it working. I have never seen such chip so can't help...
I have and I think the first mention to m88ds3103b is by crazycat in this page. In other forums there are some mentions, I have tried some of the solutions but no luck. I'll keep trying and update here if I achieve something.
now Geniatech sell update HDStar V3.0 with m88ds3103b demod. Look like same PCB, but updated demod need some driver update (some like initial clock) init diffrences
Display MoreI gotcha, so now there is another revision of m88ds3103 chip, that's gonna need among other things some updates to m88ds3103_priv.h in the sense of another table of initial register settings, etc???
ie like an additional table of init vals, and some way to trigger loading them upon recognizing a new chip id?
and guessing with no documentation, the only way we are gonna know what they should be set to is to have the newest hardware in
hand, and either do some i2c sniffing, or usb snooping of an updated windows driver that actually works?
or wait to see if dvbsky implements the new chip also, and actually contributes an updated m88ds3103 module to the kernel...
Just a guess, that we might see something from dvbsky developers before geniatech? seein as they actually went thru the hoops to implement an entire usb driver for the mainline linux kernel based on their hardware.. Assuming dvbsky has to buy the same new chip from Montage, eventually.
ughh
static const struct m88ds3103_reg_val m88ds3103b_dvbs_init_reg_vals[] = {
static const struct m88ds3103_reg_val m88ds3103b_dvbs2_init_reg_vals[] = {
I bought this version. Is it possible to make it work now with linux or I should just wait? Any way to help in the driver update?