On Sun, Oct 9, 2022 at 1:10 PM Peter Boy <firstname.lastname@example.org> wrote:
> Last week I got my hands on a FriendlyElec NanoPC-t4
> I tried to boot branch 20221008, but the boot process stopped at:
> [OK] Reached target basic.target - Basic System
> [14.886445] dracut-initqueue: WARNING: File locking is disabled.
> Starting dbs-broker.serv…ice - D-Bus System Message Bus …
> [OK] Found device dev-mapper-fe…ice - /dev/mapper/fedora-root.
> [OK] Reached target initrd-root...e.target – Initrd Root Device.
> [OK] Started dbus-broker.service – D-Bus System Message Bus.
> The same is true with Beta 1.5 and with Fedora 36.
The above isn't particularly useful for debug, can you put the entire
output of the boot process (U-Boot through dmesg) into a paste service
> It looks similar to an error I had with my Radxa Rock Pi 4a which was resolved (the Rock Pi boots that branch without any problems, even from NVMe disk using Armbian SPI Flash, by the way).
> Some branches earlier the process stopped at the same line, but after about 15 mins continued repeatedly showing the same error message again and again, and finally an emergency mode shell prompt.
> Unfortunately I didn't noted any details because I run out of time. So I retried today with the current branch. It it helps I can try to find the branch with the latter behaviour.
I'm not sure what you mean by branches in this context.
arm mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue