Posts by mglae

You can just rebuild the package:

PROJECT=Generic ARCH=x86_64 scripts/clean pixman
PROJECT=Generic ARCH=x86_64 scripts/build pixman:host

Or using MT build with generated log:

PROJECT=Generic ARCH=x86_64 scripts/clean pixman
PROJECT=Generic ARCH=x86_64 scripts/buildmt pixman:host

After changing the package contents the clean step is not needed.

Use a pastebin site for posting logs. Please add build.LibreELEC-Generic.x86_64-9.80-devel/build/pixman-0.40.0/.x86_64-linux-gnu/build.ninja

To test configure build type add PKG_TOOLCHAIN="configure" to package.mk.

Does it fail on compiling pixman:host or pixman:target? Please always provide full logs from the failing package.

Meson may be part of the problem, the package is only configured for configure.

chewitt Was corrected in post #3 :-)))

Fixed in 20201230 nightly.

Graphics drivers are build into the kernel and cannot be blacklisted

You can modify the udev rules:

cp /usr/lib/udev/rules.d/97-xorg.rules /storage/.config/udev.rules.d/

Remove the unwanted graphics driver line with nano /storage/.config/udev.rules.d/97-xorg.rules - in this case "radeon".

Optional suffix is possible:

 # sleep --help
BusyBox v1.31.0 (2020-10-25 23:41:19 UTC) multi-call binary.

Usage: sleep [N]...

Pause for a time equal to the total of the args given, where each arg can
have an optional suffix of (s)econds, (m)inutes, (h)ours, or (d)ays

autoexec.sh does not need to be executable, to create or add the delay just do:

echo "sleep 30" >> /storage/.config/autostart.sh

Sorry, my fault. "dumb" was lost by accident. Will PR a fix.

I'm sure you already know, but:

The default device has no passthrough capabilities, but support 7.1 channels PCM:

     Device 1
         m_deviceName      : @
         m_displayName     : Default (NVidia CK804 NVidia CK804)
         m_deviceType      : AE_DEVTYPE_PCM
         m_channels        : FL, FR, BL, BR, FC, LFE, SL, SR
         m_streamTypes     : No passthrough capabilities

The only passthrough device is the S/PDIF device with 2 PCM channels (5.1 via AC3):

     Device 4
         m_deviceName      : iec958:CARD=CK804,DEV=0
         m_displayName     : NVidia CK804
         m_deviceType      : AE_DEVTYPE_IEC958
         m_channels        : FL, FR
         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512

I'm afraid as long you do not find a physical connection and kodi configuration to output hearable sound via the S/PDIF interface (like TV(AC3) from Audio quickstart guide - Official Kodi Wiki) there is no passthrough support.

chewitt Did not look for any discussion.

The error message in the source is here. In mt7601u_init_hardware() first the firmware is loaded in mt7601u_mcu_init() and later the EEPROM is checked in mt7601u_eeprom_init().

I'm afraid you both do waste your time. The firmware is loaded successfully and the version is printed but the driver does not support devices without EEPROM (or valid EEPROM data).

Which alsa device from your Kodi log is now selected for having sound?

elmismo In alsamixer do you have a volume bar for S/PDIF or can you only toggle between "MM" and "0"?

That surprise me. I've tested 20201221 from USB stick on my Kaveri system, reproduced the issue and solved it by choosing amdgpu.

Please post complete pastekodi log again

For these Southern and Sea Island GPUs you can switch to the amdgpu kernel driver that is not affected by the bug.

Make /flash writable: mount -o remount,rw /flash.

Edit syslinux configuration: nano /flash/syslinux.cfg and add radeon.si_support=0 amdgpu.si_support=1 to the APPEND line.

Crash log is from version 20201211 and does not help.

Access 20201221 via ssh, use pastekodi and post the URL to collect more information.

Or just type pastecrash in your ssh session and post the resulting URL here.

If you are still using a RPI2 you do need LibreELEC-RPi2.arm-9.80-nightly-20201218-76a852d.img.gz

> Does the update go inside /storage/.update?

Yes

> Does the firmware go inside /storage/.config/firmware/rtl_bt?

Yes

> When updating this version, will the system continue to update automatically?

No.

> with the next update will the change be lost?

No

Put the new firmware into /storage/.config/firmware/brcm