switched kernel meson64 to sunxi and it's not booting anymore

[Onira]

Hello

 

I wanted to change kernel from meson to sunxi[code]

$ dpkg -l | grep linux-image
rc  linux-image-current-meson64       24.11.1                             arm64        Armbian Linux current kernel image 6.6.63-current-meson64
ii  linux-image-current-sunxi:armhf   24.11.1                             armhf        Armbian Linux current kernel image 6.6.62-current-sunxi[/code]

and after reboot It is not booting

What can I do is it possible to copy some files from fresh downloaded image or edit any file to make it boot from sunxi kernel?

[Werner]

First question? Why???

 

Replace boot: https://docs.armbian.com/User-Guide_Recovery/#replacing-boot

Easiest would be if you had another arm64 based system since you could simply chroot into the sdcard and then do regular apt operations to install correct packages again.

[Onira]

It's not SD but it is eMMC and I hope replacing /boot will be the same

I don't remember how to chroot I've done it over 10 years ago when installing gentoo but it is still alive and don't need to chroot

Edited Friday at 06:06 PM by Onira

[SteeMan]

47 minutes ago, Onira said:

I hope replacing /boot will be the same

Replacing /boot is not the same.  You also have to make sure that the contents of the kernel modules are present for the kernel you are loading (i.e. /lib/modules)

[SteeMan]

On 1/1/2025 at 3:21 PM, Onira said:

to make it boot from sunxi kernel?

You didn't answer the question from Werner above.  What are you trying to do?  meson (i.e. Amlogic cpus) and sunxi (i.e. Alwinner cpus) are completely different kernels designed for different CPU families from different CPU manufacturers.  You can only use the kernel built for your CPU. 

[Onira]

I just thought that if it's available in repo I can switch between those kernels

 

I have downloaded

https://mirror.hostiko.network/armbian/pool/main/l/linux-6.6.63/linux-image-current-meson64_24.11.
1_arm64__6.6.63-Sbff3-D0531-P0ad2-Cf15dH1526-HK01ba-Ve377-B59f0-R448a.deb
https://mirror.hostiko.network/armbian/pool/main/l/linux-dtb-current-meson64/linux-dtb-current-mes
on64_24.11.1_arm64__6.6.63-Sbff3-D0531-P0ad2-Cf15dH1526-HK01ba-Ve377-B59f0-R448a.deb
https://mirror.hostiko.network/armbian/pool/main/a/armbian-firmware/armbian-firmware_24.11.1_all__
1-SA8dbb-B6c7f-R448a.deb
But don't know about root filesystem

Edited Friday at 08:09 PM by Onira

[SteeMan]

FYI. Using armbian-config will limit you to compatible kernels for your current distribution.

[Werner]

3 minutes ago, Onira said:

But don't know about root filesystem

Have you read https://docs.armbian.com/User-Guide_Recovery/#replacing-boot ?

There is also procedure how to extract the contents of .debs to the sdcard without chroot.

 

 

 

[Onira]

Yes I am reading it and there are 4 things to download but I can't find the first one

Is there 4th thing I should download?

With those 3 I've downloaded I don't see uInitrd and initrd

Edited Friday at 09:14 PM by Onira

[Onira]

I have flashed another sd card with 24.11.1 Bookworm Minimal / IOTand upgraded kernel to 6.6.63

please an advice which files / folder shoult I copy?

[Werner]

Easiest is probably to copy the whole /boot directory. Make sure to adjust the UUID in armbianEnv.txt to match the target sdcard. Otherwise boot will probably stuck in initramfs.

Use blkid to get the value.

[Onira]

the old card has /lib directory while the new has ~lib pointing to /usr/lib 

is this a matter?

I guess I have to copy correct version of modules to the specific directory

[going]

1 час назад, Onira сказал:

I have flashed another sd card with 24.11.1 Bookworm Minimal / IOTand upgraded kernel to 6.6.63

please an advice which files / folder shoult I copy?

Did you download the device from the SD card?
Is your broken space located on eMMC?
If so, you will need to mount your eMMC.

sudo mount /dev/mmcblk*** /mnt

sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo mount --bind /dev /mnt/dev
sudo mount --bind /dev/pts /mnt/dev/pts

sudo chroot /mnt

apt update; apt install linux-image-current-meson64 linux-dtb-current-meson64

exit
sudo umount /mnt/dev/pts
sudo umount /mnt/dev
sudo umount /mnt/sys
sudo umount /mnt/proc

 

[Onira]

I copied whole /boot directory changing UUID and copied modules to /usr/lib

