search

ayufan-rock64 / linux-build

Rock64 Linux build scripts, tools and instructions
MIT License
562 stars 98 forks source link

After update to 0.6.53 Rock64 no longer booting #219

Open spryroX opened 6 years ago

spryroX commented 6 years ago

Rock64 was working great on 4.4.120-rockchip-ayufan-213

Then updated by doing sudo apt-get dist-upgrade and now I can't seem to boot anymore. Please help since I was stupid enough not to make a backup pre-update.

DDR version 1.08 20170628
In
LPDDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT

U-Boot SPL 2017.09-ga0a2b48 (Apr 02 2018 - 16:01:39)
setup_ddr_param  1
booted from eMMC
Trying to boot from MMC1
NOTICE:  BL31: v1.3(debug):9d3f591
NOTICE:  BL31: Built : 14:39:02, Jan 17 2018
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initia_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmutime services
WARNING: No OPTEE provided by BL2 boot loader, Boed for OPTEE will return SMC_UK
ERROR:   Error initializing ru EL3 exit to normal world
INFO:    Entry point address = 0x2000

U-Boot 2017.09-ga0a2b48 (Apr 02 2018 - 16:01:54 +0000), Build: jenkins-linux-bu9

Model: Pine64 Rock64
DRAM:  4 GiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
Card did not respond to voltage select!
mmc_init: -95, time 9
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b50303930303900000000120918
serial=fdb482d7dd1a1b6
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:6...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
688 bytes read in 3 ms (223.6 KiB/s)
select kernel
1:      kernel-latest
2:      kernel-previous
Enter choice: 1:        kernel-latest
Retrieving file: /initrd.img
reading /initrd.img
6677437 bytes read in 810 ms (7.9 MiB/s)
Retrieving file: /Image
reading /Image
18995208 bytes read in 2299 ms (7.9 MiB/s)
append: rw root=LABEL=linux-root rootwait rootfstype=ext4 panic=10 init=/sbin/ib
reading /dtb
56836 bytes read in 10 ms (5.4 MiB/s)
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to fc8a3000, end fcf013bd ... OK
   Loading Device Tree to 00000000fc892000, end 00000000fc8a2e03 ... OK

Starting kernel ...

After this nothing happens, Rock64 is stuck

spryroX commented 6 years ago

If I select previous kernel during boot process the Rock64 boots again, did I do something wrong in the kernel upgrade process?

sudo uname -a 
Linux rock64 4.4.120-rockchip-ayufan-213 #1 SMP Sun Apr 29 20:27:33 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

Here is the log from updating:

sudo apt-get dist-upgrade

Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-4.4.126-rockchip-ayufan-260 linux-image-4.4.126-rockchip-ayufan-260
The following packages will be upgraded:
  dirmngr gnupg gnupg-agent gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv imagemagick imagemagick-6-common
  imagemagick-6.q16 libmagickcore-6.q16-3 libmagickwand-6.q16-3 linux-libc-dev linux-rock64 linux-rock64-package u-boot-rock64
