Entschuldigung, das ist nicht korrekt.
Wireguard ist seit Version 5.1 in Linux enthalten, ältere Versionen müssen es out-of-tree erstellen und benötigen kein CONFIG_WIREGUARD. Diese OE-A-Konfiguration ist also falsch.
Posted by neo on 17 May 2024 - 17:23
Entschuldigung, das ist nicht korrekt.
Wireguard ist seit Version 5.1 in Linux enthalten, ältere Versionen müssen es out-of-tree erstellen und benötigen kein CONFIG_WIREGUARD. Diese OE-A-Konfiguration ist also falsch.
Posted by neo on 13 June 2023 - 19:20
Looks like a buggy plugin, which doesn't define its callbacks properly.
Anything you installed recently?
Posted by neo on 11 June 2023 - 11:46
on the openpli 8.3 feed gives me the old version 11714, can you send me version 11719 compiled for openpli 8.3?
You were told to wait until the build update was finished, see https://openpli.org/, on the left.
If you want to hack your system manually that is not a problem, but at least study and get some linux experience before you do...
Posted by neo on 11 June 2023 - 10:39
We don't make software for dreamboxes, so you'll have to ask whomever created that fake OpenPLi image....
Posted by neo on 1 June 2023 - 10:48
So, the stripped down slot 0 is the only possible good idea... or new recovery menu that replace enigma on a stripped down image. I considered both options but i just decided to don't waste more time. Feel free to implement it.
Like Littlesat I also look at it from an end-user perspective, but I don't agree with him using slot 0 (or whatever) as a normal slot. Give a user a hammer, and they'll find something to hit...
Holiday's coming up, but I'm willing to look at the partitioning and the stripped down slot 0.
They only thing we're missing compared to the boxes that support this by default is the forced trigger (reset button, pressed-down power button, etc) to start the recovery image. That would require changes to the bootloader, which we can't make. So be it.
@dpeddi,
I think your work sofar is brillant, we should have had this years ago !
But I think you need to keep in mind the difference in perspective between image (makers). When OpenPLi talks about end-users, we talk about users just about able to use the remote. They can't play with files, they don't visit forums like this, etc. We would like solutions to be stable and workable for those users too... One could argue that those users shouldn't use multiboot, but as it is an available feature, you can't block them from doing so. So it better be fool-proof...
Posted by neo on 9 May 2023 - 23:25
Ok. Then I'm afaid in needs more work.
It's a shame all those patched versions are distributed as binary, instead of sharing the code for the patch, so we could see what the problem could be.
Posted by neo on 3 May 2023 - 19:45
https://docs.yoctopr...quirements.html doesn't mention it as well, but our buildservers have it installed:
$ apt list fakeroot Listing... Done fakeroot/jammy,now 1.28-1ubuntu1 amd64 [installed]
and my own server has it installed too
$ dnf list installed fakeroot Installed Packages fakeroot.x86_64 1.30.1-1.el8 @epel
Posted by neo on 2 May 2023 - 19:03
Fixed.
Switching to some other tarball is not done when the source repo is available.
Posted by neo on 1 May 2023 - 17:58
No timing has been set yet.
Posted by neo on 1 May 2023 - 16:04
No.
If you want Python 3 you need to switch to the Nightly Builds, or wait until the release of OpenPLi 9.0.
Posted by neo on 30 April 2023 - 16:34
Pretty obvious, I think?
fatal: unable to access 'https://repo.or.cz/oscam.git/': Failed to connect to repo.or.cz port 443: Connection timed out
get a coffee, try again. These things happen .
Posted by neo on 25 April 2023 - 16:01
My point is that that field has been repurposed, and I need to enter "all" to be able to flash other images. And that forces me to remove my own URL.
So I can have my home builds, or all other builds except my home build, but not both?
edit: and yes, my homebuild url is a full http URL to my local webserver.
Posted by neo on 23 April 2023 - 10:28
Done.
Posted by neo on 7 April 2023 - 23:20
We build on 8 cores with 16GB, and 20 cores with 32GB.
By default both BB_NUM_THREADS and PARALLEL_MAKE "-j" is set by bitbake to the number of cores, which is way to high, especially for machines with large numbers of cores (btw, what CPU is that?).
We have limited both to 12 on the Core i9 10900K, and that can already max out the 32GB if the parallel processing timing is unlucky (like when qtwebengine, kodi and a few other heavyweights compile at the same time).
Posted by neo on 4 April 2023 - 23:14
So now they're being forced to change their ways, even though it's not coming from VU+.
No, there are not. There is nothing multiboot in the standard image. You need to manually enable "multiboot mode" if you want to use it.