Posts by mglae

Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0:   device [8086:9c14] error status/mask=00001000/00002000
Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0:    [12] Timeout               
Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0:   device [8086:9c14] error status/mask=00001000/00002000
Nov 16 14:28:04 HPElec kernel: pcieport 0000:00:1c.0:    [12] Timeout               

This is already discussed in Milhouse testbuld thread on forum.kodi.tv.

Only work around so far is using kernel 4.18 or older.

You do have installed the addon service.bluetooth-audio from the LibreELEC repo. A "Bluetooth Audio Device Changer" that "Provides the ability to change the kodi audio device if a bluetooth audio device is connected".

On kodi startup the addon selects the default audio device configured in the addon settings (with or without bluetooth).

Fix the addon setting or uninstall/disable the addon if you don't use it.

11:53:03.123 T:140228283045632  NOTICE: service.bluetooth-audio: starting add-on
11:53:03.123 T:140228283045632   DEBUG: CAddonSettings[service.bluetooth-audio]: loading setting definitions
11:53:03.123 T:140228283045632   DEBUG: CAddonSettings[service.bluetooth-audio]: trying to load setting definitions from old format...
11:53:03.124 T:140228283045632   DEBUG: CAddonSettings[service.bluetooth-audio]: loading setting values
11:53:03.127 T:140229608470272    INFO: CActiveAE::ApplySettings - Forcing samplerate to 48000

_{Let me guess: the addon set what you have configured ....}

#3062 should fix it.

A "sony notebook boot menu" web search results in i.e. How to Change Boot Order in Sony Vaio E Series - Laptops - Laptop Tech Support.

You do need to know how external device boot works to set up the ext4 partition(s) for multiboot. (or in case your XP does not boot any more).

There are several threads in this forum regarding dual/multi boor, please use the search function.

There's a bug prohibiting avahi (the zeroconf service) to start.

To fix this:

rm /storage/.cache/services
mkdir /storage/.cache/services

and reboot.

Quote from Softlander

CvH I'm wondering, Is it possible to use the remote control supplied with the tt-4600 for example with libreelec?

I've created a keymap for the S2-4600 about two years ago, but not used it (and never tested with LE9). Use ir-keytable -c -w <file> to load.

There are some issues: all keys are using two different key codes (handled by the keymap) and there is a fast autorepeat than cannot be configured.

Let me guess: this occurs since Microsoft did update your Windows 10 this week?

Change the boot order in your BIOS to boot from USB first. Or look for the magic key to open a boot device menu.

IMO the boot order was always boot from hard disk first, but the empty hard disk was detected an skipped in the first case.

Don't get me wrong but you should be happy that your ~10 years old P8700 with Mobile Intel® GM45 graphics is still supported, albeit with reduced function set.

The Kodi addon packages are only used to install docker and portainer. They are started before Kodi as systemd services wanted by multi-user.target .

It is always possible to define your own modes, see Intel NUC, kodi on 4K is limited to 30FPS.

Try TV (AC3) from Audio quickstart guide - Official Kodi Wiki

Systemd only knows when Kodi is started and has no information about the internal state.

You can create a systemd timer with OnBootSec= that start your service after a short time at boot.

vnsiserver use

/storage/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config/plugins/vnsiserver/allowed_hosts.conf

That is not a LE issue, it comes from Kodi itself.

According to Video nodes - Official Kodi Wiki Kodi use the default nodes from /usr/share/kodi/system/library/ if ~/.kodi/userdata/library/ does not exist.

But Kodi creates ~/.kodi/userdata/library/ while starting up disabling this feature.

Until this is fixed copy the default rules manually or use the Add-on:Library Node Editor.

Quote from ajiratech

Where can I see logs for the attempt to run autostart.sh ?

For the record:

journalctl -u kodi-autostart