Posts by escalade

    RShT

    Probably not, as I don't have one myself and no knowledge of it's workings.

    Did you try the new RPi build, is it still panicking?

    Blackhazard

    Take a look at /storage/.config/emulationstation/es_systems.cfg to see what platforms are configured for Emulationstation. There are some missing systems, ScummVM, ResidualVM and Dosbox. This is due to the nature of these emulators as you can't simply point them to a ROM file. I've been meaning to add a menu that launches each of these, but haven't had the time to investigate user friendly ways of doing this yet.

    I didn't understand your transparency issue, perhaps you could be more detailed and/or provide a screenshot.

    You may update the RetroArch cores through the core downloader in the menu. Keep in mind that in doing so, the cores you download will override the ones I ship in the updated images. The buildbot cores from Lakka may have issues because of the different toolchain used as well. As for other systems, the only way to update them are through upgrading to a new image. This is the nature of LibreELEC as a read-only squashfs.

    The udev rule is simply to launch the udevil mount command when the disk is plugged. Then udevil tells the kernel to mount the drive. If it can't then it's a kernel issue, nothing to do with user space. Looks like the kernel version is different, 4.8.2 vs 4.8.6. As it's a milhouse build you should report it in his thread, he will know if there's been a change in kernel configuration or what not. I'd give the latest LE alpha a try as well, it has 4.9 kernel.

    20170102:

    Code
    - Rebased on latest LE8 master (most significant change is Kodi 17 RC2)
    - Compiled with -Os instead of -O2 (fixes the youtube issue)
    - Version bumps for the following packages: mesa, vulkan-loader, retroarch, mgba-libretro, fbalpha-libretro, residualvm, btrfs-progs
    - New driver RTL8723BS (common wireless/bluetooth combo in cherry trail devices)
    - Added patch for ACPI bug in some cherry trail devices causing wireless to not work unless LPSS is set to PCI in the bios

    Atom optimized build with drm-next currently building. I'll probably do an RPi build as well if someone wants to test.


    In my opinion: Rpi 2

    That's an odd comment considering even an overclocked RPi 3 is not powerful enough to render the GUI at normal speed, and the ethernet connection is 10/100. No browser addon either so no amazon prime (i think). It is definitely not the "best hardware for Kodi" and doesn't fulfill any of the criterias in the OP.

    As a cheaper alternative to the NUC, I can recommend the Tronsmart Ara X5 Plus. There are some minor issues with Cherry Trail, but at this point it's quite stable and works well.

    mklein49

    Yes, I've narrowed it down to the -O2 optimization that I use. New rebased builds with -Os are on the way that will fix the youtube issue.

    I'm not sure why this is suddenly an issue, as I've been using -O2 without issue from the very start of this build. The only package to ever have an issue with -O2 was Kodi itself which would segfault on ARM. I've tried using -Os only on libressl/kodi/python to narrow it down further but still same issue.

    dtw_2000

    There isn't a solution for that AFAIK. I don't know if it's a technical issue with the kernel driver, or if it's with the BlueZ bluetooth stack, but it's definitely not a LibreELEC specific issue. Same problem with the DS4 as well, quite annoying.

    mgkasper6

    I don't keep an archive, but I think someone mentioned an older build posted a few pages back so have a look. I guess a rebuild should be tried as well as there has been RPi firmware updates in master. My only build machine is my i3 laptop which is busy with the other builds atm so it'll have to wait.

    Blackhazard

    Probably not. Like I said, that would require a lot of work. All the packages would need additional addon install routines, source code would probably need to be modified to store addon data in the proper "Kodi way" under /storage/.kodi/userdata/addon_data (see here for a horrific example of that), scripts would have to be rewritten, etc. Then there's the practical bits around creating a repo to host them (as LE might not want to host some of these addons), build scripts to update the repo and so on. I'm not a big believer in the Kodi addon system as a package management tool, it's simply a lot of extra work for the packager and for little benefit.

    As it is now, most of the packages have been polished and tested, most of the work I do is simply bumping the version in package.mk and run make, then there's a fresh .tar to upload. Using standard install routines and putting everything into the image allows me to add new packages with little work. I do some mods to the LE core system as well, like building some libraries as shared libraries which allows me to run Google Chrome and Spotify. Consider that my motivation for this work is to extend LE for my own HTPC use, I'm simply sharing it as others might find it useful.

    If anyone would like to undertake the task to convert my packages to addons, feel free to do so :)

    pawnthep

    I could, but I'd rather not maintain out of tree patches for niche products that I don't even own. Why don't you create a PR for getting it into LE? Or try getting it in the upstream Linux kernel? Then it would trickle down to my build eventually.