now I get

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 121174
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
Wait bl30...Done
Sending bl301.......OK.
Run bl301...
1 from SD, src: 0x00020200, des: 0x10100000, size: 0x00011130


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: eLoad bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00080f90
f be ad de d f0 ad ba ef be ad de not ES chip
[0.235956 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2019.07-armbian (Sep 02 2019 - 01:17:47 +0200) odroid-c2

Model: Hardkernel ODROID-C2
Soc:   Amlogic Meson GXBB (S905) Revision 1f:b (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
=>

and it stucks, not doing anything more...

 

If I plug any USB with SDcard it reboots and doesn't boot properly

Edited Saturday at 06:03 PM by Onira

[going]

01.01.2025 в 23:21, Onira сказал:

wanted to change kernel from meson to sunxi[code]

$ dpkg -l | grep linux-image
rc  linux-image-current-meson64       24.11.1                             arm64        Armbian Linux current kernel image 6.6.63-current-meson64
ii  linux-image-current-sunxi:armhf   24.11.1                             armhf        Armbian Linux current kernel image 6.6.62-current-sunxi[/code]

and after reboot It is not booting

I think we need to remember this and publish it in the documentation in the section HOW TO KILL\DESTROY THE DEVICE CORRECTLY.

[Onira]

Well is there any way to rescue this system?

[Werner]

Is /boot/boot.env present?

[going]

13 минут назад, Onira сказал:

Well is there any way to rescue this system?

Download the device from the SD card.
Mount the eMMC in /mnt.
Post what is there:

ls -al /mnt/boot
ls -al /mnt/usr/lib/modules

 

[Onira]

ls -l /mnt/sdcard/boot/armbianEnv.txt  
-rw-r--r-- 1 1011 1011 161 01-04 18:39 /mnt/sdcard/boot/armbianEnv.txt

cat /mnt/sdcard/boot/armbianEnv.txt  
verbosity=1
console=both
overlay_prefix=meson
rootdev=UUID=015d852a-9602-49c3-9c98-b032271fcc05
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

mount | grep sdcard
/dev/sdd1 on /mnt/sdcard type ext4 (rw,relatime)

blkid | grep sdd
/dev/sdd1: UUID="015d852a-9602-49c3-9c98-b032271fcc05" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c21f0000-01"

 

ambian minimal doesn't seem to have any USB support I don't see any USB device that I connect, SD reader flash drive network card or anything else

 

ls -al /mnt/sdcard/boot/
razem 61308
drwxr-xr-x  3 root root     4096 01-04 18:39 .
drwxr-xr-x 20 root root     4096 01-04 12:31 ..
-rw-r--r--  1 1011 1011      161 01-04 18:39 armbianEnv.txt
-rw-r--r--  1 root root    38518 11-17 13:43 boot.bmp
-rw-r--r--  1 1011 1011     8061 11-17 13:40 boot.cmd
-rw-rw-r--  1 root root     8133 11-17 13:43 boot.scr
-rw-r--r--  1 root root   259048 11-25 12:33 config-6.6.63-current-meson64
lrwxrwxrwx  1 root root       26 01-04 17:20 dtb -> dtb-6.6.63-current-meson64
drwxr-xr-x  3 root root     4096 01-04 17:19 dtb-6.6.63-current-meson64
lrwxrwxrwx  1 root root       30 01-04 16:49 Image -> vmlinuz-6.6.63-current-meson64
-rw-r--r--  1 root root 15287081 01-04 16:52 initrd.img-6.6.63-current-meson64
-rw-r--r--  1 root root        0 01-04 16:49 .next
-rw-r--r--  1 root root  4429862 11-25 12:33 System.map-6.6.63-current-meson64
lrwxrwxrwx  1 root root       30 01-04 16:52 uInitrd -> uInitrd-6.6.63-current-meson64
-rw-r--r--  1 root root 15287145 01-04 16:52 uInitrd-6.6.63-current-meson64
-rw-r--r--  1 root root 27429376 11-25 12:33 vmlinuz-6.6.63-current-meson64

ls -al /mnt/sdcard/usr/lib/modules
razem 12
drwxr-xr-x  3 root root 4096 01-04 12:33 .
drwxr-xr-x 72 root root 4096 01-04 18:49 ..
drwxr-xr-x  3 root root 4096 11-17 13:42 6.6.63-current-meson64

Edited Saturday at 07:01 PM by Onira

[Onira]

I found nanopineo+2 from someone at my work and borrowed it but I get

$ sudo mount --bind /proc /mnt/proc
$ sudo mount --bind /sys /mnt/sys
$ sudo mount --bind /dev /mnt/dev
$ sudo mount --bind /dev/pts /mnt/dev/pts
$ sudo chroot /mnt
chroot: failed to run command ‘/bin/bash’: No such file or directory

 

[going]

8 часов назад, Onira сказал:

I found nanopineo+2 from someone at my work and borrowed it but I get

First, you need to mount your memory device in the /mnt folder.

ls -l /mnt/bin/bash

 

[Onira]

I did it first

$ sudo mount /dev/sda1 /mnt

Before all those --bind mounting

$ ls -l /mnt/bin/bash
-rwxr-xr-x 1 root root 1346480 Mar 29  2024 /mnt/bin/bash

 

there you go

[going]

Maybe so:

sudo chroot /mnt/

or

sudo chroot /mnt/bin/bash

or

cd /mnt
sudo chroot ./bin/bash

 

[Onira]

$ sudo mount /dev/sda1 /mnt
$ sudo mount --bind /proc /mnt/proc
$ sudo mount --bind /sys /mnt/sys
$ sudo mount --bind /dev /mnt/dev
$ sudo mount --bind /dev/pts /mnt/dev/pts
$ sudo chroot /mnt/
chroot: failed to run command ‘/bin/bash’: No such file or directory
$ sudo chroot /mnt/bin/bash
chroot: cannot change root directory to '/mnt/bin/bash': Not a directory
$ cd /mnt
/mnt$ sudo chroot ./bin/bash
chroot: cannot change root directory to './bin/bash': Not a directory