Currently there is no addons built for nightly images. Use LE10 stable image instead. There is no functional difference.
Posts by jernej
-
-
Ah, you can play a bit with patch itself, or checkout 5.10.61 kernel, make same edits and create patch.
-
Of course it's not certain yet (freezing is accidental), but it looks good!
Unfortunately, next day it didn't work anymore for me, even with CPU devfreq totaly thrown out. I'll borrow another OPi3 to check again. I have a feeling that this is not so common issue, otherwise there would be more complaints, either here or IRC #linux-sunxi.
How can I compile LE10 with the necessary changes?
just make patch file from link I posted above and put it in projects/Allwinner/devices/H6/patches/linux/ It should just work...
-
Output is actually RGB. YUV output is not yet supported by the display driver. HDMI driver automatically converts image to limited RGB, if needed by standard (99% of the time) and that's not possible to override.
I suggest you test this video: http://jernej.libreelec.tv/videos/h264/2-APL%20Clipping.mp4 If you see range about 16 - 235, then limited range works fine.
-
LuRu I think I found important difference. While it's true that wireless power supply is a mess, really important bit is CPU voltage range. I copied over One Plus values and my OPi3 seems to be much more stable. Please test this update:
Index of /test/opi3-stability/
Apply it to ordinary OrangePi 3 image.
DT changes: http://ix.io/3yMQ
If that doesn't work for you, I have one additional DT change to test. But I would really hope it's not the culprit.
-
Interesting analysis, thanks!
I compared OrangePi One Plus and OrangePi 3 DTs and one detail caught my attention immediately. BLDO3 power supply is marked as unused and not connected anywhere in OrangePi 3 DT . However, schematic shows it should be used for VCC-PG, VCC-PM and VCC-WIFI-IO. I'm not sure if this is the culprit of instability but certainly something to look into.
Unfortunately I'm busy with some other, more pressing issues. Would you please look into this matter a bit further and try to pinpoint exact issue? As you already noticed, OrangePi 3 and OrangePi One Plus DTs are pretty similar, so there is not much things to change and test. All you need to do is to make some changes in OrangePi 3 DT, create a patch, build your own image with that patch, update your system and test. Rinse and repeat until your board becomes stable. If you need help with that, just ask.
-
Composite TV out literally supports only PAL and NTSC modes (720x576i and 720x480i, respectively). No amount of tricks on your part will change that, sorry.
I find it surprising that your TV wouldn't support at least of one of those modes. They are few decades old standards. I tested this on some camera display from ebay and it worked fine, but it has normal RCA connector, without any resistors in between. I can probably get RCA to SCART adapter, but no promises when.
-
-
Since everything is done in spare time, it could be 1 month or 1 year or more. Most things work more or less, only DRM driver needs to be finished up and at least one audio output needs to be added. Currently it seems analog will be easier to support, since driver already exists for similar variant.
-
Summer is time for vacations and travels, so no.
-
Last attempt at making A10 work was done here: GitHub - jernejsk/LibreELEC.tv at mele
There are no images made from these sources anymore. I don't recall what was wrong, but it wasn't much useful afaik.
First thing is to build image, assess what works and what not and start fixing things. If you're not familiar with Linux and U-Boot (if boot doesn't work), you have a long road ahead.
-
everything working except that pvr.iptvsimple CANNOT be installed
Currently nightly image has no real benefit over stable, so if you need addons, I highly suggest stable image from LE download page.
It is written that 9.97.1 should be able to upgrade automatically, but that didn't work for me, so I have flashed again with final 10.0 LE. But I wonder if it really has to be able to update on our boards, or only manual is our way?
Automatic updates are turned on with a slight delay (few days). Allwinner platform is not treated any differently with automatic updates.
-
Images are linked on download page: Allwinner – LibreELEC
-
levitsky86 I would not use 11 nightly images just yet. A lot of updates went in and yes, addons need to be rebuild. I strongly suggest you use latest LE10 RC image.
-
Default governor is schedutil - this should good enough for most needs. Consider also that you're comparing two completely different ecosystems. If you would check Android serial console, you'll notice that kernel often disables cores due to too high temperature. It's complete chaos there regarding temperature control. It's also possible that temperature sensor is not completely correctly calibrated on LE. You can check that with thermo gun, if you have one.
-
unmesh Thanks, so now I know owners of all 3 wifi variants. After LE10 is released, I'll start preparing wifi support (with mainline drivers).
chalesy Your board could be supported, but first somebody (most likely you since others probably don't have interest in your box) have to submit board support patches to U-Boot and Linux. As soon as there is general consensus that they're ok (that can be before they're actually merged), I can add support for it here. If you want help with this, I can coach you, since I'm reviewer for Allwinner Linux patches and U-Boot contributor.
Please understand that we have this procedure in place in order to be able to drop patches in not so far future. Nobody likes to maintain patches forever.
-
There is, but you would have to power up wifi first via DT (overlay or editing). It's easier to crack it open. However, if you don't feel like doing it, that's ok.
-
In my case, the problem may not be related to ffmpeg. I just restarted the system and then I didn't do anything.
This is probably something else, then.
I was surprised that the serial console log contains only the system boot and then nothing.
Printing on serial in theory slows down boot, if only for a second or less.
Would it be possible to make some debug image that would write in detail to the serial console?
no need, just remove quiet from extlinux.conf. If you want terminal on serial, also add systemd.debug-shell=ttyS0