@Quonith did you reboot several times ? (kinda curious as to why it would just suddenly work, logs would be interesting to see)
as to adressing the matter im fairly certain that this is an upstream problem not a OSMC problem when googling these specific error messages we get hits from OE and upstream about this firmware so they are working on a fix, but when it will be fixed that its anyone guess.
in the meantime try what @Quonith suggested and if you get it working please put up a log again for my personal interest // Cheers Toast
Hi, i have the same hardware and want to test it, but i can’t find the mn88473 kernel module (OSMC December 2015.12-3 at Raspi2). Did you compile the module yourself or do you use an development version of osmc.
Honestly I have no idea where the problem is, but if it works for @Quonith, then it should work for me too, I think… That’s why I think that there is NO problem, just something is not perfectly set on my side.
The logs:
only the DVB-C MN88473 is enabled in tvheadend, 1 empty network is created and attached to this adapter. And a simple reboot. (no rtl2832 errors, but a failed firmware download attempt) [ 35.882244] usb 1-1.4: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000) [ 36.466427] mn88473 3-0018: downloading firmware from file 'dvb-demod-mn88473-01.fw' [ 36.811947] mn88473 3-0018: firmware download failed=-32 [ 36.988923] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 0 out of range (42000000..1002000000) [ 37.165403] mn88473 3-0018: downloading firmware from file 'dvb-demod-mn88473-01.fw' [ 37.686958] mn88473 3-0018: firmware parity check succeeded=0x20
did no change anything in tvheadend config, but made a complete poweroff (even removed the power supply): (no firmware errors, but an rtl2832 error) [ 37.033030] usb 1-1.4: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000) [ 37.762630] mn88473 3-0018: downloading firmware from file 'dvb-demod-mn88473-01.fw' [ 38.283117] mn88473 3-0018: firmware parity check succeeded=0x20 [ 38.464188] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 0 out of range (42000000..1002000000) [ 38.551131] rtl2832 3-0010: i2c reg read failed -32 [ 41.135236] mn88473 3-0018: firmware already running
enabled the RTL2832 tuner in tvheadend, and rebooted. It solved the i2c reg read failed -32 problem, but the MN88473 disappeared from tvheadend (Neither firmware nor rtl2832 errors, but MN88473 disappeared) [ 37.753149] usb 1-1.4: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000)
My issue is no matter what I do, it does not start scanning… actually it doesn’t do anything.
Just had a look at the logs on my system and I get 1 rtl2832 i2c error followed by the mn88473 firmware already running message. But it all still works fine, and no other errors show up… but I’m using mine for DVB-T/T2 so maybe there is an issue with the DVB-C side?
@Toast I tried a few things including multiple reboots, disconnecting and reconnecting the tuner, re downloading the firmware before power cycling. nothing else worked.
It’s the same dongle which has both DVB-C DVB-T and DVB-T2
I think the problem might be in tvheadend start which might be the reason why the dongle fails to start up. here you can find a description of the problem we are having the adapter are out of range i wonder if triggering a manual scan as recommend guyee removes this problem.
It would be interested to know which command guyee dvb5-scan did to start the dongle and will try to see if it fixes the problem
Ok managed to get the panasonic channel to work and it looks like guyee is right you need to initialise the dongle before turning on Tvheadend.
How i did it i installed w-scan via
sudo apt-get install w-scan.
Triggered a scan on a fresh boot via typing w_scan and started Tvheadend and now i can see the channels on the dongle
Exactly, I did nothing special, the first time I tried to start scanning with dvbv5-scan it worked.
What I did:
I tried a scan with Panasonic DVB-T tuner in tvheadend, and it worked.
I used dvbv5-scan to inititate a scan with the Pana DVB-C tuner, and it worked.
Went back to tvheadend, set up everything again (the same way I did it a hundred times before), and worked perfectly (and is working since then)
So I have 2 possible suspects:
Using the DVB-T tuner in Pana does something that makes the DVB-C part work, or
dvbv5 sets up the Pana tuner correctly, but tvheadend does not.
The strage part is that whatever happened, it’s persisted across reboots, it has to be done once in the lifetime of the tuner…
I’ll try to put the stick back into the Windows machine it came from, maybe the Windows drivers will revert the stick to a non-working (or Windows-only ) state.
Well, no luck. I plugged my Astrometa back into a Windows server, installed and configured MediaPortal 2 (needless to say that everything went flawlessly).
Then plugged back into raspi hoping that firmware uploading issues will restart, but it succeed right when I plugged it in, and channel scanning in tvheadend was working as well…
So I have no idea what happened when I first tried it, if I ever reinstalled my raspi I will try to reproduce the issue.
(Neither firmware nor rtl2832 errors, but MN88473 disappeared)
would like to know which command i would need to parse to get it working.
) state.