Fedora hang at systemd without error and other logs

Ask Fedora
, ,
1

Hi,

I am new to fedora and intrested in fedora/riscv. I am trying to run fedora on my self-defined riscv machine.

I use qemu to emulate a self-defined machine, and i opensbi and uboot to boot fedora 38 ( I downloaded the fedora image from here Fedora-Developer-3820230519.n.0-qemu.raw.img.xz).

I have run fedora on QEMU virt machine successfully. But I can’t boot fedora on my QEMU self-defined machine. It always hangs at the systemd like the pic. And It never outputs “[ OK ]” label log everytime I run fedora on my qemu machine, but virt machine does.

image
image1920×1264 381 KB

image
image1920×1216 319 KB

My bootcommand is here:

virtio scan
setenv kernel_addr_r 0x4040000000
setenv ramdisk_addr_r 0x4080000000
setenv fdt_addr_r 0x4fff745be0
setenv kernel_comp_addr_r 0x4100000000
setenv kernel_comp_size 0x4000000
setenv bootargs "rw rootwait root=/dev/vda2 rhgb LANG=en_US.UTF-8 ealycon systemd.log_level=debug systemd.log_target=kmsg systemd.debug-shell=1 console=ttyS0 console=tty1 selinux=0 debug loglevel=7 sysrq_always_enabled=1"
ext4load virtio 0:1 ${kernel_addr_r} vmlinuz-6.2.16-300.0.riscv64.fc38.riscv64
ext4load virtio 0:1 ${ramdisk_addr_r} initramfs-6.2.16-300.0.riscv64.fc38.riscv64.img
virtio dev reset
booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}

Could someone help me to figure out the problems or tell me how to debug ? I am confused with the situation.

Thanks so much !!!

2

Has it ever worked?
Can you use a newer version? 38 is very old in Fedora world.

1 Like
3

It has never worked. My self-defined RISC-V machine uses a non-standard memory map, unlike the QEMU virt machine. Is it necessary to modify Fedora to adapt to my machine? What steps do I need to take to achieve this? I can find very few documents about it.

1 Like
4

You know a lot more about this then I do!

1 Like