I can try it but first how to go back to boot from external?
Code
fw_setenv bootcmd 'run startfromext; run storeboot'Or use the toothpick method again. Both will end up with the same result. 
Posts by dtech
-
-
To my surprise this time it booted instantly from flash:)
But... there is always but when external hdd not connected - otherwise is a long boot.
Unfortunately, if a storage device is connected to an external USB (external HDD, flash drive, etc.), it would try to boot from there first.
If you need to ignore startfromext, you need to set this:
Codefw_setenv bootcmd run storebootAnd then reboot. If all goes well, it will no longer try to boot from an exernal device (not even an SD card).
-
please help libreelec for this m8s working box.
Next time please use a translator because the only accepted language on the forum is English.
Unfortunately, I don’t see exactly the type of wifi chip on your photo, but basically one of two images can be good:
- Universal n200: Ampak AP6330 or Realtek wifi,
- OTT M8S+ (n200C): multiple broadcom/ampak wifi.
Please try them out and report back in the linked topic.
-
I need some enterprising Minix X8 / X8-H / X8-H Plus testers in this topic:
-
You are right. How to check flash size then?
Well, the easiest way to really do this is to type the ID at the top of the chip into a search engine.
This really matters if you run from there. (E.g. if it is installed to the internal memory with installtointernal script.)
This is my M8S (n200C), LE runs from the internal NAND:
Code: df -hFilesystem Size Used Available Use% Mounted on devtmpfs 766.4M 4.0K 766.4M 0% /dev /dev/system 975.9M 124.1M 835.8M 13% /flash /dev/loop0 122.0M 122.0M 0 100% / /dev/data 5.3G 1.3G 3.9G 25% /storage tmpfs 768.4M 0 768.4M 0% /dev/shm tmpfs 768.4M 9.1M 759.2M 1% /run tmpfs 768.4M 0 768.4M 0% /sys/fs/cgroup tmpfs 768.4M 2.2M 766.2M 0% /var tmpfs 768.4M 0 768.4M 0% /tmp -
Code
/dev/mmcblk0p1 511.7M 134.2M 377.6M 26% /flash /dev/mmcblk0p2 13.9G 288.0M 13.6G 2% /storageThis is not your SD card?
-
Can't access this file (repository.libreelec.tv-9.2.1.zip) on your server.
Sorry, the link has been link fixed. There is no SSL certificate for this subdomain on my server, so the HTTPS is not valid in the URL.
But this stupid Crome found it funny to add that idiot s to http. No comment...
BTW That's my box mainboard in attachment - it shows tronsmart on sticker and 8gb but it is 16gb.
NCEFAT28-08G -> It is interesting because this is a 8GB eMMC on your PCB.
-
Okay, the manual workaround is here for the "repo bug after update":
(However, as a new installation, everything will work immediately, and there is no need for manual intervention.)
IMPORTANT!
If you installed it as an update and you have a problem installing addons, you will need to manually update the LE repository addon:
For v9.2.8.1 and earlier versions I also replaced the old repo, and the only package included is this:
After that you just need to update and point to the location of the new repo (S8X2):
-
I wouldn't bother with that bug too much(tbh i downloaded only one add-on from repo and it is a skin;) - just add in first post that "users have to do a fresh install every time new build is released" and wait for LE to fix it.
This is a "catch-22" situation: If LE fix this bug, how do you install it if you don't reach the repo itself?
I'm trying to find a bridging solution...
-
Install failure. It looks like LE can't see files from this repo as it is not showing size. I did update from old snapshot(the one from 10th). Will check with new installation as well.
Yes - it is upgrade related as fresh installation is working ok.Okay, I investigated and all new images in the S8X2 project are affected: M8S+, MXIII*, Uni-n200.
The cause of the error is probably not in my own build, but rather in Kodi or LE.
It is a fact: The repository link for the devices has changed.
Old: http://libreelec.dtech.hu/packages/9.2.0/M8S-Plus/arm
New: http://libreelec.dtech.hu/packages/9.2.0/S8X2/arm
But that's still not the real reason, because both paths work and point to the same target (symlink).
Code2021-09-14 06:37:34.376 T:3010805760 WARNING: Repository add-on repository.libreelec.tv uses plain HTTP for add-on downloads in path http://libreelec.dtech.hu/packages/9.2.0/S8X2/arm - this is insecure and will make your Kodi installation vulnerable to attacks if enabled! 2021-09-14 06:38:04.143 T:2901406592 WARNING: Previous line repeats 32 times. 2021-09-14 06:38:04.143 T:2901406592 ERROR: Requested path http://libreelec.dtech.hu/packages/9.2.0/M8S-Plus/arm/virtual.dvb-tools/virtual.dvb-tools-9.2.0.105.zip not found in known repository directoriesThe repository link is good, the download link is working, it's just from the old index file.
Somehow the index would have to be updated to point to the new location, but I have no idea where LE stores this.
Update #1:
It doesn't work either: https://wiki.libreelec.tv/how-to/force-add-on-update
It can be updated, but it will still use the old URL when downloading add-ons. What a stupid bug is this?
Update #2: The Kodi backup/restore solution does not work either.
-
Not working for me as well(just checked) - there is no size beside them - installation failed. Kodi add-on repository is working without any problems. But i don't care about add-ons anyway.
Okay, it is strange.
First question: The v9.2.8.2 was an update or a new installation?
Second question: It was a download failure or install failure?
I need a kodi log...
-
Latest update from Index of /3rdParty/S8X2/Universal-n200-S812_2G-AP6330/
Couldn't install anything from the LibreELEC repo
Please check your device connection. I tried it a few minutes ago from a new SD card and I have no problem with LE addon downloads from my repo.
-
MXIII-G 4K 2GB/16GB
LibreELEC-n200-AP6330_2G.arm-9.2.8.2 - some glitches at boot(when you see "linux things" - same with last snapshot but not important). Wifi no problem(connects with kodi repo straight away and is downloading skin without any issues), movie freeze gone. If there were no more changes from previous snapshot then i was testing it for hours and it is working flawless.
No volume/mute osd but i think it might be related to my avr/panasonic 4k tv but my older openelec build works without that glitch - will try to track it down with debug..
LibreELEC-MXIII-Plus.arm-9.2.8.2.img - no wifi for me so didn't test it more. Glitches at boot.
That glitch is normal, also present in M8S+, due to the framebuffer reset (by platform_init script).
However, this is necessary to correct the freezing error, but I think we can live with that.
Since you have a clone with the AP6330, the universal n200 image is basically the best (and perhaps the only working) choice.
I enabled the image as stable, thanks for your feedback.
-
My guess is that you have a clone device and it is a gxbb (s905) platform, that would explain the PLL error. I'll send you gxbb blobs, well worth a try…
I don’t want to have a say, but you could try it with the image I made in the same way. (Extract the content with the customization tool.)
I only dare to suggest this because the same model of device has already been revived with it.
-
LibreELEC v9.2.8.2 (2021-09-12) has been released for S8X2 devices only.
Changes since v9.2.8.1 (2021-08-14):- restore whitelist patch to fix cadence-correct playback problems (eg. 23.976 and 29.97 fps),
- disable all Realtek SDIO and USB wifi/bluetooth adapter drivers in kernel configuration,
- M8S-Plus: enable some external Realtek USB wifi adapter drivers.
- 3rdParty images: enable some updated external Realtek SDIO and USB wifi/bluetooth adapter drivers in options,
- 3rdParty images: merge MXIII-S8X2 devices to main S8X2 project,
- Minix-S8X2 images: sync boot scripts and kernel with datrh's repo (based on 9.0.2 with custom Kodi version),
- 3rdParty images: platform_init script replaced to prevent freeze problems after stop or seek.
- 3rdParty images: zram service is disabled on devices that have more than 1 GB of RAM.
Images can only be published after testing and positive confirmation!
So far, this has happened to these devices:
- OTT M8S+ (tested by me),
- Universal n200 devices (tested by loki7777 on an MXIII-G clone, gjstroom and Jerry on M8S clones).
Not-affected S8X2 devices: WeTek Core.
Affected but not yet confirmed
(waiting for feedback):- Minix X8/X8-H,
- Minix X8-H Plus,
- MXIII-1G,
- MXIII-G/-Plus.
If you would like to help with testing, please indicate what device you have and what you experienced during the test.Only these images can be used for testing:(snapshot directory link removed)After positive confirmation, the images will be transferred to their own download directory.I do not wait anymore... (2021-10-11)
IMPORTANT!If you installed it as an update and you have a problem installing addons, you will need to manually update the LE repository addon:
-
Bad news, I mainly use Nextpvr, pihole or adguard a bit of a shame it won't be supported, but it's good that at least you have refresh the old boxes
I would be happy to re-implement the support if someone submits it in PR.
Unfortunately, I don't have time to investigate lately. Since I don't use the docker, I couldn't even test it.
-
I only have a problem with the docker
"Cannot connect to the Docker daemon at unix: ///var/run/docker.sock. Is the docker daemon running?"
I have no idea what is missing.
From branch 9.2, along with the end of official amlogic support, aml-specific patches for docker support was also dropped.
The docker compatibility was not a priority in my builds, so I wasn’t really concerned with re-implementing background support.
-
The other thing is volume bar - it's missing with every skin - how to fix it?
I can't comment on that, I've never encountered such a bug so far.
