Jump to content

RockPro64 kernel v5.4 doesn't boot on eMMC (while kernel v4.4 does)

Baptiste

By Baptiste
in Pine RockPro64

 Share

Recommended Posts

Baptiste

Baptiste

Posted
Posted

Hi,

 

I have had some issues trying to boot from eMMC with the last version of Armbian (kernel v5.4) while it's working perfectly on Armbian with a v4.4 kernel.

 

Images not working:

https://dl.armbian.com/rockpro64/archive/Armbian_20.05.2_Rockpro64_bionic_current_5.4.43.img.xz

https://dl.armbian.com/rockpro64/archive/Armbian_20.05.4_Rockpro64_focal_current_5.4.46.img.xz

 

Working image:

https://dl.armbian.com/_old/rockpro64/archive/Armbian_5.98_Rockpro64_Debian_buster_default_4.4.192.7z

 

I though I messed up with the SPI or the eMMC card but after trying all I could, it finally worked using an old version of Armbian.

 

The new images are working on a SD-Card but it's much slower to boot.

 

On a eMMC card it get completely stuck (see attached file),  I managed to get the "Done" displayed waiting much longer (just after the "Running /scripts/local-premount" step but nothing more).

 

The CPU is becoming super hot while it stuck.

 

I have the same issue on two different RockPro64 cards and with two different eMMC cards.

 

I have tried the "Disable SPI while booting" step but it didn't help:

https://wiki.pine64.org/index.php/ROCKPro64#Disable_SPI_.28while_booting.29

 

It would be great if I could have a kernel 5.4 running on eMMC on those cards, please let me know if I can help.

 

Kind regards,

Baptiste

boot-fail.jpeg

0
NicoD

NicoD

Posted
Posted

Could you try pulling out the HDMI cable and wait a few seconds?
It is a known problem. It is fixed in later kernels. Once booted you can update the kernel with armbian-config -> system -> other
 

0
Baptiste

Baptiste

Posted
  • Author
Posted (edited)

I have tried that but the card never appeared on the network, but I just gave another try (being much more patient) and it worked, thank you for the advice!

 

BUT even after an update it's taking ages (around 4 minutes) to boot and the CPU get super warm (52 degres Celcius instead of 44 degres for another running server):

 

  Reveal hidden contents

 

I guess I will have to stick with the 4.4 kernel for now :-/

 

It takes only 38 seconds on the 4.4 vs 200s for the 5.4.

 

Here are the 4.4 logs:

 

  Reveal hidden contents

 

 

Edited by TRS-80
put long output inside spoiler
0
piter75

piter75

Posted
Posted
  On 7/27/2020 at 8:25 PM, baptiste said:

It takes only 38 seconds on the 4.4 vs 200s for the 5.4.

Expand  

This is a known issue with rk3399 boards using mainline kernel and it was mitigated for all other boards using mainline u-boot some time ago.

RockPro64 is the last one that is uses u-boot v2017.09 but I am planning to switch it to mainline for the next Armbian release (v20.11).

For now you need to either be patient or stay with 4.4.y.

1
Local Containers

Local Containers

Posted
Posted

I'm having this issue, and sadly it seems like for my use case I need the newer Linux kernel (some Docker images).

Currently I'm getting the behaviour as follows.

Micro SD

Debian 4.4.y - boots
Debian 5.10.y - boots
 

eMMC

Debian 4.4.y - boots
Debian 5.10.y - blank screen never even seen any boot logs

I do hope this gets fixed in the future as I would like to keep using my eMMC module but I know the Armbian team doesn't get paid and sadly the Pine64 team does not do any software support (sadly I've made the mistake of buying from them twice now). When the NAS box works it is good but there is just so much trial and error to get to a working and supported Linux going on it. 😞

0
MisterDark

MisterDark

Posted
Posted

I seem to have the same problem. Is there no fix for this?

I'm trying to boot from eMMC with the latest release but the board doesn't boot. I'm getting the same behaviour as shown on the photo in the first post of this thread.

0
ssspeq

ssspeq

Posted
Posted

Is this issue resolved? I have a rockpro64 booting from emmc on armbian 10, running stuff I really need. I would like to upgrade it, but I don't dare to do that unless this issue is resolved. Does anyone know?

0
denni_isl

denni_isl

Posted
Posted

This error was common on my nanopim4v2 and i did have to start it manually all the time.  Did fix it by adding

rootdelay=5 in /boot/armbianEnv.txt and with the help of serial adapter did  apply this method to u-boot. 

Stop u-boot, printenv (inspecting),  setenv bootdelay 5, saveenv (printenv to see if bootdelay shanged), reset.  

 

Side issue.  The gparted icon did not start gparted on "Armbian 22.02.1 Focal with Linux 5.15.25-rockchip64" rockpro64.   Installing poicykit-1-gnome did fix that after reboot.   Now it ask for password while starting.

 

0

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.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept