Code Monkey home page Code Monkey logo

media_tree's People

Stargazers

 avatar  avatar  avatar

Watchers

 avatar

Forkers

fat-fred micha137

media_tree's Issues

TerraTec Electronic GmbH Cinergy S2 Box

I have a TerraTec Electronic GmbH Cinergy S2 Box connect to my Gentoo Linux Box with kernel 4.19.97-gentoo.
The kernel i had patched with these files https://github.com/devegoo/Monatge_3103b coverted to kernel 4.19.97-gentoo.
Patch dw2102.c https://pastebin.com/a7AP9T06
Patch m88ds3103.c https://pastebin.com/scvt0wVr
Patch m88ds3103_priv.h https://pastebin.com/mekJZAuA

The driver load all related modules:
dvb.log

But if i start tvheadend or w_scan nothing works.
The log file is full of:
dw2102: i2c read request failed: i2c status 7

I tried a 5.5 kernel and a 5.6-rc1 kernel. Everytime the same result.
How i can fix it?

Hauppauge QuadHD USB issues

I've been trying to get my Hauppauge QuadHD USB working under Raspian for a PVR. I came across your driver here and added patches to build into the Raspian kernel (4.19.y currently). Managed to build, can see the devices (shows up as 2 tuners in Plex like in Windows), But I'm experiencing some issues when scanning for QAM channels. ATSC scanning works fine and I'm able to find local broadcast stations, but with QAM I'm getting constant errors.

[  197.991956] em28xx 1-1.2.7.1.3:1.0: write to i2c device at 0xc0 failed with unknown error (status=115)
[  197.991973] mxl692 16-0060: mxl692_i2c_read: i2c read error!

This error usually shows up once when starting to scan for QAM, followed by constant FAIL messages, with an occasional

[  198.056114] mxl692_i2c_writeread() Something failed seq=X  opcode=X  pSize=X
[  198.056126] mxl692_i2c_writeread() pRxMsgHeader->payloadSize=0   rxExpectedPayloadSize=11

(The payload size mismatches are different here and there as is the status code)

I ended up fiddling with the code and changed qamAnnexType = MXL_EAGLE_QAM_DEMOD_ANNEX_B back to qamAnnexType = MXL_EAGLE_QAM_DEMOD_ANNEX_A in mxl692.c, and doing that kills the errors when scanning on QAM, BUT I'm unable to actually find any channels (Same source using a Hauppauge DualHD so confirmed it works otherwise on this same system).

Going a bit further, After scanning ATSC channels, when trying to actually stream them I'm getting the same i2c write and mxl692_i2c_writeread() FAIL error messages. Streaming somewhat works but it keeps failing intermittently.

Let me know if there's anything I can try/change, I've never poked around dvb drivers so this is a first.

Hauppauge WinTV Nova S2 - 2013:0461 Not Working

Hi,

as you requested from the other topic in the wrong section I'm opening the issue in the right place.

The device is recognized from Ubuntu 18.04.3 LTS with Linux ubuntu-x64 5.0.0-37201911191317-generic #0+mediatree+hauppauge~hwe-Ubuntu SMP.

I can use it from w_scan or TVHeadend but nothing is found during a full scan with Hotbitd 13E.

I can correctly use this device with Windows 10 so I can exlude problems in my home SAT environment or in the device itself.

I can support you with everything you need: I have also opened a ticket with Hauppauge because they certified this device with Ubuntu but, even if I have followed their instructions, I don't get it working.

Thanks your help.

Cinergy S2 Box ID 0ccd:0105 with Montage-3103b

Hi, my device is TerraTec Electronic GmbH Cinergy S2 Box ID 0ccd:0105 with Montage-3103b

informations on kernel without drivers (media_build)

lsusb:

Bus 001 Device 002: ID 0ccd:0105 TerraTec Electronic GmbH Cinergy S2 Box

dmesg :

[ 1249.760585] usb 1-1: new high-speed USB device number 4 using ehci-pci
[ 1249.890023] usb 1-1: New USB device found, idVendor=0ccd, idProduct=0105, bcdDevice= 0.00
[ 1249.890026] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1249.890029] usb 1-1: Product: TERRATEC USB Tuner
[ 1249.890031] usb 1-1: Manufacturer: Tevii
[ 1249.890033] usb 1-1: SerialNumber: 000000031

informations on kernel with drivers (media_tree) from linuxtv brad repo

ls -l /dev/dvb/adapter0 :

razem 0
crw-rw----+ 1 root video 212, 4 11-08 15:59 demux0
crw-rw----+ 1 root video 212, 5 11-08 15:59 dvr0
crw-rw----+ 1 root video 212, 7 11-08 15:59 net0

frontend is missing :

"[ 33.279671] m88ds3103 0-0068: Unknown device. Chip_id=52"

[ 27.252906] usb 1-1: USB disconnect, device number 2
[ 27.262960] dvb-usb: Terratec Cinergy S2 USB BOX successfully deinitialized and disconnected.
[ 32.830356] usb 1-1: new high-speed USB device number 4 using ehci-pci
[ 32.959923] usb 1-1: New USB device found, idVendor=0ccd, idProduct=0105, bcdDevice= 0.00
[ 32.959926] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 32.959929] usb 1-1: Product: TERRATEC USB Tuner
[ 32.959931] usb 1-1: Manufacturer: Tevii
[ 32.959933] usb 1-1: SerialNumber: 000000031
[ 32.960354] dw2102: su3000_identify_state
[ 32.960355] dvb-usb: found a 'Terratec Cinergy S2 USB BOX' in warm state.
[ 32.960365] dw2102: su3000_power_ctrl: 1, initialized 0
[ 32.962060] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 32.962188] dvbdev: DVB: registering new adapter (Terratec Cinergy S2 USB BOX)
[ 32.962194] usb 1-1: media controller created
[ 32.966918] dvb-usb: MAC address: bc:ea:2b:46:13:a5
[ 32.967297] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.

[ 33.279671] m88ds3103 0-0068: Unknown device. Chip_id=52
[ 33.279778] dvb-usb: no frontend was attached by 'Terratec Cinergy S2 USB BOX'
[ 33.280302] Registered IR keymap rc-tt-1500
[ 33.280365] rc rc0: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:04.1/usb1/1-1/rc/rc0
[ 33.280445] input: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:04.1/usb1/1-1/rc/rc0/input6
[ 33.281696] rc rc0: lirc_dev: driver dw2102 registered at minor = 0, scancode receiver, no transmitter
[ 33.281698] dvb-usb: schedule remote query interval to 250 msecs.
[ 33.281701] dw2102: su3000_power_ctrl: 0, initialized 1
[ 33.281702] dvb-usb: Terratec Cinergy S2 USB BOX successfully initialized and connected.

lsmod :

   Module                  Size  Used by
   dvb_usb_dvbsky         20480  0
   dvb_usb_v2             28672  1 dvb_usb_dvbsky
   rc_tt_1500             16384  0

        m88ds3103 28672 1 dvb_usb_dvbsky
        i2c_mux 16384 1 m88ds3103
        dvb_usb_dw2102 69632 0 <<< 0
        dvb_usb 28672 1 dvb_usb_dw2102
        dvb_core 126976 dvb_usb_v2,m88ds3103,dvb_usb,dvb_usb_dw2102,dvb_usb_dvbsky
        rc_core 40960 6 dvb_usb_v2,dvb_usb,dvb_usb_dw2102,dvb_usb_dvbsky,rc_tt_1500
        mc 40960 3 dvb_usb_v2,dvb_usb,dvb_core

module dvb_usb_dw2102 is not used with module m88ds3103 !
module m88ds3103 is used with module dvb_usb_dvbsky !

is there any option to pass m88ds3103 module load for 3103b version ?
is this lsmod is correct because dvb_usb_dw2102 is not used with module m88ds3103 ?
why this device is recognized at once by dw2102 and dvbsky/ blacklist first or second ?

is there any chance to add support for this device to your brantch Montage_3103b ?
or is already included but something is not configured ?

https://git.linuxtv.org/brad/media_tree.git/log/?h=Montage-3103b.v2

Support for TerraTec Electronic GmbH Cinergy S2 Box ID 0ccd:0105 with Montage-3103b

Hi, my device is TerraTec Electronic GmbH Cinergy S2 Box ID 0ccd:0105 with Montage-3103b

informations on kernel without drivers (media_build)

lsusb:

Bus 001 Device 002: ID 0ccd:0105 TerraTec Electronic GmbH Cinergy S2 Box

dmesg :

[ 1249.760585] usb 1-1: new high-speed USB device number 4 using ehci-pci
[ 1249.890023] usb 1-1: New USB device found, idVendor=0ccd, idProduct=0105, bcdDevice= 0.00
[ 1249.890026] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1249.890029] usb 1-1: Product: TERRATEC USB Tuner
[ 1249.890031] usb 1-1: Manufacturer: Tevii
[ 1249.890033] usb 1-1: SerialNumber: 000000031

informations on kernel with drivers (media_tree) from linuxtv brad repo

ls -l /dev/dvb/adapter0 :

razem 0
crw-rw----+ 1 root video 212, 4 11-08 15:59 demux0
crw-rw----+ 1 root video 212, 5 11-08 15:59 dvr0
crw-rw----+ 1 root video 212, 7 11-08 15:59 net0

frontend is missing :

"[ 33.279671] m88ds3103 0-0068: Unknown device. Chip_id=52"

