On first glance looks good, the detach error is normal, as it was not attached before.
After this you can apply any changes with --nand-update.
On first glance looks good, the detach error is normal, as it was not attached before.
After this you can apply any changes with --nand-update.
OK, tested boot from NAND and it’s working fine, yay
For my use case I would like to auto exec “bpir-dhcpc lan1” on every boot so I can detach UART and place it back to living room.
How do I enable this command to autoexec / retry on every boot ?
Sry, I see now that sshd is not running so the NAND recovery utils are only available via serial UART connection.
Disconnecting all the cables/antennas + opening the case + connecting UART every time I want use NAND recovery is not very practical, but I can live with it for now.
If you somehow manage to enable any remote connection to the console it would be perfect.
Maybe initrd (2GB) could help if storage is the limiting factor…
Thanks again for all your help and your recovery utils ![]()
You can make a UART connector on the rectangular hole of the case. It fits a male 2.54mm plug exactly.
Ssh is not supported from the initrd
You can use a linux sd-image as recovery for your nvme installed linux. That has ssh enabled.
@ericwoud great build/image. Having a bpi-r4 4gb for sometime with openwrt, and now just got a 8gb version that installed your archlinux build.
I want to change/add some kernel settings - I see you have this repo GitHub - ericwoud/archlinuxarm-repo at linux-bpir-git. How to build my own kernel and using your build.sh to build an image that has the kernel i build?
thank you
You do not use the build.sh at all, you build a regular archlinux package
The link is an archlinux package. You can build it on the R4, or use a x86 machine with archlinux (running from chroot if running on another linux).
git clone --branch=linux-bpir-git https://github.com/ericwoud/archlinuxarm-repo.git linux-bpir-git
cd linux-bpir-git
Edit the defconfig file as you like.
Run with specified target, as it builds from a different linux branch:
TARGET=bpir4 makepkg
You can install this linux from file with:
pacman -U filename.pkg.tar.xz
You can also change the PKGBUILD change repo + branch of the linux source. _gitroot and _gitbranch
thank you @ericwoud
all works fine with your repo
just to report also that the 6.16-main repo from Frank also works fine with your Archlinux setup
by changing PKGBUILD like the below
if [[ "$TARGET" == "bpir4" ]]; then
_target="bpir4"
# _gitbranch="mt7988-for-next"
_gitbranch="6.16-main"
elif [[ "$TARGET" == "bpirnn" ]]; then
_target="bpirnn"
# _gitbranch="bpir-net-next"
else
_target="bpir"
_gitbranch="bpir-rolling-stable"
fi
#_gitroot="https://github.com/ericwoud/linux.git"
_gitroot="https://github.com/frank-w/BPI-Router-Linux.git"
Indeed, it should work also. Please note that you are still using my config, so that may differ from Frank’s config.
The mt7988 branch I use is a fork of dangowrt’s branch. It may not be the latest anymore.
https://github.com/dangowrt/linux/tree/mt7988-for-next
For R64/R3 I have my own fork, based on rolling-stable, but for R4 not just yet.
dangowrt’s branch is quite old and a lot moved on since… works fine on 6.12 though… Frank’s works fine as it feels to be the latest (things like RSS/LRO) in particular if one wants to be on bleeding edge.
I also noted - and a warning for others - that things like fixdep that are used if one is compiling their own kernel modules (off kernel) is compiled on x86 (the host i used to create the sdcard). I had to build the kernel on the bpi4 but i guess chroot may have done it on the x86
This PKGBUILD is customized, so it can build this aarch64 kernel on x86.
Building extra modules, one would need to use the cross-compiler on x86. Building through chroot/qemu is really a lot slower, but for a few modules that would not be a big problem.
yes agree cross compiling … by the way i am using the 8gb version is all fine bearing in mind other discussions elsewhere
Thanks for the info, I could not test it myself.
If there are CONFIG_XXX that needs to be added, could you let me know? I can add them already.
As the current linux branch I used for R4 is not updated, I’ve moved the prebuild linux for R4 to @frank-w his github, 6.18-rc branch.