Linux Kernel Compilation and Booting Updates for RISC-V (rv64g) with UEFI enabled

[Billa Surendra]

Dear all,

I have compiled the Linux kernel for RISC-V (rv64g) with UEFI enabled. I have initiated the booting of Linux with QEMU in two different ways.

1. Using the -cpu rv64,c=true flag:

Under this option, the kernel booted successfully, and network services are functioning properly. I am able to SSH, and dnf is also working properly.

2. Using the -cpu rv64,c=false flag:

However, when opting for this configuration, the kernel boots successfully, but network services and firewall services are not operational, and neither SSH nor dnf are functioning.

Error Messages:

  OK  ] Started systemd-coredump@0…Process Core Dump (PID 308/UID 0).
[FAILED] Failed to st[rt 0f1irewalld.…rewalld - dynamic firewall daemon.
;31mFAILED] Failed to start firewalld.…rewalld - dynamic firewall daemon.
aSee 'systemctl seetatus firewall d.'systemctl sservice' for dettails.
tus firewalld.service' for details.
[  OK    OK  ] Reached targmet network-pre…getm - R Preparatioeachned target or Network.
[0;1;39mnetwork-pre…get - Preparation for Network.
            Startin      Startig NetworkManager.service - Network nManager...
g NetworkManager.service - Network Manager...
[2m  OK  ] Star0ted systemd-cor32edump@1…Procemss Core Dump (PID 318/UID 0).
  OK  ] Started systemd-coredump@1…Process Core Dump (PID 318/UID 0).
[FAILED] Failed to start NetworkManager.service - Network Manager.
See 'systemctl status NetworkManager.service' for details.
[FAILED] Failed to start NetworkManager.service - Network Manager.
See 'systemctl status NetworkManager.service' for details.
dency failed for Netw…[0m - Network [0m - Net[wDEPEND] Depeork Manager Wait Onlinne.
Manager Wait Online.
[  OK  ] Reached target [nework.targ[et - Netw;ork.

Can anyone please help me to solve the problem.

Thanks

Billa Surendra

[Billa Surendra]

Thanks, I'll look into it.

On Tue, Apr 30, 2024 at 12:07 PM Tommy Murphy <tommy_...@hotmail.com> wrote:

Some of your logs seems very garbled for some reason. 

But the logs are giving you advice on getting further information about the service/daemon startup failures.

Your first step should presumably be to follow this advice?

dmesg might also provide some useful info? 

And perhaps enabling core dumping and analysing any generated core dumps using GDB might help?

[FangFei Yang (Yangff)]

Sounds like you just recompiled the kernel? That means the user program may still be using the c extensions?

[Billa Surendra]

No, complete filesystem and kernel compiled without compressed instruction support.