cx23885: DVBSky S952 dvb_register failed err = -22

Hi,

using linux-3.19.1-1 (Archlinux) I get the following output while booting without the media-build-tree provided by DVBSky:

cx23885 driver version 0.0.4 loaded
cx23885 0000:04:00.0: enabling device (0000 -> 0002)
CORE cx23885[0]: subsystem: 4254:0952, board: DVBSky S952 [card=50,autodetected]
cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0]) cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes) cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-2: m88ds3103_attach: chip_id=70
i2c i2c-2: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb adapters on VID_B cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-1: m88ds3103_attach: chip_id=70
i2c i2c-1: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb on VID_C cx23885_dev_checkrevision() Hardware revision = 0xa5 cx23885[0]/0: found at 0000:04:00.0, rev: 4, irq: 17, latency: 0, mmio:
0xf7200000

Obviously there are no device in /dev/dvb. Using the media-build-tree works just fine though. The following firmware files are installed in /usr/lib/firmware:
dvb-demod-m88ds3103.fw
dvb-demod-m88rs6000.fw
dvb-demod-si2168-a20-01.fw
dvb-demod-si2168-a30-01.fw
dvb-demod-si2168-b40-01.fw
dvb-fe-ds300x.fw
dvb-fe-ds3103.fw
dvb-fe-rs6000.fw
dvb-tuner-si2158-a20-01.fw

Output of lspci -vvvnn:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/lscpi

I also set the module parameters debug, i2c_debug, irq_debug and irq_debug in cx23885.
The output is pretty verbose and can be found here:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/debug.log

Thanks,
Ole
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi,

I added some printk in cx23885-dvb.c and the problem is in i2c_new_device:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/media/pci/cx23885/cx23885-dvb.c?id=refs/tags/v3.19.1#n1935

The returned client_tuner is not NULL, but client_tuner->dev.driver is. Hence it will goto frontend_detach, which will then return -EINVAL. Any idea why client_tuner->dev.driver is NULL?

Thanks,
Ole

Am 14.03.2015 um 20:54 schrieb Ole Ernst:

Quoted 55 lines

Hi,

using linux-3.19.1-1 (Archlinux) I get the following output while booting without the media-build-tree provided by DVBSky:

cx23885 driver version 0.0.4 loaded
cx23885 0000:04:00.0: enabling device (0000 -> 0002)
CORE cx23885[0]: subsystem: 4254:0952, board: DVBSky S952 [card=50,autodetected]
cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0]) cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes) cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-2: m88ds3103_attach: chip_id=70
i2c i2c-2: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb adapters on VID_B cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-1: m88ds3103_attach: chip_id=70
i2c i2c-1: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb on VID_C cx23885_dev_checkrevision() Hardware revision = 0xa5 cx23885[0]/0: found at 0000:04:00.0, rev: 4, irq: 17, latency: 0, mmio:
0xf7200000

Obviously there are no device in /dev/dvb. Using the media-build-tree works just fine though. The following firmware files are installed in /usr/lib/firmware:
dvb-demod-m88ds3103.fw
dvb-demod-m88rs6000.fw
dvb-demod-si2168-a20-01.fw
dvb-demod-si2168-a30-01.fw
dvb-demod-si2168-b40-01.fw
dvb-fe-ds300x.fw
dvb-fe-ds3103.fw
dvb-fe-rs6000.fw
dvb-tuner-si2158-a20-01.fw

Output of lspci -vvvnn:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/lscpi

I also set the module parameters debug, i2c_debug, irq_debug and irq_debug in cx23885.
The output is pretty verbose and can be found here:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/debug.log

Thanks,
Ole
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

You don't have m88ts2022 driver installed.

Antti

Quoted 73 lines · Ole Ernst

Hi,

I added some printk in cx23885-dvb.c and the problem is in i2c_new_device:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/media/pci/cx23885/cx23885-dvb.c?id=refs/tags/v3.19.1#n1935

The returned client_tuner is not NULL, but client_tuner->dev.driver is. Hence it will goto frontend_detach, which will then return -EINVAL. Any idea why client_tuner->dev.driver is NULL?

Thanks,
Ole

Am 14.03.2015 um 20:54 schrieb Ole Ernst:

Quoted 58 lines

Hi,

using linux-3.19.1-1 (Archlinux) I get the following output while booting without the media-build-tree provided by DVBSky:

cx23885 driver version 0.0.4 loaded
cx23885 0000:04:00.0: enabling device (0000 -> 0002)
CORE cx23885[0]: subsystem: 4254:0952, board: DVBSky S952 [card=50,autodetected]
cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0]) cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes) cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-2: m88ds3103_attach: chip_id=70
i2c i2c-2: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb adapters on VID_B cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-1: m88ds3103_attach: chip_id=70
i2c i2c-1: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb on VID_C cx23885_dev_checkrevision() Hardware revision = 0xa5 cx23885[0]/0: found at 0000:04:00.0, rev: 4, irq: 17, latency: 0, mmio:
0xf7200000

Obviously there are no device in /dev/dvb. Using the media-build-tree works just fine though. The following firmware files are installed in /usr/lib/firmware:
dvb-demod-m88ds3103.fw
dvb-demod-m88rs6000.fw
dvb-demod-si2168-a20-01.fw
dvb-demod-si2168-a30-01.fw
dvb-demod-si2168-b40-01.fw
dvb-fe-ds300x.fw
dvb-fe-ds3103.fw
dvb-fe-rs6000.fw
dvb-tuner-si2158-a20-01.fw

