i have created a basic ubuntu 22.04 image with kernel 6.1.12/uboot 2023.01
made not much tests with it, but it boots up and applies network-setting i copied from my debian-image (192.168.0.19 on wan-port, 192.168.1.1 on lan-ports). So it can be a base for further configuration.
cfg80211 needs to be compiled as module to load regulatory.db from rootfs (installed via package wireless-regdb or downloaded from kernel.org regulatory.db + regulatory.db.p7s)
CONFIG_CFG80211_WEXT=y is needed else you get error ânl80211 not foundâ when using iw
wifi-module ist not loaded at system bootup. create a file /etc/modules-load.d/mt7915.conf with content âmt7915eâ and reboot, then both hostapd came up at bootime
i got a error in uboot that partition 5 was not found after mutliple boots, this is how i solved it:
No, regdb is not needed for driver to loadâŚit is only needed to start Accesspoint in 5ghz and above
What kind of usb2serial adapter do you use? Only ftdi are known to work without issues. Most others prevent wifi fronent to start with a error similar to this
Thanks for your Kernel repo and CI releases, they are quite helpful. I am trying to get Wireguard working on BPI-R3, and from a quick look Release CI-BUILD-6.1-main-6.1.60-2023-10-26_1511 ¡ frank-w/BPI-Router-Linux ¡ GitHub should work? So, I have installed the debian packages to do the kernel upgrade and they got installed, but I donât know how to choose the kernel version in u-boot, it still boots the old one that I had installed using a single image.
Do you have a corresponding single .img file for above github release? Something similar to bpi-r3 - Google Drive
I just checked, the file is part of the Kernel, for the single image that I had flashed: /boot/bananapi/bpi-r3/linux-5.15/uEnv.txt but installing the debian packages created a new folder that only has below contents:
# ls -l /boot/bananapi/bpi-r3/linux/
total 44752
-rwxr-xr-x 1 root root 8551672 Oct 26 17:13 bpi-r3-6.1.60-bpi-r3-main.itb
drwxr-xr-x 2 root root 4096 Dec 17 19:51 dtb
-rwxr-xr-x 1 root root 14025500 Dec 17 19:51 initrd.img-6.1.60-bpi-r3-main
-rwxr-xr-x 1 root root 23237184 Oct 26 17:13 uImage_nodt-6.1.60-bpi-r3-main
So, I still donât know how to upgrade and switch to new kernel just by installing debian packages as we do in Desktop Ubuntu. I will try building a single image.
Oh,seems i missed packing itb into the debâŚbut if you compiled it by yourselb you can copy it manually from bpi-r3.itb in root of source dir to bpi-boot root
The link points to kernel 5.15 for bpi-r2 overriding default 6.1
You can compile kernel by yourself and install it to the flashed card or pack kernel and point to the tar.gz file before creating the image (using skipkerneldownload=1 and kernelfile=⌠In sourcefiles_â+board+â.confâ)
You should only use the main branches (or for bpi-r4 special ones)
I was able to build the kernel with custom config, and created a image and flashed to SD card. It boots my kernel fine, but its stuck waiting for root device: Waiting for root device /dev/mmcblk0p6... any ideas? Inspecting the BPI-ROOT partition, it seems fine i.e., the filesystem it present.
[Update: Actually the modules are not installed to the SD because of disparity in INSTALL_MOD_PATH pointing to mod but also looking for SD/BPI-ROOT]
[Update2: Sorry, above update is wrong: I am getting this error BPI-Router-Linux/Makefile:741: include/config/auto.conf: No such file or directory causing the modules install to fail]
Have you loaded the right config from fit image? On r3 the sd overlay has to be loaded.
You can define a initrd by adding
initrd=rootfs.cpio.gz
To uEnv.txt
If you have such file you can get a system without depency to sdcard (ram only) to check if devicetree and drivers are right. Imho i have such on my gdrive.
I made defconfig the way it should have all necessary (except wifi) builtin to have a clean start also when booting fit via tftp
Yes in fit the initrd is commented out,but my uboot can have an initrd too to not have it in the fit (which blow up fit)âŚso i have the initrd only once on card
Ok,if the conf-sd is correctly loaded,then dt should not be the problemâŚmmc driver should be builtin
uEnv.txt is not created by image-script as it is initially empty (using my u-boot builtin environment). uEnv.txt allows to override this but it has to be created.