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
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