Output of lspci -vvvnn:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/lscpi

I also set the module parameters debug, i2c_debug, irq_debug and irq_debug in cx23885.
The output is pretty verbose and can be found here:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/debug.log

Thanks,
Ole

Signature · 4 lines

To unsubscribe from this list: send the line "unsubscribe
linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi Antti,

thanks for your quick response! Based on lsmod and modinfo I do have m88ts2022.

$ lsmod | grep m88
m88ts2022              16898  0
regmap_i2c             12783  1 m88ts2022
m88ds3103              21452  0
i2c_mux                12534  1 m88ds3103
dvb_core              102038  4 cx23885,altera_ci,m88ds3103,videobuf2_dvb
i2c_core               50240  13
drm,i2c_i801,cx23885,cx25840,m88ts2022,i2c_mux,regmap_i2c,nvidia,v4l2_common,tveeprom,m88ds3103,tda18271,videodev

$ modinfo m88ts2022
filename:
/lib/modules/3.19.1-1-ARCH/kernel/drivers/media/tuners/m88ts2022.ko.gz
license:        GPL
author:         Antti Palosaari <[email protected]>
description:    Montage M88TS2022 silicon tuner driver
alias:          i2c:m88ts2022
depends:        i2c-core,regmap-i2c
intree:         Y
vermagic:       3.19.1-1-ARCH SMP preempt mod_unload modversions

Thanks,
Ole

Am 15.03.2015 um 11:49 schrieb Antti Palosaari:

Quoted 79 lines

You don't have m88ts2022 driver installed.

Antti

Quoted 73 lines · Ole Ernst

Hi,

I added some printk in cx23885-dvb.c and the problem is in i2c_new_device:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/media/pci/cx23885/cx23885-dvb.c?id=refs/tags/v3.19.1#n1935

The returned client_tuner is not NULL, but client_tuner->dev.driver is. Hence it will goto frontend_detach, which will then return -EINVAL. Any idea why client_tuner->dev.driver is NULL?

Thanks,
Ole

Am 14.03.2015 um 20:54 schrieb Ole Ernst:

Quoted 58 lines

Hi,

using linux-3.19.1-1 (Archlinux) I get the following output while booting without the media-build-tree provided by DVBSky:

cx23885 driver version 0.0.4 loaded
cx23885 0000:04:00.0: enabling device (0000 -> 0002)
CORE cx23885[0]: subsystem: 4254:0952, board: DVBSky S952 [card=50,autodetected]
cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0]) cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes) cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-2: m88ds3103_attach: chip_id=70
i2c i2c-2: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb adapters on VID_B cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-1: m88ds3103_attach: chip_id=70
i2c i2c-1: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb on VID_C cx23885_dev_checkrevision() Hardware revision = 0xa5 cx23885[0]/0: found at 0000:04:00.0, rev: 4, irq: 17, latency: 0, mmio:
0xf7200000

Obviously there are no device in /dev/dvb. Using the media-build-tree works just fine though. The following firmware files are installed in /usr/lib/firmware:
dvb-demod-m88ds3103.fw
dvb-demod-m88rs6000.fw
dvb-demod-si2168-a20-01.fw
dvb-demod-si2168-a30-01.fw
dvb-demod-si2168-b40-01.fw
dvb-fe-ds300x.fw
dvb-fe-ds3103.fw
dvb-fe-rs6000.fw
dvb-tuner-si2158-a20-01.fw

Output of lspci -vvvnn:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/lscpi

I also set the module parameters debug, i2c_debug, irq_debug and irq_debug in cx23885.
The output is pretty verbose and can be found here:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/debug.log

Thanks,
Ole

Signature · 4 lines

To unsubscribe from this list: send the line "unsubscribe
linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hello,

what is the "chip_id" debug output from m88ts2022 module?

I think you maybe hold the old S952 card.
Its satellite tuner is M88TS2020, not M88TS2022.

Best Regards,
Max

Quoted 108 lines · Ole Ernst

Hi Antti,

thanks for your quick response! Based on lsmod and modinfo I do have m88ts2022.

$ lsmod | grep m88
m88ts2022              16898  0
regmap_i2c             12783  1 m88ts2022
m88ds3103              21452  0
i2c_mux                12534  1 m88ds3103
dvb_core              102038  4 cx23885,altera_ci,m88ds3103,videobuf2_dvb
i2c_core               50240  13
drm,i2c_i801,cx23885,cx25840,m88ts2022,i2c_mux,regmap_i2c,nvidia,v4l2_common,tveeprom,m88ds3103,tda18271,videodev

$ modinfo m88ts2022
filename:
/lib/modules/3.19.1-1-ARCH/kernel/drivers/media/tuners/m88ts2022.ko.gz
license:        GPL
author:         Antti Palosaari <[email protected]>
description:    Montage M88TS2022 silicon tuner driver
alias:          i2c:m88ts2022
depends:        i2c-core,regmap-i2c
intree:         Y
vermagic:       3.19.1-1-ARCH SMP preempt mod_unload modversions

Thanks,
Ole

Am 15.03.2015 um 11:49 schrieb Antti Palosaari:

Quoted 79 lines

You don't have m88ts2022 driver installed.

Antti

Quoted 73 lines · Ole Ernst

Hi,

I added some printk in cx23885-dvb.c and the problem is in i2c_new_device:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/media/pci/cx23885/cx23885-dvb.c?id=refs/tags/v3.19.1#n1935

The returned client_tuner is not NULL, but client_tuner->dev.driver is. Hence it will goto frontend_detach, which will then return -EINVAL. Any idea why client_tuner->dev.driver is NULL?

Thanks,
Ole

Am 14.03.2015 um 20:54 schrieb Ole Ernst:

Quoted 58 lines

Hi,

using linux-3.19.1-1 (Archlinux) I get the following output while booting without the media-build-tree provided by DVBSky:

cx23885 driver version 0.0.4 loaded
cx23885 0000:04:00.0: enabling device (0000 -> 0002)
CORE cx23885[0]: subsystem: 4254:0952, board: DVBSky S952 [card=50,autodetected]
cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0]) cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes) cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-2: m88ds3103_attach: chip_id=70
i2c i2c-2: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb adapters on VID_B cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-1: m88ds3103_attach: chip_id=70
i2c i2c-1: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb on VID_C cx23885_dev_checkrevision() Hardware revision = 0xa5 cx23885[0]/0: found at 0000:04:00.0, rev: 4, irq: 17, latency: 0, mmio:
0xf7200000

Obviously there are no device in /dev/dvb. Using the media-build-tree works just fine though. The following firmware files are installed in /usr/lib/firmware:
dvb-demod-m88ds3103.fw
dvb-demod-m88rs6000.fw
dvb-demod-si2168-a20-01.fw
dvb-demod-si2168-a30-01.fw
dvb-demod-si2168-b40-01.fw
dvb-fe-ds300x.fw
dvb-fe-ds3103.fw
dvb-fe-rs6000.fw
dvb-tuner-si2158-a20-01.fw

Output of lspci -vvvnn:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/lscpi

I also set the module parameters debug, i2c_debug, irq_debug and irq_debug in cx23885.
The output is pretty verbose and can be found here:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/debug.log

Thanks,
Ole

Signature · 4 lines

To unsubscribe from this list: send the line "unsubscribe
linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi Max,

I get a chip_id of 0x81, which returns -ENODEV in the default branch of the subsequent switch. So I guess my S952 is too old? :-( How hard would it be to add support for it?

Thanks,
Ole

Am 17.03.2015 um 02:53 schrieb Nibble Max:

Quoted 119 lines

Hello,

what is the "chip_id" debug output from m88ts2022 module?

I think you maybe hold the old S952 card.
Its satellite tuner is M88TS2020, not M88TS2022.

Best Regards,
Max

Quoted 108 lines · Ole Ernst

Hi Antti,

thanks for your quick response! Based on lsmod and modinfo I do have m88ts2022.

$ lsmod | grep m88
m88ts2022              16898  0
regmap_i2c             12783  1 m88ts2022
m88ds3103              21452  0
i2c_mux                12534  1 m88ds3103
dvb_core              102038  4 cx23885,altera_ci,m88ds3103,videobuf2_dvb
i2c_core               50240  13
drm,i2c_i801,cx23885,cx25840,m88ts2022,i2c_mux,regmap_i2c,nvidia,v4l2_common,tveeprom,m88ds3103,tda18271,videodev

$ modinfo m88ts2022
filename:
/lib/modules/3.19.1-1-ARCH/kernel/drivers/media/tuners/m88ts2022.ko.gz
license:        GPL
author:         Antti Palosaari <[email protected]>
description:    Montage M88TS2022 silicon tuner driver
alias:          i2c:m88ts2022
depends:        i2c-core,regmap-i2c
intree:         Y
vermagic:       3.19.1-1-ARCH SMP preempt mod_unload modversions

Thanks,
Ole

Am 15.03.2015 um 11:49 schrieb Antti Palosaari:

Quoted 79 lines

You don't have m88ts2022 driver installed.

Antti

Quoted 73 lines · Ole Ernst

Hi,

I added some printk in cx23885-dvb.c and the problem is in i2c_new_device:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/media/pci/cx23885/cx23885-dvb.c?id=refs/tags/v3.19.1#n1935

The returned client_tuner is not NULL, but client_tuner->dev.driver is. Hence it will goto frontend_detach, which will then return -EINVAL. Any idea why client_tuner->dev.driver is NULL?

Thanks,
Ole

Am 14.03.2015 um 20:54 schrieb Ole Ernst:

Quoted 58 lines

Hi,

using linux-3.19.1-1 (Archlinux) I get the following output while booting without the media-build-tree provided by DVBSky:

cx23885 driver version 0.0.4 loaded
cx23885 0000:04:00.0: enabling device (0000 -> 0002)
CORE cx23885[0]: subsystem: 4254:0952, board: DVBSky S952 [card=50,autodetected]
cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0]) cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes) cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-2: m88ds3103_attach: chip_id=70
i2c i2c-2: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb adapters on VID_B cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-1: m88ds3103_attach: chip_id=70
i2c i2c-1: Added multiplexed i2c bus 4 cx23885_dvb_register() dvb_register failed err = -22 cx23885_dev_setup() Failed to register dvb on VID_C cx23885_dev_checkrevision() Hardware revision = 0xa5 cx23885[0]/0: found at 0000:04:00.0, rev: 4, irq: 17, latency: 0, mmio:
0xf7200000

Obviously there are no device in /dev/dvb. Using the media-build-tree works just fine though. The following firmware files are installed in /usr/lib/firmware:
dvb-demod-m88ds3103.fw
dvb-demod-m88rs6000.fw
dvb-demod-si2168-a20-01.fw
dvb-demod-si2168-a30-01.fw
dvb-demod-si2168-b40-01.fw
dvb-fe-ds300x.fw
dvb-fe-ds3103.fw
dvb-fe-rs6000.fw
dvb-tuner-si2158-a20-01.fw

Output of lspci -vvvnn:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/lscpi

I also set the module parameters debug, i2c_debug, irq_debug and irq_debug in cx23885.
The output is pretty verbose and can be found here:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/debug.log

Thanks,
Ole

Signature · 4 lines

To unsubscribe from this list: send the line "unsubscribe
linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hello Ole,

If it is m88ts2020, there is a tuner driver "ts2020" in "dvb-frontends" directory. If fail to load m88ts2022 driver, then try to load ts2020 driver. m88ts2022 driver is an i2c driver, but ts2020 is traditional dvb-attach driver. Please check the other code using ts2020 for reference.

Best Regards,
Max

Hi Max,

I'm afraid I'm not experienced enough to adapt the ts2020 driver to interwork with the current kernel driver for the S952. I'd be more than happy to test patches though!

Thanks,
Ole

Am 18.03.2015 um 02:40 schrieb Nibble Max:

Quoted 9 lines

Hello Ole,

If it is m88ts2020, there is a tuner driver "ts2020" in "dvb-frontends" directory. If fail to load m88ts2022 driver, then try to load ts2020 driver. m88ts2022 driver is an i2c driver, but ts2020 is traditional dvb-attach driver. Please check the other code using ts2020 for reference.

Best Regards,
Max

Quoted 5 lines

Hi Max,

I'm afraid I'm not experienced enough to adapt the ts2020 driver to interwork with the current kernel driver for the S952. I'd be more than happy to test patches though!

I will migrate M88TS2022 to TS2020 and it will start working after that.

regards
Antti

Quoted 16 lines

Thanks,
Ole

Am 18.03.2015 um 02:40 schrieb Nibble Max:

Quoted 11 lines

Hello Ole,

If it is m88ts2020, there is a tuner driver "ts2020" in "dvb-frontends" directory.
If fail to load m88ts2022 driver, then try to load ts2020 driver. m88ts2022 driver is an i2c driver, but ts2020 is traditional dvb-attach driver.
Please check the other code using ts2020 for reference.

Best Regards,
Max

Very much appreciated, thanks Antti! Let me know, if you need someone to test your patches.

Am 23.03.2015 um 19:08 schrieb Antti Palosaari:

Quoted 29 lines · Ole Ernst

Quoted 5 lines

Hi Max,

I'm afraid I'm not experienced enough to adapt the ts2020 driver to interwork with the current kernel driver for the S952. I'd be more than happy to test patches though!

I will migrate M88TS2022 to TS2020 and it will start working after that.

regards
Antti

Quoted 16 lines

Thanks,
Ole

Am 18.03.2015 um 02:40 schrieb Nibble Max:

Quoted 11 lines

Hello Ole,

If it is m88ts2020, there is a tuner driver "ts2020" in "dvb-frontends" directory.
If fail to load m88ts2022 driver, then try to load ts2020 driver. m88ts2022 driver is an i2c driver, but ts2020 is traditional dvb-attach driver.
Please check the other code using ts2020 for reference.

Best Regards,
Max

Quoted 2 lines

Very much appreciated, thanks Antti! Let me know, if you need someone to test your patches.

Could you test that tree?
http://git.linuxtv.org/cgit.cgi/anttip/media_tree.git/log/?h=ts2020

git clone -b ts2020 git://linuxtv.org/anttip/media_tree.git

then compile and install whole kernel

regards
Antti

Hi Annti,

I generated a patch using git diff 8a56b6b..5786103 on your branch and applied it to the current media_build tree, because I'm more experienced with it as compared to building my own kernels. After installing it, I removed m88ts2022.ko.gz shipped with my kernel and ran depmod -a. After a power-down/up cycle I can see /dev/dvb/adapter{0,1}/{demux,dvr,frontend,net}0. Unfortunately the frontends time out while tunning to a channel.

Mär 24 10:32:54 htpc kernel: cx23885 driver version 0.0.4 loaded Mär 24 10:32:54 htpc kernel: cx23885 0000:04:00.0: enabling device (0000 -> 0002)
Mär 24 10:32:54 htpc kernel: CORE cx23885[0]: subsystem: 4254:0952,
board: DVBSky S952 [card=50,autodetected]
Mär 24 10:32:54 htpc kernel: cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0])
Mär 24 10:32:55 htpc kernel: cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
Mär 24 10:32:55 htpc kernel: cx23885_dvb_register() allocating 1 frontend(s) Mär 24 10:32:55 htpc kernel: cx23885[0]: cx23885 based dvb card Mär 24 10:32:55 htpc kernel: i2c i2c-2: m88ds3103_attach: chip_id=70 Mär 24 10:32:55 htpc kernel: i2c i2c-2: Added multiplexed i2c bus 4 Mär 24 10:32:55 htpc kernel: ts2020 4-0060: Montage Technology TS2020 successfully identified
Mär 24 10:32:55 htpc kernel: DVB: registering new adapter (cx23885[0]) Mär 24 10:32:55 htpc kernel: cx23885 0000:04:00.0: DVB: registering adapter 0 frontend 0 (Montage M88DS3103)...
Mär 24 10:32:55 htpc kernel: DVBSky S952 port 1 MAC address:
ff:ff:ff:ff:ff:ff
Mär 24 10:32:55 htpc kernel: cx23885_dvb_register() allocating 1 frontend(s) Mär 24 10:32:55 htpc kernel: cx23885[0]: cx23885 based dvb card Mär 24 10:32:55 htpc kernel: i2c i2c-1: m88ds3103_attach: chip_id=70 Mär 24 10:32:55 htpc kernel: i2c i2c-1: Added multiplexed i2c bus 5 Mär 24 10:32:55 htpc kernel: ts2020 5-0060: Montage Technology TS2020 successfully identified
Mär 24 10:32:55 htpc kernel: DVB: registering new adapter (cx23885[0]) Mär 24 10:32:55 htpc kernel: cx23885 0000:04:00.0: DVB: registering adapter 1 frontend 0 (Montage M88DS3103)...
Mär 24 10:32:55 htpc kernel: DVBSky S952 port 2 MAC address:
ff:ff:ff:ff:ff:ff
Mär 24 10:32:55 htpc kernel: cx23885_dev_checkrevision() Hardware revision = 0xa5
Mär 24 10:32:55 htpc kernel: cx23885[0]/0: found at 0000:04:00.0, rev:
4, irq: 17, latency: 0, mmio: 0xf7200000
Mär 24 10:32:59 htpc vdr[387]: [387] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage M88DS3103")
Mär 24 10:32:59 htpc vdr[387]: [387] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Montage M88DS3103")
Mär 24 10:32:59 htpc vdr[387]: [387] found 2 DVB devices
Mär 24 10:33:13 htpc vdr[387]: [406] frontend 0/0 timed out while tuning to channel 2 (ZDF HD), tp 111361
Mär 24 10:33:40 htpc vdr[387]: [387] switching to channel 1 (Das Erste HD) Mär 24 10:33:50 htpc vdr[387]: [406] frontend 0/0 timed out while tuning to channel 1 (Das Erste HD), tp 111493
Mär 24 10:34:14 htpc vdr[387]: [387] switching to channel 2 (ZDF HD) Mär 24 10:34:24 htpc vdr[387]: [406] frontend 0/0 timed out while tuning to channel 2 (ZDF HD), tp 111361

This is what the output of the media-build-tree from dvbsky.net looks like:

Mär 24 10:41:30 htpc kernel: cx23885 driver version 0.0.4 loaded Mär 24 10:41:30 htpc kernel: cx23885 0000:04:00.0: enabling device (0000 -> 0002)
Mär 24 10:41:30 htpc kernel: CORE cx23885[0]: subsystem: 4254:0952,
board: DVBSky S952 [card=50,autodetected]
Mär 24 10:41:30 htpc kernel: cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0])
Mär 24 10:41:31 htpc kernel: cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
Mär 24 10:41:31 htpc kernel: cx23885_dvb_register() allocating 1 frontend(s) Mär 24 10:41:31 htpc kernel: cx23885[0]: cx23885 based dvb card Mär 24 10:41:31 htpc kernel: DS3000 chip version: d0 attached. Mär 24 10:41:31 htpc kernel: TS202x chip version[1]: 80 attached. Mär 24 10:41:31 htpc kernel: TS202x chip version[2]: 81 attached. Mär 24 10:41:31 htpc kernel: m88ds3103_load_firmware: Waiting for firmware upload (dvb-fe-ds3103.fw)...
Mär 24 10:41:31 htpc kernel: m88ds3103_load_firmware: Waiting for firmware upload(2)...
Mär 24 10:41:32 htpc kernel: DVB: registering new adapter (cx23885[0]) Mär 24 10:41:32 htpc kernel: cx23885 0000:04:00.0: DVB: registering adapter 0 frontend 0 (Montage DS3103/TS2022)...
Mär 24 10:41:32 htpc kernel: DVBSky S952 port 1 MAC address:
ff:ff:ff:ff:ff:ff
Mär 24 10:41:32 htpc kernel: cx23885_dvb_register() allocating 1 frontend(s) Mär 24 10:41:32 htpc kernel: cx23885[0]: cx23885 based dvb card Mär 24 10:41:32 htpc kernel: DS3000 chip version: d0 attached. Mär 24 10:41:32 htpc kernel: TS202x chip version[1]: 80 attached. Mär 24 10:41:32 htpc kernel: TS202x chip version[2]: 81 attached. Mär 24 10:41:32 htpc kernel: m88ds3103_load_firmware: Waiting for firmware upload (dvb-fe-ds3103.fw)...
Mär 24 10:41:32 htpc kernel: m88ds3103_load_firmware: Waiting for firmware upload(2)...
Mär 24 10:41:33 htpc kernel: DVB: registering new adapter (cx23885[0]) Mär 24 10:41:33 htpc kernel: cx23885 0000:04:00.0: DVB: registering adapter 1 frontend 0 (Montage DS3103/TS2022)...
Mär 24 10:41:33 htpc kernel: DVBSky S952 port 2 MAC address:
ff:ff:ff:ff:ff:ff
Mär 24 10:41:33 htpc kernel: cx23885_dev_checkrevision() Hardware revision = 0xa5
Mär 24 10:41:33 htpc kernel: cx23885[0]/0: found at 0000:04:00.0, rev:
4, irq: 17, latency: 0, mmio: 0xf7200000
Mär 24 10:41:35 htpc vdr[384]: [384] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage DS3103/TS2022")
Mär 24 10:41:35 htpc vdr[384]: [384] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Montage DS3103/TS2022")
Mär 24 10:41:35 htpc vdr[384]: [384] found 2 DVB devices
Mär 24 10:41:40 htpc vdr[384]: [384] switching to channel 2 (ZDF HD) Mär 24 10:43:16 htpc vdr[384]: [384] switching to channel 1 (Das Erste HD)

