frank-w / bpi-router-linux

Linux kernel 4.14+ for BPI-R2, 5.4+ for R64, 6.1+ for R2Pro and R3

Kernel 5.15 for BananaPi R2/R64

Requirements

On a x86/x64-host you need cross compile tools for the armhf architecture (bison and flex-package are needed for kernels >=4.16):

#for r2
sudo apt install gcc-arm-linux-gnueabihf libc6-armhf-cross u-boot-tools bc make ccache gcc libc6-dev libncurses5-dev libssl-dev bison flex
#for r64
sudo apt install gcc-aarch64-linux-gnu u-boot-tools bc make gcc ccache libc6-dev libncurses5-dev libssl-dev bison flex

If you build it directly on the BananaPi-R2/R64 (not recommended) you do not need the crosscompile-packages gcc-arm-linux-gnueabihf/gcc-aarch64-linux-gnu and libc6-armhf-cross

Issues

R2

R64

• pcie-slot CN8 does not detect gen2-cards due to hardware-issue (missing capacitors)
• some pcie-cards are not detected because of wrong memory-mapping of BAR0

Usage

if you want to build for R64, change "board" in build.conf first

  ./build.sh importconfig
  ./build.sh config #To configure manually with menuconfig
  ./build.sh

the option "pack" creates a tar.gz-file which contains folders "BPI-BOOT" (content of Boot-partition aka /boot) and BPI-ROOT (content for rootfs aka /). simply backup your existing /boot/bananapi/bpi-r2/linux/uImage and unpack the content of these 2 folders to your system