[ 27.252906] usb 1-1: USB disconnect, device number 2
[ 27.262960] dvb-usb: Terratec Cinergy S2 USB BOX successfully deinitialized and disconnected.
[ 32.830356] usb 1-1: new high-speed USB device number 4 using ehci-pci
[ 32.959923] usb 1-1: New USB device found, idVendor=0ccd, idProduct=0105, bcdDevice= 0.00
[ 32.959926] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 32.959929] usb 1-1: Product: TERRATEC USB Tuner
[ 32.959931] usb 1-1: Manufacturer: Tevii
[ 32.959933] usb 1-1: SerialNumber: 000000031
[ 32.960354] dw2102: su3000_identify_state
[ 32.960355] dvb-usb: found a 'Terratec Cinergy S2 USB BOX' in warm state.
[ 32.960365] dw2102: su3000_power_ctrl: 1, initialized 0
[ 32.962060] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 32.962188] dvbdev: DVB: registering new adapter (Terratec Cinergy S2 USB BOX)
[ 32.962194] usb 1-1: media controller created
[ 32.966918] dvb-usb: MAC address: bc:ea:2b:46:13:a5
[ 32.967297] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 33.279671] m88ds3103 0-0068: Unknown device. Chip_id=52
[ 33.279778] dvb-usb: no frontend was attached by 'Terratec Cinergy S2 USB BOX'
[ 33.280302] Registered IR keymap rc-tt-1500
[ 33.280365] rc rc0: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:04.1/usb1/1-1/rc/rc0
[ 33.280445] input: Terratec Cinergy S2 USB BOX as /devices/pci0000:00/0000:00:04.1/usb1/1-1/rc/rc0/input6
[ 33.281696] rc rc0: lirc_dev: driver dw2102 registered at minor = 0, scancode receiver, no transmitter
[ 33.281698] dvb-usb: schedule remote query interval to 250 msecs.
[ 33.281701] dw2102: su3000_power_ctrl: 0, initialized 1
[ 33.281702] dvb-usb: Terratec Cinergy S2 USB BOX successfully initialized and connected.

lsmod:

Module Size Used by
dvb_usb_dvbsky 20480 0
dvb_usb_v2 28672 1 dvb_usb_dvbsky
rc_tt_1500 16384 0
m88ds3103 28672 1 dvb_usb_dvbsky
i2c_mux 16384 1 m88ds3103
dvb_usb_dw2102 69632 0
dvb_usb 28672 1 dvb_usb_dw2102
dvb_core 126976 5 dvb_usb_v2,m88ds3103,dvb_usb,dvb_usb_dw2102,dvb_usb_dvbsky
rc_core 40960 6 dvb_usb_v2,dvb_usb,dvb_usb_dw2102,dvb_usb_dvbsky,rc_tt_1500
mc 40960 3 dvb_usb_v2,dvb_usb,dvb_core

module dvb_usb_dw2102 is not used with module m88ds3103 !
module m88ds3103 is used with module dvb_usb_dvbsky !

is there any option to pass m88ds3103 module load for 3103b version ?
is this lsmod is correct because dvb_usb_dw2102 is not used with module m88ds3103 ?
why this device is recognized at once by dw2102 and dvbsky/ blacklist first or second ?

is there any chance to add support for this device to your brantch Montage_3103b ?
or is already included but something is not configured ?

https://git.linuxtv.org/brad/media_tree.git/log/?h=Montage-3103b.v2

WinTV-Nova-S2 Raspberry Pi 4 Buster latest

When you connect a nova-s2 USB device nothing happens. Adding the firmware has no effect, the device is entirely ignored.

So after hours of hackery I seem to have tricked it into working by forcing the em28xx driver to actually look at it.

modprobe em28xx card=92
echo 2013 8258 | tee /sys/bus/usb/drivers/em28xx/new_id

And hooray, it seems to work in tvheadend and scans.

Not sure if this needs to be a udev rule or the driver doesn't like the product ID my device shows up as. Just wanted to log this on here for prosperity

Pi4 4.19.75-v7 kernel PCTV 461e

Hello,

I'm after a little help / assistance applying this patch to my raspbian buster (Kernal 4.19.75-v7 )

Any point in the right direction (i.e. tut) would be hugely appreciated

Thanks

What is the status of the Montage-3103b.v2 Branch?

As an owner of two TechnoTrend S2-4600 boxes which are currently not working under Ubuntu 18.04.3 (Chip_Id=38 unknown, no frontend0 device) I was wondering if your fix has been confirmed - I tried to follow your long discussion with CvH but I'm not sure about the outcome. I'm a bit concerned since the problematic Chip_Id in the discussion was 52 and not 38 - I opened one of my boxes and there is indeed a M88DS3103B installed, so what's the deal?

And more important: if the fix is working (and able to detect and support both pre- and post-2018 versions of the hardware correctly) will it find it's way to the media_tree master and to Ubuntu as well?

Regards

Jochen

Montage-3103b.v2 suggestion: avoid dev_err on address detection

With kernel 5.7 in each boot you find the "errror" message: m88ds3103 5-006a: dt addr is 0x21

I think your use of dvb_err is unintentional and perhaps you should lower the severity a bit: dev_err(&client->dev, "dt addr is 0x%02x", dev->dt_addr); [drivers/media/dvb-frontends/m88ds3103.c line 1904].

In addition your fix still works like a charm!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.