Posts by chewitt

  • Nexbox A95X (GXBB)

    I added the driver in the rtl8189fs branch of this repo: https://github.com/jwrdegoede/rtl8189ES_linux/branches

    The rtl8189es driver that was already in the image is from the master branch of the same repo (and searches for the 'fs' driver point to that repo). It's common for an RTL driver to support multiple differently-named chips (hence it claims to be RTL8188F in dmesg) .. all part of the garbage and support debt that comes with not-upstream old vendor drivers.

    These drivers are not (and will not be) submitted to the main LE repo. I'm going to leave them in my private image for a while; I don't make any guarantee they will remain in my image so at some future point you might need to discover self-building LE images. Historically the RTL vendor drivers break with every kernel major-version bump and we bump kernels frequently so playing "hunt the patch" gets tiresome.

  • Librelec Server

    In short, no. You can install another Kodi client configured with the same add-ons/sources of media on the other TV. You cannot stream from one LE instance to another Kodi client; Kodi is not a 'server' application that streams media.

  • Nexbox A95X (GXBB)

    Code
    cd /storage/.update
wget https://chewitt.libreelec.tv/t…ELEC-AMLGX.arm-11.0.2.tar
reboot

    Please update again. That's ^ all you need to do. I think it should probe the right driver now; if yes it will probably fail to load firmware but that will show an error and we can see what's missing.

  • Realtek RTL8188EUS Wifi Adapter on Rock64 not detected

    Quote from rdorsch

    Interesting, do I get that right that there are two drivers in staging for this USB adapter? A working one from Realtek and a non-working one from Jes Sorensen?

    Not correct. Debian is building with the older vendor driver, the staging driver is not enabled in their kernel. LE is building without the vendor driver, and with the staging driver enabled. However, staging = experimental drivers that are still in actively development and/or not feature complete enough to exit staging and be included in the main kernel tree. So the staging driver could be 95% complete or .. 55% with lots still to work on (and I have no idea which).

    I'd expect Debian to have a policy of only enabling finished drivers (makes sense for a large distro) and you wouldn't enable both as that will cause conflicts. LE is happy to enable the staging driver(s) as we aren't including the vendor ones (on principle; they break often) so there is no change of conflict .. and if it happens to work that's great.

  • NFS issue with share from Debian kernel 6.x

    I don't think the RHEL article is relevant because the 4.18 kernels are ancient (even though RH backports a ton to them). That also doesn't correlate with the OP who broke his setup by updating the kernel on his OMV install.

    You can also look at Kodi changes for NFS and filesystem caching. I have fuzzy recall that there are some between K19 and K20, but as I never use NFS myself (as SMB works fine) I never pay any attention to them. Some differences to an LE9 install would be expected since the entire codebase is different, but we aren't seeing general user whinging about NFS issues with LE11 and that usually means the reported issues are more localised to a specific other software (are you also using the same OMV version?) or something else niche/environmental.

  • LE 11.01 Suddenly started booting to safe mode

    Once you're in safe mode you will remain in safe mode unless you manually revert back to the previous Kodi setup. That can be done by stopping Kodi and renaming folders to restore the previous Kodi instance to the right location. That will also restore the crashing though, but in 99/100 cases the reason for repeated crashes is a bad add-on, so watching the logs and seeing which add-on causes the crash; means you can then delete the add-on folder from /storage/.kodi/addons (and the packages folder) to get things running again. The fix of the problem then depends on what the problem was, but some kind of add-on update (new version, etc.) is usually the way forwards.

  • Realtek RTL8188EUS Wifi Adapter on Rock64 not detected

    "lsusb" reports whatever is connected to the bus, it has zero meaning for the device being probed and working. The staging driver is enabled with `"CONFIG_R8188EU=m" in the RK3328 kernel config and it appears to result in the module loading (as you found) but then nothing. I would expect to see the firmware loading and such. Are Debian using the staging driver or the vendor driver? (the module might be the same name but could would be completely different). Are Debian using any patches?

  • Compilling for Amlogic S905 - Help for extra steps

    Item 1 "git grep estouchy" should help you find the places you need to edit to prevent it being bundled. Items 2/3/4 are addressed via advancedsettings.xml configuration (more git grep will help that). Item 5 you can add packages to the image if they are LE add-ons. If they are third party add-ons it can be done, but we intentionally avoid providing instructions as there are people out there keen to bundle pirate add-ons and repos and that shitware is bad for our name. Item 6 is solved by adding "UBOOT_SYSTEM=box" to the build command.