Posts by mglae

After rethinking my suggestion: it is not really the same configuration because USB is required at startup from firmware/BIOS.

But you can check the firmware/BIOS setting. If there are any "fast boot" or other options that may prevent full chip set initialization: disable them.

Better general change is to use:

After=network-online.target

You may have to increase network timeout in LE Settings Addon

Try to attach a keyboard for investigation.

Quote from klh939

I am not sure how to proceed with this investigation

Test the DAC on different PC HW with using the same SW: LibreELEC USB stick running in "live" or "run" mode?

Logs can be shown with journalctl -u service.filebrowser

We need to rework the setup after the change

To use automatic nightlys you have to configure LE Service addon's Update tab to updates from Custom URL https://test.libreelec.tv, channel libreelec-12.2.

Quote from scaesare

One question, is there any way to confirm via the logs that that a machine is not running generic_legacy?

In Kodi you can check if X11 is mentioned in Settings -> System Information -> Video.

From console do cat /etc/os-release.

The CN60 is using the crocus DRI driver:

[    16.712] (II) intel(0): [DRI2]   DRI driver: crocus

[    20.046] (II) AIGLX: Loaded and initialized crocus

Having the choice of disabling ASPM or AER I would ever choose ASPM because this is more likely the cause of the error.

ath9k seem still being blacklisted, is it failing with kernel 6.17 too?

emveepee i965 is the vaapi driver. For intel iHD of "media-driver" package or i965 of "mesa" is used.

The i915 driver mentioned is the intel graphics kernel driver name. LE "xorg-xonfigure" package use the kernel name to choose a X11 config file if required.

Now to the confusion:

The current intel mesa Gallium3D drivers since 21.1 are named i915 (!), crocus and iris. They are chosen according to the GPU, a paste /var/log/Xorg.0.log will show the one used.

Old mesa legacy driver are named i915 (again) and i965 (but not the vaapi driver). They are still available in the mesa-amber branch, the i915 may be named i915g too.

:-(((((

Edit:

PS: is the pci=noaer still required?

Mesa 4.2 disabled DRI2 by default and Mesa 5.2 removed it completely. We had to force DRI3 for intel driver in LE13 development () and there seem to be no issues but your GPU is likely not supported.

I'm interested in /var/log/Xorg.0.log for the error case (and we should include it to pastekodi). Please cp /var/log/Xorg.0.log ~ in error case and paste it when having network.

You can try the "modesetting" driver:

cp /etc/X11/xorg-i915.conf ~/.config
nano ~/.config/xorg-i915.conf

and change Driver "intel" to Driver "modesetting"

Please test if the aspm parameter of post #23 does improve your wifi experience.

There is no KEY_B in Lircmap.xml of kodi.

Quote from chewitt

but I'm wondering if x86_64 is somehow different ..

ASPM was an issue over years e.g for the realtek r8169 driver.

Quote from emveepee

and adding the config pcie_aspm=off

If disabling ASPM is not working another parameter to try is pci=noaer.

Quote from emveepee

my setting was 10s seconds

The 10 seconds default is known to be optimistic, in ideal case DHCP take ~6 sec. If e.g. the router does not react on DHCP_REQUESTED_IP option there is an additional 15 sec delay.

Quote from scaesare

Job wait time-sync.servce/start running

I'm wondering if changing the TTYPath= from /dev/console to /dev/tty1 in journald.conf of Generic will improve the debug console user experience...

The job running indicates there is no network connection (as you assumed). Temporary work around may be using ethernet but commands can be typed blind even with this message..

Without network you can store pastekodi output locally with pastekodi -c >log.file and upload it later with paste log.file

With adding systemd.debug_shell parameter to the APPEND line you do get a debug shell on console 3. Press <Ctrl><Alt><F3> to select it. Switch back to X or default console with <Ctrl><Alt><F1>. The debug console is accessible too when booting the USB install stick into installer.

For testing multiple boot configurations can be used in syslinux. cfg. Replace the PROMPT 0 line with e.g. (using your UUIDs):

PROMPT 1
TIMEOUT 50

LABEL txt
  KERNEL /KERNEL
  APPEND boot=UUID=$UUID1 disk=UUID=$UUID2 textmode

and you can select textmode at boot with typing txt

GBM connector can be forced via advancedsettings.xml.

First ssh in and use kmsprint to get the connected connector name of the screen.

Create advancedsettings.xml (replace "Virtual-1" with your connector name):

<advancedsettings version="1.0">

<!-- Debug Logging -->
<loglevel hide="false">1</loglevel> 

<!-- No monitor selection on GBM but connector can be forced: -->
<videoscreen>
<monitor>Virtual-1</monitor>
</videoscreen>

</advancedsettings>

Debug logging is enabled to ease the setup.

Perform systemctl restart kodi to test the configuration.

The log only show a crash of the LE-Settings log uploader.

To work around the issue please enable (and test) ssh access first. After the original crash log in via ssh and use the pastecrash command.

Patch is accepted upstream in inputstream.ffmpegdirect. I've created a LE13 PR.

emveepee Thanks for testing. I should have noted gdb shows the error sequence in ffmpegdirect::FFmpegStream::GetFFMpegOptionsFromInput().

chewitt IMO more likely the commit Jeroened showed in post #9, especially making the kodi CURL class final.