you can also install direct to sd-card which makes a backup of kernelfile, here you have to change your uEnv.txt if you use a new filename (by default it's containing kernelversion)

Usage with docker

The Dockerfile in utils/docker/ provides a build environment without installing the native compilers on the local system.

The local directory will be mounted into the docker container. All changes will also be present in the respository folder.

1. Build the docker container for building once:

   sh ./utils/docker/build_container.sh

   Note: if you get this error: "Got permission denied while trying to connect to the Docker daemon socket at ..." you have to configure non-root https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user

   sudo usermod -aG docker $USER
   newgrp docker

2. Start and connect to the running docker container:

   sh ./utils/docker/run.sh

3. Now you can use the commands from above:

   ./build.sh

4. Close the container with exit or CTRL-D.

5. Your build artifacts from the build script will be in the folder ./SD/

If you want to clean up you can remove all containers (and the associated docker images) with:

docker rmi bpi-cross-compile:1 --force

Branch details

Kernel upstream + BPI-R2 / R64

• 4.9-main
• 4.14-main
• 4.19-main | 4.19-r64-main
• 5.4-main
• 5.10-main
• 5.15-main
• 6.1-main

Kernel versions

Kernel features by version

Feature	4.4	4.9	4.14	4.19	5.4	5.10	5.15
PCIe	Y	Y	Y	Y	Y	Y	Y
SATA	Y	Y	Y	Y	Y	Y	Y
2 GMAC	Y	Y	Y	Y	N	N	N
DSA	N	Y	Y	Y	Y	Y	Y
USB	Y	Y	Y	Y	Y	Y	Y
VLAN (dsa)			Y	N	Y	Y	Y
VLAN-aware Bridge			N	Y	Y	Y	Y
HW NAT (R2)		Y	Y			N	Y
HW QOS (R2)		Y	?			N	N
Crypto	Y	Y	Y		Y
WIFI (internal)		Y	Y	Y	Y	Y	Y
BT	N	N	Y	Y	Y	Y	Y
VIDEO (R2 only)	Y	N	Y	Y	Y	Y	Y
ACPI (R2)	?	N	Y	Y	Y
IR (R2)	?	N	N	N	Y	Y	?
WIFI (R64)	N	N	N	N	Y	Y	Y
BT (R64)	N	N	N	N	Y	Y	Y
Other options	--	--	--	--	--	--	--
OpenVPN	?	Y	Y	Y	Y	Y	Y
iptables (R2)	?	Y	Y	Y	Y	Y	Y
nftables (R2)	?	N	N	Y	Y	Y	Y
LXC / Docker (R2)	?	?	Y	Y	Y	Y	Y

Symbols:

Symbol	Meaning
?	Unsure
()	Testing

(Testing in separate branch wlan/hdmi/hwnat/hwqos)

• WIFI/BT on R2 needs WMT-tools called before
• HW-NAT only works between LAN and WAN (bridge unclear, wifi not supported)
• HW-QoS is merged into 4.14-main, but we do not know how to test it
• ACPI-feature means System is powered off, not only halted (power-consumption ~0.2W, no reboot on reset), reboot-problem on R2 with soldered power-switch (see #35). Power-off is also initiated by pressing the power-switch, on R64 not currently not available
• VIDEO is hdmi-output (X-server/framebuffer-console)...here some resolutions are not supported by vendor-driver. R64 does not have HDMI

kernel 4.4 / uboot 2014-04: https://github.com/frank-w/BPI-R2-4.4 mainline-uboot: https://github.com/frank-w/u-boot

Links

• BPI-R2: http://www.banana-pi.org/r2.html | BPI-R64: http://www.banana-pi.org/r64.html
• Kernel: https://www.kernel.org/ , Stable-RC: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
• linux-mediatek: https://patchwork.kernel.org/project/linux-mediatek/list/, Threaded: http://lists.infradead.org/pipermail/linux-mediatek/
• kernelci: https://kernelci.org/boot/mt7623n-bananapi-bpi-r2/
• Forum: http://forum.banana-pi.org/c/Banana-Pi-BPI-R2
• Wiki: http://www.fw-web.de/dokuwiki/doku.php?id=en/bpi-r2/start http://www.fw-web.de/dokuwiki/doku.php?id=en/bpi-r64/start

License

GPL-2.0

Free Software, Hell Yeah!

bpi-router-linux's Issues

About the mainline linux kernel bluetooth and WiFi support for MediaTek

I am really sorry to disturb with a bit of off topic issue. But I want to know how compatible is the mainline mediatek bluetooth driver a.k.a BTIF and btmtkuart/btmtksdio with the Banana Pi R2? is it usable at all? And what about the mainline WiFi support? The MT6625L is the RF frontend of the WiFi and bluetooth features right? Then there is an internal IP block for the BT/WiFi/ and whatnot on the board. How to get them working with mainline? Can you please point me to the right direction?

Debian package > 5.4 have no kernel with dtb

Hello,

While I was tring to upgrade my kernel from 5.4 to 5.10 I detected that in the debian package there are no kernel image with dtb. So in /boot/bananapi/bpi-r2/linux/ I only have this file uImage_nodt-5.10.90-bpi-r2-main and the dtb directory.

So is it normal that we don't have the image with dtb ? And if yes how can I start with this image from uboot ?

Is It possibile install Wireguard?

As the title suggests, is it possible to run Wireguard VPN on BananaPi R2?
I tried to install it from the unstable debian repositories, it goes, but once you start the quick start it gives me the following error:

ip link add dev wg0 type wireguard RNETLINK answers: Operation not supported.

I tried to follow the following Site and to install the missing linux header of the kernel version 4.19, but I cannot proceed because the linux header is missing in the /lib/module folder.

Can you help me or tell how i van obtein the linux header andò the wireguard module?

Thanks a lot!

Update to cryptodev 1.10

Hello,

I also discovered that cryptodev bring some instability when I use sftp (so I disabled it to fix this issue).

Cryptodev 1.10 is released so, maybe upgrading to cryptodev 1.10 might fix the issue.

mtk_crypto crashes

FYI there is some issues with something. Most time it was reproducible during something goes to swap, during high load on SATA and network (likely IRQ related race).

Just in case you'll see new paches about mtk_crypto, put links here.

[ 1895.593658] Unable to handle kernel paging request at virtual address 37b868a6
[ 1895.600882] pgd = dce90000
[ 1895.603645] [37b868a6] *pgd=00000000
[ 1895.607231] Internal error: Oops: 5 [#1] SMP ARM

[ 1895.660832] PC is at mtk_sha_append_sg.part.1+0x44/0xfc [mtk_crypto]
[ 1895.667149] LR is at 0xffffffe0
[ 1895.670270] pc : [<bf1ee9f0>]    lr : [<ffffffe0>]    psr: a0070113
[ 1895.676492] sp : dbb23e28  ip : 00000000  fp : dbb23e4c
[ 1895.681680] r10: 00000004  r9 : ffffe000  r8 : c0e9f340
[ 1895.686888] r7 : dcb1e390  r6 : 00000000  r5 : 00001000  r4 : da856e40
[ 1895.693375] r3 : fca378e3  r2 : fca378e3  r1 : 37b8689e  r0 : da856e40
[ 1895.699859] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[ 1895.706948] Control: 10c5387d  Table: 9ce9006a  DAC: 00000051

[ 1895.844795] [<bf1ee9f0>] (mtk_sha_append_sg.part.1 [mtk_crypto]) from [<bf1eead4>] (mtk_sha_update_slow+0x2c/0x108 [mtk_crypto])
[ 1895.856354] [<bf1eead4>] (mtk_sha_update_slow [mtk_crypto]) from [<bf1eecec>] (mtk_sha_update_start+0x13c/0x380 [mtk_crypto])
[ 1895.867612] [<bf1eecec>] (mtk_sha_update_start [mtk_crypto]) from [<bf1ef5c4>] (mtk_sha_done_task+0x124/0x188 [mtk_crypto])
[ 1895.878719] [<bf1ef5c4>] (mtk_sha_done_task [mtk_crypto]) from [<c0142828>] (tasklet_action+0x70/0x104)
[ 1895.888096] [<c0142828>] (tasklet_action) from [<c010161c>] (__do_softirq+0x13c/0x36c)
[ 1895.896010] [<c010161c>] (__do_softirq) from [<c01421f8>] (irq_exit+0xac/0x154)
[ 1895.903321] [<c01421f8>] (irq_exit) from [<c01949d0>] (__handle_domain_irq+0x70/0xc4)
[ 1895.911150] [<c01949d0>] (__handle_domain_irq) from [<c0101498>] (gic_handle_irq+0x5c/0xa0)
[ 1895.919490] [<c0101498>] (gic_handle_irq) from [<c09fcfd4>] (__irq_usr+0x54/0x80)

Banana Pi R2 Armbian

Hi

I'm currently looking into options for adding official Banana Pi R2 support to Armbian (armbian/build#2147) using your 5.4-main as base. Can you please explain which patches are needed for R2 from your 5.4-main branch vs mainline 5.4

Also, would you be interested in testing and supporting R2 on Armbian to some extent

Martin

problem with poweroff-commit

Hi Frank,

if the Powerbutton bypassed ( bridged ), the system reboot´s the whole time :-(.

Best regards,
René

bpi-r3 eth1 dropping packets

Hi,

I'm running 6.2 kernel so I can use VLAN on the eth1 Fiber SFP and I'm observing a lot of packets getting dropped. Only the received ones. The SFP and Fiber were moved from another router that it was working just fine. So I don't think it's the tranceiver or fiber cable.

Has anyone else seen similar behavior on the bpi-r3?

# ifconfig eth1
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::9065:f3ff:feec:b019  prefixlen 64  scopeid 0x20<link>
        ether 92:65:f3:ec:b0:19  txqueuelen 1000  (Ethernet)
        RX packets 11132122  bytes 10885212987 (10.1 GiB)
        RX errors 1  **dropped 875168**  overruns 0  frame 13784        <<<<<<< 875168 dropped packets
        TX packets 9577892  bytes 11333127550 (10.5 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 123  

# ethtool -S  eth1
NIC statistics:
     tx_bytes: 12214740723
     tx_packets: 10248274
     tx_skip: 0
     tx_collisions: 0
     rx_bytes: 10922473509
     rx_packets: 11473622
     rx_overflow: 0
     rx_fcs_errors: 0
     rx_short_errors: 0
     rx_long_errors: 15184
     rx_checksum_errors: 1
     rx_flow_control_packets: 0
     rx_xdp_redirect: 0
     rx_xdp_pass: 0
     rx_xdp_drop: 0
     rx_xdp_tx: 0
     rx_xdp_tx_errors: 0
     tx_xdp_xmit: 0
     tx_xdp_xmit_errors: 0
     rx_pp_alloc_fast: 23145710
     rx_pp_alloc_slow: 17668
     rx_pp_alloc_slow_ho: 0
     rx_pp_alloc_empty: 17668
     rx_pp_alloc_refill: 388807
     rx_pp_alloc_waive: 0
     rx_pp_recycle_cached: 0
     rx_pp_recycle_cache_full: 0
     rx_pp_recycle_ring: 22421931
     rx_pp_recycle_ring_full: 219858
     rx_pp_recycle_released_ref: 909866

Thanks!

Uboot

IS there a newer 2018.03 Uboot available for MT7623?

is it possible to resize the filesystem when using SD card?

I'm trying to make use of all available space however when running parted it says the SD card is 8GB and there's no additional space to allocate.

Do I need to re-create the partition table?

cryptodev

Why is cryptodev store outside of the default modules kernel path?

modules/4.14.26-main-02712-g9509a8f0d3c0/kernel/sound/
modules/4.14.26-main-02712-g9509a8f0d3c0/kernel/sound/core/
modules/4.14.26-main-02712-g9509a8f0d3c0/kernel/sound/core/snd-seq-device.ko
modules/4.14.26-main-02712-g9509a8f0d3c0/kernel/sound/core/seq/
modules/4.14.26-main-02712-g9509a8f0d3c0/kernel/sound/core/seq/snd-seq.ko
modules/4.14.26-main-02712-g9509a8f0d3c0/kernel/sound/drivers/
modules/4.14.26-main-02712-g9509a8f0d3c0/kernel/sound/drivers/snd-dummy.ko
modules/4.14.26/
modules/4.14.26/kernel/
modules/4.14.26/kernel/extras/
modules/4.14.26/kernel/extras/cryptodev.ko

It lead to confusion.

# ll /lib/modules/
total 20
drwxr-xr-x 3 1000 1000 4096 Mar  8 23:12 4.14.26
drwxr-xr-x 3 root root 4096 Mar  7 04:10 4.14.26-main-02704-g192e093549dc
drwxr-xr-x 3 1000 1000 4096 Mar  8 23:12 4.14.26-main-02712-g9509a8f0d3c0

[internal wifi] Kernel-OOPS if config missing

kernel-oops if /system/etc/firmware/WMT_SOC.cfg not existing

it happens while calling “wmt_plat_deinit();” in drivers/misc/mediatek/connectivity/common/conn_soc/mt7623/wmt_plat_alps.c

[ +0.000006] DEBUG: Passed wmt_plat_deinit 362 now calling wake lock destroy -1057754704
[ +0.000004] DEBUG: Passed wmt_plat_deinit 364 now wmtWakeLock:-1057754704
[ +0.000004] DEBUG: Passed wmt_plat_deinit 365 now wmtWakeLock->ws: -1057754704
[ +0.000013] Unable to handle kernel NULL pointer dereference at virtual address 00000000

as you see both adresses are the same:

created the messages like this way:

INT32 wmt_plat_deinit(VOID)
{
    INT32 iret = 0;
    /* 2. unreg to cmb_stub */
    iret = mtk_wcn_cmb_stub_unreg();
    printk(KERN_ALERT "DEBUG: Passed %s %d now calling wmt wakelock deinit\n",__FUNCTION__,__LINE__);
    /*3. wmt wakelock deinit */
#ifdef CFG_WMT_WAKELOCK_SUPPORT
#ifdef CONFIG_PM_WAKELOCKS
    printk(KERN_ALERT "DEBUG: Passed %s %d now calling wakeup_source_trash\n",__FUNCTION__,__LINE__);
    wakeup_source_trash(&wmtWakeLock);
#else
    printk(KERN_ALERT "DEBUG: Passed %s %d now calling wake lock destroy %d\n",__FUNCTION__,__LINE__,(int)&wmtWakeLock);
    //destroy in wakelock.h calls wakeup_source_trash (include/linux/pm_wakeup.h) with &lock->ws
    printk(KERN_ALERT "DEBUG: Passed %s %d now wmtWakeLock:%d\n",__FUNCTION__,__LINE__,(int)&wmtWakeLock);
    printk(KERN_ALERT "DEBUG: Passed %s %d now wmtWakeLock->ws: %d\n",__FUNCTION__,__LINE__,(int)&(wmtWakeLock.ws));
    wake_lock_destroy(&wmtWakeLock);
...

wmtWakeLock and its member ws is a struct and not dynamic allocated as i’ve found out, so i assume that there have no memory freed manually.

(drivers/misc/mediatek/connectivity/common/combo seems not be used, deleted from git after try to build without it)

same bug in 4.4.70, currently no idea how to fix that

Wrong DTS reference

https://github.com/frank-w/BPI-R2-4.14/blob/ee7516478dafaa8ccf7f6e763d88a8e03758af37/drivers/crypto/mediatek/mtk-platform.c#L581

https://github.com/frank-w/BPI-R2-4.14/blob/4.14-main/arch/arm/boot/dts/mt7623.dtsi#L1222

To adapt to armbian

I ported Armbian for BPI R64 so that kernels built in your repository are compatible to install to it.

Now the kernel used is from latest r64 build : https://github.com/muravjov/armbian-build/blob/banana-pi-r64/lib/distributions.sh#L202

I tested it, it works well, see http://forum.banana-pi.org/t/bpi-r64-armbian/10741.

But it turns out that armbian uses kernel features zram + swap (to avoid writing constantly logs to SD card).

It would be nice if you append to r64 config https://github.com/frank-w/BPI-R2-4.14/blob/5.4-main/arch/arm64/configs/mt7622_bpi-r64_defconfig those changes (with make menuconfig):

$ diff -Naur '/home/ilya/opt/bpi-r64/tmp/.config.5.4.17-wg-embedded' .config | grep -v '#'
--- /home/ilya/opt/bpi-r64/tmp/.config.5.4.17-wg-embedded       2020-02-29 20:55:30.000000000 +0300
+++ .config     2020-03-01 18:15:26.031627017 +0300
@@ -27,7 +27,7 @@
 CONFIG_BUILD_SALT=""
 CONFIG_DEFAULT_HOSTNAME="(mt7622)"
+CONFIG_SWAP=y
 CONFIG_SYSVIPC=y
 CONFIG_SYSVIPC_SYSCTL=y
 CONFIG_POSIX_MQUEUE=y
@@ -128,6 +128,8 @@
 CONFIG_CGROUPS=y
 CONFIG_PAGE_COUNTER=y
 CONFIG_MEMCG=y
+CONFIG_MEMCG_SWAP=y
+CONFIG_MEMCG_SWAP_ENABLED=y
 CONFIG_MEMCG_KMEM=y
 CONFIG_BLK_CGROUP=y
 CONFIG_CGROUP_WRITEBACK=y
@@ -412,6 +414,7 @@
 CONFIG_SUSPEND=y
 CONFIG_SUSPEND_FREEZER=y
 CONFIG_PM_SLEEP=y
 CONFIG_PM_SLEEP_SMP=y
@@ -667,10 +670,15 @@
+CONFIG_FRONTSWAP=y
+CONFIG_ZSWAP=y
+CONFIG_ZPOOL=y
+CONFIG_ZSMALLOC=y
 CONFIG_GENERIC_EARLY_IOREMAP=y
@@ -1318,6 +1326,7 @@
 
@@ -1390,7 +1399,23 @@
 CONFIG_OF_RESERVED_MEM=y
+CONFIG_BLK_DEV=y
+CONFIG_ZRAM=m
+CONFIG_ZRAM_WRITEBACK=y
 
@@ -1509,6 +1534,7 @@
 CONFIG_BLK_DEV_SD=y
@@ -4051,6 +4077,7 @@
 
 CONFIG_NVMEM=y
 CONFIG_NVMEM_SYSFS=y
@@ -4426,10 +4453,10 @@
-CONFIG_CRYPTO_DEFLATE=m
+CONFIG_CRYPTO_DEFLATE=y
+CONFIG_CRYPTO_LZO=y
+CONFIG_CRYPTO_LZ4=y
 
@@ -4510,8 +4537,12 @@
 CONFIG_AUDIT_ARCH_COMPAT_GENERIC=y
 CONFIG_AUDIT_COMPAT_GENERIC=y
-CONFIG_ZLIB_INFLATE=m
-CONFIG_ZLIB_DEFLATE=m
+CONFIG_ZLIB_INFLATE=y
+CONFIG_ZLIB_DEFLATE=y
+CONFIG_LZO_COMPRESS=y
+CONFIG_LZO_DECOMPRESS=y
+CONFIG_LZ4_COMPRESS=y
+CONFIG_LZ4_DECOMPRESS=y
 CONFIG_GENERIC_ALLOCATOR=y
 CONFIG_ASSOCIATIVE_ARRAY=y

[4.19-gmac] going back to mdio_device

current gmac uses switch as platform_device because it is separated from mdio-node. this is no longer supported and should be changed. current linking is with a property

https://github.com/frank-w/BPI-R2-4.14/blob/bb1e7a58082f7e9cf620ca9a59a9e731c73cf340/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts#L238

linked to

https://github.com/frank-w/BPI-R2-4.14/blob/bb1e7a58082f7e9cf620ca9a59a9e731c73cf340/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts#L224

https://github.com/frank-w/BPI-R2-4.14/blob/bb1e7a58082f7e9cf620ca9a59a9e731c73cf340/drivers/net/dsa/mt7530.c#L1399

maybe we can use

struct device_node *of_get_parent(const struct device_node *node)

https://elixir.bootlin.com/linux/v4.19.3/source/drivers/of/base.c#L635

from switch-node to reference mdio-node if switch is packed back into it

	mdio: mdio-bus {
		#address-cells = <1>;
		#size-cells = <0>;

		switch@0 {
		//.....
		}

then we can change change
mt7530_probe(struct platform_device *mdiodev) to
mt7530_probe(struct mdio_device *mdiodev) and
mt7530_remove(struct platform_device *mdiodev) to
mt7530_remove(struct mdio_device *mdiodev)

4.19 PCIe SATA

PCIe Y
SATA Y

uname -r

4.19.7-bpi-r2+

lspci

00:00.0 PCI bridge: MEDIATEK Corp. Device 0801 (rev 01)
00:01.0 PCI bridge: MEDIATEK Corp. Device 0801 (rev 01)
01:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
02:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 02)

Local FS corruption in 5.4

Hi guys,
anyone having FS issues when running 5.4.142 for more than a few days? was fine in 4.14.72
both SD card and SATA seems affected.

Errors like that:
Sep 17 04:40:04 slackware kernel: [492735.703868] EXT4-fs error (device sda1): htree_dirblock_to_tree:1025: inode #505099: block 2600519: comm updatedb: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=2620482273, rec_len=51393, name_len=230, size=4096

Compiling with Docker

Today I wanted to compile the Kernel on a fresh Archlinux and realized that installing all those cross-compiler packages may take a time. So I hacked a small Dockerfile for me, which I'll share with you:

Dockerfile:

FROM ubuntu:xenial

RUN useradd -ms /bin/bash builder

RUN apt-get update               \
 && apt-get -y -q upgrade        \
 && apt-get -y -q install        \
    bc                           \
    binutils-arm-linux-gnueabihf \
    bison                        \
    build-essential              \
    ccache                       \
    flex                         \
    gcc-arm-linux-gnueabihf      \
    gccgo-4.7-arm-linux-gnueabi  \
    gcc-aarch64-linux-gnu        \
    git                          \
    libc6-armhf-cross            \
    libncurses-dev               \
    libssl-dev                   \
    make                         \
    u-boot-tools                 \
    wget                         \
    xz-utils                     \
 && apt-get clean

USER builder
WORKDIR /srv/

Create the local image with: docker build . --tag bpi-compile:1

Run the compile environment (adjust the path before the colon):
docker run -it -v $(pwd)/SD:/SD -v $(pwd)/BPI-R2-4.14:/srv bpi-compile:1 /bin/bash

Is it worth to create a pull request for this?

Initramfs and bootargs support?

Hello,

I'm currently trying to setup an alpine with a custom initramfs and with mainline u-boot.

So far I got u-boot to boot the kernel. The kernel however seems to not get any boot args, like root= and also the initramfs is not entered at all.

I've tried the 5.10-main and 5.15-main branches. Both running into a Kernel Panic, as no root is set/can be mounted.

Is this something hardcoded in the kernel to prevent problems caused by (faulty) bootloaders (I read, that sometime this can be a problem) or is it that u-boot, not passing the args properly the the kernel and not correctly reading the initramfs?

I built the kernel with the default configs and even tried to embed the initramfs, all without success. The default config seems to be correctly configured to support this however.

Network and filesystem unstable

Since the version ~4.14.81-82 I have some some unstability.

About the network I get at the boot some errors like that:

Apr 15 21:01:38 the_hostname kernel: [   45.246392] Hardware name: Mediatek Cortex-A7 (Device Tree)
Apr 15 21:01:38 the_hostname kernel: [   45.246436] [<c01132d0>] (unwind_backtrace) from [<c010d5e0>] (show_stack+0x20/0x24)
Apr 15 21:01:38 the_hostname kernel: [   45.246453] [<c010d5e0>] (show_stack) from [<c0aa8544>] (dump_stack+0x90/0xa4)
Apr 15 21:01:38 the_hostname kernel: [   45.246465] [<c0aa8544>] (dump_stack) from [<c023c46c>] (warn_alloc+0xc8/0x17c)
Apr 15 21:01:38 the_hostname kernel: [   45.246476] [<c023c46c>] (warn_alloc) from [<c023d7bc>] (__alloc_pages_nodemask+0x11e8/0x122c)
Apr 15 21:01:38 the_hostname kernel: [   45.246485] [<c023d7bc>] (__alloc_pages_nodemask) from [<c023d9ec>] (page_frag_alloc+0x14c/0x160)
Apr 15 21:01:38 the_hostname kernel: [   45.246497] [<c023d9ec>] (page_frag_alloc) from [<c089240c>] (netdev_alloc_frag+0x40/0x48)
Apr 15 21:01:38 the_hostname kernel: [   45.246511] [<c089240c>] (netdev_alloc_frag) from [<c0717ab0>] (mtk_rx_alloc+0xac/0x34c)
Apr 15 21:01:38 the_hostname kernel: [   45.246522] [<c0717ab0>] (mtk_rx_alloc) from [<c07180f4>] (mtk_open+0x3a4/0x5f8)
Apr 15 21:01:38 the_hostname kernel: [   45.246532] [<c07180f4>] (mtk_open) from [<c08aefe4>] (__dev_open+0xb8/0x11c)
Apr 15 21:01:38 the_hostname kernel: [   45.246543] [<c08aefe4>] (__dev_open) from [<c08af3a8>] (__dev_change_flags+0x184/0x1ac)
Apr 15 21:01:38 the_hostname kernel: [   45.246553] [<c08af3a8>] (__dev_change_flags) from [<c08af3f8>] (dev_change_flags+0x28/0x58)
Apr 15 21:01:38 the_hostname kernel: [   45.246564] [<c08af3f8>] (dev_change_flags) from [<c08c2658>] (do_setlink+0x32c/0x968)
Apr 15 21:01:38 the_hostname kernel: [   45.246575] [<c08c2658>] (do_setlink) from [<c08c4898>] (rtnl_newlink+0x4d0/0x7fc)
Apr 15 21:01:38 the_hostname kernel: [   45.246585] [<c08c4898>] (rtnl_newlink) from [<c08c1ae8>] (rtnetlink_rcv_msg+0x218/0x280)
Apr 15 21:01:38 the_hostname kernel: [   45.246595] [<c08c1ae8>] (rtnetlink_rcv_msg) from [<c08eaef8>] (netlink_rcv_skb+0xd0/0xf0)
Apr 15 21:01:38 the_hostname kernel: [   45.246606] [<c08eaef8>] (netlink_rcv_skb) from [<c08c18cc>] (rtnetlink_rcv+0x20/0x24)
Apr 15 21:01:38 the_hostname kernel: [   45.246615] [<c08c18cc>] (rtnetlink_rcv) from [<c08ea648>] (netlink_unicast+0x190/0x258)
Apr 15 21:01:38 the_hostname kernel: [   45.246624] [<c08ea648>] (netlink_unicast) from [<c08eaa68>] (netlink_sendmsg+0x280/0x350)
Apr 15 21:01:38 the_hostname kernel: [   45.246634] [<c08eaa68>] (netlink_sendmsg) from [<c088a024>] (sock_sendmsg+0x24/0x34)
Apr 15 21:01:38 the_hostname kernel: [   45.246642] [<c088a024>] (sock_sendmsg) from [<c088a7e4>] (___sys_sendmsg+0x1ec/0x214)
Apr 15 21:01:38 the_hostname kernel: [   45.246651] [<c088a7e4>] (___sys_sendmsg) from [<c088b674>] (__sys_sendmsg+0x50/0x7c)
Apr 15 21:01:38 the_hostname kernel: [   45.246660] [<c088b674>] (__sys_sendmsg) from [<c088b6b8>] (SyS_sendmsg+0x18/0x1c)
Apr 15 21:01:38 the_hostname kernel: [   45.246671] [<c088b6b8>] (SyS_sendmsg) from [<c0108cc0>] (ret_fast_syscall+0x0/0x54)

And about the (ext4) filesystem (with the sata port) for some file when I try to read it I get this:

ls: impossible d'ouvrir le répertoire '/usr/local/lib/python3.5/dist-packages/pip': Ne peut allouer de la mémoire
d????????? ? ?    ?        ?            ? pip

And in the kernel log I get this:

Apr 15 21:08:03 the_hostname kernel: [  399.051628] grow_buffers: requested out-of-range block 16879718369374422450 for device sda1

With the all new kernel version (4.14 and 4.19) I have theses error. The only version wich run cleanly is <= 4.14.67. Since the version 4.14.74 I detected some issue about the network. And between the version 4.14.81 and the version 4.14.82 I get the filesystem problem.

I think that it's due to a service which generate this unstability because with a clean rootfs I don't get theses problem.

I give you my boot sequence (of a unstable kernel version if it could help you):

[    5.181665] mtk-msdc 11230000.mmc: GPIO lookup for consumer wp
[    5.187468] mtk-msdc 11230000.mmc: using device tree for GPIO lookup
[    5.193812] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@11230000[0]'
[    5.202561] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@11230000[0]'
[    5.211217] mtk-msdc 11230000.mmc: using lookup tables for GPIO lookup
[    5.217700] mtk-msdc 11230000.mmc: lookup for GPIO wp failed
[    5.267609] mmc0: host does not support reading read-only switch, assuming write-enable
[    5.277724] mmc0: new high speed SDHC card at address 0001
[    5.284266] of_get_named_gpiod_flags: parsed 'gpios' property of node '/leds/green[0]' - status (0)
[    5.293314] no flags found for gpios
[    5.296975] of_get_named_gpiod_flags: parsed 'gpios' property of node '/leds/blue[0]' - status (0)
[    5.305909] no flags found for gpios
[    5.309554] of_get_named_gpiod_flags: parsed 'gpios' property of node '/leds/red[0]' - status (0)
[    5.318396] no flags found for gpios
[    5.322373] mmcblk0: mmc0:0001 00000 29.3 GiB 
[    5.328881]  mmcblk0: p1 p2 p3
[    5.332415] hidraw: raw HID events driver (C) Jiri Kosina
[    5.337918] usbcore: registered new interface driver usbhid
[    5.343479] usbhid: USB HID core driver
[    5.348406] mtk-iommu-v1 10205000.mmsys_iommu: bound 14010000.larb (ops mtk_smi_larb_component_ops)
[    5.357426] mtk-iommu-v1 10205000.mmsys_iommu: bound 16010000.larb (ops mtk_smi_larb_component_ops)
[    5.366431] mtk-iommu-v1 10205000.mmsys_iommu: bound 15001000.larb (ops mtk_smi_larb_component_ops)
[    5.376452] NET: Registered protocol family 17
[    5.381428] NET: Registered protocol family 41
[    5.385959] 8021q: 802.1Q VLAN Support v1.8
[    5.386088] mmc1: new high speed MMC card at address 0001
[    5.386638] mmcblk1: mmc1:0001 8WPD3R 7.28 GiB 
[    5.386987] mmcblk1boot0: mmc1:0001 8WPD3R partition 1 4.00 MiB
[    5.387309] mmcblk1boot1: mmc1:0001 8WPD3R partition 2 4.00 MiB
[    5.387631] mmcblk1rpmb: mmc1:0001 8WPD3R partition 3 512 KiB
[    5.417890] ThumbEE CPU extension supported.
[    5.422157] Registering SWP/SWPB emulation handler
[    5.541905] mtk-pcie 1a140000.pcie-controller: Port0 link down
[    5.578190] mtk-pcie 1a140000.pcie-controller: PCI host bridge to bus 0000:00
[    5.585314] pci_bus 0000:00: root bus resource [io  0x0000-0xffff] (bus address [0x1a160000-0x1a16ffff])
[    5.594747] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
[    5.601591] pci_bus 0000:00: root bus resource [bus 00-ff]
[    5.607071] pci 0000:00:01.0: [14c3:0801] type 01 class 0x060400
[    5.613079] pci 0000:00:01.0: reg 0x14: [mem 0x00000000-0x0000ffff]
[    5.619359] pci 0000:00:01.0: supports D1
[    5.623357] pci 0000:00:01.0: PME# supported from D0 D1 D3hot
[    5.629282] PCI: bus0: Fast back to back transfers disabled
[    5.634840] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    5.642938] pci 0000:01:00.0: [1b21:0611] type 00 class 0x010185
[    5.648930] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[    5.655950] pci 0000:01:00.0: reg 0x10: [io  size 0x0008]
[    5.661334] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[    5.668335] pci 0000:01:00.0: reg 0x14: [io  size 0x0004]
[    5.673716] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[    5.680728] pci 0000:01:00.0: reg 0x18: [io  size 0x0008]
[    5.686098] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[    5.693114] pci 0000:01:00.0: reg 0x1c: [io  size 0x0004]
[    5.698483] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[    5.705496] pci 0000:01:00.0: reg 0x20: [io  size 0x0010]
[    5.710880] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x000001ff]
[    5.717111] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    5.750754] PCI: bus1: Fast back to back transfers disabled
[    5.756294] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    5.762913] pci 0000:00:01.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
[    5.769658] pci 0000:00:01.0: BAR 9: assigned [mem 0x60100000-0x601fffff pref]
[    5.776851] pci 0000:00:01.0: BAR 1: assigned [mem 0x60200000-0x6020ffff]
[    5.783611] pci 0000:00:01.0: BAR 7: assigned [io  0x1000-0x1fff]
[    5.789670] pci 0000:01:00.0: BAR 6: assigned [mem 0x60100000-0x6010ffff pref]
[    5.796861] pci 0000:01:00.0: BAR 5: assigned [mem 0x60000000-0x600001ff]
[    5.803622] pci 0000:01:00.0: BAR 4: assigned [io  0x1000-0x100f]
[    5.809678] pci 0000:01:00.0: BAR 0: assigned [io  0x1010-0x1017]
[    5.815746] pci 0000:01:00.0: BAR 2: assigned [io  0x1018-0x101f]
[    5.821817] pci 0000:01:00.0: BAR 1: assigned [io  0x1020-0x1023]
[    5.827873] pci 0000:01:00.0: BAR 3: assigned [io  0x1024-0x1027]
[    5.833943] pci 0000:00:01.0: PCI bridge to [bus 01]
[    5.838875] pci 0000:00:01.0:   bridge window [io  0x1000-0x1fff]
[    5.844944] pci 0000:00:01.0:   bridge window [mem 0x60000000-0x600fffff]
[    5.851700] pci 0000:00:01.0:   bridge window [mem 0x60100000-0x601fffff pref]
[    5.859028] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[    5.865272] pcieport 0000:00:01.0: Signaling PME with IRQ 221
[    5.871345] ahci 0000:01:00.0: version 3.0
[    5.875427] ahci 0000:01:00.0: enabling device (0140 -> 0143)
[    5.881235] ahci 0000:01:00.0: SSS flag set, parallel bus scan disabled
[    5.887850] ahci 0000:01:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl IDE mode
[    5.895827] ahci 0000:01:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs 
[    5.905731] scsi host0: ahci
[    5.908996] scsi host1: ahci
[    5.912097] ata1: SATA max UDMA/133 abar m512@0x60000000 port 0x60000100 irq 221
[    5.919446] ata2: SATA max UDMA/133 abar m512@0x60000000 port 0x60000180 irq 221
[    5.927202] mediatek-dpi 14014000.dpi: Found bridge node: /hdmi@14015000
[    5.934133] mediatek-drm 14000000.dispsys: bound 14007000.ovl (ops mtk_disp_ovl_component_ops)
[    5.942724] mediatek-drm 14000000.dispsys: bound 14008000.rdma (ops mtk_disp_rdma_component_ops)
[    5.951473] mediatek-drm 14000000.dispsys: bound 1400b000.color (ops mtk_disp_color_component_ops)
[    5.960377] mediatek-drm 14000000.dispsys: bound 14012000.rdma (ops mtk_disp_rdma_component_ops)
[    5.969143] mediatek-drm 14000000.dispsys: bound 14014000.dpi (ops mtk_dpi_component_ops)
[    5.977363] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    5.983948] [drm] No driver support for vblank timestamp query.
[    5.989864] [drm] Cannot find any crtc or sizes
[    5.994849] [drm] Initialized mediatek 1.0.0 20150513 for 14000000.dispsys on minor 0
[    6.002991] mt7530 switch@0: GPIO lookup for consumer reset
[    6.008532] mt7530 switch@0: using device tree for GPIO lookup
[    6.014366] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/switch@0[0]' - status (0)
[    6.023880] DSA: switch 0 0 parsed
[    6.027282] DSA: tree 0 parsed
[    6.037408] mdio_bus dsa-0.0: GPIO lookup for consumer reset
[    6.043053] mdio_bus dsa-0.0: using lookup tables for GPIO lookup
[    6.049105] mdio_bus dsa-0.0: lookup for GPIO reset failed
[    6.056200] libphy: dsa slave smi: probed
[    6.060408] Generic PHY dsa-0.0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:00, irq=POLL)
[    6.070932] Generic PHY dsa-0.0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:01, irq=POLL)
[    6.081367] Generic PHY dsa-0.0:02: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:02, irq=POLL)
[    6.091777] Generic PHY dsa-0.0:03: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:03, irq=POLL)
[    6.102176] Generic PHY dsa-0.0:04: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:04, irq=POLL)
[    6.112423] of_get_named_gpiod_flags: can't parse 'link-gpios' property of node '/switch@0/ports/port@5/fixed-link[0]'
[    6.125528] of_get_named_gpiod_flags: can't parse 'link-gpios' property of node '/switch@0/ports/port@6/fixed-link[0]'
[    6.138903] hctosys: unable to open rtc device (rtc0)
[    6.144159] clk: Not disabling unused clocks
[    6.148422] vdd_fixed_vgpu: disabling
[    6.152100] vusb: disabling
[    6.154883] vmc: disabling
[    6.157577] vgp1: disabling
[    6.160374] vcamaf: disabling
[    6.163351] ALSA device list:
[    6.166295]   No soundcards found.
[    6.420742] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    6.428445] ata1.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133
[    6.434695] ata1.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    6.443141] ata1.00: configured for UDMA/133
[    6.447918] scsi 0:0:0:0: Direct-Access     ATA      ST4000VN008-2DR1 SC60 PQ: 0 ANSI: 5
[    6.456867] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    6.464588] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    6.469850] sd 0:0:0:0: [sda] Write Protect is off
[    6.474627] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    6.479750] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    6.542848]  sda: sda1 sda2 sda3 sda4 sda5 sda6
[    6.549238] sd 0:0:0:0: [sda] Attached SCSI disk
[    6.782204] ata2: SATA link down (SStatus 0 SControl 300)
[    6.787676] md: Waiting for all devices to be available before autodetect
[    6.794453] md: If you don't use raid, use raid=noautodetect
[    6.800677] md: Autodetecting RAID arrays.
[    6.804770] md: autorun ...
[    6.807543] md: ... autorun DONE.
[    6.915266] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    6.922968] VFS: Mounted root (ext4 filesystem) readonly on device 8:1.
[    6.971125] devtmpfs: mounted
[    6.976385] Freeing unused kernel memory: 1024K
[    7.607379] random: fast init done
[    7.841106] systemd[1]: System time before build time, advancing clock.
[    8.166953] NET: Registered protocol family 10
[    8.172978] Segment Routing with IPv6
[    8.193136] ip_tables: (C) 2000-2006 Netfilter Core Team
[    8.251228] random: systemd: uninitialized urandom read (16 bytes read)
[    8.276106] random: systemd: uninitialized urandom read (16 bytes read)
[    8.287706] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTI)
[    8.306348] systemd[1]: Detected architecture arm.

