Upgrading to Bullseye (troubleshooting Armbian 21.08.1)


ebin-dev
 Share

11 11

Recommended Posts

Armbian is a community driven open source project. Do you like to contribute your code?

Hi everyone! Thank you for all the updates on this. I have now fully upgraded my Helios64 with a ZFS pool from Armbian 21.08.2 Buster to Armbian 21.08.2 Bullseye (full Debian and Armbian repos). All good, no issues. As currently I'm just using the emmc to boot with system installed on sata1, the emmc speed impact is negligble in my case - but hopefully this will be sorted in the near future.

Link to post
Share on other sites

Did anyone try 21.08.2? Is it worth upgrading already?
I made an upgrade buster -> bullseye yesterday on Pine64 . It just works .

Upgrade needed only if you need some updated software from Bullseye . As for me trigger was mpd (my Pine64 board used mostly as audio player / receiver ) .

Sent from my M2007J20CG using Tapatalk

Link to post
Share on other sites

Hello everyone,

 

I am currently trying to repair my Helios64.


I exposed my problem in this topic

A member ( @IcerJo ) said that this problem could be related to this topic. So I read the posts of this topic looking for a solution.

 

I removed the hard drives from my NAS (to avoid a false manipulation) and I opened it (to be able to force the boot from the microSD with the jumper cab P10). Then I followed the instructions of the @TDCroPower message (here

 

Unfortunately, it didn't work. My NAS refuses to boot from the eMMC (fail at step 10 of the @TDCroPower message). Note that I tried 2 times these instructions: first with the Armbian_21.08.2_Helios64_buster_current_5.10.63 image. Then with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image. My current version is: Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64 and my NAS can only boot from the MicroSD card. Moreover, I can only communicate with it through the usb−usb-c cable, via picocom. SSH doesn’t work (I have an error message " WARNING: remote host identification has changed! "...).

 

Concerning the boot from the eMMC, I understood that it was maybe necessary to refresh the bootloader on eMMC. I didn’t understand very well the procedure to follow to make such thing. I went to armbian-config > System > Install > 5 - Install/Update the bootloader on SD/eMMC, then I rebooted... but nothing. Here is what picocom returns when I try to boot from the eMMC

 

Spoiler

picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 1500000
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready
DDR Version 1.24 20191016
In
channel 0
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 254
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 67971
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5af4
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 03 2021 - 22:43:46 +0100)

SoC: Rockchip rk3399
Reset cause: POR
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
166 bytes read in 13 ms (11.7 KiB/s)
15701569 bytes read in 1507 ms (9.9 MiB/s)
28580352 bytes read in 2727 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15701505 Bytes = 15 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f4ff6000, end f5eef601 ... OK
   Loading Device Tree to 00000000f4f79000, end 00000000f4ff5fff ... OK

Starting kernel ...

 

I'm a little bit lost. I don't understand much about it. Does anyone have a clue for me? Whether the NAS runs on eMMC or MicroSD doesn't really matter to me. I just want to be able to get a working NAS and recover the data from my hard drives (previously configured with OpenMediaVault). 

 

Thank you very much, everyone.

Link to post
Share on other sites

14 hours ago, Cariboux said:

I removed the hard drives from my NAS (to avoid a false manipulation) and I opened it (to be able to force the boot from the microSD with the jumper cab P10). Then I followed the instructions of the @TDCroPower message (here :

 

Unfortunately, it didn't work. My NAS refuses to boot from the eMMC (fail at step 10 of the @TDCroPower message). Note that I tried 2 times these instructions: first with the Armbian_21.08.2_Helios64_buster_current_5.10.63 image. Then with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image. My current version is: Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64 and my NAS can only boot from the MicroSD card. Moreover, I can only communicate with it through the usb−usb-c cable, via picocom. SSH doesn’t work (I have an error message " WARNING: remote host identification has changed! "...).

 

 

 

If you boot from sdcard while your previous system was on eMMC the ssh identification is different. If you want to connect to the sd card rescue system:

ssh -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no -o  "PasswordAuthentication yes" root@helios64

I mean if your system is on eMMC and you boot from a sd card rescue system you have to tell ssh to ignore the host (and force password auth because the sd card system will not have public kay auth set up).

 

about the failure at step 10 ... you should remove the sd card before boot (and your jumper mod) to boot from eMMC and all should be fine.

Mind the process you followed did not tell to set the jumper 10 because it tells to switch boot media via u-boot prompt a command "run bootcmd_mmc1" for sd and "run bootcmd_mmc0" for eMMC. Doing both jumper 10 and u-boot bootcmd_mmc1 is undefined. Simply do one or the other not both.

 

Cheers

Link to post
Share on other sites

22 hours ago, prahal said:

about the failure at step 10 ... you should remove the sd card before boot (and your jumper mod) to boot from eMMC and all should be fine.

Mind the process you followed did not tell to set the jumper 10 because it tells to switch boot media via u-boot prompt a command "run bootcmd_mmc1" for sd and "run bootcmd_mmc0" for eMMC. Doing both jumper 10 and u-boot bootcmd_mmc1 is undefined. Simply do one or the other not both.

 

Cheers

 

Hi @prahal, thank you for helping me !

 

So, I have remove the jumper cap and the MicroSD card, but the boot from eMMC doesn’t work. 

This is what I have when I try to start from eMMC : 

Spoiler

DDR Version 1.24 20191016
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 323
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 79411
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5ba8
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Sep 08 2021 - 10:55:50 +0000)

SoC: Rockchip rk3399
Reset cause: RST
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
=>                                                 
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
166 bytes read in 12 ms (12.7 KiB/s)
15701569 bytes read in 1508 ms (9.9 MiB/s)
28580352 bytes read in 2726 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15701505 Bytes = 15 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f4ff6000, end f5eef601 ... OK
   Loading Device Tree to 00000000f4f79000, end 00000000f4ff5fff ... OK

Starting kernel ...
 

 

... and the kernel never start. (The System activity LED of the Front Panel is blue still. It’s not blinking.)

 

