lanefu

whats git branch -vva say

Honestly that means you have something Heavily logging... either in debug mode, or you have an issue.. That's the issue you should solve. if you want it to log that much you can disable the log2ram service.. but that will add wear to your disk systemctl stop armbian-ramlog.service systemctl disable armbian-ramlog.service

hmm... -b may have created a local branch named v20.02 instead of what you wanting.. did you do a get fetch? may need to do git check out origin/v20.02

If you want to build a "stable" image from the same code as the images we publish use v20.02 branch. If you want to build "unstable" image with latest and greatest us master branch.

Surprise! About a month is what we're shooting for. Sorry for the poor communication. We're still learning how to manage this process. Ideally we will start a bit earlier and release closer to the beginning of the month Master will continue on as a rolling release. You'll see that its version is already v20.05-trunk on master. Relevant fixes applied to v20.02 going forward should be cherry-picked to master. Although so far we've actually been cherry-picking fixes from master to v20.02. Going forward we'll update v20.02 for major bugs and stability issues until v20.05 is released. rc0 and rc1 branches will be deleted. Rc1 ended up being a rolling branch this time. Not sure how we'll handle this next time. A lot will be on how manage publishing test images.

Just built some fresh le potato images from master. Error message is Wrong Ramdisk image format. Console dump here: http://ix.io/2c0y I think it's related to stuff going on here, but not sure how to troubleshoot yet https://github.com/armbian/build/blob/master/config/sources/families/include/meson64_common.inc#L34

okay i disabled that patch in the v20.02 repo... was able to build a working le potato desktop.... Audio is overdriven, but i think thats a known issue... there are _other_ issues with building le potato in master. i'll start a seperate thread for that. TLDR; we can build le potato from v20.02 now with kernel 5.4.20

looks like culprit is https://github.com/armbian/build/blob/master/patch/kernel/meson64-current/meson64_fclk_div3.patch doing some more tests to confirm

Hi... so good news.... it IS one of these patches thats the problem https://github.com/armbian/build/tree/master/patch/kernel/meson64-current . i built without patches and it booted When I said i tested earlier.. i lied... ( I always get meson64 and mvebu64 mixed up)

I tried removing all patches and that didnt change the behavior. Ill take a look at kernel config again, but it seemed like it hasnt changed since we switched to mainline

Only on le potato. Not odroid c2. We have some different uboot steps for s905x but i haven't been able to understand them. @Igor do you think the gxl stuff in the uboot steps is relevant?

Hmmm I wish i understood how the armbian debian packaging worked a little better. Is there a short answer for why its a problem? Can we not lock kernels to a release?

Since the scope is only le potato, my thoughts are to update v20.02 branch (lepotato and v20.02 only) to use the older kernel config just for le potato. Then we can focus on fixing correctly for v20.05. I'll start working on a PR for that in a bit. If we find another solution thats fine.

Le Potato Update: I built and tested images through several commits, and patch adjustments. Le Potato has been broken since our switch to mainline kernel from this merge https://github.com/armbian/build/pull/1748 I was able to build a working image from here https://github.com/armbian/build/commit/cc7ab6a6b1d91977bd9e154245307e85f7f76519

check out the branch direclty and try what i said here

I'm just curious.. what do you use 1500 orange pc plus for?

Le Potato seems to be broken. I did several clean builds and always did the same thing. Another user in IRC confirmed not working on recent kernels for them as well. http://ix.io/2bUZ

git checkout master git pull sudo ./compile.sh will take you back to the master branch that you normally use.... FYI master is a rolling release..which may have looked like 19.11.x but its actually newer.. In fact we've updated the version in master release to reflect it as v20.05-trunk

git fetch git checkout v20.02-rc1 sudo ./compile.sh FORCE_CHECKOUT=no Unofficial release notes https://gist.github.com/lanefu/e32eb43aaaa7928c51ca8890af58c841#file-temp_notes-md

Armbian doens't manage those packages.. that would be upstream debian or ubuntu, dependin on what you're using. try running a `sudo apt clean` and then try again

thanks for testing.. did wifi working on the H64-b on previous kernels?

Maybe but... 4600 validating accounts disagree

yeah basically just.. don't allow posts until email is validated?

We hope to release RC1 by the end of the weekend. Last call for issues! If you're aware of any issues with RC1, please provide debugging information and instructions on how to replicate,

Probably running the default... which board are you testing? I'm glad you pointed out the verbosity setting.. i had assumed it was something else preventing output... were you able to get more verbose logging after updating armbianEnv.txt?