Kernel panic with prebuilt image on AD9081+VCK190

This issue is still under investigation. To workaround is to use an older image and copy the versal boot from the new to the old image.

https://wiki.analog.com/resources/tools-software/linux-software/adi-kuiper_images/release_notes

Can you try 2019_R1 ?

-Michael

Hi Michael, I am doing something similar. However, I was not able to find 2019_R1 and used 2019_R2 instead.

Linux booting stuck at: random: systemd: uninitialized urandom read (16 bytes read)

See the image.

May you have suggestions?

Hi Michael, I am doing something similar. However, I was not able to find 2019_R1 and used 2019_R2 instead.

Linux booting stuck at: random: systemd: uninitialized urandom read (16 bytes read)

See the image.

May you have suggestions?

Hi Zach2023 and petalinux ,

The problem is related to the hardware clock, that by default has a date from future and in 64bit format, but the root file system in on 32 bit and cannot read it properly. So there is a kernel panic when it tries to start the main OS process :  

 Run /sbin/init as init process

Two workarounds are available, both being documented on Kuiper Linux Release Notes wiki page (Known issue #3):

1. You can get into uboot menu and type 

mw F12A0000 1717398087

2. You can etch on an SD Card a basic Kuiper image with 64bit root file system (download link), boot it and then type next in terminal:

''date -s "$(wget -qSO --max-redirect=0 google.com 2>&1 | grep Date: | cut -d' ' -f5-8)Z" & hwclock --systohc''

Afterwards, the VCK190 should boot fine with any SD Card Kuiper image.

Thanks,

Stefan.