Re: NanoPC-t4 does not boot with branch 20221008

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


> Am 12.10.2022 um 19:14 schrieb Peter Robinson <pbrobinson@xxxxxxxxx>:
> Peter,
> Can you try adding modprobe.blacklist=phy_rockchip_inno_usb2 to the
> kernel command line and see if that works for you?
> Peter
> On Mon, Oct 10, 2022 at 8:21 AM Peter Robinson <pbrobinson@xxxxxxxxx> wrote:
>> On Sun, Oct 9, 2022 at 1:10 PM Peter Boy <pboy@xxxxxxxxxxxxx> 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 System
>>> [14.886445] dracut-initqueue[696]: 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 Device.
>>> [OK] Started dbus-broker.service – D-Bus System Message Bus.

I used branch 20221009
(with „branch“ I mean )

I had to edit the club.cfg file, because the keyboard is not initialised.

The system blows up immediately after the line to which it got without that addition:
[16…] Unable to handle kernel execution from non executable memory at virtual address 000…000 
[16…] Mem Abort info:
[16…] ESRO ox000000...0004
[16…] EC = 0x21: ….

Would I get better and more helpful information it I get a seriell interface cable? I suppose, delivery would need 2-3 days.

And I detected another possible issue:

The arm-image-installer shows a message I previously missed (Sorry, I just noticed the last success line):
= Writing image complete!
>>>>>>sed: can't read /tmp/fw/EFI/fedora/grubenv: No such file or directory<<<<<<<<
= Writing idbloader.img for nanopc-t4-rk3399 .... on media /dev/mmcblk0
280+0 records in

As I see that are lines where sed is adding some kernel configuration. If I install the rock-pi target, these lines don’t show up.

And if I install the F36 version for nanopc, that sed-line doesn’t show up either.

By the way, the F36 version works well with nanopc as long as you don’t populate the NVMe onboard m.2 interface. If you do so, when booting from mSD a warning message shows like „Use NVMe for p3 LVM instead of mmcblk0 because I saw that first“. It proceeds but finally stops and obviously can’t use NVMe for p3/LVM. I hope it is not important because everyone will use the onboard eMMC module and hopefully the problem doesn’t exist with faster emmc memory. I saved the complete installation log file, and can upload it if useful.


arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux