[dvblast-devel] dvblast - cannot go further

[Christophe Massiot]

You can try -y 99, it will try to open ca99 which doesn't exist so it will just fail and ignore CA device.

> On 18 Apr 2025, at 19:49, Henrik SEKUJ <henrisekuj at yahoo.com> wrote:
> 
> thank you for the help
>  I think that driver is the problem too. I am using a linux stb zgemma h7, that has one adatper0 with three frontends: one frontend0 satellite and 1,2 terrestial and cable each
> I log the first steps:
> 
> root at h7:~# dvblast -a 0 -n 1 -f 852000000 -s 6900000 -5 DVBC_ANNEX_A -m qam_256
> DVBlast 3.4 (git-3.4-7-g6fa5ef5-dirty)
> warning: restarting
> debug: compiled with DVB API version 5.10
> debug: using DVB API version 5.10
> debug: Frontend "DVB-T/T2/C" supports:
> debug:  frequency min: 48250000, max: 863250000, stepsize: 62500, tolerance: 0
> debug:  symbolrate min: 0, max: 9360000, tolerance: 4000
> debug:  capabilities:
> debug:   INVERSION_AUTO
> debug:   FEC_1_2
> debug:   FEC_2_3
> debug:   FEC_3_4
> debug:   FEC_4_5
> debug:   FEC_5_6
> debug:   FEC_6_7
> debug:   FEC_7_8
> debug:   FEC_8_9
> debug:   FEC_AUTO
> debug:   QAM_16
> debug:   QAM_32
> debug:   QAM_64
> debug:   QAM_128
> debug:   QAM_256
> debug:   QAM_AUTO
> debug:   BANDWIDTH_AUTO
> debug:   GUARD_INTERVAL_AUTO
> debug:   HIERARCHY_AUTO
> debug:   MULTISTREAM
> debug:   FE_CAN_RECOVER
> debug:   FE_CAN_MUTE_TS
> debug:  delivery systems:
> debug:   DVBT2
> debug:   DVBT
> debug:   DVBC_ANNEX_A
> debug:   DVBC_ANNEX_C
> debug: tuning DVB-C frontend to f=852000000 srate=6900000 inversion=-1 modulation=qam_256
> debug: CA interface with 2 slots
> debug:   CI high level interface type
> debug:   CI link layer level interface type
> debug:   CI physical layer level interface type (not supported) 
> debug:   built-in descrambler detected
> debug:   simple smart card interface
> debug:   8 available descramblers (keys)
> debug:   ECD scrambling system supported
> debug:   NDS scrambling system supported
> CAM none
> error: en50221_Poll: couldn't reset slot 0
> CAM none
> error: en50221_Poll: couldn't reset slot 1
> debug: setting filter on PID 0
> debug: setting filter on PID 16
> debug: setting filter on PID 17
> debug: setting filter on PID 18
> debug: setting filter on PID 19
> debug: setting filter on PID 20
> error: no config file
> error: en50221: cannot read from CAM device (-1:Invalid argument)
> error: en50221_Poll: couldn't get info on slot 0
> error: en50221_Poll: couldn't get info on slot 1
> error: en50221: cannot read from CAM device (-1:Invalid argument)
> error: en50221: cannot read from CAM device (-1:Invalid argument)
> error: en50221: cannot read from CAM device (-1:Invalid argument)
> -----million of this line--
> 
> info hardware:
> 
> root at h7:~# ls /dev/dvb/adapter0
> audio0     ca1        ca3        ca5        ca7        demux1     demux3     demux5     demux7     dvr1       dvr3       dvr5       dvr7       frontend1  video0
> ca0        ca2        ca4        ca6        demux0     demux2     demux4     demux6     dvr0       dvr2       dvr4       dvr6       frontend0  frontend2
> root at h7:~#
> 
> The drivers are closed source and too old, kernel's  4.12(I think older)
> Many utilities has problem tuning with them, especially cable, but enigma2 application not. It compensates all driver problems and tunes ok   and with maximum  signal strength
> 
> May be dvblast can tune ok also. We cannot verify it because of this persistent check of ci where there is not any cam & card inserted, not needed because transponder is fta
> 
> All I need is to disable cam module
> 
> thanking for the help
> 
> 
> 
> 
> 
> On Friday, April 18, 2025 at 01:35:05 AM GMT+2, Christophe Massiot <cmassiot at upipe.org> wrote:
> 
> 
> Which DVB card are you using? It seems the driver is buggy.
> 
>> On 17 Apr 2025, at 21:17, Henrik SEKUJ <henrisekuj at yahoo.com> wrote:
>> 
>> Hello,
>> 
>> I am playing with dvblast, let it to examine the transponder when I have a lot of 
>> 
>> error: en50221: cannot read from CAM device (-1:Invalid argument)
>> 
>> quite 45mb of this line in few seconds
>> Please tell me how can avoid this
>> If it has to be with CI, I dont need it, how can I disable CAM module completely?
>> 
>> thanks in advance
>> 
>> _______________________________________________
>> dvblast-devel mailing list
>> dvblast-devel at videolan.org
>> https://mailman.videolan.org/listinfo/dvblast-devel
> 
> _______________________________________________
> dvblast-devel mailing list
> dvblast-devel at videolan.org <mailto:dvblast-devel at videolan.org>
> https://mailman.videolan.org/listinfo/dvblast-devel
> _______________________________________________
> dvblast-devel mailing list
> dvblast-devel at videolan.org
> https://mailman.videolan.org/listinfo/dvblast-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/dvblast-devel/attachments/20250418/d83918c2/attachment-0001.htm>