Posts by Meiden

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.

Quote from Booza

Hi Meiden. Are you using a Rpi?

Would be good to know if anyone has the HD Star v3 or equivalent working on RPi and if so what they are using to give me something to persist with? I've lost countless hours now and all I've got to show for it is a bit more familiarity with the command line.

Hi Booza,

Nope. I'm afraid I'm using a mini-itx computer with Ubuntu Server 18.04 LTS.

OK, it is working now. But I have my dmesg log flooded by:

[  671.614860] dw2102: su3000_identify_state
[  671.614863] dvb-usb: found a 'SU3000HD DVB-S USB2.0' in warm state.
[  671.614874] dw2102: su3000_power_ctrl: 1, initialized 0
[  671.615241] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  671.615478] dvbdev: DVB: registering new adapter (SU3000HD DVB-S USB2.0)
[  671.615484] usb 1-6: media controller created
[  671.619659] dvb-usb: MAC address: 00:af:78:66:2e:de
[  671.620254] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[  671.955776] dw2102: i2c read request failed: i2c status 7
[  671.956003] dw2102: i2c read request failed: i2c status 7
[  671.956006] Invalid probe, probably not a DS3000
[  671.956022] dw2102: su3000_frontend_attach: attaching demodulator of type m88ds3103b at i2c address 0x6a
[  671.970143] i2c i2c-5: Added multiplexed i2c bus 6
[  671.971653] m88ds3103 5-006a: dt addr is 0x21
[  672.031898] ts2020 6-0060: Montage Technology TS2022 successfully identified
[  672.031995] usb 1-6: DVB: registering adapter 0 frontend 0 (Montage Technology M88RS6000)...
[  672.032010] dvbdev: dvb_create_media_entity: media entity 'Montage Technology M88RS6000' registered.
[  672.066530] Registered IR keymap rc-su3000
[  672.066708] rc rc0: SU3000HD DVB-S USB2.0 as /devices/pci0000:00/0000:00:15.0/usb1/1-6/rc/rc0
[  672.066930] rc rc0: lirc_dev: driver dw2102 registered at minor = 0, scancode receiver, no transmitter
[  672.067119] input: SU3000HD DVB-S USB2.0 as /devices/pci0000:00/0000:00:15.0/usb1/1-6/rc/rc0/input12
[  672.067297] dvb-usb: schedule remote query interval to 150 msecs.
[  672.067305] dw2102: su3000_power_ctrl: 0, initialized 1
[  672.067307] dvb-usb: SU3000HD DVB-S USB2.0 successfully initialized and connected.
[  672.067513] usbcore: registered new interface driver dw2102
[  672.121793] dw2102: su3000_power_ctrl: 1, initialized 1
[  672.122033] dw2102: i2c read request failed: i2c status 7
[  672.122442] dw2102: i2c read request failed: i2c status 7
[  672.122901] dw2102: i2c read request failed: i2c status 7
[  672.123380] dw2102: i2c read request failed: i2c status 7
[  672.130713] dw2102: i2c read request failed: i2c status 7
[  672.131085] dw2102: i2c read request failed: i2c status 7
[  672.131440] dw2102: i2c read request failed: i2c status 7
[  672.131498] usb 1-6: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)
[  672.133116] dw2102: i2c read request failed: i2c status 7
[  672.133653] dw2102: i2c read request failed: i2c status 7
[  672.134043] dw2102: i2c read request failed: i2c status 7
[  672.134490] dw2102: i2c read request failed: i2c status 7
[  672.140918] dw2102: i2c read request failed: i2c status 7
[  672.141291] dw2102: i2c read request failed: i2c status 7
[  672.141715] dw2102: i2c read request failed: i2c status 7
[  674.155095] dw2102: i2c read request failed: i2c status 7
[  674.155637] dw2102: i2c read request failed: i2c status 7
[  674.156114] dw2102: i2c read request failed: i2c status 7
[  676.171095] dw2102: i2c read request failed: i2c status 7
[  676.171635] dw2102: i2c read request failed: i2c status 7
[  676.172113] dw2102: i2c read request failed: i2c status 7
[  678.187110] dw2102: i2c read request failed: i2c status 7
[  678.187678] dw2102: i2c read request failed: i2c status 7
[  678.188204] dw2102: i2c read request failed: i2c status 7

Compiled last crazycat's media_build over kernel 5.3.0-42-generic in Ubuntu 18.04.

My HDStar still fails:

[269757.290648] dw2102: su3000_identify_state
[269757.290651] dvb-usb: found a 'SU3000HD DVB-S USB2.0' in warm state.
[269757.290660] dw2102: su3000_power_ctrl: 1, initialized 0
[269757.291037] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[269757.291396] dvbdev: DVB: registering new adapter (SU3000HD DVB-S USB2.0)
[269757.291402] usb 1-6: media controller created
[269757.295526] dvb-usb: MAC address: 00:af:78:66:2e:de
[269757.296413] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[269757.639718] Invalid probe, probably not a DS3000
[269757.639732] dvb-usb: no frontend was attached by 'SU3000HD DVB-S USB2.0'
[269757.672217] Registered IR keymap rc-su3000
[269757.672341] rc rc0: SU3000HD DVB-S USB2.0 as /devices/pci0000:00/0000:00:15.0/usb1/1-6/rc/rc0
[269757.672443] input: SU3000HD DVB-S USB2.0 as /devices/pci0000:00/0000:00:15.0/usb1/1-6/rc/rc0/input12
[269757.672696] rc rc0: lirc_dev: driver dw2102 registered at minor = 0, scancode receiver, no transmitter
[269757.672700] dvb-usb: schedule remote query interval to 150 msecs.
[269757.672705] dw2102: su3000_power_ctrl: 0, initialized 1
[269757.672707] dvb-usb: SU3000HD DVB-S USB2.0 successfully initialized and connected.
[269757.672789] usbcore: registered new interface driver dw2102

... I'm probably doing something wrong.

Installation steps that I've followed:

git clone Bitbucket

cd media_build

make distclean

make

sudo make install

Quote from CvH

Install https://bitbucket.org/crazycat/media_build

Thanks mate.

LE community is f***** awesome.

Quote from CvH

did you use the build from Index of /test/ds3103b/ ??

the RPi image is confirmed working

It works!

Is there any way to "extract" the driver and use it in any other linux distro?

Quote from crazycat

Look like this old build without using ds3k frontend driver

Any solution?

Quote from NukeMania

Hi,

Vendor sent to me new driver and there is support for DS3103B

I don't have V3.0 hardware i can't test for it

But still I can't watch high bitrate channels with v2.1 board

i think it is related to usb bandwidth problem of linux

MEGA

Display More

This driver doesn't work either.

CvH  crazycat last message from my supplier (literally):

hi friend,

   please you send email to our engineer [email protected].
   Our engineer will help you.

thanks

Quote from crazycat

in my repo this geniatech specific ds3000 driver present as ds3k (also present original V4L DVB ds3000 frontend driver).

i change dw2102 driver for using ds3k for su3000 devices and this work with my old HDStar with TS2020/DS3000. Kernel 4.4 (Kubuntu 14.04.05)

And i not see any new ds3103 revision support in this driver. So this geniatech media_build just updated to latest kernels/distros since first from end 2014.

Display Spoiler

04.07.2018 23:45:13 usb 1-1.3 new high-speed USB device number 10 using ehci-pci

04.07.2018 23:45:13 usb 1-1.3 New USB device found, idVendor=1f4d, idProduct=3000

04.07.2018 23:45:13 usb 1-1.3 New USB device strings: Mfr=1, Product=2, SerialNumber=3

04.07.2018 23:45:13 usb 1-1.3 Product: USB Stick

04.07.2018 23:45:13 usb 1-1.3 Manufacturer: Max

04.07.2018 23:45:13 usb 1-1.3 SerialNumber: 080116

04.07.2018 23:45:13 dw2102 su3000_identify_state

04.07.2018 23:45:13 dvb-usb found a 'SU3000HD DVB-S USB2.0' in warm state.

04.07.2018 23:45:13 dw2102 su3000_power_ctrl: 1, initialized 0

04.07.2018 23:45:13 dvb-usb will pass the complete MPEG2 transport stream to the software demuxer.

04.07.2018 23:45:13 dvbdev DVB: registering new adapter (SU3000HD DVB-S USB2.0)

04.07.2018 23:45:13 usb 1-1.3 media controller created

04.07.2018 23:45:13 dvb-usb MAC address: 00:af:78:66:33:0d

04.07.2018 23:45:13 dvbdev dvb_create_media_entity: media entity 'dvb-demux' registered.

04.07.2018 23:45:13 ds3k_attach

04.07.2018 23:45:13 ds3k_readreg read reg 0x00, value 0xe0

04.07.2018 23:45:13 ds3k_readreg read reg 0x01, value 0xc0

04.07.2018 23:45:13 ds3k_readreg read reg 0x02, value 0x00

04.07.2018 23:45:13 DS3000 chip version 0.192 attached.

04.07.2018 23:45:13 ds3k_readreg read reg 0x01, value 0xc0

04.07.2018 23:45:13 ds3k_readreg read reg 0x02, value 0x00

04.07.2018 23:45:13 ds3k_readreg read reg 0xb2, value 0x01

04.07.2018 23:45:13 Chip ID = [DS300X]!

04.07.2018 23:45:13 usb 1-1.3 DVB: registering adapter 11 frontend 0 (Montage Technology DS3000/TS2020)...

04.07.2018 23:45:13 dvbdev dvb_create_media_entity: media entity 'Montage Technology DS3000/TS2020' registered.

04.07.2018 23:45:13 Registered IR keymap rc-su3000

04.07.2018 23:45:13 rc rc0 SU3000HD DVB-S USB2.0 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/rc/rc0

04.07.2018 23:45:13 input SU3000HD DVB-S USB2.0 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/rc/rc0/input12

04.07.2018 23:45:13 rc rc0 lirc_dev: driver dw2102 registered at minor = 0, scancode receiver, no transmitter

04.07.2018 23:45:13 dvb-usb schedule remote query interval to 150 msecs.

04.07.2018 23:45:13 dw2102 su3000_power_ctrl: 0, initialized 1

04.07.2018 23:45:13 dvb-usb SU3000HD DVB-S USB2.0 successfully initialized and connected.

Display More

Sorry, english isn't my native tongue, and I don't know if I'm understanding you. Do you mean that you had to change dw2102 driver in order to get your old HDStar working on Ubuntu? Is that possible with this new revision?

PS: it's a shame because I updated to 4.13 kernel because it was needed to build the driver. I dind't save any log of the building process in 4.4 and idk how to boot in 4.4 again from ssh.

Quote from CvH

From the log you can see that it was properly installed but not working

Yep, i know. Obviusly the driver doesn't work.

Thanks for your support.

I asked him again he sent me the driver for windows and he insists that the linux driver is the proper one.

Quote from crazycat

can you try with 4.4 kernel ? Ubuntu 14.04.05 or 16.04.xx ?

I tried before, and it says that 4.7 or higher is required.

It doesn't work on Ubuntu either:

Quote from crazycat

make distclean

make

sudo make install

Thank you very much

Quote from CvH

updated an additional RPi2/3 image to Index of /test/m88ds3103b/

I think that it isn't a proper driver:

http://ix.io/1fkc

http://ix.io/1fkd

No device appears on TVh.

Quote from CvH

I scrolled through the changes and I have no idea what they did here.

m88ds3103b · GitHub

that is the patch (manually reverted the applied media_build patches) - looks too scary and messy but maybe it works, Iam doing an build

Any way to apply ir manually?

Ok, just needed to add my kernel version at /linux/.version. Then it installed succesfully, but now neither my HDStar nor my RTL2838 DVB-T (which used to work before) work right now.