Jump to content

Armbian images are now available for Rock 5b!


Igor
 Share

Recommended Posts

Check forum guidelines to use maximum potential!

Thanks a lot Igor. 
I've read elsewhere:
 

Quote

"since Rock 5B (RK3588’s PCIe30X4(4L) controller [1]) maxes out at Gen3 x4 if you buy an SSD capable of Gen4 speeds (or better) take care that it is not just x2 since this ends up with degraded speed: Gen3 x2. Buy a x4 SSD if you’re after maximum performance (though buy quality SSDs anyway since cheap SSD garbage will underperform always regardless of interface specs)"

 

So if anyone of you has feedback on NVMe SSDs that work well with the Rock5, please let me know.

And if I understand correctly from your message Igor and from this post, I will have (for the time being) to boot on something else (like a USB key) and then use the NVMe.

Edited by gounthar
Link to comment
Share on other sites

This is great so far, and I was able to get the image to work from the maskrom method to the eMMC.

 

Some things I've noticed:

 

- Video driver is the default software renderer, I've followed the steps here to use an alternative https://launchpad.net/~liujianfeng1994/+archive/ubuntu/panfork-mesa 

- That video driver seems to have some issues still, and does not feel very stable

- Chrome & FF will need some work to make use of the Mali video card, currently seems to be all software based render for the browsers 

Link to comment
Share on other sites

 installed the sid version yesterday... stable so far.

Problem ist just docker won't start, has some troubles with the NIC

 

Oct 31 07:59:39 rock-5b dockerd[2020]: time="2022-10-31T07:59:39.824310727+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///>
Oct 31 07:59:39 rock-5b dockerd[2020]: time="2022-10-31T07:59:39.824334642+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" mod>
Oct 31 07:59:39 rock-5b dockerd[2020]: time="2022-10-31T07:59:39.840906001+01:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Oct 31 07:59:39 rock-5b dockerd[2020]: time="2022-10-31T07:59:39.850225021+01:00" level=info msg="Loading containers: start."
Oct 31 07:59:39 rock-5b dockerd[2020]: time="2022-10-31T07:59:39.896340052+01:00" level=warning msg="Running iptables --wait -t nat -L -n failed with >
Oct 31 07:59:40 rock-5b dockerd[2020]: time="2022-10-31T07:59:40.162820791+01:00" level=info msg="stopping event stream following graceful shutdown" e>
Oct 31 07:59:40 rock-5b dockerd[2020]: failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to c>
Oct 31 07:59:40 rock-5b dockerd[2020]:  (exit status 4)
Oct 31 07:59:40 rock-5b systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE

 

wrapped text

 

+01:00" level=info msg="Loading containers: start."
+01:00" level=warning msg="Running iptables --wait -t nat -L -n failed with message: `iptables v1.8.8 (nf_tables): Could not fetch rule set generation>
+01:00" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
alizing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: iptabl>

de=exited, status=1/FAILURE

Link to comment
Share on other sites

I have been able to run armbian on a Samsung 970 Evo Plus 250GB SSD. Really nice...

 

It is though necessary to note that only a 5 Volt USB-C power supply is working with the Rock 5 Model B.

Edited by UdoA
More info
Link to comment
Share on other sites

Great news. Sure, some work to be done, but have to start somewhere, and that it boots and works, is great.  ( well that is IF you have a power-supply that will accommodate the PD issue..  i dont, yet )

Link to comment
Share on other sites

Yes, I fortunately had one pretty decent one from my Sony Smartphone which has Quickcharge 3.0 so increased supply and this happened to work.

 

Edit: With the hint from @blahblahblah on the Mali G610 driver I could get the graphical desktop working again, not rock solid, but good.

Edited by UdoA
New info
Link to comment
Share on other sites

  

On 11/2/2022 at 3:15 AM, UdoA said:

It is though necessary to note that only a 5 Volt USB-C power supply is working with the Rock 5 Model B.

 

I'm using a Baseus 65W GaN3 Pro CCGAN65-1ACC bought off eBay

 

root@rock5:~# uname -a; cat /etc/issue; sensors | grep -A3 ^tcpm
Linux rock5 5.10.72-rockchip-rk3588 #trunk.0080 SMP Sun Oct 23 18:45:28 UTC 2022 aarch64 GNU/Linux
Armbian 22.11.0-trunk Sid \l 

tcpm_source_psy_4_0022-i2c-4-22
Adapter: rk3x-i2c
in0:          20.00 V  (min = +20.00 V, max = +20.00 V)
curr1:         2.25 A  (max =  +2.25 A)

 

 

 

On 10/31/2022 at 11:16 PM, al83837773 said:

Problem ist just docker won't start, has some troubles with the NIC

 

 

Do this as root:

update-alternatives --set iptables /usr/sbin/iptables-legacy
update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

 

 

 

Thanks @Igor, nice job. 

I notice that linux-image-legacy-rockchip-rk3588 is also listed in Packages of armbian-bullseye.

What needs fixing to get rock5 to run -stable, or something less explosive than sid? ;)

Link to comment
Share on other sites

  

On 10/28/2022 at 5:44 AM, gounthar said:

So if anyone of you has feedback on NVMe SSDs that work well with the Rock5, please let me know.

 

 

I chose a 1TB Samsung MZ-V7S1T0BW 970 EVO Plus and one of the Radxa NVME heatsinks with 2x clear bands holding it on.

No paste, no sticky pad, didn't remove the sticker (sue me ;) ).

It idles along at 35°C in the acrylic case with the Radxa fan (which is on the other side of the board, obviously!), while the CPU is also around 35°C (ambient is currently 25°C).

During the fio tests below (after running several times) the drive's internal temperature peaked at 69°C, and the external temp at 59°C.

It seemed like good value (and speed) for money at AU$179 ( ~ US$115? ) on Amazon(.au).

 

root@rock5:~# hdparm -tT --direct /dev/nvme0n1

/dev/nvme0n1:
 Timing O_DIRECT cached reads:   3514 MB in  2.00 seconds = 1758.52 MB/sec
 Timing O_DIRECT disk reads: 5472 MB in  3.00 seconds = 1823.70 MB/sec
root@rock5:~# fio --filename=/mnt/nvme/test.bin --direct=1 --rw=write --ioengine=libaio --bs=2m --iodepth=64 --size=10G --numjobs=1 --runtime=60 --time_base=1 --group_reporting --name=test-seq-write
test-seq-write: (g=0): rw=write, bs=(R) 2048KiB-2048KiB, (W) 2048KiB-2048KiB, (T) 2048KiB-2048KiB, ioengine=libaio, iodepth=64
fio-3.32
Starting 1 process
test-seq-write: Laying out IO file (1 file / 10240MiB)
Jobs: 1 (f=1): [W(1)][100.0%][w=3064MiB/s][w=1532 IOPS][eta 00m:00s]
test-seq-write: (groupid=0, jobs=1): err= 0: pid=17830: Fri Nov 11 12:22:56 2022
  write: IOPS=1527, BW=3054MiB/s (3203MB/s)(179GiB/60041msec); 0 zone resets
    slat (usec): min=196, max=4245, avg=463.28, stdev=87.74
    clat (usec): min=32206, max=80119, avg=41428.38, stdev=2070.37
     lat (usec): min=32694, max=80591, avg=41891.66, stdev=2063.49
    clat percentiles (usec):
     |  1.00th=[39584],  5.00th=[40109], 10.00th=[40109], 20.00th=[40109],
     | 30.00th=[40109], 40.00th=[40633], 50.00th=[40633], 60.00th=[40633],
     | 70.00th=[40633], 80.00th=[43779], 90.00th=[45351], 95.00th=[45351],
     | 99.00th=[45876], 99.50th=[46400], 99.90th=[49021], 99.95th=[51643],
     | 99.99th=[73925]
   bw (  MiB/s): min= 2992, max= 3096, per=100.00%, avg=3057.25, stdev=18.13, samples=119
   iops        : min= 1496, max= 1548, avg=1528.59, stdev= 9.04, samples=119
  lat (msec)   : 50=99.93%, 100=0.07%
  cpu          : usr=14.26%, sys=59.82%, ctx=65623, majf=0, minf=11
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=99.9%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=0,91694,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
  WRITE: bw=3054MiB/s (3203MB/s), 3054MiB/s-3054MiB/s (3203MB/s-3203MB/s), io=179GiB (192GB), run=60041-60041msec

Disk stats (read/write):
  nvme0n1: ios=0/374636, merge=0/0, ticks=0/15378262, in_queue=15378262, util=99.85%
root@rock5:~# fio --filename=/mnt/nvme/test.bin --direct=1 --rw=read --ioengine=libaio --bs=2m --iodepth=64 --size=10G --numjobs=1 --runtime=60 --time_base=1 --group_reporting --name=test-seq-read
test-seq-read: (g=0): rw=read, bs=(R) 2048KiB-2048KiB, (W) 2048KiB-2048KiB, (T) 2048KiB-2048KiB, ioengine=libaio, iodepth=64
fio-3.32
Starting 1 process
Jobs: 1 (f=1): [R(1)][100.0%][r=3145MiB/s][r=1572 IOPS][eta 00m:00s]
test-seq-read: (groupid=0, jobs=1): err= 0: pid=17996: Fri Nov 11 12:24:25 2022
  read: IOPS=1568, BW=3137MiB/s (3289MB/s)(184GiB/60040msec)
    slat (usec): min=130, max=6520, avg=402.38, stdev=133.63
    clat (msec): min=18, max=159, avg=40.33, stdev= 2.01
     lat (msec): min=18, max=163, avg=40.73, stdev= 2.04
    clat percentiles (msec):
     |  1.00th=[   37],  5.00th=[   40], 10.00th=[   40], 20.00th=[   40],
     | 30.00th=[   41], 40.00th=[   41], 50.00th=[   41], 60.00th=[   41],
     | 70.00th=[   41], 80.00th=[   41], 90.00th=[   42], 95.00th=[   42],
     | 99.00th=[   44], 99.50th=[   46], 99.90th=[   52], 99.95th=[   72],
     | 99.99th=[  138]
   bw (  MiB/s): min= 2327, max= 3164, per=100.00%, avg=3140.59, stdev=75.34, samples=119
   iops        : min= 1163, max= 1582, avg=1570.24, stdev=37.73, samples=119
  lat (msec)   : 20=0.05%, 50=99.83%, 100=0.09%, 250=0.02%
  cpu          : usr=1.91%, sys=67.30%, ctx=54414, majf=0, minf=32787
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=99.9%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=94176,0,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
   READ: bw=3137MiB/s (3289MB/s), 3137MiB/s-3137MiB/s (3289MB/s-3289MB/s), io=184GiB (198GB), run=60040-60040msec

Disk stats (read/write):
  nvme0n1: ios=384613/0, merge=11752/0, ticks=15331918/0, in_queue=15331918, util=100.00%

 

Link to comment
Share on other sites

5 hours ago, mzb said:

What needs fixing to get rock5 to run -stable, or something less explosive than sid?

 

Sid / Kinetic user land is good enough for hardware that is fresh from the PCB assembly machinery. Stability is defined by components that have nothing to do with Debian (boot loader "bios", kernel and testing of those components). Even legacy kernel is pretty stable, real mainline Linux support with stability Armbian is satisfied is IMO at least a year away. This is how hardware is brought up nowadays ...  https://docs.armbian.com/User-Guide_FAQ/

 

If you need Bullseye / Jammy, you can always build an image for it https://github.com/armbian/build 
 

Another option is that you take responsibility dealing with users complains https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/ and stable userland builds can be enabled. Its a long term commitment.

Link to comment
Share on other sites

Please don't misunderstand my question: I'm not asking for you to "hurry up and deliver the finished product so I can use it".

I do know how this game works, and I have seen evidence over the years of the colossal effort you put into this project.

You've done a great job, as usual, producing an image *THAT WORKS* (so well) in such a short time ... I'm very grateful.

It's because of efforts from you, and others in the Armbian project, that I get to use Debian on devices that probably wouldn't be supported otherwise.

 

I'm simply asking what is preventing us/me/you/everyone from using Bullseye with the kernel you've used for the Sid image?

Is there something in particular that's in the debian-sid (or armbian-sid?) userland that is required?

 

There are a number of things I'd like to try out on this board (headless), and running Debian-stable makes that a lot easier (eg: PHP) without having to containerise everything.

Link to comment
Share on other sites

8 hours ago, mzb said:

what is preventing us/me/you/everyone from using Bullseye with the kernel you've used for the Sid image

Nobody prevents you from using any available kernel in any available userspace by simply building the combination of your choice via our build framework. However there is no guarantee that this will work/boot or even compile properly.

Quote

Not per se. Armbian is a build framework that allows users to create ready-to-use images with working kernels in variable userspace configurations for various single board computers (SBCs).

We do provide various prebuilt images for some boards, but mostly for users convenience.

https://docs.armbian.com/User-Guide_FAQ/

 

And it is our choice which prebuilt images we provide for convenience since building and providing those takes lots of computing and storage ressources ;)

 

Link to comment
Share on other sites

For anyone looking to have the official cooler+fan autostart at boot, place the following rule in /etc/udev/rules.d/99-pwm-fan.rules:

ACTION=="add", SUBSYSTEM=="pwm", ATTR{npwm}=="1", ATTR{export}="0", ATTR{pwm0/duty_cycle}="6000", ATTR{pwm0/period}="12000", ATTR{pwm0/polarity}="normal", ATTR{pwm0/enable}="1"

 

Link to comment
Share on other sites

First real experience with Armbian here.

Rock5B with eMMC

 

So far: the locales settings is really hell (I set the timezone somewhere in Europe and the system wants to set the language to local as well, even after 5 attempts I still some messages not in english and some LC_ALL error).

 

The display, I changed the sources.list for the mesa files like mentioned above:

#deb [signed-by=/usr/share/keyrings/oibaf.gpg] http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu/ jammy main
deb https://ppa.launchpadcontent.net/liujianfeng1994/panfork-mesa/ubuntu/ jammy main

In the /etc/apt/sources.list itself some changes to prevent armhf libraries from installing:

deb [arch=arm64] http://ports.ubuntu.com/ kinetic main restricted universe multiverse

 

And finally after removing most armhf libraries I get a system dependency on lybcrypt1:armhf.

root@rock-5b:~# apt remove libcrypt1:armhf
..
The following packages will be REMOVED:
  libc6:armhf libcrypt1:armhf libgcc-s1:armhf libidn2-0:armhf libunistring2:armhf
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  libcrypt1:armhf libc6:armhf (due to libcrypt1:armhf)
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 25.2 MB disk space will be freed.
E: Removing essential system-critical packages is not permitted. This might break the system.

 

Very annoying, but for a not-yet-supported-system I think it is promising.

I did get X working and the network (both eth0 and the RTL8192, the 8811 and 8821 unfortunately not yet due to dkms problems with the installed kernel).

 

It would be helpfull if I knew how to set the locales to english.

The armhf system-dependency looks like some  garbage that needs to be removed before the official release.

Link to comment
Share on other sites

6 hours ago, specs said:

So far: the locales settings is really hell (I set the timezone somewhere in Europe and the system wants to set the language to local as well, even after 5 attempts I still some messages not in english and some LC_ALL error).

Don't set locales on location. Choose "no" when asked at boot. And select the locales you want.
I'm from Belgium but want English. So I choose. No, 47, 7, 6, 1
Or change locales with "sudo armbian-config" 
 

 

7 hours ago, specs said:

And finally after removing most armhf libraries I get a system dependency on lybcrypt1:armhf.

No idea why you have armhf packages. Did you install box86 or something else that use armhf?

Link to comment
Share on other sites

@TaNGSoFT@gounthar Armbian has supported u-boot spi image since its initial support for rock5b. If you are using spi flash image from radxa wiki, you will failed to boot armbian because that is not a GPT image.  There are two ways to write the spi flash image from armbian to the spi nor flash:

1, Boot armbian from sdcard or emmc first, and use nand-sata-install to install the u-boot to spi flash.

2, You can download the u-boot deb file from the repo of armbian: https://mirrors.tuna.tsinghua.edu.cn/armbian/pool/main/l/linux-u-boot-rock-5b-legacy/linux-u-boot-legacy-rock-5b_22.08.6_arm64.deb. Extrat it using `dpkg -x linux-u-boot-legacy-rock-5b_22.08.6_arm64.deb`, and find the spi image file `rkspi_loader.img`, and write it to spi flash referring to radxa's wiki: https://wiki.radxa.com/Rock5/install/spi

Then use dd or ether to install armbian image to your NVME SSD.

Link to comment
Share on other sites

20 hours ago, NicoD said:
On 11/13/2022 at 3:58 PM, specs said:

So far: the locales settings is really hell (I set the timezone somewhere in Europe and the system wants to set the language to local as well, even after 5 attempts I still some messages not in english and some LC_ALL error).

Don't set locales on location. Choose "no" when asked at boot. And select the locales you want.
I'm from Belgium but want English. So I choose. No, 47, 7, 6, 1
Or change locales with "sudo armbian-config"

I found the culprit:

Some applicaton put LC_ALL and nl_NL.UTF* in the ~/.xsessionrc, after removing that file the language was restored to english.

The armbian-config  does the same thing as "dpkg-reconfigure locales", so it did not help me.

 

20 hours ago, NicoD said:

 

On 11/13/2022 at 3:58 PM, specs said:

And finally after removing most armhf libraries I get a system dependency on lybcrypt1:armhf.

No idea why you have armhf packages. Did you install box86 or something else that use armhf?

Exactly my opinion!

Why would Armbian ship armhf binaries with the Rock5 image?

And why would Armbian not exclude armhf repositories by default?

(Removing CONFIG_COMPAT from the kernel configuration might be a bridge too far for now, though I'd appreciate it.)

 

Probably some of the reasons this image is still "work in progress".

 

PS like others above I needed to install using a RPI 5V 3A power supply. After installation I could switch to a USB PD power supply.

Edited by specs
Link to comment
Share on other sites

Цитата

1, Boot armbian from sdcard or emmc first, and use nand-sata-install to install the u-boot to spi flash.

@amazingfateHello, I burned the armbian image to an SD disk and inserted it into rock5b, booted successfully, set up the video as above in the comments, docker and repositories and would like to transfer the root partition to the eMMC disk, but so far it does not work.
Usually nand-sata-install is enough, but after copying the root of the radlen on eMMC rock5b it does not load (blue LED is on)
I also tried Write U-Boot images to SPI

 

root@rock-5b:~# lsblk 
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
mtdblock0     31:0    0   16M  0 disk 
mmcblk1      179:0    0 14.5G  0 disk 
└─mmcblk1p1  179:1    0 14.3G  0 part 
mmcblk1boot0 179:32   0    4M  1 disk 
mmcblk1boot1 179:64   0    4M  1 disk 
mmcblk0      179:96   0 29.7G  0 disk 
├─mmcblk0p1  179:97   0  256M  0 part /boot
└─mmcblk0p2  179:98   0 29.2G  0 part /var/log.hdd
                                      /
zram0        254:0    0  7.7G  0 disk [SWAP]
zram1        254:1    0   50M  0 disk /var/log
root@rock-5b:~# mount | grep /boot
/dev/mmcblk0p1 on /boot type ext4 (rw,relatime,errors=remount-ro,commit=600)

 

 

At the same time, I have another rock5b board and the image from radxa and there were no problems with loading from eMMC, I copied it according to the instructions:

 

sudo xzcat rock-5b-ubuntu-focal-server-arm64-20221118-1434-gpt.img.xz | dd of=/dev/mmcblk1 bs=1M

 

 

It seems necessary to add rockchip-rk3588 to the FIRSTSECTOR=32768 selection

root@rock-5b:~# grep -A 1 -B 1 3588 /usr/sbin/nand-sata-install
case ${LINUXFAMILY} in
	rk3328|rk3399|rk35xx|rockchip64|rockpis|station*|media|rockchip-rk3588)
		FIRSTSECTOR=32768
root@rock-5b:~# fdisk -l /dev/mmcblk1
Disk /dev/mmcblk1: 14.45 GiB, 15518924800 bytes, 30310400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E59818E7-7EBB-4A74-B733-23CCC88A05FD

Device         Start      End  Sectors  Size Type
/dev/mmcblk1p1 32768 29982719 29949952 14.3G Linux filesystem

root@rock-5b:~# dd if=/usr/lib/linux-u-boot-legacy-rock-5b_22.11.0-trunk.0126_arm64/idbloader.img of=/dev/mmcblk1 seek=64
556+0 records in
556+0 records out
284672 bytes (285 kB, 278 KiB) copied, 0.0747147 s, 3.8 MB/s
root@rock-5b:~# dd if=/usr/lib/linux-u-boot-legacy-rock-5b_22.11.0-trunk.0126_arm64/u-boot.itb of=/dev/mmcblk1 seek=16384
2647+0 records in
2647+0 records out
1355264 bytes (1.4 MB, 1.3 MiB) copied, 0.23995 s, 5.6 MB/s

 

Edited by whitefox
Link to comment
Share on other sites

Quote
On 11/15/2022 at 1:17 AM, amazingfate said:

There are two ways to write the spi flash image from armbian to the spi nor flash:

Thanks a lot. Both way should work, I used 2. It worked but now failed to spi boot nvme again. no clue.

 

By the way, according to @Googulator , because of M2(pin 58/60 is definied by Radax as I2C, which should interfence with PD power pin) device, I have to  " Masked off the I2C pins (58-61) with some tape", to make card and PD power adaper working fine.

Edited by TaNGSoFT
Link to comment
Share on other sites

Great! Received 5b today and booting from nvme as per recipe above. All looks good, but am not as familiar with Armbian as I'd like. How do I get it to boot in console mode when I mostly don't need the desktop? The usual

 

sudo systemctl enable multi-user.target

 

Doesn't seem to apply.

Edited by lurk101
spelling
Link to comment
Share on other sites

@IgorHello, I always use the same power supply with PD and maybe after updating the linux-u-boot-rock-5b-legacy package or after connecting the nvme disk PD stopped working

 

Linux rock-5b 5.10.72-rockchip-rk3588 #trunk.0102 SMP Sat Nov 5 07:56:18 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

dpkg -l| grep -e rock -e rk3588
ii  armbian-bsp-cli-rock-5b                 22.11.0-trunk.0134                       arm64        Armbian board support files for rock-5b
ii  armbian-bsp-desktop-rock-5b             22.11.0-trunk                            arm64        Armbian Board Specific Packages for desktop users using arm64 rock-5b machines
ii  linux-dtb-legacy-rockchip-rk3588        22.11.0-trunk.0102                       arm64        Armbian Linux DTB, version 5.10.72-rockchip-rk3588 legacy
ii  linux-headers-legacy-rockchip-rk3588    22.11.0-trunk.0102                       arm64        Linux kernel headers for 5.10.72-rockchip-rk3588 on arm64 legacy
ii  linux-image-legacy-rockchip-rk3588      22.11.0-trunk.0102                       arm64        Linux kernel, armbian version 5.10.72-rockchip-rk3588 legacy
ii  linux-u-boot-rock-5b-legacy             22.11.0-trunk.0134                       arm64        Uboot loader 2017.09


tcpm_source_psy_4_0022-i2c-4-22
Adapter: rk3x-i2c
in0:           5.00 V  (min =  +5.00 V, max =  +5.00 V)
curr1:         0.00 A  (max =  +0.00 A)


    3.235464] pd := on
[    3.235474] pending state change SNK_WAIT_CAPABILITIES -> SNK_SOFT_RESET @ 310 ms [rev3 NONE_AMS]
[    3.545502] state change SNK_WAIT_CAPABILITIES -> SNK_SOFT_RESET [delayed 310 ms]
[    3.545509] AMS SOFT_RESET_AMS start
[    3.545513] state change SNK_SOFT_RESET -> AMS_START [rev3 SOFT_RESET_AMS]
[    3.545516] state change AMS_START -> SOFT_RESET_SEND [rev3 SOFT_RESET_AMS]
[    3.545520] PD TX, header: 0x8d
[    3.547664] sending PD message header: 8d
[    3.547672] sending PD message len: 0
[    3.549591] IRQ: 0x41, a: 0x00, b: 0x00, status0: 0xc1
[    3.549601] IRQ: BC_LVL, handler pending
[    3.551465] IRQ: 0x41, a: 0x00, b: 0x00, status0: 0x81
[    3.551469] IRQ: BC_LVL, handler pending
[    3.553269] IRQ: 0x41, a: 0x00, b: 0x00, status0: 0x81
[    3.553272] IRQ: BC_LVL, handler pending
[    3.555058] IRQ: 0x41, a: 0x10, b: 0x00, status0: 0x81
[    3.555062] IRQ: BC_LVL, handler pending
[    3.555064] IRQ: PD retry failed
[    3.555067] PD TX complete, status: 2
[    3.555077] state change SOFT_RESET_SEND -> HARD_RESET_SEND [rev3 SOFT_RESET_AMS]
[    3.555083] AMS SOFT_RESET_AMS finished
[    3.555085] AMS HARD_RESET start
[    3.555087] PD TX, type: 0x5
[    3.557966] IRQ: 0x41, a: 0x08, b: 0x00, status0: 0x81
[    3.557968] IRQ: BC_LVL, handler pending
[    3.557969] IRQ: PD hardreset sent
[    3.558731] PD TX complete, status: 0
[    3.558735] state change HARD_RESET_SEND -> HARD_RESET_START [rev3 HARD_RESET]
[    3.563289] pd := off

 

 

I tried to track changes in the package linux-u-boot-rock-5b-legacy

linux-u-boot-rock-5b-legacy:
  Installed: 22.11.0-trunk.0134
  Candidate: 22.11.0-trunk.0134
  Version table:
 *** 22.11.0-trunk.0134 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
        100 /var/lib/dpkg/status
     22.11.0-trunk.0133 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
     22.11.0-trunk.0132 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
     22.11.0-trunk.0131 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
     22.11.0-trunk.0130 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
     22.11.0-trunk.0129 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
     22.11.0-trunk.0128 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
     22.11.0-trunk.0127 500
        500 http://beta.armbian.com kinetic/main arm64 Packages
     22.11.0-trunk.0126 500
        500 http://beta.armbian.com kinetic/main arm64 Packages

 

But did not find any commits or build tags from 22.11.0-trunk.0134 https://github.com/armbian/build

Edited by whitefox
Link to comment
Share on other sites

22 hours ago, TaNGSoFT said:

like what I posted in radxa forum thread , nand-sata-install did the tricks. booting up stuck is due to PD issue, like tape i2c pin in m2 key, I taped specific m2 nvme pin to make directly nvme boot into Armbian.(without EMMC)

tangsoft@rock-5b:~$lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
mtdblock0    31:0    0   16M  0 disk 
zram0       254:0    0  7.7G  0 disk [SWAP]
zram1       254:1    0   50M  0 disk /var/log
nvme0n1     259:0    0  1.8T  0 disk 
├─nvme0n1p1 259:1    0  256M  0 part 
└─nvme0n1p2 259:2    0  1.8T  0 part /var/log.hdd
                                     /

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...