When I boot from the MicroSD card (with the command « run bootcmd_mmc1 »), it’s working. 

 

 When I boot from the MicroSD card, at the step 5 of the @TDCroPower’s message (https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=128305 ), I see this (I don’t know if it’s normal, especialy what is in red)

Spoiler

Welcome to Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64

 

No end-user support: work in progress

 

System load:   7%               Up time:       0 min    
Memory usage:  3% of 3.77G      IP:           192.168.2.155
CPU temp:      51°C               Usage of /:    5% of 29G        
RX today:      16 KiB      
 

root@helios64:~# mkdir -p /mnt/system
root@helios64:~# mount /dev/mmcblk2p1 /mnt/system
root@helios64:~# cd /mnt/system/
root@helios64:/mnt/system# ll
total 102792
lrwxrwxrwx   1 root root        7 Feb  4  2021 bin -> usr/bin
drwxr-xr-x   3 root root     4096 Oct 13 17:47 boot
drwxr-xr-x   2 root root     4096 Oct 13 17:46 dev
drwxr-xr-x 112 root root    12288 Sep 16 16:13 etc
drwxr-xr-x   2 root root     4096 Jan 12  2021 export
drwxr-xr-x   3 root root     4096 Feb 18  2021 home
lrwxrwxrwx   1 root root        7 Feb  4  2021 lib -> usr/lib
-rw-r--r--   1 root root   314356 Jul  8 19:32 linux-dtb-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root   316512 Sep  8 13:19 linux-dtb-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 11533048 Jul  8 19:32 linux-headers-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 11466188 Sep  8 13:19 linux-headers-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 40272020 Jul  8 19:33 linux-image-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 41246520 Sep  8 13:19 linux-image-current-rockchip64_21.08.2_arm64.deb
drwx------   2 root root    16384 Feb  4  2021 lost+found
drwxr-xr-x   2 root root     4096 Feb  4  2021 media
drwxr-xr-x   2 root root     4096 Feb  4  2021 mnt
drwxr-xr-x   2 root root     4096 Feb  4  2021 opt
drwxr-xr-x   2 root root     4096 Nov 22  2020 proc
drwx------   7 root root     4096 Mar 16  2021 root
drwxr-xr-x   2 root root     4096 Oct 13 16:32 run
lrwxrwxrwx   1 root root        8 Feb  4  2021 sbin -> usr/sbin
drwxrwxr-x   2 root root     4096 Feb  4  2021 selinux
drwxr-xr-x   7 root root     4096 Feb 28  2021 srv
drwxr-xr-x   2 root root     4096 Nov 22  2020 sys
lrwxrwxrwx   1 root root       42 Sep 16 16:13 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0
drwxrwxrwt   2 root root     4096 Oct 13 17:47 tmp
drwxr-xr-x  10 root root     4096 Feb  4  2021 usr
drwxr-xr-x  14 root root     4096 Feb 18  2021 var
 

 

( Maybe I have made a mistake because when I have do the step 6 of @TDCroPower’s message, I only « wget » 3 packages of this link : http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.63-rockchip64/ : linux-dtb-current-rockchip64_21.08.2_arm64.deblinux-headers-current-rockchip64_21.08.2_arm64.deb and linux-image-current-rockchip64_21.08.2_arm64.deb. I didn’t « wget » the 3 packages « 21.05.9 ».

(But, when i have try the downgrading with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image on my MicroSD, i have « wget » all the three packages of http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.35-rockchip64/ . But it was not working neither....) )

 

Link to post
Share on other sites

On 10/15/2021 at 3:20 PM, Cariboux said:

This is what I have when I try to start from eMMC : 

  Hide contents

DDR Version 1.24 20191016
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 323
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 79411
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5ba8
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Sep 08 2021 - 10:55:50 +0000)

SoC: Rockchip rk3399
Reset cause: RST
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
=>                                                 
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
166 bytes read in 12 ms (12.7 KiB/s)
15701569 bytes read in 1508 ms (9.9 MiB/s)
28580352 bytes read in 2726 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15701505 Bytes = 15 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f4ff6000, end f5eef601 ... OK
   Loading Device Tree to 00000000f4f79000, end 00000000f4ff5fff ... OK

Starting kernel ...
 

 

... and the kernel never start. (The System activity LED of the Front Panel is blue still. It’s not blinking.)

 

check that eMMC boot/armbianEnv.txt contains:
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u

 

Note rootdev=UUID= will be different. You can check your by running

sudo blkid

from the sdcard os.

 

I believe yours is fine so you could also:

fsck /dev/mmcblk2p1

when booting from sdcard (booting kernel that has the emmc fix only ! your log shows 5.10.63 armbian 22.08.2 so your are fine. But double check before fscking).

Fscking will tell you if the filesystem is fine (readable/mountable by for one u-boot itself to start the kernel).

 

My mmcblk2p1 boot/armbianEnv.txt content was wrong as I ran fsck when my emmc was unstable (this was a bad idea). Thus u-boot was unable to start the system. Restoring armbianENv.txt fixed my boot.

 

On 10/15/2021 at 3:20 PM, Cariboux said:

When I boot from the MicroSD card (with the command « run bootcmd_mmc1 »), it’s working. 

 

 When I boot from the MicroSD card, at the step 5 of the @TDCroPower’s message (https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=128305 ), I see this (I don’t know if it’s normal, especialy what is in red)

  Hide contents

Welcome to Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64

 

No end-user support: work in progress

 

System load:   7%               Up time:       0 min    
Memory usage:  3% of 3.77G      IP:           192.168.2.155
CPU temp:      51°C               Usage of /:    5% of 29G        
RX today:      16 KiB      
 

root@helios64:~# mkdir -p /mnt/system
root@helios64:~# mount /dev/mmcblk2p1 /mnt/system
root@helios64:~# cd /mnt/system/
root@helios64:/mnt/system# ll
total 102792
lrwxrwxrwx   1 root root        7 Feb  4  2021 bin -> usr/bin
drwxr-xr-x   3 root root     4096 Oct 13 17:47 boot
drwxr-xr-x   2 root root     4096 Oct 13 17:46 dev
drwxr-xr-x 112 root root    12288 Sep 16 16:13 etc
drwxr-xr-x   2 root root     4096 Jan 12  2021 export
drwxr-xr-x   3 root root     4096 Feb 18  2021 home
lrwxrwxrwx   1 root root        7 Feb  4  2021 lib -> usr/lib
-rw-r--r--   1 root root   314356 Jul  8 19:32 linux-dtb-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root   316512 Sep  8 13:19 linux-dtb-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 11533048 Jul  8 19:32 linux-headers-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 11466188 Sep  8 13:19 linux-headers-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 40272020 Jul  8 19:33 linux-image-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 41246520 Sep  8 13:19 linux-image-current-rockchip64_21.08.2_arm64.deb
drwx------   2 root root    16384 Feb  4  2021 lost+found
drwxr-xr-x   2 root root     4096 Feb  4  2021 media
drwxr-xr-x   2 root root     4096 Feb  4  2021 mnt
drwxr-xr-x   2 root root     4096 Feb  4  2021 opt
drwxr-xr-x   2 root root     4096 Nov 22  2020 proc
drwx------   7 root root     4096 Mar 16  2021 root
drwxr-xr-x   2 root root     4096 Oct 13 16:32 run
lrwxrwxrwx   1 root root        8 Feb  4  2021 sbin -> usr/sbin
drwxrwxr-x   2 root root     4096 Feb  4  2021 selinux
drwxr-xr-x   7 root root     4096 Feb 28  2021 srv
drwxr-xr-x   2 root root     4096 Nov 22  2020 sys
lrwxrwxrwx   1 root root       42 Sep 16 16:13 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0
drwxrwxrwt   2 root root     4096 Oct 13 17:47 tmp
drwxr-xr-x  10 root root     4096 Feb  4  2021 usr
drwxr-xr-x  14 root root     4096 Feb 18  2021 var
 

 

The red is fine it is color for deb file type.

 

 

 

On 10/15/2021 at 3:20 PM, Cariboux said:

( Maybe I have made a mistake because when I have do the step 6 of @TDCroPower’s message, I only « wget » 3 packages of this link : http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.63-rockchip64/ : linux-dtb-current-rockchip64_21.08.2_arm64.deblinux-headers-current-rockchip64_21.08.2_arm64.deb and linux-image-current-rockchip64_21.08.2_arm64.deb. I didn’t « wget » the 3 packages « 21.05.9 ».

(But, when i have try the downgrading with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image on my MicroSD, i have « wget » all the three packages of http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.35-rockchip64/ . But it was not working neither....) )

 

 

just  a note. The steps were to download from :

root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-dtb-current-rockchip64_21.05.4_arm64.deb
root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-headers-current-rockchip64_21.05.4_arm64.deb
root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-image-current-rockchip64_21.05.4_arm64.deb

not 5.10.63 ... but 5.10.63 will be fine too per

 ie 21.08.2 has the emmc fix.

Link to post
Share on other sites

On 10/16/2021 at 10:27 PM, prahal said:

check that eMMC boot/armbianEnv.txt contains:
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u

 

I booted from the MicroSD (command « run bootcmd_mmc1 »). The command « sudo vim /boot/armbianEnv.txt » shows

Spoiler

verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=a7a41236-bd7e-4b26-a31d-e30f47633de7
rootfstype=ext4 
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
"/boot/armbianEnv.txt" 6L, 166C                               1,1           All
 

 

So, I added (with vim) the line « overlays=dwc3-0-host ». 

 

When I enter « sudo blkid », I have this 

Spoiler

root@helios64:~# sudo blkid
/dev/mmcblk2p1: UUID="e4e3bcd6-3f03-4362-bbe0-f1654138c5d8" TYPE="ext4" PARTUUID="aaedb48e-01"
/dev/mmcblk1p1: UUID="a7a41236-bd7e-4b26-a31d-e30f47633de7" TYPE="ext4" PARTUUID="436f9809-01"
/dev/zram0: UUID="5c89530a-5757-4e66-a8d6-987959cbd813" TYPE="swap"
/dev/mmcblk2: PTUUID="aaedb48e" PTTYPE="dos"
/dev/mmcblk1: PTUUID="436f9809" PTTYPE="dos"
/dev/zram1: LABEL="log2ram" UUID="8ad8e588-16b9-46e0-bc70-be4de52f85c5" TYPE="ext4"
 

 

I entered « fsck /dev/mmcblk2p1 » and it showed this 

Spoiler

root@helios64:~# fsck /dev/mmcblk2p1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
/dev/mmcblk2p1: recovering journal
/dev/mmcblk2p1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mmcblk2p1: 101902/924288 files (0.1% non-contiguous), 771522/3774692 blocks
 

 

I turned off the NAS, removed the MicroSD, turned on.... and... it’s not working...

What did I miss ? Do I have to change the « rootdev=UUID » in boot/armbianEnv.txt ? Remplacing the actual UUID of the MicroSD by the UUID of the eMMC

(Note : now, if the MicroSD is in the NAS, this one boot automatically with no need of the command « run bootcmd_mmc1 »)

Link to post
Share on other sites

5 hours ago, Cariboux said:

What did I miss ? Do I have to change the « rootdev=UUID » in boot/armbianEnv.txt ?

 

On emmc (/dev/mmcblk2p1) you just need to replace the root UUID in /etc/fstab and in /boot/armbianEnv.txt to match the UUID of your emmc (e4e3bcd6-3f03-4362-bbe0-f1654138c5d8). Then reboot without microsd in the slot...

Link to post
Share on other sites

16 hours ago, ebin-dev said:

On emmc (/dev/mmcblk2p1) you just need to replace the root UUID in /etc/fstab and in /boot/armbianEnv.txt to match the UUID of your emmc (e4e3bcd6-3f03-4362-bbe0-f1654138c5d8). Then reboot without microsd in the slot...

 

I am deeply sorry to ask such a beginner's question, but : how can I do that ? I mean : I know how to edit (with « sudo vim ») /etc/fstab and /boot/armbianEnv.txt, but I don’t know how to « reach » theses files in the eMMC (/dev/mmcblk2p1)...  

