Jump to content


Photo

EDISION OS MIO+4K

tuner

  • Please log in to reply
120 replies to this topic

Re: EDISION OS MIO+4K #21 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 18:54

This is OPENPLI Nightly Build image. 

 

The same problem is with OPENPLI 8.3. With OPENPLI 8.3 there is another problem, green screen. If I select tuner A DVB-S2X and tuner B only DVB-T2 (instead DVB-T2 + DVB-S2) when I go to signal finder or if I'd like to perform manual scan with DVB-T2 (switching between tuners) the system crashes (green screen). The seller in my country knows about this issue and he said OPENPLI should resolve it. When the channels are installed I can watch DVB-T2 (tuner B) and DVB-S2X (tuner A). If I have tuner B DVB-T2 + DVB-S2 (both enable) there is no green screen using signal finder or manual scan.

 

But programs with high SR have the same problem with all image except OPENPLI 7.3. and OPENATV 6.3. All new image have that problem (I tried also: OPENATV 7.1, OPENATV 7.2., OPENHDF 7.0, OPENVIX 6.3.).

 

When I was trying to understand what was the problem (first I thought it was multistream (Italians) the problem) than I realized programs with high SR have the same problem "Tune failed!" Some channels (Czech and VTK do not broadcast any more) with problem:

 

Italians 5°W SR  35300   MS

Italians 9°E  31400 and 41950   MS (checked today)

VTV 51,5°E 45000

Czech 51,5°E 45000

VTK 45°E 30000

Russians on 80°E  45000 (checked today)



Re: EDISION OS MIO+4K #22 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 20 December 2023 - 19:06

Anyway, the AVL6261 driver for the two, now three images will be the same T2MI-Enabled 5.15 kernel version for all three images.