It looks as if the firmware dvb-fe-ds3103.fw is not getting downloaded with your patch. I thought there shouldn't be nodes in /dev/dvb/ in this case?

To roll back I reinstalled the old tree, moving the original m88ts2022.ko.gz back in and running depmod -a. Rebooting didn't bring the S952 up, it said:

Mär 24 10:39:07 htpc kernel: Unable to find Montage chip
Mär 24 10:39:07 htpc kernel: cx23885[0]: frontend initialization failed Mär 24 10:39:07 htpc kernel: cx23885_dvb_register() dvb_register failed err = -22
Mär 24 10:39:07 htpc kernel: cx23885_dev_setup() Failed to register dvb adapters on VID_B

So maybe it left it in a strange/undefined state? I had to poweroff the machine and start from there. Afterwards everything is fine again.

Thanks,
Ole

Am 23.03.2015 um 23:52 schrieb Antti Palosaari:

Quoted 13 lines · Ole Ernst

Quoted 2 lines

Very much appreciated, thanks Antti! Let me know, if you need someone to test your patches.

Could you test that tree?
http://git.linuxtv.org/cgit.cgi/anttip/media_tree.git/log/?h=ts2020

git clone -b ts2020 git://linuxtv.org/anttip/media_tree.git

then compile and install whole kernel

regards
Antti

Looks strange as firmware is not downloaded. It is downloaded on when first tuning attempt is done, so nodes are created in any case. TS2020 tuner is detected correctly, which looks somehow promising. Could you test my patches again as I have done some changes (tree is rebased).

Am 24.03.2015 um 13:54 schrieb Antti Palosaari:

Quoted 4 lines

Looks strange as firmware is not downloaded. It is downloaded on when first tuning attempt is done, so nodes are created in any case. TS2020 tuner is detected correctly, which looks somehow promising. Could you test my patches again as I have done some changes (tree is rebased).

Hi Antti,

I don't know what went wrong on first try, but after enabling some debug output I can see the firmware being downloaded.
Mär 24 15:15:47 htpc kernel: cx23885 driver version 0.0.4 loaded Mär 24 15:15:47 htpc kernel: cx23885 0000:04:00.0: enabling device (0000 -> 0002)
Mär 24 15:15:47 htpc kernel: CORE cx23885[0]: subsystem: 4254:0952,
board: DVBSky S952 [card=50,autodetected]
Mär 24 15:15:47 htpc kernel: cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0])
Mär 24 15:15:48 htpc kernel: cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
Mär 24 15:15:48 htpc kernel: cx23885_dvb_register() allocating 1 frontend(s) Mär 24 15:15:48 htpc kernel: cx23885[0]: cx23885 based dvb card Mär 24 15:15:48 htpc kernel: i2c i2c-2: m88ds3103_attach: chip_id=70 Mär 24 15:15:48 htpc kernel: i2c i2c-2: Added multiplexed i2c bus 4 Mär 24 15:15:48 htpc kernel: ts2020 4-0060: Montage Technology TS2020 successfully identified
Mär 24 15:15:48 htpc kernel: DVB: registering new adapter (cx23885[0]) Mär 24 15:15:48 htpc kernel: cx23885 0000:04:00.0: DVB: registering adapter 0 frontend 0 (Montage M88DS3103)...
Mär 24 15:15:48 htpc kernel: DVBSky S952 port 1 MAC address:
ff:ff:ff:ff:ff:ff
Mär 24 15:15:48 htpc kernel: cx23885_dvb_register() allocating 1 frontend(s) Mär 24 15:15:48 htpc kernel: cx23885[0]: cx23885 based dvb card Mär 24 15:15:48 htpc kernel: i2c i2c-1: m88ds3103_attach: chip_id=70 Mär 24 15:15:48 htpc kernel: i2c i2c-1: Added multiplexed i2c bus 5 Mär 24 15:15:48 htpc kernel: ts2020 5-0060: Montage Technology TS2020 successfully identified
Mär 24 15:15:48 htpc kernel: DVB: registering new adapter (cx23885[0]) Mär 24 15:15:48 htpc kernel: cx23885 0000:04:00.0: DVB: registering adapter 1 frontend 0 (Montage M88DS3103)...
Mär 24 15:15:48 htpc kernel: DVBSky S952 port 2 MAC address:
ff:ff:ff:ff:ff:ff
Mär 24 15:15:48 htpc kernel: cx23885_dev_checkrevision() Hardware revision = 0xa5
Mär 24 15:15:48 htpc kernel: cx23885[0]/0: found at 0000:04:00.0, rev:
4, irq: 17, latency: 0, mmio: 0xf7200000
Mär 24 15:15:52 htpc kernel: i2c i2c-2: m88ds3103_init:
Mär 24 15:15:52 htpc kernel: i2c i2c-2: m88ds3103_init: firmware=00 Mär 24 15:15:52 htpc kernel: i2c i2c-2: m88ds3103: found a 'Montage M88DS3103' in cold state
Mär 24 15:15:52 htpc kernel: i2c i2c-2: m88ds3103: downloading firmware from file 'dvb-demod-m88ds3103.fw'
Mär 24 15:15:53 htpc kernel: i2c i2c-2: m88ds3103: found a 'Montage M88DS3103' in warm state
Mär 24 15:15:53 htpc kernel: i2c i2c-2: m88ds3103: firmware version 3.B Mär 24 15:15:53 htpc vdr[388]: [388] DVB API version is 0x050A (VDR was built with 0x050A)
Mär 24 15:15:53 htpc vdr[388]: [388] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage M88DS3103")
Mär 24 15:15:53 htpc kernel: i2c i2c-1: m88ds3103_init:
Mär 24 15:15:53 htpc kernel: i2c i2c-1: m88ds3103_init: firmware=00 Mär 24 15:15:53 htpc kernel: i2c i2c-1: m88ds3103: found a 'Montage M88DS3103' in cold state
Mär 24 15:15:53 htpc kernel: i2c i2c-1: m88ds3103: downloading firmware from file 'dvb-demod-m88ds3103.fw'
Mär 24 15:15:54 htpc kernel: i2c i2c-1: m88ds3103: found a 'Montage M88DS3103' in warm state
Mär 24 15:15:54 htpc kernel: i2c i2c-1: m88ds3103: firmware version 3.B Mär 24 15:15:54 htpc vdr[388]: [388] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Montage M88DS3103")
Mär 24 15:15:54 htpc vdr[388]: [388] found 2 DVB devices