Link to post
Share on other sites

mount your eMMC to some random folder. mkdir ~/mount && mount /dev/mmcblk2p1 ~/mount && cd ~/mount

Link to post
Share on other sites

Beware ! Do not change your sdcard /boot/armbianEnv.txt. Only the one of the emmc ! thus /mnt/boot/armbianEnv.txt if you mount /dev/mmcblk2p1 to /mnt .

As I understood you checked the  /boot/armbianEnv.txt  of the Sdcard which is not right. If you boot from the sdcard then this one is correct, do not change it.

But check your emmc one is not corrupted. Thus /mnt/boot/armbianEnv.txt and compare with the one I gave.

 

As fsck showed your emmc partition was corrupted and fixed by fsck. Try to run

fsck /dev/mmcblk2p1

as second time and paste output just to be confident it is now ok.

 

Then when yoiu boot without sdcard try to force u-boot to boot from emmc.

run bootcmd_mmc0

from u-boot prompt.

 

Cheers. There are not many option for a failed boot. But check emmc not sdcard files.

From your lsblk output :

rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8

 

Link to post
Share on other sites

6 minutes ago, prahal said:

Beware ! Do not change your sdcard /boot/armbianEnv.txt. Only the one of the emmc ! thus /mnt/boot/armbianEnv.txt if you mount /dev/mmcblk2p1 to /mnt .

As I understood you checked the  /boot/armbianEnv.txt  of the Sdcard which is not right. If you boot from the sdcard then this one is correct, do not change it.

But check your emmc one is not corrupted. Thus /mnt/boot/armbianEnv.txt and compare with the one I gave.

 

You are right ! : I made the mistake of editing the /boot/armbianEnv.txt of the SDcard. (I didn’t touch the UUID but I added this line « overlays=dwc3-0-host ».)

 

So, I followed what @Werner wrote (« mkdir ~/mount && mount /dev/mmcblk2p1 ~/mount && cd ~/mount ») and this is what I see with « root@helios64:~/mount# sudo vim /boot/armbianEnv.txt » 

Spoiler

verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=a7a41236-bd7e-4b26-a31d-e30f47633de7
rootfstype=ext4
overlays=dwc3-0-host
~
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
"/boot/armbianEnv.txt" 8L, 189C                               8,1           All

 

 

« root@helios64:~/mount# sudo vim /mnt/boot/armbianEnv.txt » gives this (!)

Spoiler

~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
"/mnt/boot/armbianEnv.txt" [New DIRECTORY]                    0,0-1         All

(Yes, it’s empty !)

 

 

« root@helios64:~/mount# sudo vim /etc/fstab » gives this

Spoiler

UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8 / ext4 defaults,noatime,commit=600,err
ors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
"/etc/fstab" 2L, 136C                                         1,40          All
 

 

 

And « root@helios64:~/mount# fsck /dev/mmcblk2p1 », that (...) 

Spoiler

root@helios64:~/mount# fsck /dev/mmcblk2p1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
/dev/mmcblk2p1 is mounted.
e2fsck: Cannot continue, aborting.
 

 

 

Link to post
Share on other sites

42 minutes ago, Cariboux said:

« root@helios64:~/mount# sudo vim /mnt/boot/armbianEnv.txt » gives this (!)

  Reveal hidden contents

~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
"/mnt/boot/armbianEnv.txt" [New DIRECTORY]                    0,0-1         All

(Yes, it’s empty !)

 

If you followed the example given by werner it should be mounted to /mount ...

Try this: sudo vim /mount/boot/armbianEnv.txt

Link to post
Share on other sites

If it is empty then you now know why u-boot fails to boot the kernl.

Mine was filled with garbage due to the FS corruption (due to the emmc bug)

 

Fill the emmc armbianEnv.txt with:

echo 'verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u' > /mount/boot/armbianEnv.txt

and reboot. You are done !

Link to post
Share on other sites

17 minutes ago, prahal said:

If it is empty then you now know why u-boot fails to boot the kernl.

Mine was filled with garbage due to the FS corruption (due to the emmc bug)

 

Fill the emmc armbianEnv.txt with:

echo 'verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u' > /mount/boot/armbianEnv.txt

and reboot. You are done !

 

I just tried it and it doesn't work (« "/mount/boot/armbianEnv.txt" E212: Can't open file for writing », with VIM). 

 

Then, I was struck by a doubt... So, I checked if armbianEnv.txt exists (in my eMMC). I have mount my eMMC as @Werner said (here). Then, I tried this

Spoiler

root@helios64:~# cd ~/mount
root@helios64:~/mount# ls -a
.             linux-dtb-current-rockchip64_21.05.1_arm64.deb      root
..            linux-dtb-current-rockchip64_21.08.2_arm64.deb      run
.autorelabel  linux-headers-current-rockchip64_21.05.1_arm64.deb  sbin
bin           linux-headers-current-rockchip64_21.08.2_arm64.deb  selinux
boot          linux-image-current-rockchip64_21.05.1_arm64.deb    srv
dev           linux-image-current-rockchip64_21.08.2_arm64.deb    sys
.dpkg-old     lost+found                                          thermal_zone0
etc           media                                               tmp
export        mnt                                                 usr
home          opt                                                 var
lib           proc
root@helios64:~/mount# cd /mnt
root@helios64:/mnt# ls -a
.  ..  system
 

As you can see, it seems that there is nothing except « system » in /mnt. No armbianEnv.txt here. 

 

But I have find armbianEnv.txt in /boot. Look : 

Spoiler

root@helios64:~/mount# ls -a
.             linux-dtb-current-rockchip64_21.05.1_arm64.deb      root
..            linux-dtb-current-rockchip64_21.08.2_arm64.deb      run
.autorelabel  linux-headers-current-rockchip64_21.05.1_arm64.deb  sbin
bin           linux-headers-current-rockchip64_21.08.2_arm64.deb  selinux
boot          linux-image-current-rockchip64_21.05.1_arm64.deb    srv
dev           linux-image-current-rockchip64_21.08.2_arm64.deb    sys
.dpkg-old     lost+found                                          thermal_zone0
etc           media                                               tmp
export        mnt                                                 usr
home          opt                                                 var
lib           proc
root@helios64:/# cd /boot
root@helios64:/boot# ls -a
.                               dtb
..                              dtb-5.10.63-rockchip64
armbianEnv.txt                  Image
armbianEnv.txt.out              initrd.img-5.10.63-rockchip64
armbian_first_run.txt.template  .next
boot.bmp                        System.map-5.10.63-rockchip64
boot.cmd                        uInitrd
boot.scr                        uInitrd-5.10.63-rockchip64
config-5.10.63-rockchip64       vmlinuz-5.10.63-rockchip64
 

So, I have edited this armbianEnv.txt here (with copy-paste of that ). 

 

I have checked the UUID in /etc/fstab (here). « root@helios64:/etc# sudo vim fstab »

Spoiler

UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8 / ext4 defaults,noatime,commit=600,err
ors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
~                                                                               
"fstab" 2L, 136C                                              1,39          All
 

 

Then... I turned off the NAS..... removed the MicroSD.... restart.... and..... 

 

... It doesn't work !!! Same problem as usual

Spoiler

Starting kernel ...

DDR Version 1.24 20191016
In
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 254
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 67786
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5af4
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE
 will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 03 2021 - 22:43:46 +0100)

SoC: Rockchip rk3399
Reset cause: POR
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
=> run bootcmd_mmc0           
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
166 bytes read in 13 ms (11.7 KiB/s)
15701569 bytes read in 1508 ms (9.9 MiB/s)
28580352 bytes read in 2727 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15701505 Bytes = 15 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f4ff6000, end f5eef601 ... OK
   Loading Device Tree to 00000000f4f79000, end 00000000f4ff5fff ... OK

Starting kernel ...
 

(kernel never start.)

 

 

After that, I restarted with the MicroSD... as usual... and I see that (!) 

Spoiler

Starting kernel ...

DDR Version 1.24 20191016
In
channel 0
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 254
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 78781
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5ba8
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE
 will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Sep 08 2021 - 10:55:50 +0000)

