groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure):
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
flash-kernel (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On Groovy arm64 running on Raspberry Pi 4B,
apt-get install flash-kernel fails with the following message
root@ubuntu:~# apt-get install flash-kernel
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
flash-kernel
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/35.1 kB of archives.
After this operation, 206 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package flash-kernel.
(Reading database ... 63789 files and directories currently installed.)
Preparing to unpack .../flash-
Unpacking flash-kernel (3.100ubuntu2) ...
Setting up flash-kernel (3.100ubuntu2) ...
Creating config file /etc/default/
flash-kernel: deferring update (trigger activated)
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for flash-kernel (3.100ubuntu2) ...
Unsupported platform.
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
E: Sub-process /usr/bin/dpkg returned an error code (1)
description: | updated |
tags: | added: raspi |
summary: |
- groovy arm64: Unsupported platform. dpkg: error processing package + groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure): |
I suspect this was down to one of the newer revisions of the Pi board (the rev 1.4 4B?) appearing during the cycle.
This was fixed at some point during the Groovy release though, firstly by adding the explicit "rev 1.4" entry, and later by adding the "Raspberry Pi *" wildcard entry (in 3.100ubuntu3). I'll set this to "Fix Released" but if you're still having the issue, please do set it back to "New" and I'll dig into it.