118 replies to this topic

[Dimitrij]

linux-firmware-dvb-fe-avl62x1_1.8.27679

Edited by Dimitrij, 30 January 2024 - 18:31.

[WanWizard]

Grmpff...

 

That should have never happened. Reverted.

[rantanplan]

?
That's exactly how it was communicated!
Where is the error now?

The feedback here in the forum was good and the missing satellites that were not recognized before were recognized.
Why is this being put back so hastily now?

[WanWizard]

Sorry, I was under they impression Dimitrij requested that because of issues reported?

 

It is difficult to interpret what simply a posted link means...

[rantanplan]

I don't really care, but the feedback shown here and in the ATV Forum has been positive.
With the update, frequencies are displayed that were not previously displayed.
snr also worked.

But maybe
@athoik will say something about it, he seems to be active again.

https://github.com/a...ailink/issues/3

That's why it was updated

[EnoSat]

The firmware update basically just enabled ShortFrameRate support. GSE supported only 6261A.

[rantanplan]

The question is rather why it was put back again.
Where is the error message for the current firmware?

[athoik]

Firmware was fixing an issue with S2X.

In the process if it's causing an issue on normal S2, that's undesired.

So what's the current state?
We want to enable it on PLI meta, without bbappend?

[Dimitrij]

Sorry, I was under they impression Dimitrij requested that because of issues reported?

 

It is difficult to interpret what simply a posted link means...

 

I didn't ask revert, it was just information .

 

 

 

[WanWizard]

I didn't ask revert, it was just information .

 

I find it sometimes difficult to understand your intentions, if it isn't clear, my autistic mind starts filling in the blanks, often not a good thing

 

So what's the current state?
We want to enable it on PLI meta, without bbappend?

 

If the update is the correct one, then yes, it belongs in the BSP.

[rantanplan]

Firmware was fixing an issue with S2X.

In the process if it's causing an issue on normal S2, that's undesired.

So what's the current state?
We want to enable it on PLI meta, without bbappend?

Thanks for the feedback.
Yes, an update in the BSP is of course desirable.
The bbappend was actually only created because it was easy to transfer to versions 8.3 and 9.0.
Unfortunately, this takeover did not take place.
Now it's reset anyway.
 

[WanWizard]

So what is the current status now, as I am completely lost?

 

As I read it now: the update fixed an S2X issue, but introduced an S2 issue? So eitherway we have a problem for some of the users?

[rantanplan]

I do not know it either.

I saw the S2x error as a log and it was fixed.
I can't understand what's wrong with the S2 error.
There is no log.
There are no user error messages here either, but that doesn't mean anything because only a few will have tested the current firmware.

Whether a dev can test it with such a box in the background?

It looks like the driver would have to be adjusted after the firmware update.
But I can't say that exactly either.

Maybe there will also be an update from Avalink?
You would just have to provide the error there with a proper log.

[WanWizard]

We'll need someone with such a box, and both S2 and S2X reception (which rules me out). And with the knowledge what to test and how to report.

 

The OE-A commit isn't clear at all as to what the error reported was.

[EnoSat]

Where is the S2 bug with 1.8.27679 described or reported?

[rantanplan]

I've tried to question it, but so far without any qualified information.

There are 2(3) topics about this in the ATV forum.
So once, as described in git by athoik, the error is fixed.

Another topic refers to a problem that has nothing to do with the firmware itself.
The third topic refers to problems with SD channels after a firmware update within the existing channel list.

Unfortunately there is no log for this.
I would really be interested in a log and feedback.
Feedback from people who previously had problems was rather the opposite and showed no problems with SD channels.

Like I said, I don't know.
I don't have the box either and can't check it myself.
But I created the update after logging and successful logging and feedback.
So I'm surprised that it is now being reset without any problem and without an error message including a log.

As I said...
I'm looking forward to hearing from athoik again and he certainly knows more and can certainly solve the problem.

[EnoSat]

thanks,

so, according to olwaldi, the new FW of the tuner is responsible for the problems with the gstreamer transition from 1.22.7 to 1.22.8 and EMC

https://www.opena.tv...html#post554357

it's a pity that he didn't return the old FW and didn't try to see if the error of the new gstreamer also manifests itself with the old FW

[rantanplan]

thanks,

so, according to olwaldi, the new FW of the tuner is responsible for the problems with the gstreamer transition from 1.22.7 to 1.22.8 and EMC

https://www.opena.tv...html#post554357

it's a pity that he didn't return the old FW and didn't try to see if the error of the new gstreamer also manifests itself with the old FW

No...
There are some things that don't fit with the topic.
He had hardware problems before.
I first brought it to his attention to test the new firmware.
After that nothing happened for a long time, only then did he try the other way around.

His problem has other causes and unfortunately these are not understandable.
No log

https://www.opena.tv...ach-update.html

An sd problem is presented here, unfortunately without more detailed information and also without a log.
However, replacing the firmware was successful in resolving the error.

This is all entirely possible, but I really wonder why people would just reset something like this without verification.
Just for your information, the users who have just verified and shown the error with log like athoik in git will be in touch again in a few days.
This was fixed with the firmware update.
I really would have liked a little more substantive data here before a change/revert.

Now it is in such a way as it is and I think athoik looks after it.
He can log and in possession mio4k.
Besides, he already had contact with the manufacturer of the proficient product and the manufacturer of the tuners

Edited by rantanplan, 31 January 2024 - 23:52.

[radionov]

We'll need someone with such a box, and both S2 and S2X reception (which rules me out). And with the knowledge what to test and how to report.

The OE-A commit isn't clear at all as to what the error reported was.

I have an edition os mio 4k+, I can test but tell me exactly how to log the error. Only with open pli 8.0 everything works without problem. I have tested many images.

Изпратено от моят moto x4 с помощта на Tapatalk

[radionov]

With OpenPLi 9.0 everything works normally. I've been testing it for a few days.

Изпратено от моят moto x4 с помощта на Tapatalk