[BPI-R64] debian buster with new bootchain and linux 5.10

Hi,

i’ve created a new sdcard-image (currently for testing only) with new Bootchain (new Preloader/ATF/uboot-fip), GPT and linux 5.10 (including sdcard-fix)

i guess it’s not complete and maybe it is too big for emmc (have not tested), i used a fixed value of 8000MB (truncate breaks image, maybe my calculation does not work for gpt :thinking: )

https://drive.google.com/drive/folders/1wpBrJEstSPb90HE7R17NncQ9MsXHzWcx?usp=sharing

  • r64_buster_newatf_5.10.img.gz
  • r64_buster_newatf_5.10.img.gz.md5

login

  • user: root
  • password: bananapi

regards Frank

What login and password?

root/bananapi as in my other images :slight_smile:

btw. my truncate-calculation is at follows (don’t wanted to add this to first post):

myimage=myimage.img
size=$(fdisk -l $myimage | tail -1 | awk '{print $3}')
truncate --size=$[($size+1)*512] $myimage

so basicly use end-sector ($3) of last partition (tail -1), add 1 (sector counts from 0) and multiply with sector-size (512bytes). maybe i need to add 2 because GPT stores backup of main data in last sector, so image needs to be 1 sector larger than mapped to partitions

I know this is offtop but someone know how adjust internet and ssl acses to debian. Because I can get access to serial interface only.

openssh should be configured to ip 192.168.0.18 on port lan0, root-access enabled (should be disabled if other users are created)

change /etc/network/interfaces to different ip setting

https://wiki.fw-web.de/doku.php?id=en/bpi-r2/network/start

for bridging you need to install bridge-utils first and then add this to interfaces file (example for lan1+lan2)

auto lan1
iface lan1 inet manual
auto lan2
iface lan2 inet manual

auto br0
iface br0 inet static
    address 192.168.40.1
    netmask 255.255.255.0
    bridge_ports lan1 lan2
    bridge_fd 5
    bridge_stp no

and run (better from serial console, because ssh will be dropped)

service networking restart

you need to change dns (in image 192.168.0.10) in /etc/resolv.conf and default gateway (in interfaces file too) before you can install anything. so just change lan0-ip to one in your subnet and gateway in interfaces + nameserver in resolv.conf first

i see wan-port is configured as dhcp-client, but have not tested it, because i use fixed ip’s here

Hi Frank,

I’ve got both the R64 and R2 running with Ubuntu 20.04 and Kernel 5.4. Can you please point me in the right direction to get the kernel version to 5.8? I need both JIT eBPF and native support for Intel AX200 2723, which does not work with the backports. For the life of me I cannot find the BPI process to update the uBoot’s to 5.8. Mainline works with 5.8 for both arm7 and arm64 so it should be a fairly simple upgrade(I hope).

Thanks, Werner

As 5.8 is no lts you should use 5.10. You can get it from my repo and install the known way.

  • change build.conf to r64
  • build.sh importconfig
  • build.sh config # to add your driver
  • build.sh # compile and use install option to install to sdcard (install fit)
  • add entry fit=yourfilename to uenv.txt
1 Like

Thanks Frank. This is great news. Will update

Just wanted to shout out a huge thank you for the above Frank. Compiled right through with the second attempt. Full XDP and the Intel 200A X is working a treat on the R64. Compiling the R2 code now.

'[    7.173076] iwlwifi 0000:01:00.0: loaded firmware version 46.3cfab8da.0 cc-a0-46.ucode op_mode iwlmvm
[    7.344003] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    7.513981] iwlwifi 0000:01:00.0: base HW address: 34:13:e8:c7:9f:a7
[    7.589387] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
ISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"
Linux bpi-r64 5.10.25-bpi-r64-main #1 SMP PREEMPT Tue Apr 6 20:15:39 SAST 2021 aarch64 aarch64 aarch64 GNU/Linux
Plus KVM:
[root@bpi-r64 ~]# kvm-ok 
INFO: /dev/kvm exists
KVM acceleration can be used'

All support in 18.04 for what is needed. Will post some results of performance on XDP on the AX. Tonight it is all LXC with WRT to control that card.

Thanks a stack

Is the same sdcard-image planned for R2?

No atf is only for arm64