SoC: Rockchip rk3399
Reset cause: POR
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
=> run bootcmd_mmc1  
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 5 ms (622.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
189 bytes read in 5 ms (36.1 KiB/s)
13868411 bytes read in 591 ms (22.4 MiB/s)
28580352 bytes read in 1212 ms (22.5 MiB/s)
81924 bytes read in 13 ms (6 MiB/s)
272 bytes read in 9 ms (29.3 KiB/s)
Applying kernel provided DT overlay rockchip-dwc3-0-host.dtbo
2698 bytes read in 10 ms (262.7 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    13868347 Bytes = 13.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f51b6000, end f5eefd3b ... OK
   Loading Device Tree to 00000000f5139000, end 00000000f51b5fff ... OK

Starting kernel ...


openmediavault 5.6.14-1 (Usul) helios64 ttyS2
Copyright (C) 2009-2021 by Volker Theile. All rights reserved.

To manage the system visit the openmediavault web control panel:

eth0: 192.168.2.155
eth0: fd00:ab:cd::2e9
eth0: fd00:ab:cd:0:6662:66ff:fed0:58a
eth0: fe80::6662:66ff:fed0:58a

By default the web control panel administrator account has the
username 'admin' and password 'openmediavault'.
It is recommended that you change the password for this account
within the web control panel or using the 'omv-firstaid' CLI
command.

For more information regarding this appliance, please visit the
web site: https://www.openmediavault.org

helios64 login: root
Password: 
Last login: Tue Apr 13 20:43:55 CEST 2021 from 192.168.1.10 on pts/0
 _   _      _ _            __   _  _   
| | | | ___| (_) ___  ___ / /_ | || |  
| |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ 
|  _  |  __/ | | (_) \__ \ (_) |__   _|
|_| |_|\___|_|_|\___/|___/\___/   |_|  
                                       
Welcome to Armbian 21.08.1 Buster with Linux 5.10.63-rockchip64

No end-user support: built from trunk

System load:   5%               Up time:       4 min    
Memory usage:  6% of 3.77G      IP:           192.168.2.155
CPU temp:      55°C               Usage of /:    22% of 15G    

 

What I put in purple color is new for the situation. I guess I found my OMV installation, more or less !

Link to post
Share on other sites

4 minutes ago, Cariboux said:

What I put in purple color is new for the situation. I guess I found my OMV installation, more or less !

 

Confirmation : I’m able to connect to my OpenMediaVault with web browser. It’s here ! Thank god you, guys ! 

So, what do I do next ? Update OMV (and Armbian, via the Update Management of OMV) ? Or fix the eMMC boot problem ? 

Link to post
Share on other sites

You should settle the dust down. First check where you mount /dev/mmcblk2p1. Do you:

mount /dev/mmcblk2p1 /mnt

or

mount /dev/mmcblk2p1 /mount

?

Because the content of the emmc will show up in the above command right directory. It will not be in /mount  or /mnt if you did not made it so in the mount command.

 

Second give use the emmc boot/armbianEnv.txt because it could be  you set the sdcard armbianEnv.txt to boot with sdcard kernel and "rootdev" (ie boot partition) as emmc. Thus it works but you have to let the sdcard for the boot which is fragile.

It ought ot contains:

verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u

only. "echo" and "> /mount/boot/armbianEnv.txt" where only there so you could paste the full command and have it write the armbianEnv.txt in /mount/boot for you. If you write them down in armbianEnv.txt it kills boot.

 

Then feel free to update. I currenty run OMV with buster and armbian up to date on my helios64.

Link to post
Share on other sites

On 9/16/2021 at 3:08 AM, prahal said:

bisected eMMC breakage:
06653ebc0ad2e0b7d799cd71a5c2933ed2fb7a66 is the first bad commit
 

commit 06653ebc0ad2e0b7d799cd71a5c2933ed2fb7a66
Author: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Date:   Thu May 20 01:12:23 2021 +0300

    regulator: core: resolve supply for boot-on/always-on regulators
    
    commit 98e48cd9283dbac0e1445ee780889f10b3d1db6a upstream.
    
    For the boot-on/always-on regulators the set_machine_constrainst() is
    called before resolving rdev->supply. Thus the code would try to enable
    rdev before enabling supplying regulator. Enforce resolving supply
    regulator before enabling rdev.
    
    Fixes: aea6cb99703e ("regulator: resolve supply after creating regulator")
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20210519221224.2868496-1-dmitry.baryshkov@linaro.org
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 drivers/regulator/core.c | 6 ++++++
 1 file changed, 6 insertions(+)

 

is https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/regulator/core.c?id=98e48cd9283dbac0e1445ee780889f10b3d1db6a
from thread https://lore.kernel.org/all/20210519221224.2868496-1-dmitry.baryshkov@linaro.org/

 

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 7b3de8b0b1ca..043b5f63b94a 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -1422,6 +1422,12 @@ static int set_machine_constraints(struct regulator_dev *rdev)
         * and we have control then make sure it is enabled.
         */
        if (rdev->constraints->always_on || rdev->constraints->boot_on) {
+               /* If we want to enable this regulator, make sure that we know
+                * the supplying regulator.
+                */
+               if (rdev->supply_name && !rdev->supply)
+                       return -EPROBE_DEFER;
+
                if (rdev->supply) {
                        ret = regulator_enable(rdev->supply);
                        if (ret < 0) {

 

EDIT 1: this change to return EPROBE_DEFER if regulator has a supply name but no supply ready was intended to complete commit aea6cb99703e17019e025aa71643b4d3e0a24413 which  expects set_machine_constraints to return this eprobe_defer error to attempt to resolve the supply ( before attempting a second run of set_machine_constraints).

 

One still need to find out if aea6cb99703e17019e025aa71643b4d3e0a24413 fails to resolve the supply and thus does not make a second attempt to set_machine_constraints thus leaves the regulator disabled or else.

 

 

commit aea6cb99703e17019e025aa71643b4d3e0a24413
Author: Micha? Miros?aw <mirq-linux@rere.qmqm.pl>
Date:   Sat Sep 26 23:32:41 2020 +0200

    regulator: resolve supply after creating regulator
    
    When creating a new regulator its supply cannot create the sysfs link
    because the device is not yet published. Remove early supply resolving
    since it will be done later anyway. This makes the following error
    disappear and the symlinks get created instead.
    
      DCDC_REG1: supplied by VSYS
      VSYS: could not add device link regulator.3 err -2
    
    Note: It doesn't fix the problem for bypassed regulators, though.
    
    Fixes: 45389c47526d ("regulator: core: Add early supply resolution for regulators")
    Signed-off-by: Micha? Miros?aw <mirq-linux@rere.qmqm.pl>
    Link: https://lore.kernel.org/r/ba09e0a8617ffeeb25cb4affffe6f3149319cef8.1601155770.git.mirq-linux@rere.qmqm.pl
    Signed-off-by: Mark Brown <broonie@kernel.org>

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index ff8e99ca0306..9f704a6c4802 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -5280,15 +5280,20 @@ regulator_register(const struct regulator_desc *regulator_desc,
        else if (regulator_desc->supply_name)
                rdev->supply_name = regulator_desc->supply_name;
 
-       /*
-        * Attempt to resolve the regulator supply, if specified,
-        * but don't return an error if we fail because we will try
-        * to resolve it again later as more regulators are added.
-        */
-       if (regulator_resolve_supply(rdev))
-               rdev_dbg(rdev, "unable to resolve supply\n");
-
        ret = set_machine_constraints(rdev, constraints);
+       if (ret == -EPROBE_DEFER) {
+               /* Regulator might be in bypass mode and so needs its supply
+                * to set the constraints */
+               /* FIXME: this currently triggers a chicken-and-egg problem
+                * when creating -SUPPLY symlink in sysfs to a regulator
+                * that is just being created */
+               ret = regulator_resolve_supply(rdev);
+               if (!ret)
+                       ret = set_machine_constraints(rdev, constraints);
+               else
+                       rdev_dbg(rdev, "unable to resolve supply early: %pe\n",
+                                ERR_PTR(ret));
+       }
        if (ret < 0)
                goto wash;

 

 

 

My logs for bad shows:

[    1.257297] reg-fixed-voltage vcc1v8-sys-s0: Failed to register regulator: -517
[    1.257446] reg-fixed-voltage vcc0v9-s3: Failed to register regulator: -517
[    1.257588] reg-fixed-voltage avdd-0v9-s0: Failed to register regulator: -517
[    1.257728] reg-fixed-voltage avdd-1v8-s0: Failed to register regulator: -517
[    1.258114] reg-fixed-voltage pcie-power: Failed to register regulator: -517
[    1.258312] reg-fixed-voltage vcc3v3-sys-s3: Failed to register regulator: -517
[    1.258451] reg-fixed-voltage vcc3v0-sd: Failed to register regulator: -517
[    1.258705] reg-fixed-voltage vcc5v0-usb: Failed to register regulator: -517
[    1.261721] reg-fixed-voltage usblan-power: Failed to register regulator: -517
[    2.158719] vdd_log: supplied by regulator-dummy
[    2.230749] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    2.230781] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    2.230792] rk808-regulator rk808-regulator: max buck steps per change: 4
[    2.240854] rk808 0-001b: failed to register 12 regulator
[    2.249848] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
[    2.253127] fan53555-regulator 0-0041: FAN53555 Option[8] Rev[1] Detected!
[    2.423549] reg-fixed-voltage vcc1v8-sys-s0: Failed to register regulator: -517
[    2.424263] reg-fixed-voltage vcc0v9-s3: Failed to register regulator: -517
[    2.424830] reg-fixed-voltage avdd-0v9-s0: Failed to register regulator: -517
[    2.425443] reg-fixed-voltage avdd-1v8-s0: Failed to register regulator: -517
[    2.556287] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    2.556318] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    2.556328] rk808-regulator rk808-regulator: max buck steps per change: 4

 

while for good:

[    2.172993] vdd_log: supplied by regulator-dummy
[    2.330040] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    2.330071] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    2.330081] rk808-regulator rk808-regulator: max buck steps per change: 4
[    2.347345] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
[    2.350525] fan53555-regulator 0-0041: FAN53555 Option[8] Rev[1] Detected!

 

