Vu+
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Polsat Ci CAM issue

Discussion in 'CI Modules' started by spdpl, May 2, 2021.

  1. spdpl

    spdpl Vu+ Newbie

    Messages:
    5
    Hi,

    I've got vu+ duo2, and use Polsat CI CAM.

    I have problems with CI CAM Polsat.

    When i connect new cam, after initialization, CAM works perfectly for 2-3 months. And some day it stops working. Decoder can not see the CI CAM. But from time to time it again see the CAM for 30 seconds, maybe 1 minut, and then again it disappears.

    Turning decoder off, disconnect power for 30 seconds starting decoder, helps for short time 4-5 minutes, and then the problem returns.

    When I return the CAM, they say it works, but as for now, they provide me with new CAM, and everything starts over again, and again. At this time I've already replace 3 CAMs.

    In logs there is only one line repeating all the time:

    May 2 21:59:50 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:00:08 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:00:19 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:00:36 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:00:54 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:01:06 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:01:22 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:01:43 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:01:52 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:02:00 vuduo2 user.warn kernel: [VID]: VIDEO_STOP 1 1
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: AUDIO_STOP 7988016
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7988016 0 aph=0x0
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: AUDIO_CONTINUE aph=0 0 0
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: AUDIO_SELECT_SOURCE 0
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: AUDIO_SET_BYPASS_MODE 1
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: downmix 0 state : 0
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: AUDIO_PAUSE 7988016
    May 2 22:02:00 vuduo2 user.warn kernel: [AUD]: AUDIO_PLAY 7988016 decoder start : 0
    May 2 22:02:00 vuduo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
    May 2 22:02:00 vuduo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 1
    May 2 22:02:00 vuduo2 user.warn kernel: [VID]: VIDEO_FREEZE 7988016 0
    May 2 22:02:00 vuduo2 user.warn kernel: [VID]: VIDEO_PLAY 7988016 5 2
    May 2 22:02:01 vuduo2 user.warn kernel: [VID]: VIDEO_SLOWMOTION 0 1
    May 2 22:02:01 vuduo2 user.warn kernel: [VID]: VIDEO_FAST_FORWARD 0 1
    May 2 22:02:01 vuduo2 user.warn kernel: [VID]: VIDEO_CONTINUE 7988016 1
    May 2 22:02:01 vuduo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7988016 1 aph=0xc9527180
    May 2 22:02:01 vuduo2 user.warn kernel: [AUD]: Mute : 0
    May 2 22:02:01 vuduo2 user.warn kernel: [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
    May 2 22:02:01 vuduo2 user.warn kernel: [VID]: VIDEO_GET_SIZE aspect: 1 0
    May 2 22:02:04 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:02:13 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:02:33 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:02:51 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:03:09 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:03:27 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:03:35 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:03:47 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:03:58 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode
    May 2 22:04:09 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode


    When it stops decoding, it shows on tv screen info that it authenticates module, then that module is authenticated, and that module works fine, but it is not decoding, and it repeats several time, and then it stops even trying to access module.

    Did anyone had similar issues?
    Can I check or change something in decoder to resolve the issue?
    Can I make vuduo to write more details to the log, regarding this issue?

    Regards
     
  2. Thomas67

    Thomas67 Vip

    Messages:
    680
    What image are you using? Is it Balckhole or OpenBlackhole ?
     
  3. spdpl

    spdpl Vu+ Newbie

    Messages:
    5
    It is 2021-02-01-VTI-master.

    But I tried different images, and the problem is the same. I tried:
    openpli
    OpenBlackHole
    openatv

    And this observation is not true "Turning decoder off, disconnect power for 30 seconds starting decoder, helps for short time 4-5 minutes, and then the problem returns." It doesn't matter if If turn decoder off or not. It was just coincident. Today it didn't work.
     
  4. Shiro

    Shiro BH-C

    Messages:
    1,742
    If you use Vti please ask in vti board.
     
  5. spdpl

    spdpl Vu+ Newbie

    Messages:
    5
    Now I use BH. In slot1 there is the same issue:

    May 3 16:01:42 vuduo2 user.warn kernel: !!!Accessing Mem in IO Mode

    When i change it to slot0, after tuner restart, enigma2 is restarting all the time. No additional info in logs.

    Can you provide me with any hints?
     
  6. spdpl

    spdpl Vu+ Newbie

    Messages:
    5
    And one more thing. When I change to OHB 4.1 logs look like this:

    May 3 18:17:10 vuduo2 user.warn kernel: timeout error 1620062225 664474 5000 slot:1
    May 3 18:17:16 vuduo2 user.warn kernel: timeout error 1620062230 724463 5000 slot:1
    May 3 18:17:21 vuduo2 user.warn kernel: timeout error 1620062236 25484 5000 slot:1
    May 3 18:17:26 vuduo2 user.warn kernel: timeout error 1620062241 326381 5000 slot:1
    May 3 18:17:31 vuduo2 user.warn kernel: timeout error 1620062246 385477 5000 slot:1
    May 3 18:17:35 vuduo2 user.warn kernel: >>connection_id : 0, slot id : 0 reason : 4 slot :1
    May 3 18:17:46 vuduo2 user.warn kernel: >>connection_id : 1, slot id : 0 reason : 0 slot :0
    May 3 18:17:46 vuduo2 user.warn kernel: ROLT
    May 3 18:17:46 vuduo2 user.warn kernel: TLPD
    May 3 18:17:47 vuduo2 user.warn kernel: 0: link init fail slot:0
    May 3 18:17:51 vuduo2 user.warn kernel: timeout error 1620062266 245364 5000 slot:0
    May 3 18:17:56 vuduo2 user.warn kernel: timeout error 1620062271 532466 5000 slot:0
    May 3 18:18:02 vuduo2 user.warn kernel: timeout error 1620062276 833489 5000 slot:0
    May 3 18:18:07 vuduo2 user.warn kernel: timeout error 1620062282 194530 5000 slot:0
    May 3 18:18:12 vuduo2 user.warn kernel: timeout error 1620062287 495496 5000 slot:0
    May 3 18:18:17 vuduo2 user.warn kernel: timeout error 1620062292 796461 5000 slot:0
    May 3 18:18:23 vuduo2 user.warn kernel: timeout error 1620062297 856463 5000 slot:0

    I changed the slot in a mean time.

    So the question is: Is it looks more like an issue with decoder( hardware or software) or rather it is an issue with CI module?
     
    Last edited: May 3, 2021
  7. spdpl

    spdpl Vu+ Newbie

    Messages:
    5
    Hey,
    I replaced the CAM again. Now everything works perfectly. So it is not decoder hardware or software issue. It look like it is just shi**y CAM which brokes quite often.

    Anyway, thanks for your help.
    Regards
     

Share This Page