Ubuntu server kernel issue

Is the mentioned file there?

In boot partition is this file not present:

-rwxr-xr-x 1 root root   155578 jan  7 11:20 config-4.4.154-104-rockchip-g3037f71a0de7
-rwxr-xr-x 1 root root   155489 okt 21 08:43 config-4.4.154-95-rockchip-gd2ab1f26e1b3
drwxr-xr-x 4 root root     2048 feb 21 07:30 dtbs
drwxr-xr-x 2 root root     2048 feb 23 16:50 extlinux
-rwxr-xr-x 1 root root     1806 feb 22 08:12 hw_intfc.conf
drwxr-xr-x 2 root root     2048 nov 19 08:20 overlays
-rwxr-xr-x 1 root root  4561892 jan  7 11:20 System.map-4.4.154-104-rockchip-g3037f71a0de7
-rwxr-xr-x 1 root root  4567572 okt 21 08:43 System.map-4.4.154-95-rockchip-gd2ab1f26e1b3
-rwxr-xr-x 1 root root 19494920 jan  7 11:20 vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
-rwxr-xr-x 1 root root 19496968 okt 21 08:43 vmlinuz-4.4.154-95-rockchip-gd2ab1f26e1b3

So you are missing the file. Put it there and have fun with running OS.

@pbies I really don’t know why I need to install something which I really don’t need and will in future need to patch… Im make run OS with setting root=/dev/nvme0n1p5 system with that boot normally to new updated kernel and run without any issues… It only do not boot if I try to use UUID of that partition …

That’s kernel ramdisk, a general and base code/data that the Linux runs on. You need it here or there. You want running OS so you need to configure/use it properly.

Awaiting resolution of the boot problem in your next post.

As Im said I don’t have boot problem. I can normaly boot to old or to ne kernel…
Radxa has not probably put initrd image to system for some reason. I don’t have it on sdcard ubuntu and is also missing from nvme ubuntu system… Also Im not sure how to install that image and if it will fix freezing issue which if now with latest kernel little better but still freeze after few days(before upgrade it freeze every day…

When system run ok blue led blink twice every second. But when system freeze blue led is all time turned off…

You have clearly said that the OS does not boot. You have changed your mind or the situation with the board has changed? If you are changing problems in the meantime there is no way to help you.

I have in my first post in this thread boot issues after upgrade kernel. I did not change my mind and Im at least two times in two posts write that board boot. No boot issue we fix with user rua1 when I change in extlinux.conf from:

timeout 10
menu title select kernel

label kernel-4.4.154-104-rockchip-g3037f71a0de7
    kernel /vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
    devicetreedir /dtbs/4.4.154-104-rockchip-g3037f71a0de7
    append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=/dev/nvme0n1p5

label kernel-4.4.154-95-rockchip-gd2ab1f26e1b3
    kernel /vmlinuz-4.4.154-95-rockchip-gd2ab1f26e1b3
    devicetreedir /dtbs/4.4.154-95-rockchip-gd2ab1f26e1b3
    append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE

To:

timeout 10
menu title select kernel

label kernel-4.4.154-104-rockchip-g3037f71a0de7
    kernel /vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
    devicetreedir /dtbs/4.4.154-104-rockchip-g3037f71a0de7
    append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=/dev/nvme0n1p5

So to be clear again. Board boot to system with latest kernel but only if I use for root /dev/nvme0n1p5 instead of UUID …

But with latest kernel I still have freezing issues which is not resolved.

That is expected since there are no relevant changes between Oct. 21 - Jan 7th.