From the debug log:
[eDVBServicePMTHandler] tune failed.
[eDVBServicePlay] DVB service failed to tune - error 1
[eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
[eDVBServicePMTHandler] incorrect namespace. expected: 5a0000 current: ffffffff
[eDVBServicePMTHandler] incorrect transport_stream_id. expected: 18e1 current: ffffffff
[eDVBServicePMTHandler] incorrect original_network_id. expected: 217c current: ffffffff

 

 

As a test, you might want to install a fresh install of the nightly build on one of the receiver slots without restoring or importing anything. Manually Scan only one satellite and see if the problem exists.
 


Edited by el bandido, 20 December 2023 - 19:07.


Re: EDISION OS MIO+4K #23 WanWizard

  • PLi® Core member
  • 70,219 posts

+1,798
Excellent

Posted 20 December 2023 - 19:12

Note that the develop build is undergoing BSP changes at the moment and may not be stable. Use 9.0-release instead, there is no difference when it comes to scanning and drivers.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: EDISION OS MIO+4K #24 rantanplan

  • PLi® Contributor
  • 1,857 posts

+87
Good

Posted 20 December 2023 - 19:26

Was this debug log created as a takeover without a settings list?
Could there be a utf8 problem in the settings?

A debuglog without adopting settings would be desirable.
So simply set up the image (9.0/develop) clean.



Re: EDISION OS MIO+4K #25 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 19:30

Anyway, the AVL6261 driver for the two, now three images will be the same T2MI-Enabled 5.15 kernel version for all three images.

From the debug log:
[eDVBServicePMTHandler] tune failed.
[eDVBServicePlay] DVB service failed to tune - error 1
[eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
[eDVBServicePMTHandler] incorrect namespace. expected: 5a0000 current: ffffffff
[eDVBServicePMTHandler] incorrect transport_stream_id. expected: 18e1 current: ffffffff
[eDVBServicePMTHandler] incorrect original_network_id. expected: 217c current: ffffffff

 

 

As a test, you might want to install a fresh install of the nightly build on one of the receiver slots without restoring or importing anything. Manually Scan only one satellite and see if the problem exists.

I tried in the past. Total reset of the receiver. I used one SW, (I don't remember the name), because one image (I don't remember the name), has crashed and the receiver didn't boot. After that, I had to install image from USB. So the boot logo now is not Edision but OPENATV.

Could be a LNB problem? If yes, why the OPENPLI 7.3 works OK?



Re: EDISION OS MIO+4K #26 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 19:32

Was this debug log created as a takeover without a settings list?
Could there be a utf8 problem in the settings?

A debuglog without adopting settings would be desirable.
So simply set up the image (9.0/develop) clean.

I'll try fresh install in one slot without import anything (no plugin, no channel list, no nothing)



Re: EDISION OS MIO+4K #27 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 20 December 2023 - 19:58

The bootlogo change from Edision to OpenATV is no concern. Put in a simple way, PLi images do not change the manufacturer logo while OpenATV does. This is why you still see the OpenATV logo when a PLi image is installed. Nothing to worry about.



Re: EDISION OS MIO+4K #28 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 19:59

I made a fresh installation of OPENPLI 9.0. No green screen switching between tuners like on the 8.3. This is very good.

I made a manual scan just of CH 27 (DVB-T) and DVB-S2X 9°E 12466V 16APSK 419502/3 PLS Gold 262140 Multistream Stream 12. The transponder data were in the image. I will report you after 20-30 minutes.



Re: EDISION OS MIO+4K #29 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 20:36

Tune failed. I waited 31 minutes, than I turned on the receiver and the there is the same problem. The problem could be the image or receiver or LNB. Any idea what to do (any test to make)?



Re: EDISION OS MIO+4K #30 WanWizard

  • PLi® Core member
  • 70,219 posts

+1,798
Excellent

Posted 20 December 2023 - 20:40

SR issues are either the tuner itself (in which case it will never work) or the tuner driver ( in which case the manufacturer has to fix it, it is closed source ).

 

If Edision can't or won't, it suggests that they too have dumped their in-house developer and have lost the capability to fix it.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: EDISION OS MIO+4K #31 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 20:45

But why the old 7.3 is working OK?



Re: EDISION OS MIO+4K #32 Tech

  • Forum Moderator
    PLi® Core member
  • 14,888 posts

+485
Excellent

Posted 20 December 2023 - 20:47

Different/other drivers?


Aan de rand van de afgrond is een stap voorwaarts niet altijd vooruitgang....

On the edge of the abyss, a step forward is not always progress....

Hardware: 2x Daily used Vu+ Ultimo 4K - Vu+ Duo 4K SE and a lot more.... - VisioSat BiBigsat - Jultec Unicable Multiswitch 4 positions: 19.2/23.5/28.2 East - Diseqc motorized flatdish antenna

Software : HomeBuild OpenPLi Develop and Scarthgap builds, local cards driven by OsCam

Press the Posted Image button on the buttom right of this message ;)

Have you tried our wiki yet? Many answers can be found in our OpenPLi wiki


Re: EDISION OS MIO+4K #33 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 20:51

Is it possible to change drivers only?



Re: EDISION OS MIO+4K #34 WanWizard

  • PLi® Core member
  • 70,219 posts

+1,798
Excellent

Posted 20 December 2023 - 20:56

7.3 release uses the driver set dated 20200409, which was updated to 20211103 on Nov 4, 2021 by Edision, for the upgrade to the 5.15 kernel.

 

As I said before, it looks like a driver regression and Edision needs to fix that, they are the only ones with the driver source code.

 

Using old drivers isn't possible with Edision, as they are linked to the kernel version, and Edision is the only vendor that updates those regularly.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: EDISION OS MIO+4K #35 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 20 December 2023 - 21:19

What about 7.3 and working channels T2 MI (33°E)?



Re: EDISION OS MIO+4K #36 WanWizard

  • PLi® Core member
  • 70,219 posts

+1,798
Excellent

Posted 20 December 2023 - 21:28

Then you'll have to backport a lot of enigma code. If at all possible,

 

The only options you have are

  1. continue bugging Edision until they fix their problem.
  2. and continue doing that.
  3. if not getting a response, get a box that does support what you want.
  4. or get a developer that can get a new enigma branch to run on an old OE.

Don't expect any of us to do 4. for you, a lot of work for solving someone elses ( = Edision) problem...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: EDISION OS MIO+4K #37 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 20 December 2023 - 22:16

What about 7.3 and working channels T2 MI (33°E)?

What is the kernel version of this image that works correctly for you????
Menu--->Information--->About



Re: EDISION OS MIO+4K #38 WanWizard

  • PLi® Core member
  • 70,219 posts

+1,798
Excellent

Posted 20 December 2023 - 22:25

From what I can see, 7.3-release on the Edision OS Mio+ 4K uses kernel 5.5.16.

 

OpenPLi 8.x and newer use 5.15.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: EDISION OS MIO+4K #39 Jamo1700

  • Senior Member
  • 37 posts

+1
Neutral

Posted 21 December 2023 - 00:34

OPENPLI 7.3 has Kernel 5.5.16 and is working OK, except for T2 MI (33°E).



Re: EDISION OS MIO+4K #40 Dimitrij

  • PLi® Core member
  • 10,262 posts

+347
Excellent

Posted 21 December 2023 - 11:01

Jamo1700

 

1)When go another service/satttelite same messsage "Tune failed"?

2)When not use standby all switch services work?


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users