+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88)
+--- Thread: Arch Linux Arm --> Kernel 5.8 breaks installation (/showthread.php?tid=10999)
Pages:
1
2
RE: Arch Linux Arm --> Kernel 5.8 breaks installation - t4_4t - 08-12-2020
https://archlinuxarm.org/platforms/armv8/rockchip/rock64
The board I tried this time is Ver2, and I am practicing the above faithfully.
Confirmation is for SD-CARD only, not confirmed for eMMC.
Below, I will write only the main points.
Code:
---
37171712 bytes read in 1798 ms (19.7 MiB/s) <= "Image"
50174 bytes read in 40 ms (1.2 MiB/s) <= "rk3328-rock64.dtb"
8339435 bytes read in 419 ms (19 MiB/s) <= "initramfs-linux.img"
...
printenv
kernel_addr_r=0x02000000
ramdisk_addr_r=0x04000000
scriptaddr=0x00500000
fdt_addr_r=0x01f00000kernel_addr_r: 0x02000000 + 37171712 => 0x04373200
ramdisk_addr_r: 0x04000000
It overlaps with the kernel area, it is natural that it does not work.
I fixed it to ramdisk_addr_r = 0x06000000 as a trial.
As a result, it boot with only this fix.
---
Try adding the following one-line and rebuilding "boot.src" .
Code:
part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs console=ttyS2,1500000 root=PARTUUID=${uuid} rw rootwait earlycon=uart8250,mmio32,0xff130000
setenv fdtfile rockchip/rk3328-rock64.dtb
setenv ramdisk_addr_r 0x06000000 <= AppendeMMMC has the same problem (at least it can't boot),
But I'm not sure if this is the only problem.
For eMMC, please check by yourself.
---
Thanks, m.bakhterev
I own four boards, but this is the only one that hasn't stabilized at 800MHz.
Under heavy load conditions such as Kernel-Build, and under heavy load fluctuations,
an error occurs with a high probability.
Well, this one is a disappointing board.
RE: Arch Linux Arm --> Kernel 5.8 breaks installation - tomarm - 08-18-2020
Thanks t4_4t for posting this fix. It worked on my v2. Where did you get this fix (link pls) and is it to be kept perm or temp ?
I have latest arch rock u-boot and fully upgraded. No other changes to stock install made here.
PS Arch arm post says a recompile of current u-boot works too
RE: Arch Linux Arm --> Kernel 5.8 breaks installation - as365n4 - 08-31-2020
From the alarm device page:
Quote:wget http://os.archlinuxarm.org/os/rockchip/boot/rock64/rksd_loader.img
wget http://os.archlinuxarm.org/os/rockchip/boot/rock64/u-boot.itb
dd if=rksd_loader.img of=/dev/sdX seek=64 conv=notrunc
dd if=u-boot.itb of=/dev/sdX seek=16384 conv=notrunc
But just "re-flashing" these 2 files won't work from my experience, I had to setup my Rock64 from scratch again as I have not the knowledge on how to compile and install u-boot from source.