Bug #3940
Digital Devices MAX S8
0%
Description
Does anyone else have problems with this adapter and tvheadend ?
It keeps loosing signal for me during the scan of muxes.
[ 1100.229160] Digital Devices PCIE bridge driver 0.9.24, Copyright (C) 2010-16 Digital Devices GmbH
[ 1100.229512] DDBridge driver detected: Digital Devices MAX S8 4/8
[ 1100.229532] DDBridge: HW 01010007 REGMAP 00010001
[ 1100.338071] Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2 MAX
[ 1100.338075] init link 0, input 0, regs 00000200
[ 1100.338077] init link 0, input 0, handler 8
[ 1100.338079] init link 0, io 0, dma 0, dmaregs 00000300 bufregs 00002000
[ 1100.338080] init link 0, input 1, regs 00000210
[ 1100.338082] init link 0, input 1, handler 9
[ 1100.338084] init link 0, io 1, dma 1, dmaregs 00000310 bufregs 00002100
[ 1100.338086] Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-S2 MAX
[ 1100.338088] init link 0, input 2, regs 00000220
[ 1100.338090] init link 0, input 2, handler 10
[ 1100.338092] init link 0, io 2, dma 2, dmaregs 00000320 bufregs 00002200
[ 1100.338093] init link 0, input 3, regs 00000230
[ 1100.338095] init link 0, input 3, handler 11
[ 1100.338097] init link 0, io 3, dma 3, dmaregs 00000330 bufregs 00002300
[ 1100.338099] Port 2: Link 0, Link Port 2 (TAB 3): DUAL DVB-S2 MAX
[ 1100.338101] init link 0, input 4, regs 00000240
[ 1100.338102] init link 0, input 4, handler 12
[ 1100.338105] init link 0, io 4, dma 4, dmaregs 00000340 bufregs 00002400
[ 1100.338107] init link 0, input 5, regs 00000250
[ 1100.338108] init link 0, input 5, handler 13
[ 1100.338110] init link 0, io 5, dma 5, dmaregs 00000350 bufregs 00002500
[ 1100.338112] Port 3: Link 0, Link Port 3 (TAB 4): DUAL DVB-S2 MAX
[ 1100.338114] init link 0, input 6, regs 00000260
[ 1100.338116] init link 0, input 6, handler 14
[ 1100.338118] init link 0, io 6, dma 6, dmaregs 00000360 bufregs 00002600
[ 1100.338119] init link 0, input 7, regs 00000270
[ 1100.338121] init link 0, input 7, handler 15
[ 1100.338123] init link 0, io 7, dma 7, dmaregs 00000370 bufregs 00002700
[ 1100.340291] 0 netstream channels
[ 1100.340299] DVB: registering new adapter (DDBridge)
[ 1100.340301] DVB: registering new adapter (DDBridge)
[ 1100.340303] DVB: registering new adapter (DDBridge)
[ 1100.340304] DVB: registering new adapter (DDBridge)
[ 1100.340306] DVB: registering new adapter (DDBridge)
[ 1100.340307] DVB: registering new adapter (DDBridge)
[ 1100.340309] DVB: registering new adapter (DDBridge)
[ 1100.340311] DVB: registering new adapter (DDBridge)
[ 1100.343131] mx5xx: padMuxBond=00000001, prcmChipId=00000584, prcmSoCId=00000003
[ 1100.344687] mxl5xx: Hydra chip version 2
[ 1100.368359] Read mxl_fw from link 0
[ 1105.664346] mxl5xx: Hydra FW alive. Hail!
[ 1105.720648] mxl5xx: chipID=00000001
[ 1105.720982] mxl5xx: chipVer=00000002
[ 1105.721315] mx5xx: FWVer=02010109
[ 1105.840485] mxl5xx: DIGIO = 00000000
[ 1105.840487] mxl5xx: set drive_strength = 1
[ 1105.896082] ddbridge 0000:04:00.0: DVB: registering adapter 0 frontend 0 (MXL5XX)...
[ 1105.944055] ddbridge 0000:04:00.0: DVB: registering adapter 1 frontend 0 (MXL5XX)...
[ 1105.992055] ddbridge 0000:04:00.0: DVB: registering adapter 2 frontend 0 (MXL5XX)...
[ 1106.040054] ddbridge 0000:04:00.0: DVB: registering adapter 3 frontend 0 (MXL5XX)...
[ 1106.040955] ddbridge 0000:04:00.0: DVB: registering adapter 4 frontend 0 (MXL5XX)...
[ 1106.041514] ddbridge 0000:04:00.0: DVB: registering adapter 5 frontend 0 (MXL5XX)...
[ 1106.042406] ddbridge 0000:04:00.0: DVB: registering adapter 6 frontend 0 (MXL5XX)...
[ 1106.042704] ddbridge 0000:04:00.0: DVB: registering adapter 7 frontend 0 (MXL5XX)...
[ 1108.181318] ddbridge 0000:04:00.0: DVB: adapter 7 frontend 0 frequency 0 out of range (950000..2150000)
[ 1108.181673] ddbridge 0000:04:00.0: DVB: adapter 6 frontend 0 frequency 0 out of range (950000..2150000)
[ 1108.181906] ddbridge 0000:04:00.0: DVB: adapter 5 frontend 0 frequency 0 out of range (950000..2150000)
[ 1108.182139] ddbridge 0000:04:00.0: DVB: adapter 4 frontend 0 frequency 0 out of range (950000..2150000)
[ 1108.182369] ddbridge 0000:04:00.0: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)
[ 1108.182603] ddbridge 0000:04:00.0: DVB: adapter 2 frontend 0 frequency 0 out of range (950000..2150000)
[ 1108.182832] ddbridge 0000:04:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000)
[ 1108.183181] ddbridge 0000:04:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)
[ 1971.524054] i2c write error
[ 1971.524114] i2c read error 1
[ 1971.524121] i2c read error 2
[ 1971.524168] i2c write error
[ 1971.524215] i2c write error
[ 1971.524262] i2c read error 1
[ 1971.524267] i2c read error 2
[ 1971.524313] i2c write error
[ 1971.524360] i2c write error
[ 1971.524406] i2c read error 1
[ 1971.524411] i2c read error 2
[ 1971.524456] i2c write error
[ 1971.524502] i2c write error
[ 1971.524632] i2c write error
2016-08-18 04:52:42.496 linuxdvb: MXL5XX : DVB-S #4 - FE_READ_STATUS error Operationen er ikke tilladt
2016-08-18 04:52:42.501 linuxdvb: MXL5XX : DVB-S #5 - FE_READ_STATUS error Operationen er ikke tilladt
2016-08-18 04:52:42.501 linuxdvb: MXL5XX : DVB-S #6 - FE_READ_STATUS error Operationen er ikke tilladt
2016-08-18 04:52:42.503 linuxdvb: MXL5XX : DVB-S #7 - FE_READ_STATUS error Operationen er ikke tilladt
2016-08-18 04:52:42.506 linuxdvb: MXL5XX : DVB-S #3 - FE_READ_STATUS error Operationen er ikke tilladt
2016-08-18 04:52:42.508 linuxdvb: MXL5XX : DVB-S #1 - FE_READ_STATUS error Operationen er ikke tilladt
2016-08-18 04:56:45.782 linuxdvb: MXL5XX : DVB-S #4 - poll TIMEOUT
2016-08-18 04:56:45.787 linuxdvb: MXL5XX : DVB-S #1 - poll TIMEOUT
2016-08-18 04:56:45.795 linuxdvb: MXL5XX : DVB-S #5 - poll TIMEOUT
2016-08-18 04:56:45.795 linuxdvb: MXL5XX : DVB-S #3 - poll TIMEOUT
2016-08-18 04:56:45.806 linuxdvb: MXL5XX : DVB-S #2 - poll TIMEOUT
2016-08-18 04:56:45.806 linuxdvb: MXL5XX : DVB-S #7 - poll TIMEOUT
2016-08-18 04:56:45.809 linuxdvb: MXL5XX : DVB-S #8 - poll TIMEOUT
2016-08-18 04:56:45.819 linuxdvb: MXL5XX : DVB-S #8 - retune nodata
2016-08-18 04:56:45.824 linuxdvb: MXL5XX : DVB-S #4 - retune nodata
2016-08-18 04:56:45.982 linuxdvb: MXL5XX : DVB-S #7 - retune nodata
2016-08-18 04:56:46.118 linuxdvb: MXL5XX : DVB-S #1 - retune nodata
2016-08-18 04:56:46.196 linuxdvb: MXL5XX : DVB-S #2 - retune nodata
2016-08-18 04:56:46.233 linuxdvb: MXL5XX : DVB-S #3 - retune nodata
2016-08-18 04:56:46.374 linuxdvb: MXL5XX : DVB-S #5 - retune nodata
Ubuntu 14.04 4.4.0-34-generic
History
Updated by Alfred Zastrow about 8 years ago
Updated by Pls try this:
create this file:
/etc/modprobe.d/ddbridge.conf
with this content:
options ddbridge msi=0
Updated by Mark Clarkstone about 8 years ago
Updated by - Status changed from New to Invalid
This is a hardware issue 
not a Tvheadend one. Please use the forums 
Updated by danny skjodt about 8 years ago
Updated by Alfred Zastrow wrote:
Pls try this:
create this file:
/etc/modprobe.d/ddbridge.conf
with this content:
options ddbridge msi=0
Already using that folowed the guide on : http://support.digital-devices.eu/knowledgebase.php?article=151
Mark Clarkstone wrote:
This is a hardware issue
If its a hardware issue, why does it not happend in mediaportal, astra dvblast etc other dvb software.
Updated by Mark Clarkstone about 8 years ago
danny skjodt wrote:
Alfred Zastrow wrote:
Pls try this:
create this file:
/etc/modprobe.d/ddbridge.conf
with this content:
options ddbridge msi=0
Already using that folowed the guide on : http://support.digital-devices.eu/knowledgebase.php?article=151
Mark Clarkstone wrote:
This is a hardware issue
If its a hardware issue, why does it not happend in mediaportal, astra dvblast etc other dvb software.
It looks like Tvheadend is using all tuners to scan at once and the driver (or hardware) can't keep up. IIRC mediaportal only uses one tuner at a time to do a scan (it did the last time I used it) and I'm pretty sure the others do the same.
Try using one tuner only and see if it happens then.
Updated by danny skjodt about 8 years ago
That helped, I notice now that even zapping channels fast like staying 0.1 second on each before zapping to next cause the driver to crash also. I want my money back
Updated by Mark Clarkstone about 8 years ago
danny skjodt wrote:
That helped, I notice now that even zapping channels fast like staying 0.1 second on each before zapping to next cause the driver to crash also. I want my money back
If you have time (before the option of return expires) contact Digital Devices - they should be able to help.