Kernel crashes Raspberry PI 3B+
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
flash-kernel (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
[sudo] password for astroberry:
root@astroberry
Setting up flash-kernel (3.103ubuntu1~
Using DTB: bcm2710-
Installing /etc/flash-
Taking backup of bcm2710-
Installing new bcm2710-
ln: failed to create symbolic link '/boot/
dpkg: error processing package flash-kernel (--configure):
installed flash-kernel package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
flash-kernel
Raspberry PI says this is an UBUNTU problem. Ubuntu says this is a Raspberry PI issue.
This is the bug.
'/boot/
/boot/dtb
/boot/dtb-1
/boot/dtb-
cannot be written into. They are all empty.
I have multiple Linux machines. This is the only one which fails to install Flash Kernel since Nov 20, 2020.
root@astroberry
total 20
drwxr-xr-x 2 root root 4096 Sep 2 2020 .
drwxr-xr-x 11 root root 16384 Dec 31 1969 ..
root@astroberry
total 20
drwxr-xr-x 2 root root 4096 Oct 20 2019 .
drwxr-xr-x 11 root root 16384 Dec 31 1969 ..
root@astroberry
total 20
drwxr-xr-x 2 root root 4096 Apr 22 22:54 .
drwxr-xr-x 11 root root 16384 Dec 31 1969 ..
These folders are empty. Nothing can be copied into them
1.
root@astroberry
Description: Ubuntu 20.10
Release: 20.10
2.
root@astroberry
N: Unable to locate package pkgname
root@astroberry
3.
Installation of Flash Kernel.
4.
Failed. Dows not install properly. Prevents other installations from completing.
The Raspberry Pi company are certainly correct that this would be an Ubuntu / Debian issue (RaspiOS né Raspbian doesn't use flash-kernel to install its kernel on the boot partition). However, the "/boot/dtb-" link is worrying (after the dash should come a kernel version) and suggests something rather more serious is amiss.
Can I ask which Ubuntu image you're using specifically, and exactly how it's installed? (the fact that f-k is complaining about "operation not permitted" when it's running as root suggests something like a boot partition being mounted read-only).