[BPI-R3] Debian Bullseye Image

Did you mean CONFIG_BPF_SYSCALL?

I would have to check if I have CONFIG_BPF_SYSCALL enabled… From an older .config I can see from here that I have that set to Y, so I assume on latest version it is the same.

So radek can use archlinuxarm, or extract the kernel from the package, which is a simple archive.

No, he needs bpf support in cgroups, so CONFIG_CGROUP_BPF but this depends on syscall.

Only copied previous from the error message without searching for exact config option

That I do not have set (yet).

It’s a pity that there is no full-fledged Linux image. My goal is to build a linux server on a bpi-r3 with a wifi router, NAS, print server, docker, etc. For users with less experience with kernel compilations, this is very complicated.

It is a dev-board…we did much work to get it as easy as possible :slight_smile:

Every user has different requirements and build all possible options into it…that makes testing more time consuming…so i added the common options and for specific things users have to add it.

I totally understand and admire your work! I will try to sort through all of this and create a Linux server according to my needs. Thanks for all the help.

I can only maintain a minimal image, then it is up to the user to install packages he/she would like to use.

I do build every stable version 6.x.y (rolling-stable) and present it as readily build package. But that package is not Debian.

Any user can make a request to add any kernel-config and, if reasonable, I will add it. That is why I was asking what exactly is needed here… You will then always have the newest stable version available, with the kernel config options you need.

This topic is not the correct one to make that request, it should be done here [BPI-R3] [BPi-R3-Mini] Imagebuilder R3 ArchlinuxArm, linux-rolling-stable

added BPF cgroup to my r3/r4 defconfigs in 6.6-main…when pipeline is finished you can use the build kernel or build a new image with my images-repo

Hello. I used a Debian image and burned it to an SD card. I set up Debian to my needs. Is there a way to copy it from SD card to eMMC? Is it possible to simply use dd to convert an image from SD card to eMMC?

You cannot copy directly as filogic has only 1 mmc controller so not both simultanous available. And sdcard should not be the active rootfs (so no changing data while getting image)…so use external system to get the image from the card.

But you can make an image from your sdcard and flash this after booting from nand/nor with emmc enabled.

Then you need to flash emmc bl2 to boot0 and set partition config so that boot0 is active. And flash emmc fip to the fip-partition.

https://wiki.fw-web.de/doku.php?id=en:bpi-r3:uboot#writing_emmc

Yes, I have linux on nand. I have the Debian image on a USB flash drive. I will boot into linux in nand. I mount the USB using mount. I use dd to copy Debian image from USB to eMMC. Is it enough like this?

flash full image to emmc and flash bl2 (emmc needs this in boot0) and replace fip

Can I do everything from Openwrt linux installed in nand?

you can flash image, fip and maybe bl2 from a linux-system like openwrt. bl2 maybe requires to set force_ro to 0 as boot-partitions normally set to readonly

but setting bootconf is imho only possible from uboot

Cool. I finally succeeded. Now I can’t detect SSD in M.2 KEY-M PCIe inerface. Do I need to install something?

Where do you need the nvme? Uboot/linux,debian/openwrt?

In debian it should work,you can install pciutils to use lspci,but nvme should be visible…try cat /proc/partitions

Debian Linux 6.6.36-bpi-r3-main on aarch64.

cat /proc/partitions
major minor  #blocks  name

  31        0      20480 mtdblock0
  31        1      10752 mtdblock1
  31        2        512 mtdblock2
  31        3        512 mtdblock3
  31        4        256 mtdblock4
  31        5        256 mtdblock5
 179        0    7634944 mmcblk0
 179        1       4079 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3       2048 mmcblk0p3
 179        4       2048 mmcblk0p4
 179        5     102400 mmcblk0p5
 179        6    6758400 mmcblk0p6
 179        8       4096 mmcblk0boot0
 179       16       4096 mmcblk0boot1

Mhm,my nvme is detected with same kernel version

Can I have an incompatible SSD?

Possibly,you can look in bootlog via dmesg,but this is unrelated to image so please create separate thread