canNOT boot after a normal apt upgrade
#1
The latest upgrade push kernel 4.4.126 and crash Rock64 when reboot.

By using serial cable, there is a short moment that user can select to boot from the previous kernel (the lovely stable 4.4.77).  So, be claim, everything is still there, I believe.

Unfortunately, seems that there is no hope for pure ssh remote control boxes.

Anyway, any elite kind enough to post a know-how on how to change the default boot order specifically for Rock64 on this forum.

Thank you


p.s.  if possible, also a know-how to prevent the kernel from being updated automatically.

the 1st know-how

$ sudo vi /boot/efi/extlinux/extlinux.conf

change the 2nd line from
default kernel-latest
to
default kernel-previous
  Reply
#2
2nd know-how
tested work on a fresh burnt sdcard with 4.4.77

rock64@rock64:~$ sudo apt-cache showpkg linux-image
Code:
Package: linux-image
Versions:

Reverse Depends:
  firmware-crystalhd,linux-image
Dependencies:
Provides:
Reverse Provides:
linux-image-4.4.77-rockchip-ayufan-136 0.5.15 (= )
linux-image-4.4.77-rockchip-ayufan-118 0.5.10 (= )
linux-image-4.4.77-rockchip-ayufan-104 0.5.9 (= )
linux-image-4.4.77-rockchip-ayufan-102 0.5.8 (= )
linux-image-4.4.71-rockchip-ayufan-77 0.4.12 (= )
linux-image-4.4.70-rockchip-ayufan-85 0.4.17 (= )
linux-image-4.4.70-rockchip-ayufan-83 0.4.16 (= )
linux-image-4.4.70-rockchip-ayufan-66 0.4.3 (= )
linux-image-4.4.70-rockchip-ayufan-62 0.3.7 (= )
linux-image-4.4.70-rockchip-ayufan-57 0.3.4 (= )
linux-image-4.4.70-rockchip-ayufan-55 0.3.3 (= )
linux-image-4.4.70-rockchip-ayufan-54 0.3.2 (= )
linux-image-4.4.70-ayufan-29 0.2.1 (= )
linux-image-4.4.70-ayufan-28 0.2.0 (= )
linux-image-4.4.126-rockchip-ayufan-227 0.6.41 (= )
linux-image-4.4.126-rockchip-ayufan-226 0.6.40 (= )

rock64@rock64:~$ sudo apt-mark hold linux-image-4.4.126-rockchip-ayufan-227 linux-image-4.4.126-rock
chip-ayufan-226
Code:
linux-image-4.4.126-rockchip-ayufan-227 set on hold.
linux-image-4.4.126-rockchip-ayufan-226 set on hold.

Run "apt upgrade" and you'll see that 4.4.126 is gone.

However, some people said this method induce instability due to rapid changes on all packages. So, you are warned.
  Reply
#3
I can confirm that with the latest kernel update the system hangs at boot.
Getting back to previous kernel it runs again without issues.

That's a big issue though


On the other hand the hold command you wrote did not worked for me.

I set on hold the packages
linux-rock64
linux-rock64-package
at version 0.5.15

that avoid my kernel to be upgraded

I'm using the Xenial minimal image on SD
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  How to boot an older, working kernel bits 0 111 11-01-2024, 04:43 PM
Last Post: bits
  problem with debian emmc boot G4zCDzWb 10 1,789 11-01-2024, 04:32 PM
Last Post: bits
  arch rock64 does not boot nemnob 1 998 09-20-2024, 11:18 AM
Last Post: AwU2HBg
  Rock64 won't boot dstallmo 0 658 12-27-2023, 10:34 AM
Last Post: dstallmo
  Disabling last mount time check on boot acwest 0 886 03-03-2023, 09:24 PM
Last Post: acwest
  Swap/Upgrade Storage Device? r00t3d 0 899 08-17-2022, 06:11 AM
Last Post: r00t3d
  Rock64 Rev3 doesn't boot and leds blinking fast dishins 6 8,905 06-30-2022, 06:28 PM
Last Post: rookie_267
  my rock64 can't boot rookie_267 0 1,312 06-27-2022, 06:52 PM
Last Post: rookie_267
  Setting a MAC on Rock64 U-Boot kiriakos 2 4,134 03-23-2021, 04:51 AM
Last Post: kiriakos
  Boot from USB 3.0 with hub Turbo 0 2,357 12-20-2020, 02:24 PM
Last Post: Turbo

Forum Jump:


Users browsing this thread: 1 Guest(s)