Hi,

as I read this post, I'm not certain whether this rk808 regulator issue is solved yet.

For info, I'm currently running:

kobol@helios64:~$ uname -a
Linux helios64 5.10.63-rockchip64 #21.08.2 SMP PREEMPT Wed Sep 8 10:57:23 UTC 2021 aarch64 GNU/Linux

 

and I have these logs (similar than @prahal for bad):

kobol@helios64:~$ journalctl -b | grep regulator
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage vcc1v8-sys-s0: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage vcc0v9-s3: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage avdd-0v9-s0: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage avdd-1v8-s0: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage pcie-power: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage vcc3v3-sys-s3: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage vcc3v0-sd: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage vcc5v0-usb: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage usblan-power: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: vdd_log: supplied by regulator-dummy
Oct 30 14:47:58 helios64 kernel: rk808-regulator rk808-regulator: there is no dvs0 gpio
Oct 30 14:47:58 helios64 kernel: rk808-regulator rk808-regulator: there is no dvs1 gpio
Oct 30 14:47:58 helios64 kernel: rk808-regulator rk808-regulator: max buck steps per change: 4
Oct 30 14:47:58 helios64 kernel: rk808 0-001b: failed to register 12 regulator
Oct 30 14:47:58 helios64 kernel: fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
Oct 30 14:47:58 helios64 kernel: fan53555-regulator 0-0041: FAN53555 Option[8] Rev[1] Detected!
Oct 30 14:47:58 helios64 kernel: rockchip-saradc ff100000.saradc: failed to get regulator, -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage vcc1v8-sys-s0: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage vcc0v9-s3: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage avdd-0v9-s0: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: reg-fixed-voltage avdd-1v8-s0: Failed to register regulator: -517
Oct 30 14:47:58 helios64 kernel: rk808-regulator rk808-regulator: there is no dvs0 gpio
Oct 30 14:47:58 helios64 kernel: rk808-regulator rk808-regulator: there is no dvs1 gpio
Oct 30 14:47:58 helios64 kernel: rk808-regulator rk808-regulator: max buck steps per change: 4
Oct 30 14:47:58 helios64 kernel: lm75 2-004c: supply vs not found, using dummy regulator
Oct 30 14:47:58 helios64 systemd[1]: Starting fan speed regulator...
Oct 30 14:47:59 helios64 systemd[1]: Started fan speed regulator.

 

Does there already exist a fix for such up-to-date kernel?

Regards,

Link to post
Share on other sites

Hello everyone,

 

Since the last time, I have good news and bad news.

 

I'll start with the good news : My NAS boots by itself, without the MicroSD card. (The problem was indeed on the side of the armbianEnv.txt file. The good one, I mean...) 

Without your help ( @prahal , @ebin-dev , @Werner , @IcerJo), I would never have managed to get out of it. Thank you so much, all of you! (I have made a small donation to the Armbian forum as a material thank you to the community.)

 

Now, for the bad news (sorry guys... :unsure: ) My device is still not working properly. When I do " apt upgrade ", I get the following error message :

Spoiler

DDR Version 1.24 20191016
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x82
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 322
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 68847
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5af4
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 03 2021 - 22:43:46 +0100)

