Hello,
I recently (re)enabled my old Kodi setup with some DVB Tuners I had lying around & I've been through quite some hassle on getting all of them working at the same time (Hint: Haven't managed it yet). I've read through some of the posts on the forum (as well as on the Coreelec forums), but I'm still not exactly sure about the current state of things.
I have 2 DVB-S tuners (build in Wetek Play 2 one & a DVBSky S960 - both work fine with latest drivers from kernel) and 2 DVB-T2/C tuners (that cheap Astrometa one - which works - and the Xbox tuner, which doesn't). I tried several distro driver combinations (also Coreelec with Crazycat - which works with both DVB-T ones & the DVB-Sky one, using the build in Wetek one end up in a dead TV Headend) & then settled for the latest available LibreELEC version (9.0.2), mostly because of the great work from CvH as I believed would be the best bet to get my DVB sticks up & running. It is the best setup so far, as said both DVB-S & the Astrometa DVB-T2 stick are working.
If I remember from the "old days", when I was working on some Kodi stuff, LibreELEC had the intention to ditch the old 3.14 kernel for Wetek Devices, but that didn't seem to have happened (sorry for the extremely outdated info here), which is probably the root cause for the XBox stick/driver not working, correct?!
Support for Wetek Play 2 & newer distro versions (LE 9.2.0) doesn't seem to be a thing either, correct?
Is there any (maybe even experimental) thing I could do to get the Xbox stick working alongside the others?
I'd highly appreciate some help on that matter. I've attached the `dmesg` output for all DVB related things, which might be helpful as well.
LibreELEC:~ # dmesg | grep dvb
[ 12.184768@2] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.crazycat_aml.conf
[ 12.227030@2] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.crazycat_aml/lib/modules/3.14.29
[ 16.081158@2] wetek-dvb dvb.49: Found Wetek i2c-1 adapter ...
[ 16.081164@2] wetek-dvb dvb.49: ts0: parallel
[ 16.081249@2] wetek-dvb dvb.49: dmx rst ctl = ffffffc0622d1c40
[ 16.081255@2] wetek-dvb dvb.49: asyncfifo rst ctl = ffffffc0622d1fc0
[ 16.081261@2] wetek-dvb dvb.49: ahbarb0 rst ctl = ffffffc0622d1600
[ 16.081266@2] wetek-dvb dvb.49: uparsertop rst ctl = ffffffc0622d1e00
[ 16.323704@2] usb 1-1.4: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
[ 16.338939@0] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware
[ 16.349147@0] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[ 16.395423@2] usb 1-1.4: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 16.395447@2] dvbdev: DVB: registering new adapter (Astrometa DVB-T2)
[ 16.396492@2] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 16.467847@3] dvbdev: dvb_create_media_entity: media entity 'Realtek RTL2832 (DVB-T)' registered.
[ 16.473375@3] usb 2-1.1: dvb_usb_v2: found a 'DVBSky S960/S860' in warm state
[ 16.473539@3] dvbdev: dvb_create_media_entity: media entity 'Panasonic MN88473' registered.
[ 16.487644@3] usb 2-1.1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 16.487682@3] dvbdev: DVB: registering new adapter (DVBSky S960/S860)
[ 16.490516@3] usb 2-1.1: dvb_usb_v2: MAC address: 00:17:42:54:96:0c
[ 16.491511@3] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 16.580048@0] rc rc1: lirc_dev: driver dvb_usb_rtl28xxu registered at minor = 1, raw IR receiver, no transmitter
[ 16.580114@0] usb 1-1.4: dvb_usb_v2: schedule remote query interval to 200 msecs
[ 16.589034@0] usb 1-1.4: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected
[ 16.593694@0] usbcore: registered new interface driver dvb_usb_rtl28xxu
[ 16.607201@3] dvbdev: dvb_create_media_entity: media entity 'Montage Technology M88DS3103' registered.
[ 16.642905@3] Registered IR keymap rc-dvbsky
[ 16.643713@2] rc rc2: lirc_dev: driver dvb_usb_dvbsky registered at minor = 2, scancode receiver, no transmitter
[ 16.643723@2] usb 2-1.1: dvb_usb_v2: schedule remote query interval to 300 msecs
[ 16.643730@2] usb 2-1.1: dvb_usb_v2: 'DVBSky S960/S860' successfully initialized and connected
[ 16.643847@2] usbcore: registered new interface driver dvb_usb_dvbsky
[ 16.892942@2] wetek-dvb dvb.49: Wetek NIM(s) detection in progress ...
[ 16.892957@2] wetek-dvb dvb.49: Checking for Sony CXD2841ER DVB-C/T/T2 demod ...
[ 17.088517@3] m88ds3103 4-0068: downloading firmware from file 'dvb-demod-m88ds3103.fw'
[ 17.146190@3] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state.
[ 17.150340@1] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 17.516510@1] dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner)
[ 17.517464@1] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 17.712868@1] wetek-dvb dvb.49: Checking for Panasonic MN88436 ATSC demod ...
[ 17.735333@1] dvb-usb: no frontend was attached by 'Microsoft Xbox One Digital TV Tuner'
[ 17.735345@1] dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected.
[ 17.736702@2] usbcore: registered new interface driver dvb_usb_dib0700
[ 18.532882@1] wetek-dvb dvb.49: Checking for AVL6211 DVB-S/S2 demod ...
[ 18.533255@1] wetek-dvb dvb.49: Total Wetek NIM(s) found: 1
[ 18.536413@1] dvbdev: DVB: registering new adapter (wetek-dvb)
[ 18.536428@1] DVB: wetek_dvb_init: Registered adpter: wetek-dvb
[ 18.542036@1] wetek-dvb dvb.49: DVB: registering adapter 3 frontend 0 (Availink AVL6211+AV2011 DVB-S/S2)...
[ 18.542234@1] DVB: wetek_dvb_init: WeTeK dvb frontend registered successfully.
[ 20.836565@3] wetek-dvb dvb.49: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)
[ 23.329106@2] mn88473 2-0018: downloading firmware from file 'dvb-demod-mn88473-01.fw'As said, thank you for any help in advance.
Btw.: It seems that there happened some fallout between the LE & CE members; but I'm not biased in any way. If there is a CE version with drivers that would work with all of my 4 devices, I'll take that one. If there's no way to get all 4 running, then so be it, probably going to stick with the current LE setup then, as it is the closest to my satisfaction.
