BPI-R4:Beginner questions for kernel building

ericwoud · June 7, 2025, 3:17pm

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.

frank-w · June 7, 2025, 3:33pm

No it’s no option as i need to look when a problem starts or till which it works…and there are lts kernels for productive use.

Casulo · June 9, 2025, 10:06am

Ok, i did this:

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.

frank-w · June 9, 2025, 10:53am

build.sh should add it on this error (seems it did in your case because error-message changed)…

github.com

frank-w/BPI-Router-Linux/blob/6.12-main/build.sh#L303


      
                  git fetch stable
                  ret=$?
                  if [[ $ret -eq 0 ]];then
                          newkernver=$(increase_kernel)
          		kernmajorver=$(make kernelversion | sed -e 's/\.[0-9]\+$//')
          		maxkernver=$(git for-each-ref --sort=-taggerdate --count=1  refs/tags/v${kernmajorver}.*| sed 's/^.*refs\/tags\/v//')
                          echo "newkernver:$newkernver (max:$maxkernver)"
                          git merge --no-edit v$newkernver
                  elif [[ $ret -eq 128 ]];then
                          #repo not found
                          git remote add stable https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
                  fi
                  else
                          echo "please first commit/stash modified files: $changedfiles"
                  fi
          }
          
          function changelog() {
          	get_version >/dev/null
          	lasttag=$(curl -s "https://api.github.com/repos/frank-w/BPI-R2-4.14/releases?per_page=100" | jq -r '[.[] | select(.tag_name|contains("'${kernbranch}'"))][0]' | grep "tag_name" | sed 's/.*: "\(.*\)",/\1/')
          	echo "changes since $lasttag:"

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

$ ./build.sh updatesrc
Update kernel source
remote: Enumerating objects: 862356, done.
remote: Counting objects: 100% (109197/109197), done.
remote: Compressing objects: 100% (3222/3222), done.
remote: Total 862356 (delta 106563), reused 106960 (delta 105975), pack-reused 753159
Receiving objects: 100% (862356/862356), 633.08 MiB | 3.02 MiB/s, done.
Resolving deltas: 100% (633397/633397), completed with 41345 local objects.
From https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable
...
 * [new tag]                   v6.12.24             -> v6.12.24
 * [new tag]                   v6.12.25             -> v6.12.25
 * [new tag]                   v6.12.26             -> v6.12.26
 * [new tag]                   v6.12.27             -> v6.12.27
 * [new tag]                   v6.12.28             -> v6.12.28
 * [new tag]                   v6.12.29             -> v6.12.29
 * [new tag]                   v6.12.30             -> v6.12.30
 * [new tag]                   v6.12.32             -> v6.12.32
....
newkernver:6.12.31 (max:6.12.32)
...

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?

pushed the updated tree

Casulo · June 9, 2025, 6:08pm

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.