ketominer
-
Posts
14 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by ketominer
-
-
10 hours ago, arox said:
Armbian_5.88_Rock64_Debian_stretch_default_4.4.180.7z
Armbian_5.75_Rock64_Debian_stretch_default_4.4.174.7z
LibreELEC-RK3328.arm-9.1.001-rock64.img.gz
Armbian_5.88_Rock64_Ubuntu_bionic_default_4.4.180.7z
Armbian_5.90_Rock64_Ubuntu_bionic_default_4.4.182.7z
The last one "seemed" a bit more stable but freezed and needed reset for rebooting and finally it crashed with mundane stack dump.
One symptom is that after a crash, or just a shutdown, the board enter an endless loop of panic at startup - needs reset? or cool down? or unplug/discharge? I even cannot find a safe method to restart the board !
Try going with the 4.4.180, it's the one that gives me the best results (although not on 100% of the boards)
-
1 minute ago, suberimakuri said:
"Stable Armbian" being the version from February here https://dl.armbian.com/rock64/ ??
yup. Armbian_5.75_Rock64_Ubuntu_bionic_default_4.4.174.7z
-
Actually even the stable armbian is way better, it now has dmc and the ram is clocked at 768*2! Just double checked with a few fresh installs + upgrade
-
Just switched to the latest nightly... seems to fix things a lot
-
OK after a long and painful investigation with pine64 and other people doing distributions for them + members of the community, the problem is that by default the memory runs "full" speed which is way above specs, as it should be running at 800 MHz max. We need the dmc driver and being able to setup the max clock for the memory to run these boards in good conditions.
-
4 minutes ago, ketominer said:
OK definitely not u-boot related as rc9 and rc10 has the exact same one. So the answer is somewhere in the kernel... digging deeper.
and when browsing the differences between the kernels, I come up with this which looks pretty promising... https://github.com/ayufan-rock64/linux-kernel/commit/063c10147b3cfc326adda195f004b130dbd11ff6 -- scrap that, it's for the 3399 so not related
-
On 5/1/2019 at 10:48 PM, ketominer said:
no luck. I'm starting to wonder if this is all not about something someone mentioned earlier, being that it's the u-boot settings slowing down the RAM that fix the problem...
OK definitely not u-boot related as rc9 and rc10 has the exact same one. So the answer is somewhere in the kernel... digging deeper.
-
2 hours ago, Igor said:
A little. It seems quite a mess. Try kernel below if that makes any difference for you .... I am seeing this weird thingy in the syslogs:
May 1 18:38:25 localhost kernel: [ 1416.059127] zram: Decompression failed! err=-22, page=40
no luck. I'm starting to wonder if this is all not about something someone mentioned earlier, being that it's the u-boot settings slowing down the RAM that fix the problem...
-
3 hours ago, Igor said:
OK. Please provide a link to the working kernel and as much technical information as possible: logs (armbianmonitor -u) with a bad kernel and at least dmesg from a good one.Info from "bad" kernel (freshly updated armbian bionic but it's the same for 6 months):
https://transfer.nodl.it/fJ3wP/armbianmonitor.bad.txt
(used my own transfer side because the one used by default by armbianmonitor -u doesn't show any url after upload)Info from "good" distro (that works on the "bad" boards is):
http://ix.io/1HKS (somehow worked on this one)Distribution used is
bionic-minimal-rock64-0.8.0rc9-1120-arm64.img.xz
from
https://github.com/ayufan-rock64/linux-build/releasesThe kernel is
linux-headers-4.4.167-1169-rockchip-ayufan-g3cde5c624c9c:arm64 install
linux-image-4.4.167-1169-rockchip-ayufan-g3cde5c624c9c:arm64 install
u-boot-rockchip-rock64-2017.09-rockchip-ayufan-1045-g9922d32c04 install
and board package
board-package-rock64-0.8-126 installThis leads to the correct dependencies:
https://github.com/ayufan-rock64/linux-build/releases/download/0.8.0rc9/linux-rock64-0.8.0rc9_arm64.debplease note that the rc10 of ayufan's distro breaks again what rc9 was fixing...
Hope that helps
-
1 hour ago, Igor said:
When you confirm beta kernel is working well for you, I can update main repository and all they will need to do is: apt update && apt upgradeno luck so far, I've updated previous post (maybe not a good thing to do)
-
32 minutes ago, JMCC said:
It's probably a matter of updating Armbian's kernel config to reflect ayufan's changes. I cannot test with Rock64 since I don't have one, just a Renegade.
Probably, I've even got a kernel package from him that "should" work on armbian but I've broken everything trying to install it...
-
39 minutes ago, Igor said:
One very quick fix would be switching to beta repository:
- apt update and upgrade- armbian-config -> switch to nightly beta builds
Kernel in beta repository should be close or identical to Ayufan's latest build ... but its not tested. Its on you to test it. After you switch to beta and if things works as expected, make a freeze (again in armbian-config -> system) and wait until things are properly tested by us and show up in stable repository. Then rather switch back to stable builds.
Regarding board samples we have to discuss who is willing to join this debug party. I only have Rock64, IIRC its v1 with 4G. That will take some time to arrange due to ongoing holidays. I am shortly back to the office tomorrow and can check if I can do anything in this matter - in case suggestion to beta won't do any good.For monetary support please kindly use donate page, where its possible to choose between anonymous PayPal donation and invoice issued/billed to the company. In case you want a combination with publicly known amount and donor (forum) name, use https://forum.armbian.com/subscriptions/
Thank you for your answer, will test the beta very quick and let you know how it goes. I will have to figure out how to safely push that to our users without breaking everything
update: switching to nightly, kernel panic as soon as I run my test program (simple argon2i hashing test + stress-ng running in the background, it tends to be easier to trigger under load on some boards)
(also subcription done, hopefully moving to the biggest one when we can). Let me know if you want the full test protocol along with some boards.
-
Hi,
We are using hundreds of Rock64 boards for a project and we are facing a lot of unreliabilities due to the kernel Armbian is currently using. After long discussions with Lukasz, Kamil, and Pine64 support, we concluded that some kernel fixes are necessary to have a reliable operation. These fixes are available for example in Ayufan's rc9 bionic distribution and all the boards that fail with armbian (it goes from kernel crash at boot to just some subtle miscalculations during some FPU operations) work perfectly well with his kernel.
We are ready to support Armbian by providing v2 and v3 Rock64 4GB boards as well as a monetary support to get a kernel update as quick as possible to "un-brick" the 50-60 boards we currently can't use (and to avoid having to switch to another distribution).
Please let us now if you're interested and how we could arrange that.
RK3328 Kernel
in Tinkerboard
Posted
out of 300 boards, I have about 25 % garbage that doesn't support any kind of heavy workload