Frank, an off topic matter, is firewalld / nftables working good for you? Right after a fresh install and installing firewalld,doing a firewall-cmd --add-interface=eth1 --zone=internal, throws an error.
Error: COMMAND_FAILED: 'python-nftables' failed: internal:0:0-0: Error: No such file or directory; did you mean chain ‘filter_IN_external’ in table inet ‘firewalld’?
internal:0:0-0: Error: No such file or directory; did you mean chain ‘filter_FWD_external_allow’ in table inet ‘firewalld’?
The itb is the important part,maybe it is missing in 6.13 somehow…needed to patch deb creation script to include the files,maybe something has changed recently. If the deb contains no itb there is the problem. If the itb has version in name (as i guess) you have to change fit var in uEnv.txt to boot it (of course it need to exist). The dtb/no_dt is not needed here,but created for compatibility reasons with r64 and for manual try to apply dtb
Yes,this is the way i use it too,but with install option to sdcard which installs modules too (which are installed through deb i guess) but you should make backup of your last itb before overwriting it
For missing itb,i wonder why dtb and uimage_nodt are packed for r4 as this should be done only for r64 based on my patch
Basicly github has an api where you can get the last commits and push timestamp.
Idk if there is a out-of-box notification mechanism…i did some tests years ago to get updates for forks of my repos,but cannot tell how exactly i did this without looking in the (really dirty) code.
Sfps need pcs and the usxgmii patches which are not for upstream yet. The mt7988upstream branches are only for the upstream process not for direct usage,so missing functionality and these branches are often rebased.
It is still discussion how pcs should be upstreamed. Afaik last steps are done by sean anderson.
I guess he will send v6 when rc1 is out. When pcs is clear then the usxgmii patches can follow. I only added sfp in upstream to allow access via i2c.
For testing better use main or the rc branches…as there is no 6.16-rc1 yet i have not created the 6.16-rc yet…only upstream to send dts patches as soon as possible
Ok Frank, thanks for the explanation. So, your 6.12 branch is still on 6.12.30, how to update to 6.12.32? Will this work? [BPI-R2] mt7925 - #10 by SDXC
Would it be an option to use 1 fixed branch name, that always has the latest patches? Me too I’m always searching which branch.
That’s why I stick with dangowrt’s mt7988-for-next branch for R4, which holds most latest patches and is always rebased. Then I don’t need to search and just build this one, even using a script.
git clone --depth 1 -b 6.12-main https://github.com/frank-w/BPI-Router-Linux.git
git stash
cd BPI-Router-Linux/
git config --global --add safe.directory $PWD
git stash
./build.sh updatesrc
# error:
Update kernel source
fatal: 'stable' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
# So i ran it again:
./build.sh updatesrc
Update kernel source
remote: Enumerating objects: 13545655, done.
# *** SNIP ***
* [new tag] v6.9.7 -> v6.9.7
* [new tag] v6.9.8 -> v6.9.8
* [new tag] v6.9.9 -> v6.9.9
newkernver:6.12.31 (max:6.12.32)
fatal: refusing to merge unrelated histories
./build.sh importconfig
grep 6.12 ../build/.config
# Linux/arm64 6.12.30 Kernel Configuration
So, no 6.12.32, any other alternative Frank?
So actually running 6.15.0, which came from your branch 6.16-mt7988 branch, the problems with the mt7922 seem to be been fixed, but again, the fiber ports don’t work. So, hopefully 6.12.32 has the fixes for this card.
build.sh should add it on this error (seems it did in your case because error-message changed)…
but the new error (refusing to merge unrelated histories) is strange…are you on 6.12-main (i see you cloned only this branch which should be ok - calculation of newkernver is right so far)?
i had done the last merges with another laptop, so my current sync also contains already merged tags, but basicly works
and similar for 6.12.32 without errors, maybe issue with shallow clone…maybe you need the --single-branch too, but manpage says that depth implies single-branch?
I don’t i know Frank, but i cloned the tree again and yes, 6.12.32 came. Running it now. Fiber working again, thanks for the update Frank. Nex time, i try without --depth 1.