yesterday I played a little bit with the RC and the TVHeadend package on my RPi 2 to get my dirt cheap MyGica (Geniatech) T230 DVB-T/C Stick to work, but, no luck, dmesg gave me a strange error:
Cannot add dependency job for unit display-manager.service
ignoring: Unit display-manager.service failed to load: No such file or directory.
Sorry, I’m REALLY no Linux expert, so, it would be nice if somebody could help me to get this thing working!
In Openelec it’s working like a charm (with an older Kernel) so it should (hopefully) be possible to get this thing working in OSMC! This would be great!
Thanks a lot!!!
Red_Z
Update: I read a little bit about the problem and maybe I have to enable (or install) KDM, hopefully this solves the problem! I will try it in the afternoon and tell you the results!
Which version of the Tvheadend package are you using?
I the only one I have managed to use successfully with my PCTV stick is one you compile yourself using the instructions posted by HarryL. I also found that I needed the access control file (both mentioned in OSMC RC Unable to install TVHEADEND - #49 by DBMandrake) and some firmware files I eventually found elsewhere on the net. I have failed to get my WinTV-HVR-900H working, possible due to the firmware files that worked on RASBMC.
Been trying for hours to scan channels but keep getting scan failed. Have installed correct firmware and the channels work fine on PC to rule out signal issue.
Any help would be appreciated.
osmc@osmc:~$ dmesg | grep dvb
[ 5.148233] dvb-usb: found a ‘Mygica T230 DVB-T/T2/C’ in warm state.
[ 5.392768] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.422623] dvb-usb: schedule remote query interval to 100 msecs.
[ 5.422703] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 5.422775] usbcore: registered new interface driver dvb_usb_cxusb
[ 24.809612] si2168 3-0064: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 25.560664] si2157 4-0060: downloading firmware from file ‘dvb-tuner-si2158-a20-01.fw’
I doubt it. It’s quite a common message. You could run fsck on it to be sure, though.
When I have a moment, I’ll try my stick on a fresh OSMC install. I had to compile both v4l and tvheadend when I started out but that was 3 years ago so I’d have thought all the necessary stuff would be in the kernel and tvh by now. BTW, are you using tvh? I could never get other linux tools like zap, scan or dvbscan to work.
The figures are always minus and -17.3 dBm is a very strong signal. If you’re interested, see this for an explanation of why they are always minus. So maybe not wrong firmware, though -17.3 dBm is suspiciously high.
Tested on libreelec and it worked out of box so copied fw files and transferred over to OSMC. Channels scanning in now. For those looking for correct fw files that worked for me here details:
si2168 3-0064: found a ‘Silicon Labs Si2168-B40’
[ 24.520109] si2168 3-0064: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 25.265708] si2168 3-0064: firmware version: 4.0.11
[ 25.276858] si2157 4-0060: found a ‘Silicon Labs Si2158-A20’
[ 25.278856] si2157 4-0060: downloading firmware from file ‘dvb-tuner-si2158-a20-01.fw’
[ 26.490913] si2157 4-0060: firmware version: 2.1.9
Thanks to @grahamh for testing and helping me out appreciate it bro, you saved me from chucking this stick out of the window Patience sure is a virtue lol
Forgive me if mentioned above, but you guys don’t mention if you are using DVB-C or DVB-T.
I’ve two great OSMC DVB-T2 sticks on my desk, but we need to make a commitment to a large volume. I’m wondering if there’s demand for a good DVB-T2 adapter that’s officially supported.
We plan to include firmware and driver support in OSMC and keep it supported for the forseeable future.
My stick is dvb-t2. I think it also includes dvb-c also.
Yes I think having an offical osmc dvb-t2 in store would solve a lot of headaches. I also had to wait nearly 2 months getting it shipped from China too.
YW and that’s useful to know. When I last looked, those later versions of the fw did not work with my August stick, which has the same vendor:device ID, so remind me not to have both sticks on the same system!