Posts by mglae

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?

Did you set Samba user/password in LE-Settings Addon?

LibreELEC require two partitions. You can follow my old post, just use the active grub2win *.cfg.

Now testing an extended version of the ntfs kernel mount, see: Improving ntfs3 kernel mount

As further follow up to my post here is an improved mount.ntfs script using ntfs-3g.probe and ntfsfix for fixing simple "dirty flag" issues.

This is experimental. If you are willing to test install the attached addon from ZIP on your LE12 or LE13 system.

If there are issues provide a system log, minimal with journalctl -u 'udevil-mount@*'|paste or a complete log via LE addon.

12.0.0.1 - avoid error on shutdown
12.0.0.0 - initial version

Quote from JurKub

learned a lot the last couple of days

To not trust posted samples because they may contain typos?

Thanks, fixed my posts.

The NTFS-3G addon is now installable from the LE12 repo.

Quote from JurKub

your work around didn't work

A drop in file is injected into the systemd service. Check with systemctl cat lircd and systemctl status lircd.

logging is usually done into journal. For lirc use journalctl -u lircd, for anything just journalctl.

There is at least one report that using the updated connman of a LE12 nightly does solve DHCP issues of 12.0.1.

Configure LE Service addon's Update tab to manual updates from Custom URL https://test.libreelec.tv, channel libreelec-12.0 and update to latest nightly.

Definitely a bug, use the work around.

I'm using amdgpu on this HW for years. It get more support from AMD than radeon, e.g. GL version is 4.6 instead of 4.5.

Using /var/lock/lockdev is a bug in lirc 0.10.2 release archive.

As work around create a systemd drop in file to make the required directory:

[Service]
ExecStartPre=-/usr/bin/mkdir -p /var/lock/lockdev