Changing the folder/filenames to match the upstream data in thetvdb often resolves issues. So I would use this:
Midsummer Murders/Season 1/Midsummer Murders s01e01.mkv
Posts by chewitt
-
-
i do same proccess with librelec 9 with other sd card and its booting ok.
The LE11 release announcement clearly states the boot process is different and provides a helpful link to the Amlogic wiki article where the instructions have been documented. I've also told you multiple times to read the same article. Why? .. because the process is different.
PEBKAC
-
Before I post a bug report on GitHub, can you tell me what kernel LE11 uses and is it 32 or 64-bit?
Linux 6.1.y built from the upstream Raspbeery Pi Foundation sources (that we contribute to). The kernel is 64-bit, but userspace is 32-bit.
-
but everytime i boot from weos..whats i m doing wrong?
I'd guess that you haven't set the DTB name in uEnv.ini .. but since you provide zero technical evidence or detail of what you did to create the SD card (and from what image) I can only guess blindly at the issue. Stats show a steadily increasing number of active installs so other users are able to follow the instructions and install, so the image(s) are good.
-
The wiki article explains what a box image is. I suggest you make a little effort and read it.
-
Display More
this wiki show how to use le in internel storage.
mean we will loose android side..am i right/?
i only want to use this build with sdcard.
i should do
1=download iamge for wp2 from https://chewitt.libreelec.tv/testing/
2= burn it on sdcard
3= insert card in box and restart
thats all or i have to change dtb.img file name process?
plz clear my doubts
No. Use the "box" image. Read: https://wiki.libreelec.tv/hardware/amlogic
-
Google says Tox1 is an S905X3 device. You should read the Amlogic section here https://libreelec.tv/2023/03/06/libreelec-nexus-11-0-0/ before running current AMLGX releases. The Vorke box is S912 and there is no specific device-tree, but the Q200 or Q201 device-trees will probably work fine (depending on whether 10/100 or 1Gbit Ethernet and which WiFi/BT chip).
NB: In LE terminology the "Generic" image is for x86_64 devices not arm boards. Amlogic devices use AMLGX.
-
-
However, if I remove 720x576p 50Hz from the whitelisting then the 4:3 videos display as expected.
Is this a bug or a setting I am not seeing?
It's probably a bug in the Intel GPU driver (as whitelisting removes Kodi scaling from the equation). You already found the workaround.
-
PLEASE HELP ME
Read the previous posts and follow the requests/advice then. NB: Your caps lock key appears to have gotten stuck.
-
Movies split into two halves and unordered lists smells like pirate IPTV services. You'll need to share "pastekodi" logs to continue.
-
FUSE existed in previous versions due to the dependency on NTFS-3G/FUSE for mounting NTFS drives. FUSE has been dropped from the core image in LE11 as the kernel now has native NTFS support so embedded NTFS-3G (and FUSE) are no longer required.
However it also exists in the network-tools add-on; it's a build/runtime dependency for things like sshfs. Once you've installed that you will need to reboot before the environment can find it in the add-on bin folders. Or you may need to adjust paths in your scripts to align with the new binary location.
-
You also said (and I quote) "I'm able to boot the libreelec USB live without issues." hence the instruction (quoting myself) "Please share the "pastekodi" URL from the working USB install."
If that's too complicated ..
-
It's a script that ships with MySQL so it exists (and you run it) on the external MySQL host not the LE client device.
-
I’m wondering if there’s a problem with Nexus 11 on the RK3399 chip.
Kodi has no issue on RK3399. The kernel that runs (which is nothing to do with Kodi) .. probably has an issue.
-
Wake from suspend works as you've already gone past the initial cold boot stage where the problem occurs. To be honest I have no idea how to solve this. On my own Hub box boot fails reliably with UART connected and works once I disconnect it. I've believed this to be a self-created problem, because I had to resolder the UART pins to get it working due to joints on the PCB going dry and breaking connections, and my poor quality soldering job (at the time done with a prehistoric plumbing soldering iron) was the cause of the problem.
I'll have to speak to kernel maintainers for ideas.
-
-
BCM4330B1.hcd is the BT firmware file and assuming x86_64 driver code works the same as ARM boards this shoud have no impact on WiFi. If you rename the bin/txt files to follow "brcm/http://brcmfmac4330-sdio.V5-V5.bin/txt" there will be fewer error messages in the log.
I think the original install was working fine once the bin/txt files were added but the card cannot host a tethered AP and join a WiFi network at the same time; they are mutually exclusive functions.
