There is different approach to fix v3. I'll try it and let you know.
Update: in my next build I will use drivers from CrazyCat: GitHub - crazycat69/linux_media: TBS linux open source drivers
There is different approach to fix v3. I'll try it and let you know.
Update: in my next build I will use drivers from CrazyCat: GitHub - crazycat69/linux_media: TBS linux open source drivers
Interestingly (at least for those that boot from USB), I observe that if a bootable USB is inserted AS WELL as a bootable SD, the device boots from USB without the normal long pause (almost instantly).EDIT:
All you need on the SD card are kernel.img and dtb.img and the box boots 12+ seconds faster
It's not a bug, it's a feature. The reason you are seeing long boot times is that it takes a few seconds for u-boot to initialize USB. The speedup you are suggesting will work properly when you have an SD card without LE and kernel.img + dtb.img in root folder. This is because on init the system looks for "BOOT/LIBREELEC" and "DISK" partitions and that's where it loads system and user data from. So if you put a non-LE SD card (simply put: format it clean in Rufus first) with image files and you have LE USB at the same time, the system will boot faster. But you have to remember to update kernel image and device tree on that SD card manually every time.
Because of this please keep this trick for yourself and don't advertise it.
@all Thank you for testing the first image. OP updated with a second build to test.
kakoskm I disabled it in kernel config because it is not implemented but it turned out that disabling it creates one additional issue. It will be back in the next build.
Hi Kszaq,
I read in forum that u have released retroarch addon for s805/s905 ,cant find the addon link,can u provide me the addon file to install .
Thanks
Sent from my iPhone using Tapatalk
Long time ago I compiled an addon for S805, it is no longer updated. You should look for it over at FreakTab, there's a topic for running Retroarch on S805 and S905...
karolgarlicki I use the same kernel version and config in my Krypton builds but I'm posting Jarvis builds as more people are using them. As soon as we discover a fix here, I'll update Krypton build with a patch.
New images for testing boot issue will be posted in a separate thread:
LibreELEC
In this topic I will post test images to test booting issue that some of you experience on S905 boxes with my 7.0.3.010 and 7.0.3.011 builds.
The images posted here will be based on my libreelec-7.0 branch and additionally I will be reverting some kernel patches for testing purposes. The builds will be 32-bit userspace only.
How to use:
Workaround for the issue offered in 7.0.3.012.
2017-01-04
Please indicate build githash gcb8de5f when posting your results!
Download LE image from: LibreELEC-S905.arm-7.0-devel-20170104082155-r23608-gcb8de5f.img.gz
2017-01-03
Please indicate build githash g3b038ea when posting your results!
Download LE image from: LibreELEC-S905.arm-7.0-devel-20170103162229-r23610-g3b038ea.img.gz
2017-01-02 (2nd build)
Please indicate build githash g5207357 when posting your results!
Download LE image from: LibreELEC-S905.arm-7.0-devel-20170102194735-r23609-g5207357.img.gz
2017-01-02: gc3e054b
Download LE image from:
LibreELEC-S905.arm-7.0-devel-20170102102948-r23607-gc3e054b.img.gz
2017-01-01:
Download LE image from: LibreELEC-S905.arm-7.0-devel-20170101225013-r23606-gc9b399e.img.gz
GeToChKn art.sormy I have already figured that boot logs won't help as there is no error indication. I know that from users' logs from my Jarvis build which has the same boot issues. I will start posting test images today reverting kernel commits one by one and maybe we will be able to track the bug that way. Meanwhile I still hope Minix will share their patch for Minix U1 that addressed this issue.
CGarces Adding /opt and using entware is easier than compiling what I need from the scratch with all dependencies.
This is rather a general LE request and not build-specific. I would rather not change how a general idea of LE file system works due to dragons.
Does anybody know how to show dmesg during boot on LibreELEC installed on Android box? I would like to debug issues with random hang on boot, at least would like to see whats happen on console during boot freeze.
Serial console is your friend. You need to disassemble the box.
afl1 It happens with 23.976fps VC-1.
There is different approach to fix v3. I'll try it and let you know.
Just to let you know: the latest media_build needs some more kernel patches and build tree patch to work fully. I will upload them in a few days.
dazed I follow LE repo with updates. I suppose it will be updated for the next release with Kodi 17.0rc2.
I will use updated media_build drivers in my next build from this PR: use media_build for dvb drivers by CvH · Pull Request #1073 · LibreELEC/LibreELEC.tv · GitHub
Would that be enough? I'm asking as I don't use DVB tuners at all.
I have found a reason and a fix. It will be included in my next build.
Hi all,
I'm having the problem that in Kodi the video resolution is fixed to 720p and in the settings it's greyed out (I can't change the resolution to anything else). Between my box and the AVR is a HDMI splitter, so I'm thinking that maybe Kodi is unable to get EDID information or something. I want to force the output to 1080p. I tried following methods and all failed. Any tips to send me in the right direction?
kszaq it is possible to fix BD3D in libreelec 7.90 ???
In jarvis was no problem with 3d.
At this point I have no plans to work on 3D support for several reasons: there are more important issues to solve, it needs to be implemented in Kodi - no 3D support for Amlogic, in Jarvis I used some patches from SPMC that would need to be ported - and I don't have 3D material nor 3D TV. Maybe at some point in the future.
I have a monitor with 1680x1050 resolution. You can only select 720p and 1080pHow can I fix it?
You need to implement 1680x0150 resolution support in kernel.
I try to go recovery with nand installed le 7.0.3.11 32bit.
I tried with twrp recovery.img, and original recovery.img from firmware 107, but not enter to recovery, just blank screen.
Maybe i make something wrong?
You need to have device tree from Android firmware on your SD card as dtb.img and recovery as recovery.img. This is already told in OP.
Already try, box have 1gb without device tree..
This means that the bootloader chooses 1GB because: