Posts by mglae

The nightmare is that you do accept OOM situations.

For research reasons a core dump is generated by default if possible. This can be disabled by

echo 0 >/proc/sys/vm/oom_dump_tasks

Tame your tvheadend. It was terminated while occupying 3351196kB memory.

Change WantedBy=multi-user.target=nfs to WantedBy=multi-user.target

Log Files.

For a python only lib - not needing any external dependencies or including e.g. C/C++ code - the source is the lib. Try copying the files below the "tqdm" directory.

However creating a LE python lib addon is the correct way to go.

For a python only lib you can create /storage/.kodi/addons/tqdm/lib/tqdm and copy the library files into it.

ARD/ZDF Mediathek are outdated in Kodi repo and continued at GitHub - 68000a/Gigathek: Kodi Addons zu verschiedenen deutschen öffentlich-rechtlichen TV-Mediatheken

Create and use:

#!/bin/sh
PYTHONPATH=
for addon in /storage/.kodi/addons/*/lib /storage/.kodi/addons/*/libs /usr/lib/kodi/addons/*/lib; do
  [ -d "${addon}" ] && PYTHONPATH="${PYTHONPATH:+${PYTHONPATH}:}${addon}"
done
export PYTHONPATH
exec /usr/bin/python "$@"

Yes, install 9.2 to have a working system.

And use live for any further testing not touching the working system. Only choose the correct APPEND line for any optional kernel parameters.

BTW: the board seem to be involved, web search on B450M Pro4 kernel result in e.g. [SOLVED] Ryzen 3 3200G, AsRock B450M Pro4 system crashes / Kernel & Hardware / Arch Linux Forums

Unfortunately there is nothing visible in the log.

There is still the pause_on_oops=100 parameter in the Kernel command line, you can remove it now.

amd_iommu=off is missing. Did you try it? (I'm getting out of ideas).

Quote from mjohnson007

It must be the MoBo/CPU AMD combo as I even tried putting in a extenal SSD instead of using the MoBo m.2 and stilled failed

Agree.

Maybe there are warnings/errors in the kernel log. Boot into installer, press <Alt-F3> to get the debug console and type:

mount -o rw,remount /flash
dmesg >/flash/dmesg.txt
poweroff

Put the file to a pastebin site and post the URL here.

As a wild guess: we did enable IOMMU support in the kernel at some point. You can try amd_iommu=off kernel parameter to disable it.

It's crashing while writing to the FAT FS. But there is no obvious error source visible.

1. Have you already tried a different stick on a different USB port?

2. You can test if a more recent kernel does behave better by booting a LE11 nightly from test.libreelec.tv. Do not install, LE11 is to unstable for daily use.

3. For BIOS update 5.20 one description is "Improve USB compatibility", but I really do not like recommending BIOS updates.

The first OOPS is the important one.

Add pause_on_oops=100 to the APPEND line of /syslinux.cfg and take a new picture.

Online check seem to be have fixed at 2021-08-30 in connman git.

After installing System Tools Addon you can open a terminal window. Or use ssh

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:

radeon.cik_support=0 amdgpu.cik_support=1 radeon.si_support=0 amdgpu.si_support=1

It was told the new Intel iHD drivers are not perfect on older HW but choose automatically. You can manually select them: RE: Issues on Beta 1 with X86

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.