Posts by chewitt

Quote from goofy84

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.

CONFIG_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 drivers 

I'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.

Quote from roxton

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?

Have you read the info in https://wiki.libreelec.tv/configuration/pulseaudio ?

Please update to a current LE13 nightly and share the URL from "dmesg | paste" again so we can see if there's any difference from newer kernel/drivers. If none, pastebin the system log and "lsmod" output from Manjaro so we can compare things.

The latest images in my testing share have some changes:

• FFmpeg bump to v7.1 - In brief testing I didn't see changes (no regressions, no improvements) but none were expected.
• Some patches from @sarbes that improve GUI performance - although we're firmly in the realm of marginal gains so don't expect performance changes to be overly noticeable.
• Ethernet performance on WP2 appears to have doubled (33MB/s is now 76MB/s) - although I am not sure why, but I suspect recent kernel changes suggested-by kszaq are responsible. It's nice to see as it's always bugged me why the WP2 NIC ran at half the speed of the (also 1Gb/sec) NIC on a N2+ or RPi4/5 board. I've no idea if this impacts other boxes .. but maybe. EDIT: An N2+ board also shows improvement from 75-80MB/s to ~110MB/s so this appears to be a general improvement.

Luni the subtitle issue is due to Kodi changes from @sarbes that impact Mali 400/450 GPUs. I've flagged the issues to him.

Quote from Tahurel

Mm ok, how often do the kodi repo update?

Whenever the addon author pushes an update to the Kodi repo

Both are from the same author and generated from the same codebase, but since the dontpanic repo is managed directly by the add-on author I wouldn't be suprised if there were newer versions in that repo, or more frequent updates to that repo.

Oleg (balbes150) was the original creator of the multiboot approach, hence LE/Armbian use it, but the scripts have been adapted over time for many varieties of hardware. From S905 onwards the vendor u-boot environment is quite consistent, but before that time things are more "open to interpretation" among clone-box vendors and you'll find more devices that don't work with our scripts. I'm not aware of any specific repo's that would be useful these days. There are likely forks of Oleg's repo in GitHub, but I would have no idea how to find/spot them among all the others.

You need to share the u-boot (early stage boot) serial uart output. This will either show what stage of boot something fails at, or nothing which indicates a more fundamental u-boot compile/packaging issue.

dtech I'm not well versed in Meson8 boot but it looks like the same "search for boot files" stuff used everywhere.

You can configure the RPi to not-wake the TV over HDMI-CEC when the board is turned on, but if the TV is off, the IR/BT receiver on the TV is also off, so the TV cannot send remote commands over HDMI-CEC to control the RPi board.

dtech It's basically the same "search for stuff on SD, USB, eMMC" sequence that AMLGX uses, only looking for older filenames.