Posts by mglae

Why did you omit any version number in your post?

As a hint: downgrading from LE13 nightly to LE12 stable or nightly is not supported.

I don't know which drivers chewitt has enabled, they may need additional firmware. The requested pastekodi is required but in worst case may hot give no more information.

To the intel-audio.conf: if not creating the empty file you do have the file active from /usr/lib/modprobe.d/ by default.

The medium good news: since yesterday I'm having jack sound via the Sound Open Firmware drivers on my Gemini Lake test machine. But kodi don't see HDMI audio any more. Maybe something need be polished...

Likely busybox mount is ignoring options after device and mountpoint

With dd did you unzip the image?

gzip -dc LibreELEC-RPi4.aarch64-12.0.1.img.gz|dd of=/dev/xxx bs=64k

Quote from emveepee

and in the newest version the line is the same but that rw turns to ro but I can see existing files.

ro is odd because storage is explicit mounted rw. LibreELEC-Generic.x86_64-13.0-nightly-20241206-ca4bded.img.gz has the kernel update 6.12 to 6.12.3. It include nfs commit 56a5d99 changing "something with ro". On my side it does continue working, but using NFS4.

Quote from emveepee

so maybe related to

These messages are normal, ignore them.

Quote from emveepee

I can't specify disk=NFS4 as a kernel parameter

To mount a nfs4 server use e.g. disk=NFS=172.16.3.4:/mnt/media/storage,vers=4.2

As a test you may even try with disk=NFS=172.16.3.4:/mnt/media/storage,vers=3 to see if there is any issue in the LE parsing code.

Yoyoda To enable the DSP drivers please create intel-audio.conf with

touch /storage/.config/modprobe.d/intel-audio.conf

and reboot.

chewitt We are using https://github.com/LibreELEC/Libr…ntel-audio.conf

Start with removing LIBVA_DRIVER_NAME, iHD should be default.

Quote from emveepee

it hangs at Reache dtarget kodi.target and freezes Any suggestion how I might diagnose this?

Assuming you are using Generic (GBM) this is usually caused by kodi crashing. If ssh is enabled login should still be possible. With adding systemd.debug_shell to the kernel command line a debug shell can be reached at console 3 with Alt-F3 as long kodi is not running.

Quote from emveepee

instead I get an error during boot

writer can't create directory '/storage/the number': Read onlyfile system

If you are using the overlay parameter the message is caused by this mkdir. Please check the access rights of 172.16.3.4:/mnt/media/storage

Local console is only enabled for installer mode of boot stick and does not work at all when using GBM. But for X11 using Generic-legacy image it is still possible, only kernel parameter has been changed with LE10.

Replace tty with systemd.debug_shell and you can use CTRL+ALT+F3 again.

I am referring to:

Audio:
  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster
    driver: sof-audio-pci-intel-apl bus-ID: 00:0e.0 chip-ID: 8086:5a98 

and noticed the missing sof-audio-pci-intel-apl.ko

Looks like we need to enable Sound Open Firmware. Links: https://www.sofproject.org/ https://github.com/thesofproject

Using make menuconfig create these changes.

Module name is now snd-sof-pci-intel-apl.ko but does support PCI device [8086:5A98]:

filename:       snd-sof-pci-intel-apl.ko
import_ns:      SND_SOC_SOF_PCI_DEV
import_ns:      SND_SOC_SOF_INTEL_HDA_COMMON
license:        Dual BSD/GPL
alias:          pci:v00008086d00003198sv*sd*bc*sc*i*
alias:          pci:v00008086d00005A98sv*sd*bc*sc*i*
depends:        snd-sof-intel-hda-common,snd-soc-acpi-intel-match,snd-sof-pci
retpoline:      Y
intree:         Y
name:           snd_sof_pci_intel_apl
vermagic:       6.6.63 SMP mod_unload 

Likely this is not sufficient, just a first step

When working simple errors like "only dirty flag set" or "journal need replaying" are fixed before mounting. More severe errors still let the mount fail.

Yes. According to this thread at least snd-sof-pci-intel-apl is missing.

YoyodaDo they descuss your device?

Da Flex the No soundcards found. message is visible on any Generic installation.

Yes, links were somehow garbled - fixed.

Fine that it is working now.

Did check the log again, forget my older posts

Dec 03 08:43:08.309240 LibreELEC kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug

Dec 03 08:43:08.310203 LibreELEC kernel: acpi PNP0A08:00: ignoring host bridge window [mem 0x000cc000-0x000cffff window] (conflicts with Video ROM [mem 0x000c0000-0x000cd3ff])

Dec 03 08:43:08.354949 LibreELEC kernel: [drm] BIOS signature incorrect 0 0
Dec 03 08:43:08.354974 LibreELEC kernel: resource: resource sanity check: requesting [mem 0x00000000000c0000-0x00000000000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000cbfff window]
Dec 03 08:43:08.355000 LibreELEC kernel: caller pci_map_rom+0x83/0x220 mapping multiple BARs
Dec 03 08:43:08.355135 LibreELEC kernel: amdgpu 0000:0a:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
Dec 03 08:43:08.355168 LibreELEC kernel: [drm] BIOS signature incorrect 0 0
Dec 03 08:43:08.355299 LibreELEC kernel: amdgpu 0000:0a:00.0: amdgpu: Fetched VBIOS from platform
Dec 03 08:43:08.355324 LibreELEC kernel: amdgpu: ATOM BIOS: SWBRT34978.001

Dec 03 08:43:08.357177 LibreELEC kernel: [drm] Unsupported Connector type:21!
Dec 03 08:43:08.357207 LibreELEC kernel: [drm] Unsupported Connector type:21!
Dec 03 08:43:08.357233 LibreELEC kernel: [drm] Unsupported Connector type:21!
Dec 03 08:43:08.357253 LibreELEC kernel: [drm] Unsupported Connector type:21!

A web search on Unsupported Connector type:21! lead to e.g. this thread where changing the boot mode help. Others succeed with firmware update or even create work around as here.

When firmware update is not successful I'm wondering if using pci=nocrs does change anything.

1. With updating to LE12 nightly you do get kernel 6.6.63, maybe something is fixed:

wget -P /storage/ https://test.libreelec.tv/12.0/Generic/Generic/LibreELEC-Generic.x86_64-12.0-nightly-20241204-f894320.img.gz

2. On one of the successful boots:
a. Create a log for our curiosity
b. Use getedid create to save the found configuration for further boots.

Quote from goofy84

is it a solution for a single HD setup or can i use multiple hd´ s? The libreelec partions has to be the first partions?

Any partition on multiple HDs, usually grub can access any HD. Even the partitions can be on different HDs.

Quote from goofy84

The next thing i realized is that the " aren´ t accepted by my grub2win Version.

I doubt that. But likely the grub2win app is managing the menu structure an you only need:

    search --set=root --label LE_SYS
    linux /KERNEL boot=LABEL=LE_SYS disk=LABEL=LE_DAT quiet tty

What if you power cycle again?