6 6
TonyMac32

RK3328 Kernel

Recommended Posts

1 minute ago, ketominer said:

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


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 upgrade

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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...

Share this post


Link to post
Share on other sites
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 upgrade

no luck so far, I've updated previous post (maybe not a good thing to do)

Share this post


Link to post
Share on other sites
4 minutes ago, ketominer said:

no luck so far, I've updated previous post (maybe not a good thing to do)


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.

Share this post


Link to post
Share on other sites
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/releases

 

The 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                    install

 

This leads to the correct dependencies:
https://github.com/ayufan-rock64/linux-build/releases/download/0.8.0rc9/linux-rock64-0.8.0rc9_arm64.deb

 

please note that the rc10 of ayufan's distro breaks again what rc9 was fixing...

 

Hope that helps :)
 

Share this post


Link to post
Share on other sites

Another idea for test - start from a stable repository or new image and use oldest kernel we have in repository -> armbian-config -> system -> alternative kernels.

Share this post


Link to post
Share on other sites
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
 

linux-image-rockchip64_5.83_arm64.deb

linux-dtb-rockchip64_5.83_arm64.deb

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...

 

https://transfer.nodl.it/4bgnD/armbianmonitor.txt

Share this post


Link to post
Share on other sites
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...

 

https://transfer.nodl.it/4bgnD/armbianmonitor.txt

 

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.

Share this post


Link to post
Share on other sites
(edited)
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 :(

Edited by ketominer

Share this post


Link to post
Share on other sites
On 5/1/2019 at 10:52 AM, ketominer said:

These fixes are available for example in Ayufan's rc9 bionic distribution and all the boards that fail with armbian   work perfectly well with Ayufan kernel.

Let's go back to your original point, above. Can you reproduce the situation where everything works?

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
6 6