SoC: Rockchip rk3399
Reset cause: RST
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 17 ms (182.6 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
203 bytes read in 13 ms (14.6 KiB/s)
16224611 bytes read in 1558 ms (9.9 MiB/s)
28580352 bytes read in 2727 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
272 bytes read in 28 ms (8.8 KiB/s)
Applying kernel provided DT overlay rockchip-dwc3-0-host.dtbo
2698 bytes read in 32 ms (82 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    16224547 Bytes = 15.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f4f76000, end f5eef123 ... OK
   Loading Device Tree to 00000000f4ef9000, end 00000000f4f75fff ... OK

Starting kernel ...


Armbian 21.08.3 Buster ttyS2 

helios64 login: root
Password: 
Last login: Tue Nov  2 17:42:50 CET 2021 on ttyS2
 _   _      _ _            __   _  _   
| | | | ___| (_) ___  ___ / /_ | || |  
| |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ 
|  _  |  __/ | | (_) \__ \ (_) |__   _|
|_| |_|\___|_|_|\___/|___/\___/   |_|  
                                       
Welcome to Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64

No end-user support: work in progress

System load:   9%               Up time:       3 min    
Memory usage:  36% of 3.77G      IP:           192.168.2.155
CPU temp:      55°C               Usage of /:    22% of 15G        

[ General system configuration (beta): armbian-config ]

 

root@helios64:~# sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up openmediavault (5.6.18-2) ...
Creating configuration database ...
Migrating configuration database ...
Setting up Salt environment ...
[ERROR   ] An un-handled exception was caught by salt's global exception handler:
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x81 in position 0: invalid start byte
Traceback (most recent call last):
  File "/usr/bin/salt-call", line 11, in <module>
    load_entry_point('salt==3003', 'console_scripts', 'salt-call')()
  File "/usr/lib/python3/dist-packages/salt/scripts.py", line 449, in salt_call
    client.run()
  File "/usr/lib/python3/dist-packages/salt/cli/call.py", line 58, in run
    caller.run()
  File "/usr/lib/python3/dist-packages/salt/cli/caller.py", line 112, in run
    ret = self.call()
  File "/usr/lib/python3/dist-packages/salt/cli/caller.py", line 220, in call
    self.opts, data, func, args, kwargs
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/executors/direct_call.py", line 12, in execute
    return func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 360, in orchestrate
    pillarenv=pillarenv,
  File "/usr/lib/python3/dist-packages/salt/runners/state.py", line 125, in orchestrate
    orchestration_jid=orchestration_jid,
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 1343, in sls
    initial_pillar=_get_initial_pillar(opts),
  File "/usr/lib/python3/dist-packages/salt/state.py", line 4634, in __init__
    self.client = salt.fileclient.get_file_client(self.opts)
  File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 55, in get_file_client
    )(opts)
  File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 1422, in __init__
    self.channel = salt.fileserver.FSChan(opts)
  File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 871, in __init__
    self.fs.update()
  File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 486, in update
    self.servers[fstr](**kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/fileserver/roots.py", line 161, in update
    for line in fp_:
  File "/usr/lib/python3.7/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x81 in position 0: invalid start byte
Traceback (most recent call last):
  File "/usr/bin/salt-call", line 11, in <module>
    load_entry_point('salt==3003', 'console_scripts', 'salt-call')()
  File "/usr/lib/python3/dist-packages/salt/scripts.py", line 449, in salt_call
    client.run()
  File "/usr/lib/python3/dist-packages/salt/cli/call.py", line 58, in run
    caller.run()
  File "/usr/lib/python3/dist-packages/salt/cli/caller.py", line 112, in run
    ret = self.call()
  File "/usr/lib/python3/dist-packages/salt/cli/caller.py", line 220, in call
    self.opts, data, func, args, kwargs
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/executors/direct_call.py", line 12, in execute
    return func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 360, in orchestrate
    pillarenv=pillarenv,
  File "/usr/lib/python3/dist-packages/salt/runners/state.py", line 125, in orchestrate
    orchestration_jid=orchestration_jid,
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 1343, in sls
    initial_pillar=_get_initial_pillar(opts),
  File "/usr/lib/python3/dist-packages/salt/state.py", line 4634, in __init__
    self.client = salt.fileclient.get_file_client(self.opts)
  File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 55, in get_file_client
    )(opts)
  File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 1422, in __init__
    self.channel = salt.fileserver.FSChan(opts)
  File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 871, in __init__
    self.fs.update()
  File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 486, in update
    self.servers[fstr](**kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/fileserver/roots.py", line 161, in update
    for line in fp_:
  File "/usr/lib/python3.7/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x81 in position 0: invalid start byte
dpkg: error processing package openmediavault (--configure):
 installed openmediavault package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of openmediavault-diskstats:
 openmediavault-diskstats depends on openmediavault (>= 5.6); however:
  Package openmediavault is not configured yet.

dpkg: error processing package openmediavault-diskstats (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openmediavault
 openmediavault-diskstats
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@helios64:~# 
 

 


On OpenMediaVault, when I make a change in the settings and go for the validation (" The configuration has been changed. You must apply the changes in order for them to take effect. "), the procedure fails and I get this error message :

Spoiler

ERROR

 

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color cronapt 2>&1' with exit code '1': Traceback (most recent call last): File "/sbin/omv-salt", line 151, in <module> sys.exit(main()) File "/sbin/omv-salt", line 147, in main cli() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/sbin/omv-salt", line 134, in deploy_run result = caller.cmd("state.orchestrate", names) File "/usr/lib/python3/dist-packages/salt/client/__init__.py", line 2122, in cmd return self.sminion.functions[fun](*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__ return self.loader.run(run_func, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as return _func_or_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 360, in orchestrate pillarenv=pillarenv, File "/usr/lib/python3/dist-packages/salt/runners/state.py", line 125, in orchestrate orchestration_jid=orchestration_jid, File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__ return self.loader.run(run_func, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as return _func_or_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 1343, in sls initial_pillar=_get_initial_pillar(opts), File "/usr/lib/python3/dist-packages/salt/state.py", line 4634, in __init__ self.client = salt.fileclient.get_file_client(self.opts) File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 55, in get_file_client )(opts) File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 1422, in __init__ self.channel = salt.fileserver.FSChan(opts) File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 871, in __init__ self.fs.update() File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 486, in update self.servers[fstr](**kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__ return self.loader.run(run_func, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs) File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as return _func_or_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/fileserver/roots.py", line 161, in update for line in fp_: File "/usr/lib/python3.7/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x81 in position 0: invalid start byte

 

 

-------------------------------------------------------- details --------------------------------------------------

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color cronapt 2>&1' with exit code '1': Traceback (most recent call last):
  File "/sbin/omv-salt", line 151, in <module>
    sys.exit(main())
  File "/sbin/omv-salt", line 147, in main
    cli()
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/sbin/omv-salt", line 134, in deploy_run
    result = caller.cmd("state.orchestrate", names)
  File "/usr/lib/python3/dist-packages/salt/client/__init__.py", line 2122, in cmd
    return self.sminion.functions[fun](*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 360, in orchestrate
    pillarenv=pillarenv,
  File "/usr/lib/python3/dist-packages/salt/runners/state.py", line 125, in orchestrate
    orchestration_jid=orchestration_jid,
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/modules/state.py", line 1343, in sls
    initial_pillar=_get_initial_pillar(opts),
  File "/usr/lib/python3/dist-packages/salt/state.py", line 4634, in __init__
    self.client = salt.fileclient.get_file_client(self.opts)
  File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 55, in get_file_client
    )(opts)
  File "/usr/lib/python3/dist-packages/salt/fileclient.py", line 1422, in __init__
    self.channel = salt.fileserver.FSChan(opts)
  File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 871, in __init__
    self.fs.update()
  File "/usr/lib/python3/dist-packages/salt/fileserver/__init__.py", line 486, in update
    self.servers[fstr](**kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/fileserver/roots.py", line 161, in update
    for line in fp_:
  File "/usr/lib/python3.7/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x81 in position 0: invalid start byte in /usr/share/php/openmediavault/system/process.inc:195
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusRG...', '/tmp/bgoutputmK...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

 

 

Does anyone have any idea what is going on this time? 

Link to post
Share on other sites

I upgraded with no problems. Honestly happy to see the stuff with Mesa moving along - you have a desktop with OpenGL acceleration out of the box. Thinking of trying some Retro gaming on it out of curiosity. Still looking out for transcoding or even just decoding.

Link to post
Share on other sites

 Share

11 11