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...
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...
Many thanks for the reply. Thats where I started from I used this firmware with 9.2.4 libreelec but it would not work with the HD channels. It only worked with the crazycat TBS driver but not HD. Which is why I was looking for a way around this. Hopefully libreelec this will be addressed in a later release of libreelec. I may see if I can build a libreelec with the UpdateLee DW1202 driver.
I have compared the firmware with md5sum and it is the same. So comfortable I am using the same stuff.
don't use crazycat TBS driver for that device, it is know bug for some transponders, if you use libreelec x86_64 you must upgrade to latest nightly //where kernel have support included
from Index of /
LibreELEC-Generic.x86_64-9.80-nightly-20201010-45d6ccb.tar copy to /storage/.update/
and copy firmware dvb-demod-m88ds3103b to /storage/.config/firmware/
reboot
Geniatech Mygica HDStar DVB-S2 USB HD not working
your device is probably not listed yet in linuxtv wiki version 3103B of Geniatech HD Star DVB-S2 USB2.0 - LinuxTVWiki
this group of devices from 2018 > like cinergy s2 , s4600 and some others too have already proper support in current kernel , maybe for only this one support was not merged to dw2102 or dvbsky modules
Many thanks for your response.
I was using a RPi3 with 8.2.4 (linux 4.9.80) which was using the dvb-demod-m88ds3103.fw (the B frmware). I upgraded to 9.2.4 and lost the HD channels.
Thanks your advice. I have download various nightly image for the RPi2. The 2020 10 03 and worked with my TV via HDMI but would not connect to Wifi, but works fine on Ethernet. I use tvheadend, downloaded from the nightlies, 9.80.6.123 (4.2.8-36) worked fine but did not find any channels on the muxes. Showed a reasonable signal.
I tried the RPi2 images for 4,5,6,7,8,9,10 October. On the RPi 3B connected via HDMI to a Samsung TV but none got beyond the basic boot screen. I did not connect to Ethernet to see if it was just an HDMI problem. Happy to try again with these or other builds if this is useful.
QuoteDisplay More[ 12.883604] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
[ 13.002499] usb 1-1.4: New USB device found, idVendor=1f4d, idProduct=3000, bcdDevice= 0.00
[ 13.002512] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 13.002519] usb 1-1.4: Product: DVB-S/S2 USB Box
[ 13.002526] usb 1-1.4: Manufacturer: DVB-S/S2 USB Box
[ 13.002533] usb 1-1.4: SerialNumber: 080616
[ 13.087616] dw2102: su3000_identify_state
[ 13.087626] dvb-usb: found a 'SU3000HD DVB-S USB2.0' in warm state.
[ 13.087638] dw2102: su3000_power_ctrl: 1, initialized 0
[ 13.090163] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 13.106749] dvbdev: DVB: registering new adapter (SU3000HD DVB-S USB2.0)
[ 13.106773] usb 1-1.4: media controller created
[ 13.118675] dvb-usb: MAC address: 00:af:78:66:69:d7
[ 13.120611] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 13.478509] DS3000 chip version: 0.208 attached.
[ 13.561349] ts2020 11-0060: Montage Technology TS2022 successfully identified
[ 13.561467] dw2102: Attached DS3000/TS2020!
[ 13.561481] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Montage Technology DS3000)...
[ 13.561502] dvbdev: dvb_create_media_entity: media entity 'Montage Technology DS3000' registered.
[ 13.623638] Registered IR keymap rc-su3000
[ 13.623934] rc rc0: SU3000HD DVB-S USB2.0 as /devices/platform/soc/http://3f980000.usb/usb1/1-1/1-1.4/rc/rc0
[ 13.625501] rc rc0: lirc_dev: driver dw2102 registered at minor = 0, scancode receiver, no transmitter
[ 13.625691] input: SU3000HD DVB-S USB2.0 as /devices/platform/soc/http://3f980000.usb/usb1/1-1/1-1.4/rc/rc0/input0
[ 13.625854] dvb-usb: schedule remote query interval to 150 msecs.
[ 13.625868] dw2102: su3000_power_ctrl: 0, initialized 1
[ 13.625873] dvb-usb: SU3000HD DVB-S USB2.0 successfully initialized and connected.
[ 13.625993] usbcore: registered new interface driver dw2102
[ 13.984783] input: eventlircd as /devices/virtual/input/input1
The Chris Lee Update on Unbuntu x86 gives slightly different output on dw2102 but seams to work ok for both std and HD channels.
Ziggyzhang Don't post your logs as plain text, because it will make this thread hard to read. Use quoting / code formatation for short log snippets, and services like PasteBin for longer logs. Thanks!
Are there any
I am trying to execute Crazycat system build in a RPi4 with Raspbian to support HDstar tuner. I am stuck in the following problem: ERROR: "__devm_regmap_init_sccb" [/home/pi/media_build-master/v4l/ov9650.ko] undefined.
I appreciate any help or clarification on how to clear this.
I am trying to execute Crazycat system build in a RPi4 with Raspbian to support HDstar tuner.
Would love to hear how you get on, I had trouble getting this to work on a RPi4 and gave up!
Same problem with ov9650.ko building under Ubuntu Server 20.10 for Raspberry Pi.
Hi there guys.
Can anyone provide me a step-by-step comprehensive guide on how to make this work in 2021?
I've got mini pc with Ubuntu 18.04 LTS running kernel 5.4.0. Will it work there?
Thank you very much in advance.
I switched to use ArchArm with a update lee kernel, running 5.10.13 with full rebuild of tvheadend from the git master. Works and is very reliable.
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
This is October 2022 and I’m wondering if anyone successfully installed this unit in LE. I’m using LE10.02.3 on a RockPro64 and the unit is recognised on boot but no front end is loaded.
The board is marked SU3000 V3.0 111024 so obviously it’s the V3 version. From previous posts here I’ve seen the following
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...
Is this instruction relevant now. Did anyone actually get the V3 version working in LE.
I had a couple of these and gave up on them, it's probably possible to get them working but it's a PITA. Do yourself a favour and get a Telestar DIGIBIT R1.
I had a couple of these and gave up on them, it's probably possible to get them working but it's a PITA. Do yourself a favour and get a Telestar DIGIBIT R1.
Probably and there’s a number of others that work too but this is Linux and the challenge is to get things working. We’d never have anything working if we gave up.
I’m just trying to find out if anyone had gotten this working and how they went about doing it. Thanks for the recommendation though.
Geniatech HD Star DVB-S2 USB2.0 works fine for me but I don't recommend anyone to use USB tuners with LibreELEC, because with any update the drivers can stop working.
I leave you this information so you can study my case:
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (official): 9.2.6 (Generic.x86_64)
LibreELEC:~ # uname -r
5.1.16
LibreELEC:~ # cat /etc/os-release
NAME="LibreELEC"
VERSION="9.2.6"
ID="libreelec"
VERSION_ID="9.2"
PRETTY_NAME="LibreELEC (official): 9.2.6"
HOME_URL="https://libreelec.tv"
BUG_REPORT_URL="https://github.com/LibreELEC/LibreELEC.tv"
BUILD_ID="6bd7e983a6c4b748eff6f537077ee156bb800e48"
OPENELEC_ARCH="Generic.x86_64"
LIBREELEC_ARCH="Generic.x86_64"
LIBREELEC_BUILD="official"
LIBREELEC_PROJECT="Generic"
LibreELEC:~ # lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 0bc2:ab62 Seagate RSS LLC
Bus 003 Device 003: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 002: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 8087:0a2a Intel Corp.
Bus 002 Device 005: ID 18b4:1689 e3C Technologies DUTV009
Bus 002 Device 007: ID 1f4d:3000 G-Tek Electronics Group
Bus 002 Device 006: ID 045e:02d5 Microsoft Corp. Xbox One Digital TV Tuner
Bus 002 Device 004: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 002: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
LibreELEC:~ # lsmod
Module Size Used by
8021q 24576 0
veth 28672 0
xt_nat 16384 13
xt_tcpudp 20480 39
ipt_MASQUERADE 20480 16
nf_conntrack_netlink 36864 0
nfnetlink 16384 2 nf_conntrack_netlink
iptable_nat 16384 1
xt_addrtype 16384 2
iptable_filter 16384 1
ip_tables 28672 2 iptable_filter,iptable_nat
xt_conntrack 16384 1
x_tables 28672 7 xt_conntrack,iptable_filter,xt_tcpudp,ipt_MASQUERADE,xt_addrtype,xt_nat,ip_tables
nf_nat 36864 3 ipt_MASQUERADE,xt_nat,iptable_nat
nf_conntrack 81920 5 xt_conntrack,nf_nat,ipt_MASQUERADE,xt_nat,nf_conntrack_netlink
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
br_netfilter 28672 0
bridge 131072 1 br_netfilter
stp 16384 1 bridge
llc 16384 2 bridge,stp
overlay 106496 15
rc_su3000 16384 0
ds3k 49152 1
iwlmvm 299008 0
mac80211 585728 1 iwlmvm
dvb_usb_dw2102 73728 1
iwlwifi 278528 1 iwlmvm
tda18250 24576 1
wl 6381568 0
mn88472 24576 1
intel_powerclamp 20480 0
intel_rapl 24576 0
snd_hda_codec_realtek 94208 1
snd_hda_codec_generic 73728 1 snd_hda_codec_realtek
snd_hda_codec_hdmi 53248 1
cfg80211 577536 4 wl,iwlmvm,iwlwifi,mac80211
snd_hda_intel 36864 0
snd_hda_codec 106496 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hwdep 16384 1 snd_hda_codec
snd_hda_core 69632 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
dvb_usb_dib0700 163840 0
dib3000mc 20480 1 dvb_usb_dib0700
dib9000 36864 1 dvb_usb_dib0700
dib0070 20480 1 dvb_usb_dib0700
dib7000m 24576 1 dvb_usb_dib0700
dibx000_common 16384 4 dib9000,dib7000m,dib3000mc,dvb_usb_dib0700
dib0090 36864 1 dvb_usb_dib0700
dvb_usb 32768 2 dvb_usb_dw2102,dvb_usb_dib0700
pcc_cpufreq 20480 0
mxl5005s 49152 1
ec100 20480 1
btusb 49152 0
btrtl 20480 1 btusb
btbcm 16384 1 btusb
btintel 24576 1 btusb
bluetooth 462848 5 btrtl,btintel,btbcm,btusb
dvb_usb_ec168 20480 0
dvb_usb_v2 40960 1 dvb_usb_ec168
rc_core 40960 6 dvb_usb_v2,rc_su3000,dvb_usb,dvb_usb_dw2102,dvb_usb_dib0700
dvb_core 131072 5 dib9000,dvb_usb_v2,dvb_usb,mn88472,dvb_usb_dw2102
videobuf2_vmalloc 20480 1 dvb_core
videobuf2_memops 20480 1 videobuf2_vmalloc
videobuf2_common 53248 1 dvb_core
videodev 180224 1 videobuf2_common
media 45056 5 videodev,dvb_usb_v2,dvb_usb,dvb_core,videobuf2_common
ecdh_generic 28672 1 bluetooth
rfkill 20480 3 bluetooth,cfg80211
wireguard 200704 0
ip6_udp_tunnel 16384 1 wireguard
udp_tunnel 16384 1 wireguard
Display More
I've long advocated that if you want reliable DVB with LE or any of its derivatives you should separate the head-end from the client, because it makes it much easier to e.g. run RaspiOS on the head-end (easy package installs, any drivers you like, older kernel, etc.) while the client side runs LE. Separating things allows you to keep the client current, bumping as frequently as you like, while the server side remains on whatever works (and no need to bump it).
chewitt, that is a fair statement in general for RPi users but Intel users can benefit much more.. LE is a good platform for hosting headless servers including PVR backends and the work of installing the backend is done for the user via packages (TVHeadend, VDR and NextPVR, anyway) and many users don't have to hunt for drivers or firmware.
There is also a class of users that simply want legal live tv, and for them a USB dongle, or even a remote SAT>IP or HDHR device will work ideally. It is certainly better to by a stable USB device, Geniatech is one of the worst vendors, even on standard Linux.