Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.

View Entry Info: ViX 6.3.003 bogs my box down

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
6.3.003
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
Yes
Attachments
Page 3 of 5 FirstFirst 12345 LastLast
Results 31 to 45 of 65

Thread: ViX 6.3.003 bogs my box down

  1. #31

    Title
    Member
    Join Date
    Nov 2011
    Posts
    35
    Thanks
    8
    Thanked 8 Times in 6 Posts
    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?
    Vu+ Duo 4K SE

  2. #32
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,626
    Thanks
    2,006
    Thanked 4,953 Times in 3,274 Posts
    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.
    Help keep OpenViX servers online.Please donate!

  3. #33

    Title
    ViX Beta Tester
    Join Date
    Nov 2020
    Location
    Finland
    Posts
    625
    Thanks
    217
    Thanked 77 Times in 64 Posts
    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' ...
    Last edited by Orlandox; 07-03-23 at 15:22.

  4. #34

    Title
    Member
    Join Date
    Nov 2011
    Posts
    35
    Thanks
    8
    Thanked 8 Times in 6 Posts
    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.


    003.jpg
    Vu+ Duo 4K SE

  5. #35

    Title
    Member
    Join Date
    Nov 2011
    Posts
    35
    Thanks
    8
    Thanked 8 Times in 6 Posts
    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.
    Last edited by Micci; 08-03-23 at 19:20.
    Vu+ Duo 4K SE

  6. #36
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,626
    Thanks
    2,006
    Thanked 4,953 Times in 3,274 Posts
    Quote Originally Posted by Micci View Post
    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.
    Help keep OpenViX servers online.Please donate!

  7. #37

    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2012
    Posts
    600
    Thanks
    92
    Thanked 112 Times in 86 Posts
    Quote Originally Posted by Huevos View Post
    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.

  8. #38

    Title
    ViX Beta Tester
    Join Date
    Nov 2020
    Location
    Finland
    Posts
    625
    Thanks
    217
    Thanked 77 Times in 64 Posts
    Quote Originally Posted by Huevos View Post
    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.

  9. #39

    Title
    Member
    Join Date
    Nov 2011
    Posts
    35
    Thanks
    8
    Thanked 8 Times in 6 Posts
    Quote Originally Posted by Huevos View Post
    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.
    Last edited by Micci; 09-03-23 at 08:01.
    Vu+ Duo 4K SE

  10. #40

    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2012
    Posts
    600
    Thanks
    92
    Thanked 112 Times in 86 Posts
    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.

  11. #41
    Ev0's Avatar
    Title
    V.I.P
    Join Date
    Jan 2011
    Posts
    1,053
    Thanks
    347
    Thanked 428 Times in 266 Posts
    Quote Originally Posted by tappari View Post
    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 ?


  12. #42

    Title
    Member
    Join Date
    Nov 2011
    Posts
    35
    Thanks
    8
    Thanked 8 Times in 6 Posts
    Quote Originally Posted by Ev0 View Post
    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?
    Vu+ Duo 4K SE

  13. #43
    Ev0's Avatar
    Title
    V.I.P
    Join Date
    Jan 2011
    Posts
    1,053
    Thanks
    347
    Thanked 428 Times in 266 Posts
    Has anyone tried using the openpli ci helper files, to see if anything changes (for the better or for the worse) ?


  14. #44

    Title
    Member
    Join Date
    May 2014
    Posts
    77
    Thanks
    1
    Thanked 27 Times in 18 Posts
    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.

  15. The Following 2 Users Say Thank You to Samzam For This Useful Post:

    Micci (09-03-23),tappari (09-03-23)

  16. #45

    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2012
    Posts
    600
    Thanks
    92
    Thanked 112 Times in 86 Posts
    This is true. Along with VU+ Multiboot ViX adopted too many things from BH image.

Page 3 of 5 FirstFirst 12345 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.