How is the RPi being powered? .. weak PSU's cause problems
Posts by chewitt
-
-
We don't store archived versions of the app (and anything before 1.4 is buggy) so that's not possible. You can use other apps like Win32DiskImager or Rufus or Etcher to create install media.
-
Hardware deinterlacing doesn't work even in newer SOCs?
The deinterlace IP block has never been implemented in the upstream kernel for any Amlogic hardware (older or newer). The main difference is that newer SoCs generally have more CPU grunt than the older ones and can cope with software deinterlace on 1080p media. Improvements made in the last year for better software deinterlace mean it's actually quite good.
But what changes were made in LE 9.x, that even software deinterlace got worse?
No idea, it's before my time and the vendor codebase is a crapfest so I have no interest in investigating. Feel free to look in the commit history here to guess the breaking change: https://github.com/LibreELEC/linu…amlogic-3.14.y/
-
To preserve posts/thread integrity we will rename/anonymise the account and remove all identifiable data from the DB.
-
So, may I know why the Official LE does not use a vendor rock chip bootloader?
LE packaging assumes we are the sole OS being installed on a device (so we don't need to consider other OS bootloaders) and we choose to use and champion upstream open-source codebases whenever possible. RK3399 is well supported by current u-boot so there is no need for our releases to use vendor sources.
-
The codebase for those images is long-dead. The developers who might have half a clue about the issue are long-gone. The newer (upstream) codebase used in AMLGX doesn't support hardware deinterlacing.
-
YouTube is something that periodically breaks due to upstream Google API changes, so you'll see periods where the developer(s) push updates and make releases via the upstream GitHub (code) repo, but the Kodi (add-on) repo remains outdated for a while until the changes are fully addressed. If the author pushes updates to the Kodi repo users expect the add-on to work, so it's often better for the authors to leave something broken until fixed than deliver partial fixes that attract more support noise.
-
Yoyoda see if https://chewitt.libreelec.tv/testing/LibreE…_64-12.80.0.tar works? - this based on LE13 nightlies (ignore the odd version number). There's an .img.gz in the same folder if preferred. This has some more kernel options set. Please share a "pastekodi" URL after updating.
-
ok i somehow missed that kodi has libretro integrated for a while
Since about 2016 .. it's not the best-documented thing but if you've experience with other retrogaming systems and understand the components it's not so hard to figure out (in the end, it is just retroplayer, in Kodi).
-
Code
e2label /dev/nvme0n1p1 "NAME"^ Label the filesystem and this will be used for the mount instead of the default 'composite' name which tends to be a bit long..
-
Do i need to use the older nivida image with my system specs?
Yes, for nVidia cards you need the Generic-Legacy image. It's the only one that includes drivers for them. Using the normal Generic image would explain the lack of graphics
-
I've added a wiki article for future users/reference: https://wiki.libreelec.tv/configuration/fonts
-
You can add an Arial based font that contains the language support you need to /storage/.kodi/userspace/Fonts/Arial.ttf and then reboot to have the file selectable in Kodi settings > interface > skin > fonts (quoting from memory so might not be exact). The capital F and A letters in the file path are intentional/required.
-
The "fail to initialize ptp_kvm" message is harmless and correct because you're not running under a KVM hypervisor. However if you got that far the good news is; the device has booted the LE kernel. If you remove "quiet" from boot params you'll see more output dumped onto the screen which might hint why the UI is not coming up. I also forget whether we still enable a local console to poke around in, but if we do (and we booted that far) it will be on CTRL+ALT+F3. I have a hunch the console output will stop when we load userspace, and this probably means we're failling to load it - although failure to find/load the SYSTEM file normally results on an obvious on-screen error message.
-
Code
Display MoreCONFIG_SND_SOC_INTEL_AVS=m # # Available DSP configurations # # CONFIG_SND_SOC_INTEL_AVS_MACH_DA7219 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_DMIC is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_ES8336 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_HDAUDIO is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_I2S_TEST is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_MAX98927 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_MAX98357A is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_MAX98373 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_NAU8825 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_PROBE is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_RT274 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_RT286 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_RT298 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_RT5514 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_RT5663 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_RT5682 is not set # CONFIG_SND_SOC_INTEL_AVS_MACH_SSM4567 is not set # end of Intel AVS Machine driversI'm not that familiar with Intel hardware these days, but I can see we have CONFIG_SND_SOC_INTEL_AVS set but none of the DSP drivers like CONFIG_SND_SOC_INTEL_AVS_MACH_ES8336 are set.
Is that what you were referring to mglae ?
-
Nothing stands out in the log but the most popular cause of crashes is add-ons, so I would start with a clean install of latest LE12 or LE13 nightly and then manually restore add-on settings and other essential preferences, and then reinstall the addons using latest versions from the repo. This generally negates old addons that cause issues, or you discover which add-on causes the problem as you work your way through the list.
-
On Linux this *is* a true statement and anything you read on Kodi in the LE wiki will be written from a Linux perspective.
Feel free to continue using Windows.
-
Here's what the problem looks like
The image shows you trying to use "root" as the user. That's correct for SSH access, but the default Samba user is "libreelec" with password "libreelec" so that could be the obvious problem?
