Known and will be resolved in LE11 beta 2
Posts by chewitt
-
-
If the system was installed/working and then stopped; the most likely cause is the USB stick (or whatever device you boot from) has failed. LE is packaged with the entire OS contained in two compressed files (KERNEL and SYSTEM). In a conventional distro, if you have bad sectors on disk it will impact only the couple of files that are written to those sectors, and often the impacted files are not critical files so everything will appear to work until the whole disk gives up. Due to the way LE is packaged, if media corruption impacts any sector involved in storing either of KERNEL/SYSTEM the OS cannot boot at all.
If corruption was due to something like unexpected file loss you might be able to boot Ubuntu and scan/fix the filesystem. If it was due to bad media (underlying pyhsical disk or flash memory issues) then you bin everything and start over with a new USB etc. - You might be able to get the contents or important things from /storage as that's a separate partition on the disk.
-
IMHO there will only be one RPi killer, and that's another RPi
RPi4 is not the best spec thing in the market, but only comparing hardware specs misses the point about RPi boards. They have massively better long-term software support, so they are reliable and continue to improve with age.
Although bitrate is probably involved somewhere in the overall scheme of things, I'd guess internal bandwidth between IP blocks is where things are on/approaching the limit, so (repeating myself) some overclock might be helpful.
-
Do you have any other devices to attach to the same HDMI port? .. perhaps an older RPi board, laptop, etc. and does the TV exhibit similar behaviour when display resolutions are changed?
-
Check how much disk space you have on the SD card (or USB, etc.). If there's not enough space the download might be truncating causing the mismatch in expected filesize vs. filesize on disk. The ChromeOS image is 1-1.2GB in size IRRC (and then you need additional space to unpack it and get the widevine lib inside).
-
2 mins boot time sounds terribly slow (should be more like 20 secs). Please share the URL from "pastekodi" over SSH so I can boot logs.
Kodi Settings > Interface > Regional .. all the format/timezone things are there.
-
If the RPi4 is "almost" able to keep up, and as long as you have a decent case (for thermals) perhaps some mild overclock will help?
-
1. Yes
2. No need to rename, edit uEnv.ini to use the right file. See: https://wiki.libreelec.tv/hardware/amlogic
3. Right process, but will fail due to #2 being wrong
4. Once booted from AMLGX the u-boot environment is modifed to find AMLGX boot files, meaning it will no longer find legacy image boot files. However if you remove the USB and repeat the 'toothpick' forced-recovery boot it should then search for and find the legacy image boot scripts and work with content on eMMC again.
I don't have a U9-H so USB boot isn't tested, but it should be the same as an SD card. If it doesn't work, try different ports, or an SD card.
-
It's impossible to comment upon or investigate mirror/download issues without knowing which mirror is being used. This should be visible in kodi.log if you look. Otherwise there are 20+ mirrors and
-
Shall I try LE10?
Whatever works for you, works for us.
-
Make backup before update to 10.95.0!
I tried (RPi3B+) and after a day changed back to LE11-nightly, far better.
Right now the difference between 10.95.0 and nightlies is basically zero, so that's a placebo update.
-
For the sake of speaking heresy and pointing out the obvious: If you're otherwise happy with the RPi4, run an Ethernet cable. You might not like cables but it's often the cheapest and better option.
-
Do I need to rename dtb file into dtb.img
No. Please read the wiki article I linked.
-
I would like to be able to put the operating system inside on the internal. I have a beelink gt 1 ultimate. Is there any option???? thanks for letting us keep using nexus. It would be great to be able to put it in the internal memory.
Not supported and no plan to support: https://wiki.libreelec.tv/hardware/amlog…s-android-boxes
-
Also note that there is no support for the internal DVB tuners (and that's unlikely to change)
-
Please help me to use LibreELEC on my almogic s912 box (MAGICSEE400 PLUS)
Which version should be used?
How can I install on my flash memory?
Thanks in advance.
You should be able to install the AMLGX "box" image, read https://wiki.libreelec.tv/hardware/amlogic
You will need to experiment with meson-gxm-* device-tree names in uEnv.ini as there is nothing specific for Magicsee 400+ right now. Most boxes are quite similar though, so it's easy to find something.
NB: We do not support internal installations on Android boxes and older scripts will (100% guaranteed) brick things if used.
-
If there was write protection on eMMC all writes would fail, so partial write (7%) means there is probably an issue with the eMMC chips, or the power supply which causes instability during writes. It's a common issue with older and cheaper Android boxes due to age/wear on eMMC chips and the low-bin/low-quality components used.
7% restored means that some boot code (u-boot) exists on the box now and this should be enough to boot LE from SD card. We don't support installs to internal storage on random Android boxes so you will need to run LE from an SD anyway. Use the AMLGX Android "box" image with the toothpick method to hook into u-boot. You will need to experiment with different device-tree filenames in uEnv.ini to find something that works with your box. If the box has Gigabit Ethernet the S905D vero4k-plus dtb will probably work. If the box has 10/100 Ethernet the p212 dtb should work.
-
Did you migrate the HDD from an older device to the newer one?
If yes, do "systemctl stop kodi && mv /storage/.kodi /storage/.kodi-old && systemctl start kodi" as an experiment to see if moving all the old config out of the way resolves something.
2023-01-30 20:58:25.001 T:770 debug <general>: CDRMUtils::SetMode - found crtc mode: 3840x2160 @ 60 Hz
2023-01-30 20:58:25.001 T:770 debug <general>: CGBMUtils::CreateSurface - created surface with size 1920x1080^ that looks wrong to me
It's odd that it claims to have no ELD data, but then finds all the resolutions and there is HDMI audio showing. It might be a case where the upstream drivers are still work in progress.
