View Full Version : [VU+ Duo4K SE] ViX 6.3.003 bogs my box down
Tried to couch flash the version 6.3.003, but the TV picture freezes on every channel and the box becomes very sluggish. When I try to couch flash back to the previous version, the box stops at the backup manager at the very beginning and won’t start the flash at all.
Had to finally flash 6.3.002 from a USB stick.
No one else has this problem and it has been heavily tested on the Vu+ Duo4k SE. So if you want help you are going to need to provide us with debug logs. Most likely you had a background process running.
I'm afraid I don't know how to get any logs. And besides, I've already flashed back to .002. Another Duo 4K SE owner on a Finnish forum said 6.3.003 stopped his CI+ from working (His Ultimo 4K was working fine on 6.3.003, though). Admittedly my channels freezing looked just like the CI+ stopped working, but it did this on FTA channels as well.
After I flashed back to .002, I had to pull the CI+ module out and push it back in again before any scrambled channels started working.
I'm afraid I don't know how to get any logs. And besides, I've already flashed back to .002. Another Duo 4K SE owner on a Finnish forum said 6.3.003 stopped his CI+ from working (His Ultimo 4K was working fine on 6.3.003, though). Admittedly my channels freezing looked just like the CI+ stopped working, but it did this on FTA channels as well.
After I flashed back to .002, I had to pull the CI+ module out and push it back in again before any scrambled channels started working.
This is true. I first made coachflas with 003. Then fresh flash with usb-stick without restore. CI+ is not working.
I had ViX 5.4 016 with Openmultiboot and there CI+ was working.
In my Ultimo4K no problem with 003/CI+.
Obviously something wrong in VU+ Duo4K SE image 6.3 003.
This is the adapter
64934
Works fine now with 6.3 002 image.
Can you guys check FCC plugin is showing in tuner menu on Duo 4K SE
This is true. I first made coachflas with 003. Then fresh flash with usb-stick without restore. CI+ is not working.
I had ViX 5.4 016 with Openmultiboot and there CI+ was working.
In my Ultimo4K no problem with 003/CI+.
Obviously something wrong in VU+ Duo4K SE image 6.3 003.So he says FTA channels freeze. Can you check this out. And check again with CI module removed.
Can you guys check FCC plugin is showing in tuner menu on Duo 4K SE
Do you mean Fast Channel Change? Yes, that menu item is there on my .002. Suppose it's also there on .003 if I flash it and then drop in my settings backup.
Never used it though. Didn't even know it was a plugin. I've never installed such a plugin.
Will have to do any testing some other time when the family doesn't need to watch TV.
Originally this was tested by Orlandox on Ultimo4k and says it works ok on finnish channels.
Tried now to remove the FCC plugin prior to flashing to 6.3.003, so the plugin wasn’t in my plugins list in the backup file. There were some strange screens with german text flashing by a couple of times while restoring the settings backup. These screens were there when I flashed .003 the last time as well. Otherwise the 1st bootup sequence seemed normal.
The TV channels started freezing as soon as the box booted up again. Yes, the FTA channels too. Removed the CI+ module, and the FTA channels started working fine (but of course I could not view any paid channels). Reinserted the CI+ module and the freezing resumed.
The Common Interface menu says ”no module found” while the channels are frozen. When it says ”Conax CA” the channels work fine.
The picture freezes every 10-20 seconds or so and stays frozen for 5 seconds and up. And while this happens, the text in the Common interface menu changes between ”no module found” and ”Conax CA”.
Flashed back to .002. The mrs needed to watch the news.
Just for info with 6.3.003 you can use vu+ multiboot
Activate it in standby/restart then image manager flash 6.3.003 into slot 1 then your backup into slot 2
This way you can easily boot images as and when needed
Originally this was tested by Orlandox on Ultimo4k and says it works ok on finnish channels.
It also works in my Ultimo4K but not in my Duo4K SE on finnish paytv channels when CI+ is needed. I have not yet tested it in my Uno4K SE.
It also works in my Ultimo4K but not in my Duo4K SE on finnish paytv channels when CI+ is needed. I have not yet tested it in my Uno4K SE.
Thats really interesting ..positive result on Uno4k would indicate issue with Duo4K drivers? - learned recently has issues with usb 3 connection.
Thats really interesting ..positive result on Uno4k would indicate issue with Duo4K drivers? - learned recently has issues with usb 3 connection.
I just made flash to Uno4K SE with settings and plugins restore.
Ci+ authentication was quite slow, but it works. So no problem with 6.3 003.
I think with Duo4K SE problem is, that it did not make proper CI+ authentication.
I've just done a complete new flash and setup on Duo 4K SE. Tested with two CI+ Cam types and two card types, no issues at all with CI+. My 4K Tivusat card even updated itself as new use in a while. Also tested with fast channel change on and off, no issues.
Are the people with the problem using some kind of "helper" plugin?
If so you need to set up from scratch without the plugin.
Hello,
FCC working OK on my Ultimo4K, but with CI+ I have same problems than in post #10. I have reported that already before.
Ultimo4K refuses to go further than this if you want to see Conax information:
64951
And why this message is in German language?
64952
Can you guys check if you have the same problem on OpenBH 5.2 or Vu factory image?
Just save current image in multiboot.
Can you guys check if you have the same problem on OpenBH 5.2 or Vu factory image?
Just save current image in multiboot.
I can check it with OpenBH 5.2.002 later at my Ultimo4K.
P.S. My coffee break is over, have to continue work.
Are the people with the problem using some kind of "helper" plugin?
If so you need to set up from scratch without the plugin.
If you are referring to some kind of ”ciplushelper”, then no, not to my knowledge. Tinkered with one ages ago on a different image, but never on ViX.
How to check and see if there is such a plugin? And is there really no other way to remove it but to start from scratch?
Can you guys check if you have the same problem on OpenBH 5.2 or Vu factory image?
Just save current image in multiboot.
OpenBH has same problem with Conax info
64955
Yes, I can confirm that also.
64956
P.S. OpenPLi shows 'initialize module', but no disturbancies or freezing on picture.
64957
I made again clean flash without restoring setups and plugins with 003 to my Duo4K SE.
This is what happens when I insert CI+ adapter and card:
64963
It does not go further from this.
I made again clean flash without restoring setups and plugins with 003 to my Duo4K SE.
This is what happens when I insert CI+ adapter and card:
64963
It does not go further from this.Is this the same Finnish module the others are using?
Mine is a "LA Digital" (Smit) CI+ module. It shows up as "Conax CA" in the Common Interface menu.
I also have a "Finnsat CAMC-CIP" (Neotion) module that shows up as "Conax CSP CIPLUS CAM" in the Common Interface menu.
Both seem to be working in 6.3.002, although I had to reboot my box yesterday when the paychannels went black on the LA Digital (a very rare occurrence indeed).
Didn't try the Finnsat module in .003.
Mine is also Smit. This info is from 6.3 002 image:
64964
I just wonder if CI+ authentication system is from ATV because all messages are in German language?
I just wonder if CI+ authentication system is from ATV because all messages are in German language?That German is not in our enigma so no idea where it is coming from.
Somezing german has slipped into the 6.3.003 package for the Duo 4K SE?
My box had some screens in german flicker by when I was restoring my backup at 1st boot. Never done that before.
And I believe german images don't work too well together with CI+ cards.
Herr Flick of ze Gestapo has gone undercover inside our boxes?
The German is not in our enigma (based on a search of the enigma repo and its translations) so must be coming from some third party module.
From debug log:
< 225.4017> 16:15:13.3582 [CI] eDVBCIInterfaces setInputSource(10, CI1)
< 225.4027> 16:15:13.3591 [CI] Slot: 1 setSource: K
< 228.8615> 16:15:16.8179 eDVBCICAManagerSession::setCAIDs casCount = 0
< 232.0273> 16:15:19.9838 [CI] eDVBCIInterfaces setInputSource(10, CI1)
< 232.0281> 16:15:19.9845 [CI] Slot: 1 setSource: K
< 235.7083> 16:15:23.6647 eDVBCICAManagerSession::setCAIDs casCount = 0
< 238.8616> 16:15:26.8180 [CI] eDVBCIInterfaces setInputSource(10, CI1)
< 238.8624> 16:15:26.8188 [CI] Slot: 1 setSource: K
and that continues about 3 min and 13 sec after that no disturbancies and no picture freezing. But it still shows 'no module found' ...
Flashed to 6.3.003 again and am testing the Finnsat/Neotion CA module instead of the Smit module. Now everything seems to be working. But the CI info is all in german, just like Tappari said.
Will try to see if I can make a multiboot and have my .002 in the other boot slot, just in case.
64965
Is there a fix coming for those who have a Smit CI+ module? Someone on the Finnish forum noticed there were some changes to the CI files between .002 and .003.
Everything was running like a dream until .003.
IF IT WORKS, DON’T FIX IT.
I also noticed a difference during 1st boot between .002 and .003. I used the exact same Settings Backup file and restored settings & plugins to both images using the file.
.002 restore went without a hitch and rebooted to a working setup. Both CI+ modules are working.
.003 showed a message in german about a CI error (”CI fehler”) during the restore, until it eventually finished and rebooted. The Smit CI+ module doesn’t work. The Neotion module works, but it’s a bit slow with channel changes.
IF IT WORKS, DON’T FIX IT.Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.
Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.
With which modules it didn`t work? And what are those lot more modules?
Please list them.
Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.
Is it possible to add a selectable parameter to 'CiSelection' menu, where you can select your module type ? Then both module types should work OK.
Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.
You can't be serious that I'll have to throw away BOTH my modules. One of them is a very new one (supposed to be state-of-the-art) and it started working very sluggishly after the update (channel changes are much slower). Both were working just fine before.
Can you list the modules that DO work, so I don't waste any more money on the wrong one.
Why did you at first deny that there were any changes to the CI files, when there clearly are? And why don't these problems affect any other boxes, just the Duo 4K SE?
Again, if it works, don't fix it.
I have 4 modules and SmartWi 3 with 4 client cards. Ultimo4K, Duo4K SE, Uno4K SE and Sony tv are using those.
I`m not going to by 3 new adapters and pair them just because of 6.3 003 image failures.
I just use VU+ Multiboot and 002 image and watch if you and OpenBlackHole team can fix it.
With which modules it didn`t work? And what are those lot more modules?
Please list them.
How can anyone list which modules work and which ones don't, without having access to every module out there to test with ?
How can anyone list which modules work and which ones don't, without having access to every module out there to test with ?
Then how can one say it works with a lot more modules, if they can't test them?
Has anyone tried using the openpli ci helper files, to see if anything changes (for the better or for the worse) ?
There always has been two kind of images related to ci-modules. German based group OpenATV, OpenBH, VTi and UK based group OpenVIX, PurE2, OpenPLi. Some modules works only in German group and some modules work only in UK group and some might work on both. Now OpenVIX has jumped to German group and my ci-module is working only in UK group so I must change a enigma2 image to somenthing other if I want to get newest image updates.
This is true. Along with VU+ Multiboot ViX adopted too many things from BH image.
This is true. Along with VU+ Multiboot ViX adopted too many things from BH image.
As much as I understand your frustration, the issue with the CI modules has nothing to do with the E2 images from ViX or BH, except how the Ci+ modules are included.
.. and as I wrote a significant amount of the Vu Multiboot E2 code, I take it that you don't think much of my contribution. So if you don't like it, don't use it .
As much as I understand your frustration, the issue with the CI modules has nothing to do with the E2 images from ViX or BH, except how the Ci+ modules are included.
.. and as I wrote a significant amount of the Vu Multiboot E2 code, I take it that you don't think much of my contribution. So if you don't like it, don't use it .
It`s not the question of frustration or your contribution but the thing is that most of CI+ modules don`t work with OpenViX 6.3 003 image. Of cource we don`t use 003 version at the moment. 002 version runs like Buick.
Guys, I've had quick browse through this thread, whoever is having an issue have you done a complete NEW flash with NO RESTORE. Setup the receiver complete new. So go through the setup wizard, then do a new scan and insert the CI+ Module.
***DO NOT INSTALL ANY EXTRA PLUGINS. USE A VIRGIN IMAGE. LEAVE FAST CHANNEL CHANGE AS OFF TO TEST INITIALLY.***
Also what's the encryption method your cards are using?
It`s not the question of frustration or your contribution but the thing is that most of CI+ modules don`t work with OpenViX 6.3 003 image. Of cource we don`t use 003 version at the moment. 002 version runs like Buick.
I've tested TWO brands of CI+ modules without issue and two types of Nagravision smartcards. So you statement of 'most' is a bit baseless.
Guys, I've had quick browse through this thread, whoever is having an issue have you done a complete NEW flash with NO RESTORE. Setup the receiver complete new. So go through the setup wizard, then do a new scan and insert the CI+ Module.
***DO NOT INSTALL ANY EXTRA PLUGINS. USE A VIRGIN IMAGE. LEAVE FAST CHANNEL CHANGE AS OFF TO TEST INITIALLY.***
Also what's the encryption method your cards are using?
This does not help because ViX Ci+ comes from OpenBlackHole image when you are using ViX 003 image.
Hello guys,
let's cool down and think about how to solve this to make everybody happy. What about what I wrote at post #38 ? Is it possible to do ? So for example if you select CAM type 1 -> it uses Ci.py code from 6.3.002 and if you select CAM type 2 it uses Ci.py code from 6.3.003 ? So is it possible to make some kind of 'if..then else' -sentences of python3 ? Just a thought...
I've tested TWO brands of CI+ modules without issue and two types of Nagravision smartcards. So you statement of 'most' is a bit baseless.
So you Sicilian tell us what bradns of Ci+ modules you have been testing and after that quit your bullshit.
So you Sicilian tell us what bradns of Ci+ modules you have been testing and after that quit your bullshit.
Why would I 'bullshit'??? I think you need to calm your attitude down! Do you want me to post a video of them working or something???
One is the Smardcam Tivusat 4K Cam with the latest Black 4K card (Nagravision). The other I have not got to hand right now, from memory it was Telesystem smarcam with Gold HD (Nagravision) card.
Why would I 'bullshit'??? I think you need to calm your attitude down! Do you want me to post a video of them working or something???
One is the Smardcam Tivusat 4K Cam with the latest Black 4K card (Nagravision). The other I have not got to hand right now, from memory it was Telesystem smarcam with Gold HD (Nagravision) card.
Tivusat explains the Italian need.
This does not help because ViX Ci+ comes from OpenBlackHole image when you are using ViX 003 image.
Please point out this change on our repo.
Another problem with .003: Scrolling through the channel list is very choppy. It stops and skips all the time.
Not so in .002, which is very fast and smooth.
The settings on both images are identical.
Hello,
looks like 6.3.004 solved CI+ problems here in Finland. Thanks for that !
looks like 6.3.004 solved CI+ problems here in Finland. Thanks for that !People will need to find something else to shout about now.
Same for me in Germany :-)
Thanks
Yes, the CI+ module seems to be working now.
But is there some sort of memory leak or something in these last images (.003 to .005)? After a while (a day or so), scrolling through menus and the channel list starts stuttering really badly. A reboot usually helps, but the problem returns again soon.
I am using the new built-in multiboot, if that does affect it in any way.
Yes, the CI+ module seems to be working now.
But is there some sort of memory leak or something in these last images (.003 to .005)? After a while (a day or so), scrolling through menus and the channel list starts stuttering really badly. A reboot usually helps, but the problem returns again soon.
I am using the new built-in multiboot, if that does affect it in any way.
If you are using the Vu multiboot(?) how many images have you installed - in eMMC or on usb ?
All are installed in the internal flash (I guess that's the eMMC you are speaking of?).
0: 6.3.003 (fallback image, not used)
1: 6.3.005 (main image)
2: 6.3.002
EDIT:
Memory usage, freshly booted.
Total memory 1619080
Free memory 1325836
Buffers 8228
Cached 125852
Total swap 0
Free swap 0
FLASH
Total 3.5G
Free 1.9G
Yes, the CI+ module seems to be working now.
But is there some sort of memory leak or something in these last images (.003 to .005)? After a while (a day or so), scrolling through menus and the channel list starts stuttering really badly. A reboot usually helps, but the problem returns again soon.
I am using the new built-in multiboot, if that does affect it in any way.
I think there is an issue with lcd4linux, it has been reported to the plugin author to fix.
Is that so? I am using LCD4Linux as well, so it’s a possibility. Is it a memory leak?
Is that so? I am using LCD4Linux as well, so it’s a possibility. Is it a memory leak?
No idea, i've not looked into it, just seen a report of similar issues to what you have said and the author has been notified
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.