Posts by mglae

No, objtool error occur after successfully compiled.

PS: e.g. here you do find build patches up to kernel 6.17 (but the kernel will continue to complain).

There likely will be a patch to compile wl_linux..c. But the kernel will continue to BUG() every boot on the outdated binary Broadcom blob.

You have to change --latency too.

Use systemctl stop service.snapclient and systemctl start service.snapclient while testing, reboot only as final test.

If i still failing we will start talking about logging

The parameters are used in /storage/.kodi/addons/service.snapclient/snapclient.start

Nice issue.

The implementation does only allow full minutes to be shown (beside seconds <= 60).

If it still fails ssh in and post the URL of:

grep audiooutput ~/.kodi/userdata/guisettings.xml|paste

AC3 5.1 is transported over PCM 2.0.

If it does not work post a debug log playing some 5.1 content.

Optical cable is using the same protocol as ARC channel and only support PCM 2.0 or AC3 5.1.

Use TV(AC3) settings of Audio quickstart guide - Official Kodi Wiki.

It's a feature. When connecting to the Logfiles share a new log zip is generated. This may take some time on weak devices.

Quote from palle_c

, after some investigation it seems that the Z890 chipset has a fault, in some circumstances you need to "disable" internal graphics

No. LE is only supporting a single GPU. If there are more than one the first configured wins the race. Unfortunately both GPUs may have been configured in parallel causing a crash.

Look for "xorg-configure" lines in your log.

Some discussion without fix (LE is mentioned): https://github.com/xbmc/xbmc/issues/16990

ledzilla Temperature can be an issue. Not working case/CPU fans are part of the "obvious damage". In bad case it may be required to reassemble the CPU heat sink with new thermal paste.

Da Flex This only a debug message of a required operation.

You are right, a dying PSU can be cause of the errors - but require testing with a spare PSU.

Kodi did abort() when freeing some memory.

I recommend usual service practice:

1. Remove power cord, open the case and look for obvious damage.
2. Test CMOS battery. Replace if needed.
3. Remove and reassemble DIMMS
4. Power up, open firmware settings and perform "Set Default Settings". Only change settings required to boot.

If still failing and having multiple DIMMS assembled test them one by one.

Quote from treysis

Can I somehow get the wireless stack to be more verbose in its output?

Create:

[Service]
ExecStart=
ExecStart=/usr/lib/iwd -d

Quote from patfenton

One other question, should I be worried about this line in dmesg?

7.888136] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Not really, but you can try (from mind, may be fuzzy):

umount /dev/sdb1
fsck -a /dev/sdb1

Try this.

[    8.021395] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 2230 BGN, REV=0xC8
[    8.034790] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
[    8.034841] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.

Card is detected but disabled by configuration.

Is there a physical Wifi DIsable switch at your case? If not check the BIOS settings.

You must not add a new APPEND line (or any new line to the file).

Keep the original contents and only add the parameter video=LVDS-1:d (alone!) to the end of the APPEND line separated by a space.