Posts by mglae

    grub.cfg is only needed (and used) on EFI32 systems. Check /proc/cmdline after boot if your parameters are included.


    On N4000 usually EFI64 (or legacy boot) is implemented. Configuration file is /syslinux.cfg.



    On the AMD you can even use the amdgpu driver with:


    Code
    radeon.cik_support=0 amdgpu.cik_support=1 radeon.si_support=0 amdgpu.si_support=1
    Code
    2021-09-18 04:37:57.812 T:139920263327360   DEBUG: LogindUPowerSyscall - Received unknown signal NameAcquired
    2021-09-18 04:37:57.812 T:139920263327360  NOTICE: Quitting due to POSIX signal

    That is looking unusual - receiving unexpected signal, quitting and google drive addon is hanging on exit.


    1. 9.2 is EOL, logs of 10.0 are preferred (although I can follow the idea old release for old device).


    2. Use pastekodi to generate logs, it may include more information.

    Should i keep this version of service.libreelec.settings ?

    Yes, if further backups are desired ;-)


    What will happen in the next version update of LibreELEC ?

    This version is continued to be executed a long the addon version of the update is still 10.0. Keep in mind to delete the installed addon.


    If mglae can do a PR and it ticks all the correct boxes, then it could be in the next release.

    It's almost done.

    There is an interrupt that cannot be handled:

    IRQ 20 is used for PCI Interrupt Link [LUS0] enabled at IRQ 20 (IMO the USB) and PCI Interrupt Link [Z00F] enabled at IRQ 20 (no idea what this is).


    Likely a driver for the Z00F device is missing.


    Try adding the mentioned irqpoll kernel parameter to the APPEND line in /flash/syslinux.cfg (after mount -o remount,rw /flash).

    Last directory acceessed is logged with /storage/.kodi/userdata/peripheral_data. Please post the output of:

    Code
    ls -la /storage/.kodi/userdata/peripheral_data


    And while you are on it for the log naming issue:

    Code
    ls -la /storage/.kodi/temp
    Code
    Feb 02 17:30:58.586444 LibreELEC-PI4 kodi.sh[988]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20210202173055.log

    Surprisingly crash log is generated but not included in the paste.


    Please do

    Code
    paste /storage/.kodi/temp/kodi_crashlog_20210202173055.log

    and post the URL.

    Do you really expect that I'm able to theoretically choose the the correct combination of uid, gid, forceuid and forcegid parameters needed in your configuration?

    Unfortunately there is no useful information in the old log.


    Ssh into your device and do

    Code
    echo DEBUG=1 >>/storage/.config/kodi.conf

    Enable debugging in Settings>System Settings>Logging of kodi GUI, reboot, reproduce the crash and upload the crash log again.