Stable OpenWrt version for 64-bit ARM (Raspberry Pi4B)

For Developers
1

When will a stable 64-bit version for the Raspberry Pi 4B become available? I hear it will be in OpenWRT version 20. When is this planned to be released?

Thank you.

2

See OpenWrt 20.XX ? Any news on this?

1 Like
3

I realize you asked about "stable" but why not use a snapshot? I recompile mine on each new kernel release and have never had a problem.

4

I am using a snapshot, but the kernel modules get out of sync within a few days, so new ones can’t be installed anymore, and then within a few weeks new packages cannot be installed. So, I have to recompile again, which is getting old. It’s my primary firewall, and there’s too much that hinges on it being reliable nowadays, so constant recompiles and restores are not feasible for me.

1 Like
5

then compile all kernel modules and host it locally or on github/gitlab pages (statically) so you'll have access to it

6

When I commit to a snapshot, after reviewing the buildbot and git commits, I take a mirror of the target and package repository. Then I update /etc/opkg/distfeeds.conf to point to a local web server or even better, once I've resized the ext4 partition, copy the lot locally onto the SD card.

export DATE=20201104 
export snapdir="openwrt-snapshot-$DATE"
mkdir -p "$snapdir"/armv8/packages "$snapdir"/armv8/kmods "$snapdir"/aarch64_generic
cd $snapdir

rsync -va --progress --stats --exclude 'kmods' --exclude '*pine64*gz' --exclude '*radxa*gz' --exclude '*.tar.*' rsync://downloads.openwrt.org/downloads/snapshots/targets/rockchip/armv8/ armv8/

At this point I write the ext4 image to sd card, resize the partitions, and boot so I can double-check the kmod version in /etc/opkg/distfeeds.conf

# boot, log in, check /etc/opkg/distfeeds.conf for package repos

export KMODVER=5.4.74-1-63fa2731cb0f8e88239410e4cc044b42
mkdir -p armv8/kmods/"$KMODVER"
rsync -va --progress --stats rsync://downloads.openwrt.org/downloads/snapshots/targets/rockchip/armv8/kmods/"$KMODVER"/ armv8/kmods/"$KMODVER"/

rsync -va --progress --stats --exclude '*tesseract*' --exclude '*amdgpu-firmware*' --exclude "*bnx2x-firmware*" rsync://downloads.openwrt.org/downloads/snapshots/packages/aarch64_generic/ aarch64_generic/

I try to exclude bits I'll never use for this target. This way I have a stable and accessible snapshot and don't have to compile.
This is how I update /etc/opkg/distfeeds.conf:

cp /etc/opkg/distfeeds.conf /etc/opkg/distfeeds.conf.orig  
cat /etc/opkg/distfeeds.conf | sed 's/https\:\/\/downloads.openwrt.org\/snapshots\/targets\/rockchip\//http\:\/\/10.0.0.99\/openwrt\/openwrt-snapshot-20201104\//g' > /etc/opkg/distfeeds.conf.tmp 

cat /etc/opkg/distfeeds.conf.tmp | sed 's/https\:\/\/downloads.openwrt.org\/snapshots\/packages\//http\:\/\/10.0.0.99\/openwrt\/openwrt-snapshot-20201104\//g' > /etc/opkg/distfeeds.conf
1 Like
7

Is there a reason you need to install new modules and packages for an extended period after you've installed OpenWRT?

8

I am exploring new features available in OpenWRT. The bottom line is that running on a snapshot is a temporary solution. I was inquiring about when the Raspberry Pi 4B will receive the stable version support. Once it’s supported in stable, I won’t be playing with snapshots anymore.

1 Like
9

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.