Welcome to Debian GNU/Linux 9 (stretch)!

[    8.404847] systemd[1]: Set hostname to <the_hostname>.
[    8.561300] random: systemd-cryptse: uninitialized urandom read (16 bytes read)
[   10.721764] systemd[1]: lvm2-lvmetad.socket: Cannot add dependency job, ignoring: Unit lvm2-lvmetad.socket is masked.
[   10.732416] systemd[1]: lvm2-monitor.service: Cannot add dependency job, ignoring: Unit lvm2-monitor.service is masked.
[   10.743578] systemd[1]: lvm2-activation.service: Cannot add dependency job, ignoring: Unit lvm2-activation.service is masked.
[   10.754894] systemd[1]: lvm2-activation-early.service: Cannot add dependency job, ignoring: Unit lvm2-activation-early.service is masked.
[   10.767808] systemd[1]: dm-event.socket: Cannot add dependency job, ignoring: Unit dm-event.socket is masked.
[   10.778482] systemd[1]: nscd.service: Cannot add dependency job, ignoring: Unit nscd.service is masked.
[   10.796684] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Listening on Journal Socket.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Syslog Socket.
[  OK  ] Created slice System Slice.
[  OK  ] Created slice system-getty.slice.
         Mounting POSIX Message Queue File System...
         Starting File System Check on Root Device...
[  OK  ] Created slice system-uwsgi\x2dapp.slice.
[  OK  ] Created slice system-postfix.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Starting Load Kernel Modules...
[  OK  ] Reached target Slices.
[  OK  ] Created slice system-postgresql.slice.
[  OK  ] Created slice system-openvpn\x2dclient.slice.
         Starting Nameserver information manager...
         Mounting Debug File System...
         Starting Set the console keyboard layout...
[  OK  ] Created slice system-openvpn\x2dserver.slice.
[   11.601818] cryptodev: loading out-of-tree module taints kernel.
[   11.609328] cryptodev: driver 1.9 loaded.
         Starting Restore / save the current clock...
[   11.853487] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
         Starting Journal Service...
[  OK  ] Created slice system-systemd\x2dfsck.slice.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Encrypted Volumes.
         Starting Create list of required st�…ce nodes for the current kernel...
[   12.022288] ip6_tables: (C) 2000-2006 Netfilter Core Team
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Debug File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required sta�…vice nodes for the current kernel.
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Started Nameserver information manager.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Journal Service.
[  OK  ] Started File System Check Daemon to report status.
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Started udev Kernel Device Manager.e)
[   17.511642] random: crng init done complete)
[   17.515055] random: 7 urandom warning(s) missed due to ratelimiting
[  OK  ] Started File System Check on Root Device.
         Starting Remount Root and Kernel File Systems...
[   37.885033] EXT4-fs (sda1): warning: checktime reached, running e2fsck is recommended
[   37.912735] EXT4-fs (sda1): re-mounted. Opts: (null)
[  OK  ] Started Remount Root and Kernel File Systems.
         Starting udev Coldplug all Devices...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started udev Coldplug all Devices.
[   38.511972] evbug: Connected device: input0 (mtk_cir at mtk_cir/input0)
[   38.513010] mt6397-rtc mt6323-rtc: registered as rtc0
[   38.523667] evbug: Connected device: input1 (MCE IR Keyboard/Mouse (mtk_cir) at /input0)
[  OK  ] Found device /dev/ttyS0.
[   38.558423] mtk-thermal 1100b000.thermal: Device not calibrated, using default calibration values
[  OK  ] Found device ST4000VN008-2DR166 swap.
[  OK  ] Found device ST4000VN008-2DR166 swap.
[  OK  ] Found device ST4000VN008-2DR166 home.
[  OK  ] Found device ST4000VN008-2DR166 tmp.
[  OK  ] Found device ST4000VN008-2DR166 var.
         Starting File System Check on /dev/�…bd4-f729-4f5d-babf-c7bedcafdda1...
         Starting File System Check on /dev/�…1dd-0591-42fc-bb1e-94f7eb7a8ec7...
         Starting File System Check on /dev/�…517-5eb7-456e-8020-797137bcdbca...
         Activating swap Swap Partition...
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[   40.364399] Adding 16383996k swap on /dev/sda2.  Priority:-2 extents:1 across:16383996k 
[  OK  ] Activated swap Swap Partition.
[  OK  ] Activated swap /dev/disk/by-uuid/0db86b34-3df2-448f-9ca8-b1cc7255dd65.
[  OK  ] Reached target Swap.
[  OK  ] Started File System Check on /dev/d�…4ebd4-f729-4f5d-babf-c7bedcafdda1.
         Mounting /var...
[  OK  ] Started File System Check on /dev/d�…d1517-5eb7-456e-8020-797137bcdbca.
[   40.721858] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[  OK  ] Mounted /var.
         Starting Flush Journal to Persistent Storage...
         Starting Load/Save Random Seed...
         Mounting /home...
[  OK  ] Started File System Check on /dev/d�…481dd-0591-42fc-bb1e-94f7eb7a8ec7.
[  OK  ] Started Load/Save Random Seed. complete)
         Mounting /tmp...
[   41.027244] systemd-journald[169]: Received request to flush runtime journal from PID 1
[   41.144274] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Mounted /tmp.
[   41.524180] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[  OK  ] Mounted /home.
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Set console font and keymap...
         Starting Raise network interfaces...
         Starting Enable support for additional executable binary formats...
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Enable support for additional executable binary formats.
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
         Starting Console System Startup Logging...
[  OK  ] Listening on PC/SC Smart Card Daemon Activation Socket.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Started Clean PHP session files every 30 mins.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on fcgiwrap Socket.
[  OK  ] Listening on ACPID Listen Socket.
[  OK  ] Started Daily apt download activities.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Reached target Timers.
[  OK  ] Started ACPI Events Check.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
         Starting LSB: Start/stop sysstat's sadc...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Internet superserver...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started PostSRSd Daemon.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting LSB: Start or stop stunnel��…TLS tunnel for network daemons)...
[  OK  ] Started YunoHost boot prompt.
[  OK  ] Started Name Service Cache Daemon.
         Starting LSB: service and resource monitoring daemon...
         Starting LSB: Provide limited super�…er privileges to specific users...
         Starting LSB: Start the GNUstep distributed object mapper...
         Starting PostgreSQL Cluster 9.6-main...
         Starting Initialize hardware monitoring sensors...
         Starting Login Service...
         Starting LSB: Start Monitorix daemon...
[  OK  ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
         Starting System Logging Service...
         Starting LSB: Start/stop the postgrey daemon...
[  OK  ] Started ACPI event daemon.
         Starting LSB: Demon mouse...
         Starting LSB: Add IP and MAC in /etc/issue...
[  OK  ] Started Internet superserver.
[  OK  ] Started Console System Startup Logging.
[  OK  ] Started Initialize hardware monitoring sensors.
[   44.478214] ip: page allocation failure: order:0, mode:0x1080120(GFP_ATOMIC|__GFP_COLD), nodemask=(null)
[   44.487689] ip cpuset=/ mems_allowed=0
[   44.491438] CPU: 3 PID: 668 Comm: ip Tainted: G           O    4.14.78-bpi-r2-main #1
[   44.491441] Hardware name: Mediatek Cortex-A7 (Device Tree)
[   44.491474] [<c01132d0>] (unwind_backtrace) from [<c010d5e0>] (show_stack+0x20/0x24)
[   44.491486] [<c010d5e0>] (show_stack) from [<c0aa7f44>] (dump_stack+0x90/0xa4)
[   44.491499] [<c0aa7f44>] (dump_stack) from [<c023c37c>] (warn_alloc+0xc8/0x17c)
[   44.491509] [<c023c37c>] (warn_alloc) from [<c023d6cc>] (__alloc_pages_nodemask+0x11e8/0x122c)
[   44.491518] [<c023d6cc>] (__alloc_pages_nodemask) from [<c023d8fc>] (page_frag_alloc+0x14c/0x160)
[   44.491529] [<c023d8fc>] (page_frag_alloc) from [<c089204c>] (netdev_alloc_frag+0x40/0x48)
[   44.491542] [<c089204c>] (netdev_alloc_frag) from [<c0717748>] (mtk_rx_alloc+0xac/0x34c)
[   44.491552] [<c0717748>] (mtk_rx_alloc) from [<c0717d8c>] (mtk_open+0x3a4/0x5f8)
[   44.491562] [<c0717d8c>] (mtk_open) from [<c08aec14>] (__dev_open+0xb8/0x11c)
[   44.491573] [<c08aec14>] (__dev_open) from [<c08aefd8>] (__dev_change_flags+0x184/0x1ac)
[   44.491582] [<c08aefd8>] (__dev_change_flags) from [<c08af028>] (dev_change_flags+0x28/0x58)
[   44.491592] [<c08af028>] (dev_change_flags) from [<c08c2270>] (do_setlink+0x32c/0x968)
[   44.491602] [<c08c2270>] (do_setlink) from [<c08c446c>] (rtnl_newlink+0x4d0/0x7fc)
[   44.491612] [<c08c446c>] (rtnl_newlink) from [<c08c1700>] (rtnetlink_rcv_msg+0x218/0x280)
[   44.491622] [<c08c1700>] (rtnetlink_rcv_msg) from [<c08eaab4>] (netlink_rcv_skb+0xd0/0xf0)
[   44.491632] [<c08eaab4>] (netlink_rcv_skb) from [<c08c14e4>] (rtnetlink_rcv+0x20/0x24)
[   44.491640] [<c08c14e4>] (rtnetlink_rcv) from [<c08ea204>] (netlink_unicast+0x190/0x258)
[   44.491649] [<c08ea204>] (netlink_unicast) from [<c08ea624>] (netlink_sendmsg+0x280/0x350)
[   44.491661] [<c08ea624>] (netlink_sendmsg) from [<c0889c64>] (sock_sendmsg+0x24/0x34)
[   44.491671] [<c0889c64>] (sock_sendmsg) from [<c088a424>] (___sys_sendmsg+0x1ec/0x214)
[   44.491680] [<c088a424>] (___sys_sendmsg) from [<c088b2b4>] (__sys_sendmsg+0x50/0x7c)
[   44.491688] [<c088b2b4>] (__sys_sendmsg) from [<c088b2f8>] (SyS_sendmsg+0x18/0x1c)
[   44.491698] [<c088b2f8>] (SyS_sendmsg) from [<c0108cc0>] (ret_fast_syscall+0x0/0x54)
[   44.491702] Mem-Info:
[   44.491718] active_anon:3793 inactive_anon:2378 isolated_anon:0
[   44.491718]  active_file:20127 inactive_file:101813 isolated_file:0
[   44.491718]  unevictable:0 dirty:8 writeback:0 unstable:0
[   44.491718]  slab_reclaimable:4101 slab_unreclaimable:2982
[   44.491718]  mapped:3207 shmem:2429 pagetables:224 bounce:0
[   44.491718]  free:370395 free_pcp:595 free_cma:15230
[   44.491729] Node 0 active_anon:15172kB inactive_anon:9512kB active_file:80508kB inactive_file:407252kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:12828kB dirty:32kB writeo
[   44.491745] Normal free:4680kB min:2812kB low:3512kB high:4212kB active_anon:0kB inactive_anon:0kB active_file:65556kB inactive_file:371832kB unevictable:0kB writepending:20kB present:5324B
[   44.491746] lowmem_reserve[]: 0 11703 11703
[   44.491766] HighMem free:1476900kB min:512kB low:2636kB high:4760kB active_anon:15172kB inactive_anon:9512kB active_file:14952kB inactive_file:35420kB unevictable:0kB writepending:12kB preB
[   44.491767] lowmem_reserve[]: 0 0 0
[   44.491774] Normal: 146*4kB (UME) 31*8kB (UME) 27*16kB (UE) 21*32kB (UM) 11*64kB (UE) 4*128kB (U) 2*256kB (U) 2*512kB (U) 0*1024kB 0*2048kB 0*4096kB 0*8192kB = 4688kB
[   44.491810] HighMem: 10*4kB (UMC) 25*8kB (UM) 13*16kB (UMC) 13*32kB (UMC) 3*64kB (UM) 4*128kB (UMC) 3*256kB (UMC) 0*512kB 2*1024kB (UC) 1*2048kB (C) 3*4096kB (UM) 178*8192kB (MC) = 1476896B
[   44.491850] 124367 total pagecache pages
[   44.491867] 0 pages in swap cache
[   44.491870] Swap cache stats: add 0, delete 0, find 0/0
[   44.491872] Free swap  = 16383996kB
[   44.491875] Total swap = 16383996kB
[   44.491877] 524031 pages RAM
[   44.491879] 390911 pages HighMem/MovableOnly
[   44.491881] 9059 pages reserved
[   44.491883] 16384 pages cma reserved
[   44.532616] ip: page allocation failure: order:10, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null)
[   44.532642] ip cpuset=/ mems_allowed=0
[   44.532659] CPU: 2 PID: 681 Comm: ip Tainted: G           O    4.14.78-bpi-r2-main #1
[   44.532662] Hardware name: Mediatek Cortex-A7 (Device Tree)
[   44.532692] [<c01132d0>] (unwind_backtrace) from [<c010d5e0>] (show_stack+0x20/0x24)
[   44.532704] [<c010d5e0>] (show_stack) from [<c0aa7f44>] (dump_stack+0x90/0xa4)
[   44.532717] [<c0aa7f44>] (dump_stack) from [<c023c37c>] (warn_alloc+0xc8/0x17c)
[   44.532727] [<c023c37c>] (warn_alloc) from [<c023d6cc>] (__alloc_pages_nodemask+0x11e8/0x122c)
[   44.532737] [<c023d6cc>] (__alloc_pages_nodemask) from [<c025f4d0>] (kmalloc_order+0x28/0x40)
[   44.532746] [<c025f4d0>] (kmalloc_order) from [<c025f514>] (kmalloc_order_trace+0x2c/0xd8)
[   44.532757] [<c025f514>] (kmalloc_order_trace) from [<c0717ad8>] (mtk_open+0xf0/0x5f8)
[   44.532770] [<c0717ad8>] (mtk_open) from [<c08aec14>] (__dev_open+0xb8/0x11c)
[   44.532781] [<c08aec14>] (__dev_open) from [<c08aefd8>] (__dev_change_flags+0x184/0x1ac)
[   44.532790] [<c08aefd8>] (__dev_change_flags) from [<c08af028>] (dev_change_flags+0x28/0x58)
[   44.532800] [<c08af028>] (dev_change_flags) from [<c08c2270>] (do_setlink+0x32c/0x968)
[   44.532811] [<c08c2270>] (do_setlink) from [<c08c446c>] (rtnl_newlink+0x4d0/0x7fc)
[   44.532820] [<c08c446c>] (rtnl_newlink) from [<c08c1700>] (rtnetlink_rcv_msg+0x218/0x280)
[   44.532830] [<c08c1700>] (rtnetlink_rcv_msg) from [<c08eaab4>] (netlink_rcv_skb+0xd0/0xf0)
[   44.532840] [<c08eaab4>] (netlink_rcv_skb) from [<c08c14e4>] (rtnetlink_rcv+0x20/0x24)
[   44.532849] [<c08c14e4>] (rtnetlink_rcv) from [<c08ea204>] (netlink_unicast+0x190/0x258)
[   44.532857] [<c08ea204>] (netlink_unicast) from [<c08ea624>] (netlink_sendmsg+0x280/0x350)
[   44.532870] [<c08ea624>] (netlink_sendmsg) from [<c0889c64>] (sock_sendmsg+0x24/0x34)
[   44.532880] [<c0889c64>] (sock_sendmsg) from [<c088a424>] (___sys_sendmsg+0x1ec/0x214)
[   44.532889] [<c088a424>] (___sys_sendmsg) from [<c088b2b4>] (__sys_sendmsg+0x50/0x7c)
[   44.532898] [<c088b2b4>] (__sys_sendmsg) from [<c088b2f8>] (SyS_sendmsg+0x18/0x1c)
[   44.532908] [<c088b2f8>] (SyS_sendmsg) from [<c0108cc0>] (ret_fast_syscall+0x0/0x54)
[   44.963310] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   44.982170] br0: port 1(lan0) entered blocking state
[   44.982183] br0: port 1(lan0) entered disabled state
[   44.982515] device lan0 entered promiscuous mode
[   44.982522] device eth0 entered promiscuous mode
[   44.998851] br0: port 2(lan1) entered blocking state
[   44.998861] br0: port 2(lan1) entered disabled state
[   44.999168] device lan1 entered promiscuous mode
[   45.012090] br0: port 3(lan2) entered blocking state
[   45.012100] br0: port 3(lan2) entered disabled state
[   45.012401] device lan2 entered promiscuous mode
[   45.026435] br0: port 4(lan3) entered blocking state
[   45.026444] br0: port 4(lan3) entered disabled state
[   45.026743] device lan3 entered promiscuous mode
[   45.054073] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready
[  OK  ] Started System Logging Service.
[  OK  ] Started LSB: Start/stop sysstat's sadc.
[  OK  ] Started LSB: Add IP and MAC in /etc/issue.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started LSB: Start the GNUstep distributed object mapper.
[  OK  ] Started LSB: Provide limited super user privileges to specific users.
[  OK  ] Started LSB: Demon mouse.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Started Login Service.
[  OK  ] Started LSB: service and resource monitoring daemon.
[  OK  ] Started LSB: set CPUFreq kernel parameters.
[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
[  OK  ] Reached target Network.

Add Bluetooth support

There is no bluetooth interface on 4.14.11.
Install:

apt-get install bluez bluez-utils

Enable interface:

hciconfig hci0 up

Add Mali GPU driver

https://developer.arm.com/products/software/mali-drivers/utgard-kernel

HDMI not working

added hdmi-nodes from 4.4.70 in hdmi-branch, but kernel seems not to be loaded (debug-uart stops after "Starting kernel ..."-message from uboot)

https://github.com/frank-w/BPI-R2-4.14/commits/hdmi

PWM (#3) has wrong frequency

Setup for 5kHz resulting in 1kHz

root@bpi-r2:~# echo 3 >/sys/class/pwm/pwmchip0/export
root@bpi-r2:~# echo 200000 >/sys/class/pwm/pwmchip0/pwm3/period
root@bpi-r2:~# echo 100000 >/sys/class/pwm/pwmchip0/pwm3/duty_cycle
root@bpi-r2:~# echo 1 >/sys/class/pwm/pwmchip0/pwm3/enable

see here for more: http://forum.banana-pi.org/t/gpio-python-or-shell/3912/37

remove LTE (and other) from combo-chip-folder

https://github.com/frank-w/BPI-R2-4.14/blob/2e651881b14cfd52ec02f99c436d99c10ea8a420/drivers/misc/mediatek/connectivity/Makefile#L23

[Solved] About 10x performance degradation with 5.15-main

Hello!
First I want to thank Frank-W for your wonderful work you do with these systems!
Thank you very much!

Second, it seems I found something interesting but I'm not knowledgable enough to "debug" more of it:
So I upgraded from 5.10-main.52 to 5.15-main.26 (compiled those myself with the imported config and then added some stuff I needed) and noticed that my internet was somewhat slow suddenly.

I did some performance and speedtesting and it seemed to cap at around 3MB/s at the max.
Next I did some iperf3 testing and those cap out with this: "[ 4] 13.00-14.00 sec 18.2 MBytes 153 Mbits/sec".

Since I changed my NIC between the kernel upgrade I checked with a different NIC but those also cap out the same as above.

Next I compiled the 5.10-main.110 kernel at it was back to normal: "[ 4] 7.00-8.00 sec 113 MBytes 949 Mbits/sec"

I also checked back with the older 5.10-main.52 and it was the same: "[ 4] 2.00-3.00 sec 113 MBytes 948 Mbits/sec"

Edit: In addition it seems also any kind of connection like ssh seems rather sluggish like there may be a scheduler problem or something?

So yes for some reason it seems that the 5.15-main kernel is the cause. I have no idea why though and no idea how to check it so I thought I report my finding here.

Edit2: I use a BPi-R2

[internal wifi] AP not visible if hostapd killed first time

hostapd is working the first-time, after killing it and restart, AP is not visible on clients (no error-Message on hostapd). tested on debian jessie (after upgrade to stretch it have same behavior after killing hostapd)

Kernel 4.14 deb-script problems

I compiled the latest 4.14.59 Kernel and selected option 3 to get a .deb package, but while I tried to install it on my BananaPi I received this exception:
root@server-00-bpi:~# dpkg --install bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb
(Reading database ... 251892 files and directories currently installed.)
Preparing to unpack bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb ...
Unpacking bananapi-r2-image-4.14-main (4.14.59-1) ...
dpkg: error processing archive bananapi-r2-image-4.14-main_4.14.59-1_armhf.deb (--install):
error setting ownership of './boot/bananapi/bpi-r2/linux/uImage_4.14.59-main': Operation not permitted
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
installation aborted

6.1-main deb package is not compatible with Debian Bullseye

dpkg --contents linux-image-6.1.12-bpi-r2-main_6.1.12-bpi-r2-main-2_armhf.deb
dpkg-deb: error: archive 'linux-image-6.1.12-bpi-r2-main_6.1.12-bpi-r2-main-2_armhf.deb' uses unknown compression for member 'control.tar.zst', giving up

Looks like zst support was added in Debian 12:
https://unix.stackexchange.com/questions/669004/zst-compression-not-supported-by-apt-dpkg

Stuck at "waiting for root device ..."

Hi , Thank you for porting kernel for R2.

I compiled the kernel form your repository, and stuck at "Waiting for root device..".
I compare .config bewteen version 4.4 and 4.14 and it seem no option about enabling mmc.

Is it no emmc / sd mmc support yet?

When building I get a cryptodev error...

I'm a noob to this so forgive a simple question.

Build CryptoDev
make -C  M=/home/mark/banana-pi/BPI-R2-4.14/cryptodev/cryptodev-linux ARCH=arm CROSS_COMPILE=ccache arm-linux-gnueabihf- clean
make[1]: *** M=/home/mark/banana-pi/BPI-R2-4.14/cryptodev/cryptodev-linux: No such file or directory.  Stop.
Makefile:39: recipe for target 'clean' failed
make: *** [clean] Error 2
make -C /home/mark/banana-pi/BPI-R2-4.14 M=/home/mark/banana-pi/BPI-R2-4.14/cryptodev/cryptodev-linux ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules

Any pointers?

Mark

iptables not available on kernel 6.1

Hi,

How can I add iptables support to mainline 6.1 kernel when building?

Thanks!

openvswitch issue

Adding the ports lan0-lan3 to an openvswitch bridge does not seem to work. Arp requests are forwarded correctly, but the replies do not make it to the userspace, even if the corresponding port is in promiscuous mode.

The same problem (in another scenario) is described here:
http://forum.banana-pi.org/t/ethernet-in-promiscuous-mode/6773

I tried the 4.14.169-main and 4.19.101-main kernel.
Is there something I can do to use an openvswitch bridge on the BPI-R2?

Thanks,
Marco

mt7530 doesn't work on bpi-r3 if mtk_eth is built as module

When both mt7530 and mtk_eth are built as modules, probing for mt7530 fails with error:

mtk_soc_eth 15100000.ethernet: mdio: MDIO timeout
mdio_bus mdio-bus: failed to read mt7530 register
mtk_soc_eth 15100000.ethernet: mdio: MDIO timeout
mdio_bus mdio-bus: failed to read mt7530 register
mt7530 mdio-bus:1f: chip ffff can't be supported

If mtk_eth is changed to built-in, everything works fine.
Tested on 6.1-main and 6.3-rc branches.
Any ideas how to debug this further?

Cryptodev is broken

CC [M] /opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9/ioctl.o
/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9/ioctl.c:1127:3: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
{0, },
^
/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9/ioctl.c:1127:3: note: (near initialization for 'verbosity_ctl_dir[1]')
/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9/ioctl.c:1136:3: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
{0, },
^
/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9/ioctl.c:1136:3: note: (near initialization for 'verbosity_ctl_root[1]')
cc1: some warnings being treated as errors
scripts/Makefile.build:320: recipe for target '/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9/ioctl.o' failed
make[2]: *** [/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9/ioctl.o] Error 1
Makefile:1508: recipe for target 'module/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9' failed
make[1]: *** [module/opt/kernel/BPI-R2-4.14/cryptodev/cryptodev-linux-1.9] Error 2
make[1]: Leaving directory '/opt/kernel/BPI-R2-4.14'
Makefile:27: recipe for target 'build' failed
make: *** [build] Error 2
build test-tool
cc -I.. -Wall -Werror -c -o openssl_wrapper.o openssl_wrapper.c
openssl_wrapper.c:27:11: error: field 'hmac' has incomplete type
HMAC_CTX hmac;
^~~~
openssl_wrapper.c:28:13: error: field 'md' has incomplete type
EVP_MD_CTX md;
^~
openssl_wrapper.c: In function 'remove_mapping':
openssl_wrapper.c:68:3: error: implicit declaration of function 'HMAC_CTX_cleanup' [-Werror=implicit-function-declaration]
HMAC_CTX_cleanup(&mapping->ctx.hmac);
^~~~~~~~~~~~~~~~
openssl_wrapper.c:72:3: error: implicit declaration of function 'EVP_MD_CTX_cleanup' [-Werror=implicit-function-declaration]
EVP_MD_CTX_cleanup(&mapping->ctx.md);
^~~~~~~~~~~~~~~~~~
openssl_wrapper.c: In function 'openssl_hmac':
openssl_wrapper.c:133:3: error: implicit declaration of function 'HMAC_CTX_init' [-Werror=implicit-function-declaration]
HMAC_CTX_init(ctx);
^~~~~~~~~~~~~
cc1: all warnings being treated as errors
: recipe for target 'openssl_wrapper.o' failed
make: *** [openssl_wrapper.o] Error 1

[R2] WiFi not working on self-made Alpine linux

Hello,
I don't know how to start rly so I hope I can get my issue across for some help.

I've read up quite a bit on it and I followed all steps very closely and got Alpine working with kernel 5.4-main and 5.10-main.

So after setting up everything I wante to try the on-board Wifi and the first thing that happened was weird.
I started "/usr/bin/wmt_loader" and the first thing I get is "/usr/bin/wmt_loader: No such file or directory" and I'm quite baffled here as the exectuable is in "/usr/bin" and also is +x alright.
So I looked around and found another, old, Alpine from Pantavisor and tried replacing the binaries with the ones from that Alpine, suddenly wmt_loader starts and does its thing.
So second step "/usr/bin/stp_uart_launcher -p /etc/firmware &" and same thing with wmt_loader, "/usr/bin/stp_uart_launcher: No such file or directory". I do the same thing with this binary as with wmt_loader and replace it with the one from the Pantavisor Alpine, and see there it starts, but it segfaults at the end (I don't know is this is normal).
I don't mind it as it did run and created the "/dev/wmtWifi" device. So next step is "echo A >/dev/wmtWifi" and I get "echo: write error: I/O error" as such I can never enable the ap0 interface.

dmesg shows the following:

Mar 14 18:44:40 kernel: [97563.280914] [MTK-WIFI] WIFI_open: WIFI_open: major 155 minor 0 (pid 2119) Mar 14 18:44:40 kernel: [97563.280977] [MTK-WIFI] WIFI_write: WIFI_write A Mar 14 18:44:40 kernel: [97563.281060] vcn18: mode operation not allowed Mar 14 18:44:40 kernel: [97563.282732] [WMT-CONSYS-HW][E]mtk_wcn_consys_hw_reg_ctrl(291):Read CONSYS chipId(0xfffff093) Mar 14 18:44:40 kernel: [97563.376954] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6620.defAnt'. Mar 14 18:44:40 kernel: [97563.376966] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6628.defAnt'. Mar 14 18:44:40 kernel: [97563.376974] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6630.defAnt'. Mar 14 18:44:40 kernel: [97563.377201] [WMT-CORE][E]wmt_core_stp_init(648):WMT-CORE: no hif info! Mar 14 18:44:40 kernel: [97563.377208] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 649, (0) Mar 14 18:44:40 kernel: [97563.377214] [WMT-CORE][E]opfunc_pwr_on(918):WMT-CORE: wmt_core_stp_init fail (-1) Mar 14 18:44:40 kernel: [97563.377219] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 919, (0) Mar 14 18:44:40 kernel: [97563.377229] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(1), value(0) iRet:(-1) Mar 14 18:44:40 kernel: [97563.377235] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.377242] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(0), value(0) iRet:(-1) Mar 14 18:44:40 kernel: [97563.377246] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.377257] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(3), type(0), value(0) iRet:(-2) Mar 14 18:44:40 kernel: [97563.377262] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.377542] vcn18: mode operation not allowed Mar 14 18:44:40 kernel: [97563.377579] vcn18: mode operation not allowed Mar 14 18:44:40 kernel: [97563.379176] [WMT-CONSYS-HW][E]mtk_wcn_consys_hw_reg_ctrl(291):Read CONSYS chipId(0xfffff093) Mar 14 18:44:40 kernel: [97563.476854] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6620.defAnt'. Mar 14 18:44:40 kernel: [97563.476866] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6628.defAnt'. Mar 14 18:44:40 kernel: [97563.476873] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6630.defAnt'. Mar 14 18:44:40 kernel: [97563.477095] [WMT-CORE][E]wmt_core_stp_init(648):WMT-CORE: no hif info! Mar 14 18:44:40 kernel: [97563.477102] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 649, (0) Mar 14 18:44:40 kernel: [97563.477108] [WMT-CORE][E]opfunc_pwr_on(918):WMT-CORE: wmt_core_stp_init fail (-1) Mar 14 18:44:40 kernel: [97563.477113] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 919, (0) Mar 14 18:44:40 kernel: [97563.477123] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(1), value(0) iRet:(-1) Mar 14 18:44:40 kernel: [97563.477128] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.477135] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(0), value(0) iRet:(-1) Mar 14 18:44:40 kernel: [97563.477140] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.477150] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(3), type(0), value(0) iRet:(-2) Mar 14 18:44:40 kernel: [97563.477155] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.477419] vcn18: mode operation not allowed Mar 14 18:44:40 kernel: [97563.477455] vcn18: mode operation not allowed Mar 14 18:44:40 kernel: [97563.479059] [WMT-CONSYS-HW][E]mtk_wcn_consys_hw_reg_ctrl(291):Read CONSYS chipId(0xfffff093) Mar 14 18:44:40 kernel: [97563.576847] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6620.defAnt'. Mar 14 18:44:40 kernel: [97563.576859] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6628.defAnt'. Mar 14 18:44:40 kernel: [97563.576867] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6630.defAnt'. Mar 14 18:44:40 kernel: [97563.577101] [WMT-CORE][E]wmt_core_stp_init(648):WMT-CORE: no hif info! Mar 14 18:44:40 kernel: [97563.577108] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 649, (0) Mar 14 18:44:40 kernel: [97563.577114] [WMT-CORE][E]opfunc_pwr_on(918):WMT-CORE: wmt_core_stp_init fail (-1) Mar 14 18:44:40 kernel: [97563.577119] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 919, (0) Mar 14 18:44:40 kernel: [97563.577129] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(1), value(0) iRet:(-1) Mar 14 18:44:40 kernel: [97563.577134] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.577141] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(0), value(0) iRet:(-1) Mar 14 18:44:40 kernel: [97563.577146] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.577156] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(3), type(0), value(0) iRet:(-2) Mar 14 18:44:40 kernel: [97563.577160] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:40 kernel: [97563.577427] vcn18: mode operation not allowed Mar 14 18:44:40 kernel: [97563.577462] [WMT-CORE][E]opfunc_func_on(1025):func(3) pwr_on fail(-2) Mar 14 18:44:40 kernel: [97563.577467] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 1026, (0) Mar 14 18:44:40 kernel: [97563.577514] [STP] mtk_wcn_stp_psm_enable:[W] STP Not Ready, Dont do Sleep/Wakeup Mar 14 18:44:40 kernel: [97563.577525] [MTK-WIFI] WIFI_write: WMT turn on WIFI fail! Mar 14 18:44:40 kernel: [97563.577732] [MTK-WIFI] WIFI_close: WIFI_close: major 155 minor 0 (pid 2119) Mar 14 18:44:52 kernel: [97574.912583] [MTK-WIFI] WIFI_open: WIFI_open: major 155 minor 0 (pid 2119) Mar 14 18:44:52 kernel: [97574.912645] [MTK-WIFI] WIFI_write: WIFI_write A Mar 14 18:44:52 kernel: [97574.912729] vcn18: mode operation not allowed Mar 14 18:44:52 kernel: [97574.914365] [WMT-CONSYS-HW][E]mtk_wcn_consys_hw_reg_ctrl(291):Read CONSYS chipId(0xfffff093) Mar 14 18:44:52 kernel: [97575.006889] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6620.defAnt'. Mar 14 18:44:52 kernel: [97575.006901] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6628.defAnt'. Mar 14 18:44:52 kernel: [97575.006908] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6630.defAnt'. Mar 14 18:44:52 kernel: [97575.007130] [WMT-CORE][E]wmt_core_stp_init(648):WMT-CORE: no hif info! Mar 14 18:44:52 kernel: [97575.007136] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 649, (0) Mar 14 18:44:52 kernel: [97575.007143] [WMT-CORE][E]opfunc_pwr_on(918):WMT-CORE: wmt_core_stp_init fail (-1) Mar 14 18:44:52 kernel: [97575.007148] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 919, (0) Mar 14 18:44:52 kernel: [97575.007159] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(1), value(0) iRet:(-1) Mar 14 18:44:52 kernel: [97575.007164] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.007171] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(0), value(0) iRet:(-1) Mar 14 18:44:52 kernel: [97575.007176] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.007186] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(3), type(0), value(0) iRet:(-2) Mar 14 18:44:52 kernel: [97575.007191] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.007480] vcn18: mode operation not allowed Mar 14 18:44:52 kernel: [97575.007516] vcn18: mode operation not allowed Mar 14 18:44:52 kernel: [97575.009121] [WMT-CONSYS-HW][E]mtk_wcn_consys_hw_reg_ctrl(291):Read CONSYS chipId(0xfffff093) Mar 14 18:44:52 kernel: [97575.106855] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6620.defAnt'. Mar 14 18:44:52 kernel: [97575.106867] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6628.defAnt'. Mar 14 18:44:52 kernel: [97575.106875] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6630.defAnt'. Mar 14 18:44:52 kernel: [97575.107095] [WMT-CORE][E]wmt_core_stp_init(648):WMT-CORE: no hif info! Mar 14 18:44:52 kernel: [97575.107101] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 649, (0) Mar 14 18:44:52 kernel: [97575.107108] [WMT-CORE][E]opfunc_pwr_on(918):WMT-CORE: wmt_core_stp_init fail (-1) Mar 14 18:44:52 kernel: [97575.107113] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 919, (0) Mar 14 18:44:52 kernel: [97575.107122] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(1), value(0) iRet:(-1) Mar 14 18:44:52 kernel: [97575.107127] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.107134] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(0), value(0) iRet:(-1) Mar 14 18:44:52 kernel: [97575.107139] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.107149] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(3), type(0), value(0) iRet:(-2) Mar 14 18:44:52 kernel: [97575.107154] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.107425] vcn18: mode operation not allowed Mar 14 18:44:52 kernel: [97575.107460] vcn18: mode operation not allowed Mar 14 18:44:52 kernel: [97575.109064] [WMT-CONSYS-HW][E]mtk_wcn_consys_hw_reg_ctrl(291):Read CONSYS chipId(0xfffff093) Mar 14 18:44:52 kernel: [97575.206844] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6620.defAnt'. Mar 14 18:44:52 kernel: [97575.206857] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6628.defAnt'. Mar 14 18:44:52 kernel: [97575.206864] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6630.defAnt'. Mar 14 18:44:52 kernel: [97575.207102] [WMT-CORE][E]wmt_core_stp_init(648):WMT-CORE: no hif info! Mar 14 18:44:52 kernel: [97575.207108] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 649, (0) Mar 14 18:44:52 kernel: [97575.207114] [WMT-CORE][E]opfunc_pwr_on(918):WMT-CORE: wmt_core_stp_init fail (-1) Mar 14 18:44:52 kernel: [97575.207119] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 919, (0) Mar 14 18:44:52 kernel: [97575.207130] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(1), value(0) iRet:(-1) Mar 14 18:44:52 kernel: [97575.207135] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.207142] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(5), type(0), value(0) iRet:(-1) Mar 14 18:44:52 kernel: [97575.207147] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.207157] [WMT-CORE][E]wmt_core_ctrl(499):WMT-CORE: wmt_core_ctrl failed: id(3), type(0), value(0) iRet:(-2) Mar 14 18:44:52 kernel: [97575.207162] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 501, (0) Mar 14 18:44:52 kernel: [97575.207433] vcn18: mode operation not allowed Mar 14 18:44:52 kernel: [97575.207465] [WMT-CORE][E]opfunc_func_on(1025):func(3) pwr_on fail(-2) Mar 14 18:44:52 kernel: [97575.207471] drivers/misc/mediatek/connectivity/common/conn_soc/core/wmt_core.c, 1026, (0) Mar 14 18:44:52 kernel: [97575.207520] [STP] mtk_wcn_stp_psm_enable:[W] STP Not Ready, Dont do Sleep/Wakeup Mar 14 18:44:52 kernel: [97575.207529] [MTK-WIFI] WIFI_write: WMT turn on WIFI fail! Mar 14 18:44:52 kernel: [97575.207686] [MTK-WIFI] WIFI_close: WIFI_close: major 155 minor 0 (pid 2119)

Then I did the long run and compiled the kernel ON the BPI-R2 because I thought since Alpine uses musl instead of glibc that may be the issue but no dice, the binaries still only show ": No such file or directory".
I don't know what else to do here. I want to use Alpine so another distro is out of the question for me, what can I do here?

I don' know if this is related but if I use the kernel that has NOT the ending "_nodt" the kernel panics at boot time claiming I didn't append the correct "root=" parameter. So I USE the kernel image WITH the ending of "nodt".

I'm not exactly new to this, but this is my first time going at a dsitro this way, since there is no up-to-date premade Alpine image for this board.

modprobe: ERROR: could not insert 'ath9k' : Exec format error

Hi, I'm trying to use wlan with atheros NIC on BPI-R2-V1.2.
First, I burned the bpi-r2-buster_5.4.58 image on SD card and it seemed to work well. I installed some packages including pciutils through ethernet and checked NIC well connected.
And then I have changed the configuration little bit to add ath9k module, executed ./build.sh to build kernel, and inserted directly on SD card.
Now, ath9k is installed, but Exec format error occurs when I try to modprobe the module.
mac80211 cannot be inserted because of the same error.

Any help would be appreciated.

Linux ACL's (Access Control Lists) does not work for ext4 for some reason.

Have no idea why ACL's does not work, but it is kinda might be useful for network storage part of f-ty.

# dmesg | grep acl
...
[1334842.283671] EXT4-fs (sda1): acl option not supported
[1334842.356809] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: acl
mxbpir201 renard # uname -a
Linux bpir201 4.14.27-bpi-r2-main #1 SMP Mon Mar 19 10:34:41 EET 2018 armv7l GNU/Linux
# setfacl -R -m group:ghome:rwX /mnt/md3tlocal/tmp/
setfacl: /mnt/md3tlocal/tmp/: Operation not supported

Any ideas? Kernel seems to be build with the support of EXT4 ACL's. Is it?

$ ./build.sh importconfig
$ cat .config | grep _ACL
CONFIG_EXT4_FS_POSIX_ACL=y
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_BTRFS_FS_POSIX_ACL is not set
CONFIG_F2FS_FS_POSIX_ACL=y
CONFIG_FS_POSIX_ACL=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFS_ACL_SUPPORT=y

Thanks in advance.

cryptodev not available on kernel 6.1

Hello,

I discovered that cryptodev module was not enabled on kernel 6.1. Is it normal ? And is it possible to enable it ?

Thanks

SD-Card not found!

Hi, I have this "SD-Card not found!"

Issues with gcc-arm-linux-gnueabihf package

Hello Frank,

I've got some trouble installing the "gcc-arm-linux-gnueabihf" packet via apt.
I also tried manualy downloading the packet and installing it with dpkg but it says I've got the wrong architecture.
If it helps: uname -a output: "Linux server-00-bpi 4.4.70-BPI-R2-Kernel #1 SMP Tue Nov 28 10:59:01 CST 2017 armv7l armv7l armv7l GNU/Linux"

Regards

Compile warning for pwm issue on 4.14.23

  CC [M]  drivers/pwm/pwm-mediatek.o
drivers/pwm/pwm-mediatek.c: In function 'mtk_pwm_config':
drivers/pwm/pwm-mediatek.c:124:8: warning: unused variable 'clock' [-Wunused-variable]
  ulong clock;
        ^~~~~

F2FS on BananaPi

Is it possible to use f2fs FS on BananaPi?
If yes, can you tell me how i can use it?
Thanks a lot!

Enable squashfs support in 5.4-main

Hi,

first, I would like to thank you for maintaining the banana-pi r2 kernel and u-boot forks. It still took some work but setting things up were much easier than few years ago when I purchased BPI-R2.

Can you please enable squashfs in the 5.4-main branch, so lxc would work.

I added squashfs as module and recompiled to verify that lxc works. But I would prefer not to maintain another fork only for that.

with best regards,
Martin

SFP1 vlan not working on the r3

Hi, is there any workaround for the vlan not working on SFP1?

Thanks!

May be include wireguard in 5.4-main?

Your work about 5.4-main is just fine.

I would like to use your release kernels at https://github.com/frank-w/BPI-R2-4.14/releases , but they lacks wireguard.

Yep, I know possibility to install headers and dkms (and it even works), but it turns out that to patch sources is better for me for the following reasons:

• building wireguard.ko is much longer than in my thinkpad (10x longer) => installing new kernel from deb involves rebuild => unexpected long
• headers deb now contains 2 utilities, fixdep and modpost, compiled for x86, not arm64 :( so you need manually recompile them and only then you can use them

So, may be cherry-pick wireguard from here? muravjov@c2e547f
(if you don't want to do it yourself)

I applied wireguard like armbian does it
https://github.com/armbian/build/blob/master/lib/compilation-prepare.sh#L114

Bridging between lanx and tap devices not working

Hi,

i am currently trying to setup a simple vpn client which connects to a remote vpn network and bridges this to lan0-3 on the bpi-r2. with the official kernel the bridging works but i can only reach 3MB/s of 10MB/s download, upload is working fine.

Setup with the official kernel 4.4 is as follows:
VPN => tap_01 => br0 => eth1 (all lan ports, no port separation) => client

After switching to 5.4-main i cannot get any connection between br0 and tap_01.
Setup is as follows:
VPN => tap_01 => br0 => lan0, lan1, lan2, lan3 => client

Furthermore i have seen that if i connect two devices to lan0 and lan1 (or any other two lan ports) they can communicate. Therefore i assume that bridging between tap_01 and br0 is not working properly.

Any idea?

Problem 5.4.21-bpi-r2-main

Here I am again bothering you, but I need to install the header.
After moving to the penultimate kernel build installed with sudo dpkg -i x.deb i have rebooted and the bananapi r2 changed ip, no problem.

I logged in and proceeded to install in the same way linux-libc-dev_5.4.21-bpi-r2-main-1_armhf.deb, no problem.

I had previously installed it, but I wanted to provide a screen that it works.

I reboot again and after the wget for obtein the image and the header i try to install it in the same way, but i obtein this errors..

How can I solve it? Many thanks in advance

[Question] 5.15 & hwnat

I have a question regarding branch 5.15. According to the table, HW NAT should be supported. However I couldn't find implementation in these sources. Where is it?

Default config kernel 4.14

I have compare the default config from kernel 4.4. Here is a diff, you might want to include those on the default config fro kernel 4.14.

Add CONFIG_MTK_PLATFORM="mt7623"
Add CONFIG_CRYPTO_DEV_MEDIATEK=y
NOt really about that one, CONFIG_MEDIATEK_MT6577_AUXADC?

$ egrep 'MEDIATEK|MTK' .config | grep -v '#'
CONFIG_ARCH_MEDIATEK=y
CONFIG_PCIE_MEDIATEK=y
CONFIG_ARM_MEDIATEK_CPUFREQ=y
CONFIG_NET_DSA_TAG_MTK=y
CONFIG_MTK_PLATFORM="mt7623"
CONFIG_MTK_BTIF=y
CONFIG_MTK_COMBO=y
CONFIG_MTK_COMBO_CHIP_CONSYS_7623=y
CONFIG_MTK_COMBO_CHIP="CONSYS_7623"
CONFIG_MTK_COMBO_PLAT_PATH=""
CONFIG_MTK_COMBO_COMM=y
CONFIG_MTK_COMBO_COMM_UART=y
CONFIG_MTK_COMBO_COMM_SDIO=y
CONFIG_MTK_COMBO_COMM_NPWR=y
CONFIG_MTK_COMBO_COMM_APO=y
CONFIG_MTK_COMBO_BT=y
CONFIG_MTK_COMBO_BT_HCI=y
CONFIG_MTK_COMBO_WIFI=y
CONFIG_MTK_WAPI_SUPPORT=y
CONFIG_MTK_PASSPOINT_R1_SUPPORT=y
CONFIG_MTK_PASSPOINT_R2_SUPPORT=y
CONFIG_MTK_WIFI_MCC_SUPPORT=y
CONFIG_MTK_DHCPV6C_WIFI=y
CONFIG_AHCI_MTK=y
CONFIG_NET_VENDOR_MEDIATEK=y
CONFIG_NET_MEDIATEK_SOC=y
CONFIG_WLAN_VENDOR_MEDIATEK=y
CONFIG_HW_RANDOM_MTK=y
CONFIG_PINCTRL_MTK=y
CONFIG_MTK_THERMAL=m
CONFIG_MEDIATEK_WATCHDOG=y
CONFIG_IR_MTK=y
CONFIG_DRM_MEDIATEK=y
CONFIG_DRM_MEDIATEK_HDMI=y
CONFIG_SND_SOC_MEDIATEK=y
CONFIG_USB_XHCI_MTK=y
CONFIG_MMC_MTK=y
CONFIG_COMMON_CLK_MEDIATEK=y
CONFIG_MTK_TIMER=y
CONFIG_MTK_IOMMU_V1=y
CONFIG_MTK_INFRACFG=y
CONFIG_MTK_PMIC_WRAP=y
CONFIG_MTK_SCPSYS=y
CONFIG_MTK_SMI=y
CONFIG_MEDIATEK_MT6577_AUXADC=m
CONFIG_PWM_MTK_DISP=m
CONFIG_PWM_MEDIATEK=m
CONFIG_PHY_MTK_TPHY=y
CONFIG_CRYPTO_DEV_MEDIATEK=y

Your default:

$ egrep 'MEDIATEK|MTK' arch/arm/configs/mt7623n_evb_fwu_defconfig | grep -v '#'
CONFIG_ARCH_MEDIATEK=y
CONFIG_ARM_MEDIATEK_CPUFREQ=y
CONFIG_AHCI_MTK=m
CONFIG_NET_VENDOR_MEDIATEK=y
CONFIG_NET_MEDIATEK_SOC=y
CONFIG_MEDIATEK_WATCHDOG=y
CONFIG_IR_MTK=y
CONFIG_MMC_MTK=y
CONFIG_MTK_IOMMU_V1=y
CONFIG_MTK_PMIC_WRAP=y
CONFIG_MTK_COMBO=y
CONFIG_MTK_COMBO_CHIP_CONSYS_7623=y
CONFIG_MTK_COMBO_COMM=y
CONFIG_MTK_COMBO_WIFI=y
CONFIG_MTK_COMBO_BT=y
CONFIG_MTK_COMBO_BT_HCI=y
CONFIG_PCIE_MEDIATEK=y
CONFIG_PHY_MTK_TPHY=y
CONFIG_PWM_MEDIATEK=m
CONFIG_MTK_THERMAL=m
CONFIG_DRM_MEDIATEK=m
CONFIG_DRM_MEDIATEK_HDMI=m
CONFIG_USB_XHCI_MTK=y

As a diff:

$ diff myconfig defconfig 
1c1
< CONFIG_AHCI_MTK=y
---
> CONFIG_AHCI_MTK=m
4,8c4,5
< CONFIG_COMMON_CLK_MEDIATEK=y
< CONFIG_CRYPTO_DEV_MEDIATEK=y
< CONFIG_DRM_MEDIATEK_HDMI=y
< CONFIG_DRM_MEDIATEK=y
< CONFIG_HW_RANDOM_MTK=y
---
> CONFIG_DRM_MEDIATEK_HDMI=m
> CONFIG_DRM_MEDIATEK=m
10d6
< CONFIG_MEDIATEK_MT6577_AUXADC=m
13d8
< CONFIG_MTK_BTIF=y
16d10
< CONFIG_MTK_COMBO_CHIP="CONSYS_7623"
18,21d11
< CONFIG_MTK_COMBO_COMM_APO=y
< CONFIG_MTK_COMBO_COMM_NPWR=y
< CONFIG_MTK_COMBO_COMM_SDIO=y
< CONFIG_MTK_COMBO_COMM_UART=y
23d12
< CONFIG_MTK_COMBO_PLAT_PATH=""
26,27d14
< CONFIG_MTK_DHCPV6C_WIFI=y
< CONFIG_MTK_INFRACFG=y
29,31d15
< CONFIG_MTK_PASSPOINT_R1_SUPPORT=y
< CONFIG_MTK_PASSPOINT_R2_SUPPORT=y
< CONFIG_MTK_PLATFORM="mt7623"
33,34d16
< CONFIG_MTK_SCPSYS=y
< CONFIG_MTK_SMI=y
36,39d17
< CONFIG_MTK_TIMER=y
< CONFIG_MTK_WAPI_SUPPORT=y
< CONFIG_MTK_WIFI_MCC_SUPPORT=y
< CONFIG_NET_DSA_TAG_MTK=y
44d21
< CONFIG_PINCTRL_MTK=y
46,47d22
< CONFIG_PWM_MTK_DISP=m
< CONFIG_SND_SOC_MEDIATEK=y
49d23
< CONFIG_WLAN_VENDOR_MEDIATEK=y