Posts by chewitt

  • Loosing WIFI configuration

    The mostly likely cause (and unfortunately the hardest to debug) will be "some radio issue in your environment" .. it could be interference or loading on the AP or proximity to other devices or too-strong a signal or .. /shrug

    To investigate you'd likely need to run iwd in debug mode, which will generate mountains of debug log output, which probably nobody on staff will really understand (as none of us are wireless engineers).

    Pi is close-enough to run a short cable? Ethernet really is the best solution to WiFi problems (though never the answer people want).

  • Configure default network route

    There is no "make default" command or "set as default" that you can put into ConnMan service files. You can however use connmanctl to change the service order, moving a service up or down the order. I'm not sure if the first configured gets the route or there's other black-box magic involved. You might want to email the ConnMan mailing list to get answers on that kind of question.

  • Video Orientation

    I have a hunch it's this https://github.com/xbmc/xbmc/issues/23622 albeit with a slightly different use-case/presentation. If I'm right, it's not technically a bug since current Kodi GBM code is working correctly. The issue is that current Kodi GBM code doesn't handle enough rotation scenarios. The reason it stopped working is due to RPi images swithing to the GBM display pipeline (moving away from proprietary code to standards in the now-upstream kernel).

  • No audio on a mini PC

    In earlier Googling I found the following reports:

    [0] https://github.com/clearlinux/distribution/issues/2396

    [1] https://mailman.alsa-project.org/pipermail/alsa…uly/187558.html

    If my hunch is correct, the following should invoke the quirk against the correct PCI IDs (which we now have, thanks). The link Da Flex posted also mentions adding a quirk to solve the issue, and I suspect is the same issue.

    ALSA: hda/hdmi: Add quirk to force pin connectivity on HP Prodesk 400 G4 · chewitt/linux@c63b9d1
    On this variant alsa fails to offer HDMI audio output options. Add a quirk to force connectivity. Signed-off-by: Christian Hewitt <[email protected]>
    github.com

    I'm building a tweaked LE12 image with that patch added so you can test. If it works, I'll send it upstream to the kernel. If it doesn't work there's another variant (based on the thread that Da Flex found) that we'll check.

  • Mac OSX?

    Code
    gunzip -c LibreELEC-RPi4.arm-11.0.3.img.gz | sudo dd of=/dev/disk2 bs=1m

    You can use "dd" from Terminal.app to create the SD card. Something like that ^ should work. Use "diskutil list" to find the correct /dev/device for the SD card.

  • Getting around the partition limitation

    LE is packaged so the entire OS resides in two files; the KERNEL and SYSTEM files in the first partition of whatever device you boot from. The storage (second) partition is only used for persistent data, and Kodi DB files and add-ons are the only content that might be touched during upgrades, so long-term placement of media elsewhere on /storage has no impact from upgrades. There is no need to delete media to make an update unless perhaps you reached 99%+ full on the disk (some space is required for update file unpacking).

    Update from LE12 nightlies to LE12 future releases (nightly or otherwise) is simple and supported, and currently nightlies are quite stable; at least on the RPi hardware that I use.

  • SBC for a 3D MVC platform

    RPi3B+ using LE 9.2.8 will be the "best and final" recommendation. LE 10.x and newer switch to an all-new GBM/V4L2 video pipeline where 3D support simply hasn't ever quite made the priority list for development, and while the initial RPi4 hardware is supported by the initial LE 9.2.8 release, newer iterations of RPi4 hardware need firmware that only exists in newer/current LE releases. It's possible to self-build a doctored 9.2.8 image with newer firmware etc. there's no HOWTO guide for that (although not too hard if you have a tinkering mindset). Considering the limited amount of new 3D content these days and depending on what other media you need to handle; i'd keep a spare 3B+ lying around for 3D duties when you need to play something, while using an RPi4 (or something else that meets needs) as the main player board.

  • Meson 8* Lives!

    Quote from stevie101

    I have tried your image (LibreELEC-AMLMX.arm-10.88.0-box.img)

    You've done more than me then 8o

    Martin seems to be MIA at the moment so the best I can suggest is self-building using my AMLMX branch but with the Linux package update to use his latest kernel source (Linux 6.3 IIRC) to see if anything changed.

  • [Orange Pi 3 LTS] Freezes

    If you navigate to the build folder and do "make menuconfig" it should detect the local .config file which you can then diff/copy to update the one in the project/device linux folder. I normally just mod the defconfig directly and respin the image. Once in a while settings don't stick and I need to do a little digging in kernel Kconfig to understand dependencies, but over time (with gained experience) that occurs less :)

  • Display 4.3 stretched no black bars other resolutions have black bars on top and bottom squashed.

    Stats show roughly 250 "OrangePi PC" users (including + and 2+ variants) so the gene pool for problems isn't large and I'd wager the majority of users will be running their mediacentre at HD (720p/1080p) not VGA resolutions; and things where display is out of whack often depend upon a specific monitor/TV and (often) its bad/broken EDID data; which is something to check. Also check cables and if possible ports on the TV. Also share Kodi debug and dmesg logs so we can look for errors. Also ignore "missing settings" because that's a quirk of running Kodi GBM and is not the cause of the problem (I'm pretty confident on that). I'll say again that the issue is likely nothing to do with Kodi and more likely to be something in the kernel DRM layer .. and I note that Batocera's lead maintainer is also one of the maintainers for Lakka which (being a fork of our codebase) inherits kernel sources and patches from LE, with (an educated guess) that the same content gets used with Batocera and the same kernel/patches result in the same kernel/DRM problems.