21 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 30.3 MB of archives.
After this operation, 141 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 imagemagick-6-common all 8:6.9.7.4+dfsg-16ubuntu6.2 [61.5 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 libmagickcore-6.q16-3 arm64 8:6.9.7.4+dfsg-16ubuntu6.2 [1456 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 libmagickwand-6.q16-3 arm64 8:6.9.7.4+dfsg-16ubuntu6.2 [243 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gpg-wks-client arm64 2.2.4-1ubuntu1.1 [76.6 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 dirmngr arm64 2.2.4-1ubuntu1.1 [275 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gnupg-utils arm64 2.2.4-1ubuntu1.1 [108 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gpg-wks-server arm64 2.2.4-1ubuntu1.1 [71.6 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gpg-agent arm64 2.2.4-1ubuntu1.1 [190 kB]
Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gpg arm64 2.2.4-1ubuntu1.1 [400 kB]
Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gpgconf arm64 2.2.4-1ubuntu1.1 [106 kB]
Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gnupg-l10n all 2.2.4-1ubuntu1.1 [49.5 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gnupg arm64 2.2.4-1ubuntu1.1 [249 kB]
Get:13 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases  linux-headers-4.4.126-rockchip-ayufan-260 0.6.53 [10.3 MB]
Get:14 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gpgsm arm64 2.2.4-1ubuntu1.1 [182 kB]
Get:15 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 gpgv arm64 2.2.4-1ubuntu1.1 [166 kB]
Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 gnupg-agent all 2.2.4-1ubuntu1.1 [4868 B]
Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 imagemagick-6.q16 arm64 8:6.9.7.4+dfsg-16ubuntu6.2 [424 kB]
Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 imagemagick arm64 8:6.9.7.4+dfsg-16ubuntu6.2 [14.2 kB]
Get:19 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases  linux-image-4.4.126-rockchip-ayufan-260 0.6.53 [13.2 MB]
Get:20 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases  linux-libc-dev 4.17.0-rc6-1019-ayufan [959 kB]
Get:21 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases  linux-rock64 0.6.53 [1112 B]
Get:22 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases  linux-rock64-package 0.6.53 [1308 kB]
Get:23 http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases  u-boot-rock64 0.6.53 [365 kB]
Fetched 30.3 MB in 12s (2510 kB/s)
(Reading database ... 112694 files and directories currently installed.)
Preparing to unpack .../00-imagemagick-6-common_8%3a6.9.7.4+dfsg-16ubuntu6.2_all.deb ...
Unpacking imagemagick-6-common (8:6.9.7.4+dfsg-16ubuntu6.2) over (8:6.9.7.4+dfsg-16ubuntu6) ...
Preparing to unpack .../01-libmagickcore-6.q16-3_8%3a6.9.7.4+dfsg-16ubuntu6.2_arm64.deb ...
Unpacking libmagickcore-6.q16-3:arm64 (8:6.9.7.4+dfsg-16ubuntu6.2) over (8:6.9.7.4+dfsg-16ubuntu6) ...
Preparing to unpack .../02-libmagickwand-6.q16-3_8%3a6.9.7.4+dfsg-16ubuntu6.2_arm64.deb ...
Unpacking libmagickwand-6.q16-3:arm64 (8:6.9.7.4+dfsg-16ubuntu6.2) over (8:6.9.7.4+dfsg-16ubuntu6) ...
Preparing to unpack .../03-gpg-wks-client_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gpg-wks-client (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../04-dirmngr_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking dirmngr (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../05-gnupg-utils_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gnupg-utils (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../06-gpg-wks-server_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gpg-wks-server (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../07-gpg-agent_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gpg-agent (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../08-gpg_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gpg (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../09-gpgconf_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gpgconf (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../10-gnupg-l10n_2.2.4-1ubuntu1.1_all.deb ...
Unpacking gnupg-l10n (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../11-gnupg_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gnupg (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../12-gpgsm_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gpgsm (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../13-gpgv_2.2.4-1ubuntu1.1_arm64.deb ...
Unpacking gpgv (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Setting up gpgv (2.2.4-1ubuntu1.1) ...
(Reading database ... 112694 files and directories currently installed.)
Preparing to unpack .../0-gnupg-agent_2.2.4-1ubuntu1.1_all.deb ...
Unpacking gnupg-agent (2.2.4-1ubuntu1.1) over (2.2.4-1ubuntu1) ...
Preparing to unpack .../1-imagemagick-6.q16_8%3a6.9.7.4+dfsg-16ubuntu6.2_arm64.deb ...
Unpacking imagemagick-6.q16 (8:6.9.7.4+dfsg-16ubuntu6.2) over (8:6.9.7.4+dfsg-16ubuntu6) ...
Preparing to unpack .../2-imagemagick_8%3a6.9.7.4+dfsg-16ubuntu6.2_arm64.deb ...
Unpacking imagemagick (8:6.9.7.4+dfsg-16ubuntu6.2) over (8:6.9.7.4+dfsg-16ubuntu6) ...
Selecting previously unselected package linux-headers-4.4.126-rockchip-ayufan-260.
Preparing to unpack .../3-linux-headers-4.4.126-rockchip-ayufan-260_0.6.53_arm64.deb ...
Unpacking linux-headers-4.4.126-rockchip-ayufan-260 (0.6.53) ...
Selecting previously unselected package linux-image-4.4.126-rockchip-ayufan-260.
Preparing to unpack .../4-linux-image-4.4.126-rockchip-ayufan-260_0.6.53_arm64.deb ...
Unpacking linux-image-4.4.126-rockchip-ayufan-260 (0.6.53) ...
Preparing to unpack .../5-linux-libc-dev_4.17.0-rc6-1019-ayufan_arm64.deb ...
Unpacking linux-libc-dev (4.17.0-rc6-1019-ayufan) over (4.17.0-rc6-1017-ayufan) ...
Preparing to unpack .../6-linux-rock64_0.6.53_arm64.deb ...
Unpacking linux-rock64 (0.6.53) over (0.6.34) ...
Preparing to unpack .../7-linux-rock64-package_0.6.53_all.deb ...
Unpacking linux-rock64-package (0.6.53) over (0.6.34) ...
Preparing to unpack .../8-u-boot-rock64_0.6.53_all.deb ...
Unpacking u-boot-rock64 (0.6.53) over (0.6.34) ...
Setting up imagemagick-6-common (8:6.9.7.4+dfsg-16ubuntu6.2) ...
Setting up libmagickcore-6.q16-3:arm64 (8:6.9.7.4+dfsg-16ubuntu6.2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Setting up u-boot-rock64 (0.6.53) ...
Consider upgrading device bootloader with 'rock64_upgrade_bootloader.sh'.
Setting up gpgconf (2.2.4-1ubuntu1.1) ...
Setting up linux-libc-dev (4.17.0-rc6-1019-ayufan) ...
Setting up gpg-agent (2.2.4-1ubuntu1.1) ...
Setting up gnupg-l10n (2.2.4-1ubuntu1.1) ...
Setting up linux-headers-4.4.126-rockchip-ayufan-260 (0.6.53) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up gpgsm (2.2.4-1ubuntu1.1) ...
Setting up libmagickwand-6.q16-3:arm64 (8:6.9.7.4+dfsg-16ubuntu6.2) ...
Setting up gnupg-utils (2.2.4-1ubuntu1.1) ...
Setting up linux-rock64-package (0.6.53) ...
Installing new version of config file /boot/efi/extlinux/extlinux.conf ...
Processing triggers for man-db (2.8.3-2) ...
Setting up gnupg-agent (2.2.4-1ubuntu1.1) ...
Setting up dirmngr (2.2.4-1ubuntu1.1) ...
Setting up linux-image-4.4.126-rockchip-ayufan-260 (0.6.53) ...
update-initramfs: Generating /boot/initrd.img-4.4.126-rockchip-ayufan-260
Warning: root device  does not exist
I: The initramfs will attempt to resume from /dev/zram3
I: (UUID=cef349cb-7f46-4538-8dd8-9f1757bf556c)
I: Set the RESUME variable to override this.
Using DTB: rockchip/rk3328-rock64.dtb
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb
Installing new rk3328-rock64.dtb.
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
flash-kernel: deferring update (trigger activated)
Using DTB: rockchip/rk3328-rock64.dtb
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
flash-kernel: deferring update (trigger activated)
Processing triggers for hicolor-icon-theme (0.17-2) ...
Setting up linux-rock64 (0.6.53) ...
Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
Setting up gpg (2.2.4-1ubuntu1.1) ...
Setting up imagemagick-6.q16 (8:6.9.7.4+dfsg-16ubuntu6.2) ...
Setting up gpg-wks-server (2.2.4-1ubuntu1.1) ...
Setting up gpg-wks-client (2.2.4-1ubuntu1.1) ...
Setting up imagemagick (8:6.9.7.4+dfsg-16ubuntu6.2) ...
Setting up gnupg (2.2.4-1ubuntu1.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for flash-kernel (3.92) ...
Using DTB: rockchip/rk3328-rock64.dtb
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-260/rockchip/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
flash-kernel: installing version 4.4.126-rockchip-ayufan-260
Taking backup of Image.
Installing new Image.
Taking backup of initrd.img.
Installing new initrd.img.
Taking backup of dtb.
Installing new dtb.
jerryfudd commented 6 years ago

Hi,

I believe the Rock64 build is very customised so when I also did 'sudo apt-get dist-upgrade' I was fully expecting it to fail - and as you found, it did.

I then re-imaged the SD card and found anything newer than 'jessie-openmediavault-rock64-0.5.15-136-arm64.img' wouldn't boot (see this thread -> https://github.com/ayufan-rock64/linux-build/issues/215)

Just because OMV doesn't boot I wouldn't have thought it would have effected any of the data stored on any external USB drives. I would have thought you'd just need to cautiously re-prepare your Rock64's SD card and then configure to your existing drive. That said I'm only going on what I'd expect the situation to be.

Also, if you have access to a PC you could try a live boot Ubuntu USB and then try and access your data that way... if you prepared it via OMV it should just be EXT4.

Dan

spryroX commented 6 years ago

@jerryfudd , as I mentioned in my second post I got my system up and running again (no data loss) by selecting the "previous kernel" on boot (you have to be very quick).

This way I was able to get ayufan's new version of the OS to boot with the previous kernel I had installed (which was Linux rock64 4.4.120-rockchip-ayufan-213 #1 SMP Sun Apr 29 20:27:33 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux)

DDR version 1.08 20170628
In
LPDDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT

U-Boot SPL 2017.09-ga0a2b48 (Apr 02 2018 - 16:01:39)
setup_ddr_param  1
booted from eMMC
Trying to boot from MMC1
NOTICE:  BL31: v1.3(debug):9d3f591
NOTICE:  BL31: Built : 14:39:02, Jan 17 2018
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initia_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmutime services
WARNING: No OPTEE provided by BL2 boot loader, Boed for OPTEE will return SMC_UK
ERROR:   Error initializing ru EL3 exit to normal world
INFO:    Entry point address = 0x2000

U-Boot 2017.09-ga0a2b48 (Apr 02 2018 - 16:01:54 +0000), Build: jenkins-linux-bu9

Model: Pine64 Rock64
DRAM:  4 GiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
Card did not respond to voltage select!
mmc_init: -95, time 9
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b50303930303900000000120918
serial=fdb482d7dd1a1b6
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:6...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
688 bytes read in 3 ms (223.6 KiB/s)
select kernel
1:      kernel-latest
2:      kernel-previous

**Quickly press 2 here and it should boot with the previously working kernel**

It's strange though that you aren't able to boot without anything later than 'jessie-openmediavault-rock64-0.5.15-136-arm64.img', becuase I've been running the 0.6 version of Ubuntu for months (and I think I've also tried the OMV image, but not sure which version).

You don't also have an eMMC module plugged in by any chance do you? I've ran into some issues myself when tinkering with SD card images while having the emmc also plugged in with another image/kernel combo. For some reason it would always pick the kernel from the emmc making a lot of images I burnt to sdcards not work (because they required matching kernels).

phinxy commented 6 years ago

The version 0.6.38 is working well for me. It's the 4.4.126 kernel. The very latest version is not booting, or has no hdmi, for me either. There are probably later versions that work as well but I have been sitting on this one because issues started to appear. At the moment Ayufan seems to be focusing on RockPro.

pfeerick commented 6 years ago

@phinxy I think all kernel builds post 0.6.44 will fail on the rock64 as there is a bug that was brought in in the last rebase from the rockchip kernel which has been subsequently fixed but there hasn't been another rebase to bring in that fix. (IIRC from the forum thread where this was mentioned the fix was from around 3rd of June - it was just bad timing - a day or so later and it wouldn't have been an issue).

@spryroX Boot priority is eMMC before SD, so if you have both connected and eMMC is bootable, SD will lose the race every time. Hence the need to disconnect it or use the disable jumper if you're using the SD card for testing.

spryroX commented 6 years ago

@pfeerick, I think in my case it actually was loading the image from the sdcard and the kernel from the emmc. (I know this doesn't make sense)

I had a working install on emmc that I didn't want to screw up, so I tried loading a few different images to play around with other distro's. At first trying newer version of ayufans Ubuntu. I already noticed that for some reason I was unable to install a different kernel with these images. I would install a new kernel, but after a reboot the original kernel would still be there (from my original emmc image). I only put 2+2 together after trying to boot armbian, and not getting the image to boot at all. Then at some point I took out the emmc, and bam, same image that wouldn't boot before now booted. (Btw, even by using the jumper to boot from sdcard it would load the kernel from emmc)

This was a few months ago and haven't tried since, but it took me quite a while to figure out what was going wrong.

spryroX commented 6 years ago

I tried installing 0.6.44 as @pfeerick mentioned but now I also cannot boot anymore using previous kernel. Trying to figure out how to boot the rock64 4.4.120-rockchip-ayufan-213 kernel from uboot again. If anyone can point me in the right direction it will be much appreciated.

pfeerick commented 6 years ago

Entirely possible. uboot, kernel and initrd could have been coming from the eMMC, and then the root file system from the SD card. As mentioned on the forum thread, you can either edit the file via the fat partition on another machine (including on windows), or boot from another SD card, mount the eMMC fat / /boot partition, and copy the files across.

karlskewes commented 6 years ago

Thanks @pfeerick , I was wondering why my rock64's weren't booting new kernel (from SSD) and after removing eMMC they did (I had already done SPI flash).

kdg3737 commented 5 years ago

Setting emmc max frequency from 200 to 150MHz in the .dtb solved this (or a similar) issue for me.