Recommended Posts

I got fooled by their documentation which mentioned a way to reset clock of eMMC to enter maskroom but then I couldn't erase it.. @piter75 wrote how he did it with the buttons so that I'm soon ready to test it.

I've the patches for integrating it into rockchip64 family (u-boot and 4v4 kenel) laying around since days.. (if we will base it on nanopi m4v2 we would have to change them a bit cause different bsp kernel and u-boot) but not tested cause the stock firmware didn't try do boot SD card for me. Will be tested once pinebooks display doesn't fool me anymore.. btw @TonyMac32 I might switch to upstram 2020 u-boot with the pinebook if you don't mind.

Share this post

Link to post

Share on other sites

No complaints from me, once I get kernel hell straightened out on renegade and friends I want to circle around and u-boot 2020 the tinker as well, and I might see if the MiQi will survive it, it seemed to dislike 2018+ last time ...

Share this post

Link to post

Share on other sites

BTW, about PinebookPro display issue, to make sure it is not a u-boot related issue, I've took the working 4.4.198 image, and I've copied the 5.4.13 into same SDCard, and switched the symbolic links in /boot back and forth between 4.4.198 and 5.4.13, and the issue is present only in latest one, confirming that it is not u-boot related ...

Share this post

Link to post

Share on other sites

it could still be u-boot related.. I'm not sure how pwm works in mainline.. Could be that there's a difference between mainline and BSP kernel. Well I guess I've to dive into Tobias mainline kernel deeper to figure out what goes wrong here.. A diff off his defconfig compared to a defconfig based on our .config didnd't show any obvious oddity.

Share this post

Link to post

Share on other sites

well I'll fire up the pinebook now with the rk3399 4.4 kernel (e.g. integrate it into friendly arms fork) and see if this works. If that works we would at least have 4.4 and likely @JMCC multimedia stuff working. I don't get why the driver doesn't even try to probe the display.. so something must be fishy here.. Someone would then need to test if this works with stock image on eMMC cause I removed eMMC and I don't want to open and close the pinebook for a 100 times during development (I don't see a reason for not, but I didn't expect the display fooling me that hard either).

Share this post

Link to post

Share on other sites

...is the legacy kernel not working with display right now? My last build did...

well having it in rk3399 means we swap to friendly elecs 4.4 kernelfork.. First attempt display backlight fired up but no display output (well I know the reason I just forgot to patch panel-simple).. and a few bits here and there might be needed as well (at least I found out about one).

Share this post

Link to post

Share on other sites

I saw this on my RK3328 boards, but it's now been reported on Allwinner as well, the recent libdrm updates are killing our display manager. As soon as I update my image the menus and things are no longer displaying properly, things are missing, invisible, etc. lima related perhaps?

Share this post

Link to post

Share on other sites

So looks like no solution. Older than 1.20 xserver could be configured, but the mesa 19.1 lima support is no good for xfce. Lima more or less needs shut off on Bionic, I haven't gotten too far on looking at Buster.

I will now try building an 5.5.0-rc7 and try again, but for now maybe I should also try to disable the "snd_soc" ...

EDIT: Disabling the "rt5651" node in DT bypassed the crash, it reach the "Welcome to Debian GNU/Linux 10 (buster)!", but no login prompt ! Rebooting again, it didn't reach the same place : I think it is thermal issue, because my board doesn't have heatsink, and RK3399 is barely touchable ... Let's cool it and I will try the 5.5.0-rc7 build when finished ...

Share this post

Link to post

Share on other sites

I verified the 1.5 GHz operating point for rk3328, had forgotten where the max frequency variable was set. The default is 1.3 GHz max, can be set by the user to 1.5. we are missing a 1.4 GHz operating point though.

Share this post

Link to post

Share on other sites

What ever I try to boot, either CURRENT, DEV, or preview 5.5.0-rc7, I get the "Welcome to Debian GNU/Linux 10 (buster)!", but always end up with a freeze with "[ 56.562910] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument"...