However, the tuner still times out even with your rebase. I sometimes also get this output from vdr:
Mär 24 15:22:20 htpc vdr[388]: [407] ERROR (dvbdevice.c,727): Die Wartezeit für die Verbindung ist abgelaufen
Which basically says the waiting time has exceeded.

I was playing a bit with femon plugin and often there will be a regained lock, with no picture though. Two times I also got a divide error:

Mär 24 15:21:27 htpc vdr[388]: [407] frontend 0/0 regained lock on channel 2 (ZDF HD), tp 111361
Mär 24 15:21:28 htpc vdr[388]: [407] frontend 0/0 lost lock on channel 2 (ZDF HD), tp 111361
Mär 24 15:21:28 htpc vdr[388]: [407] frontend 0/0 regained lock on channel 2 (ZDF HD), tp 111361
Mär 24 15:21:29 htpc vdr[388]: [407] frontend 0/0 lost lock on channel 2 (ZDF HD), tp 111361
Mär 24 15:21:30 htpc kernel: divide error: 0000 [#1] PREEMPT SMP Mär 24 15:21:30 htpc kernel: Modules linked in: uinput cfg80211 rfkill ts2020(O) m88ds3103(O) i2c_mux snd_hda_codec_hdmi cx25840(O) iTCO_wdt iTCO_vendor_support gpio_ich joydev mousedev ppdev evdev mac_hid intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm psmouse pcspkr serio_raw nvidia(PO) nls_iso8859_1 nls_cp437 vfat fat cx23885(O) altera_ci(O) tda18271(O) altera_stapl(O) i2c_i801 videobuf2_dvb(O) hid_logitech_hidpp videobuf2_dma_sg(O) ir_xmp_decoder(O) tveeprom(O) ir_lirc_codec(O) cx2341x(O) lirc_dev(O) ir_sharp_decoder(O) ir_mce_kbd_decoder(O) dvb_core(O) ir_sanyo_decoder(O) videobuf2_memops(O) ir_jvc_decoder(O) videobuf2_core(O) ir_sony_decoder(O) v4l2_common(O) ir_rc6_decoder(O) lpc_ich snd_usb_audio ir_rc5_decoder(O) drm ir_nec_decoder(O) videodev(O) Mär 24 15:21:30 htpc kernel: snd_usbmidi_lib snd_rawmidi snd_seq_device media(O) snd_hda_intel i2c_core snd_hda_controller rc_rc6_mce(O) snd_hda_codec nuvoton_cir(O) snd_hwdep snd_pcm parport_pc e1000e snd_timer parport rc_core(O) snd mei_me ptp mei soundcore pps_core shpchp button processor sch_fq_codel w83627ehf hwmon_vid coretemp hwmon xts gf128mul algif_skcipher af_alg dm_crypt dm_mod sr_mod cdrom sd_mod hid_logitech_dj usbhid hid uas usb_storage ata_generic pata_acpi atkbd libps2 crct10dif_pclmul crc32_pclmul crc32c_intel firewire_ohci ehci_pci ata_piix ghash_clmulni_intel cryptd firewire_core libata scsi_mod xhci_pci crc_itu_t xhci_hcd ehci_hcd usbcore usb_common i8042 serio ext4 crc16 mbcache jbd2
Mär 24 15:21:30 htpc kernel: CPU: 1 PID: 512 Comm: femon osd Tainted: P

           O   3.19.1-1-ARCH #1

Mär 24 15:21:30 htpc kernel: Hardware name: /DP67DE,
BIOS BAP6710H.86A.0072.2011.0927.1425 09/27/2011
Mär 24 15:21:30 htpc kernel: task: ffff8801fcbb1dd0 ti: ffff8800dd9a0000 task.ti: ffff8800dd9a0000
Mär 24 15:21:30 htpc kernel: RIP: 0010:[<ffffffffa0ee4335>]

[<ffffffffa0ee4335>] m88ds3103_read_snr+0x205/0x2a0 [m88ds3103]
Mär 24 15:21:30 htpc kernel: RSP: 0018:ffff8800dd9a3ba8  EFLAGS: 00010246
Mär 24 15:21:30 htpc kernel: RAX: 0000000000000036 RBX: ffff88020975e800

RCX: 00000000aaaaaaab
Mär 24 15:21:30 htpc kernel: RDX: 0000000000000000 RSI: ffff8800dd9a3b5f
RDI: ffff88020975e808
Mär 24 15:21:30 htpc kernel: RBP: ffff8800dd9a3bf8 R08: 0000000000000000
R09: 0000000000000003
Mär 24 15:21:30 htpc kernel: R10: ffff8800dd9a3b38 R11: 0000000000000246
R12: 0000000000000000
Mär 24 15:21:30 htpc kernel: R13: ffff8800dd9a3bbd R14: 00000000000000a2
R15: 0000000000000000
Mär 24 15:21:30 htpc kernel: FS: 00007ff4edd84700(0000) GS:ffff880217500000(0000) knlGS:0000000000000000
Mär 24 15:21:30 htpc kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Mär 24 15:21:30 htpc kernel: CR2: 00007ff868bef000 CR3: 00000000dd858000
CR4: 00000000000407e0
Mär 24 15:21:30 htpc kernel: Stack:
Mär 24 15:21:30 htpc kernel: ffff8800dd9a3de0 ffff8800dd9a3de0 1200000000000000 000000001ddfd430
Mär 24 15:21:30 htpc kernel: ffff8800dd9a3bf8 ffff8800dd9a3de0 0000000080026f48 ffff8801fcb69100
Mär 24 15:21:30 htpc kernel: ffff880209773400 ffff88020975e838 ffff8800dd9a3d38 ffffffffa054f1a6
Mär 24 15:21:30 htpc kernel: Call Trace:
Mär 24 15:21:30 htpc kernel: [<ffffffffa054f1a6>] dvb_frontend_ioctl_legacy.isra.8+0xa6/0xc80 [dvb_core]
Mär 24 15:21:30 htpc kernel: [<ffffffff810dd199>] ? lock_hrtimer_base.isra.22+0x29/0x60
Mär 24 15:21:30 htpc kernel: [<ffffffff810dd263>] ? hrtimer_try_to_cancel+0x93/0x120
Mär 24 15:21:30 htpc kernel: [<ffffffff810dd312>] ? hrtimer_cancel+0x22/0x30
Mär 24 15:21:30 htpc kernel: [<ffffffff811e5930>] ? poll_select_copy_remaining+0x150/0x150
Mär 24 15:21:30 htpc kernel: [<ffffffffa054fe54>] dvb_frontend_ioctl+0xd4/0x1310 [dvb_core]
Mär 24 15:21:30 htpc kernel: [<ffffffffa0545da5>] dvb_usercopy+0x115/0x190 [dvb_core]
Mär 24 15:21:30 htpc kernel: [<ffffffffa054fd80>] ?

dvb_frontend_ioctl_legacy.isra.8+0xc80/0xc80 [dvb_core]
Mär 24 15:21:30 htpc kernel:  [<ffffffff810f0672>] ? do_futex+0x132/0xad0
Mär 24 15:21:30 htpc kernel:  [<ffffffff8155e328>] ? __schedule+0x908/0xa30
Mär 24 15:21:30 htpc kernel:  [<ffffffffa0545e43>]
dvb_generic_ioctl+0x23/0x40 [dvb_core]
Mär 24 15:21:30 htpc kernel:  [<ffffffff811e4c98>] do_vfs_ioctl+0x2f8/0x500
Mär 24 15:21:30 htpc kernel:  [<ffffffff811ef3e2>] ? __fget+0x72/0xb0
Mär 24 15:21:30 htpc kernel:  [<ffffffff811e4f21>] SyS_ioctl+0x81/0xa0

Mär 24 15:21:30 htpc kernel: [<ffffffff815622e9>] system_call_fastpath+0x12/0x17
Mär 24 15:21:30 htpc kernel: Code: 48 c7 c2 79 52 ee a0 48 c7 c7 20 67 ee a0 48 8d 70 48 31 c0 e8 4d af 3f e0 e9 48 fe ff ff 0f 1f 84 00 00 00 00 00 31 d2 45 31 e4 <66> 41 f7 f7 0f b7 f8 e8 5f 03 67 ff 89 c0 48 8b 7d b8 48 8d 04
Mär 24 15:21:30 htpc kernel: RIP [<ffffffffa0ee4335>] m88ds3103_read_snr+0x205/0x2a0 [m88ds3103]
Mär 24 15:21:30 htpc kernel: RSP <ffff8800dd9a3ba8>
Mär 24 15:21:30 htpc kernel: ---[ end trace 7e7bc66b3dd96971 ]---

Don't know if it matters, but I'm using SCR/Unicable for getting several transponders through to my dvb card. Thus, proper diseqc commands are essential. Maybe that is the issue?

Someone has reported SCR/Unicable does not work with that demod driver, but I have no personal experience from whole thing... Could you try direct connection to LNB?

Am 24.03.2015 um 16:22 schrieb Antti Palosaari:

Quoted 3 lines

Someone has reported SCR/Unicable does not work with that demod driver, but I have no personal experience from whole thing... Could you try direct connection to LNB?

I will test a direct connection over Easter, as I don't have physical access to the htpc right now. I will try to get someone else to test your patch, who hopefully doesn't use SCR.

Ole

Hi Antti,

I was able to test your current tree (8a56b6b..754594d) without SCR and the frontends still run into a timeout. There seems to be an issue with the patch in general. Is there something else I can test/try or do you require some debug output?

Thanks,
Ole

Am 24.03.2015 um 20:51 schrieb Ole Ernst:

Quoted 10 lines

Am 24.03.2015 um 16:22 schrieb Antti Palosaari:

Quoted 3 lines

Someone has reported SCR/Unicable does not work with that demod driver, but I have no personal experience from whole thing... Could you try direct connection to LNB?

I will test a direct connection over Easter, as I don't have physical access to the htpc right now. I will try to get someone else to test your patch, who hopefully doesn't use SCR.

Ole