OPI3 LTS Armbian 23.02 Bullseye use "console=serial" boot fail

[张军]

I'm using Armbian 23.02 Bullseye CLI. I didn't want the HDMI to show the boot system log and TTY1 login screen. According to the armbian documentation, I changed "console=both" to "console=serial" in /boot/armbianEnv.txt. I checked /boot/boot.cmd related to console, and I confirmed that this modification is OK, but it cannot start, uboot printed "Starting kernel..." After that, there is no output, and the power supply is only 5V 170mA. The following is the printing of the serial port. If anyone has been in a similar situation, please give me a little help, thank you very much.

 

U-Boot SPL 2022.07-armbian (Feb 17 2023 - 22:32:08 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.2(debug):a04808c1-dirty
NOTICE:  BL31: Built : 22:32:01, Feb 17 2023
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc086990, model: OrangePi 3 LTS
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
NOTICE:  PMIC: AXP805 detected
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9

U-Boot 2022.07-armbian (Feb 17 2023 - 22:32:08 +0000) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3 LTS
DRAM:  2 GiB
Core:  50 devices, 14 uclasses, devicetree: separate
WDT:   Not starting watchdog@7020400
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from FAT... Unable to use mmc 1:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3259 bytes read in 2 ms (1.6 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
204 bytes read in 1 ms (199.2 KiB/s)
MMC: no card present
** Bad device specification mmc 0 **
37640 bytes read in 4 ms (9 MiB/s)
3844 bytes read in 3 ms (1.2 MiB/s)
Applying kernel provided DT fixup script (sun50i-h6-fixup.scr)
## Executing script at 45000000
17091365 bytes read in 844 ms (19.3 MiB/s)
21803016 bytes read in 1077 ms (19.3 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41730000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    17091301 Bytes = 16.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 48fb3000, end 49fffae5 ... OK
   Loading Device Tree to 0000000048f41000, end 0000000048fb2fff ... OK

Starting kernel ...

[going]

Most likely, it's not about the direction of the log output.
It looks like you've done two things.
For example, we updated the kernel and\or u-boot packages and then changed the output for u-boot.
 

20.05.2023 в 17:51, 张军 сказал:

mmc1(part 0) is current device
Scanning mmc 1:1...

This is loading from the memory on the board.
Write the image to the SD card and boot from it.

Mount the device memory to the /mnt folder and mount the dev, proc, sys folders there

leo@bananapim64:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           199M  3,3M  196M   2% /run
/dev/mmcblk0p1  7,2G  982M  6,2G  14% /
tmpfs           994M     0  994M   0% /dev/shm
.....
leo@bananapim64:~$ ls /dev/mmc*
/dev/mmcblk0  /dev/mmcblk0p1  /dev/mmcblk2  /dev/mmcblk2boot0  /dev/mmcblk2boot1  /dev/mmcblk2p1

leo@bananapim64:~$ sudo mount /dev/mmcblk2p1 /mnt
leo@bananapim64:~$ sudo mount --bind /dev /mnt/dev
leo@bananapim64:~$ sudo mount --bind /proc /mnt/proc
leo@bananapim64:~$ sudo mount --bind /sys /mnt/sys

leo@bananapim64:~$ sudo chroot /mnt /bin/bash
root@bananapim64:/# 

Next, make the necessary correction. In this case, reinstall the kernel package.

Or to begin with, try to return the original state of the file /boot/armbianEnv.txt

 

 

I just did this and the download went fine.

leo@bananapim64:~$ cat /boot/armbianEnv.txt 
verbosity=7
bootlogo=false
console=serial
.......

 

[Gunjan Gupta]

Thanks for reporting this. Made me realize why I was not able to boot any 5.15 kernel on my custom build images. 

 

I have added few fixes for 6.1 and 6.5 kernel. Feel free to upgrade to them from beta repository i.e. beta.armbian.com. Stable repository is lacking fixes for wifi though which are currently included only in kernel from beta repository

[张军]

On 9/20/2023 at 1:28 PM, Gunjan Gupta said:

I have added few fixes for 6.1 and 6.5 kernel. Feel free to upgrade to them from beta repository i.e. beta.armbian.com. Stable repository is lacking fixes for wifi though which are currently included only in kernel from beta repository

Thank you for your support, I will update the kernel tonight to test it. But i would to ask how I update them from beta repository. Choose another kernel through the armbian-config->System->Other? What do i need to configure to point to this repository?

[Gunjan Gupta]

Fixes are now available in stable kernel as well. so you should be able to upgrade the kernel without needing to switch to beta repository.

[张军]

On 9/21/2023 at 7:12 PM, Gunjan Gupta said:

Fixes are now available in stable kernel as well. so you should be able to upgrade the kernel without needing to switch to beta repository.

I tested it using Armbian 23.11.0-trunk.125 Bookworm with Linux 6.1.54-current-sunxi64 and the problem was fixed.