apt error, fresh install Debian 12/Dell desktop

Bob Crochelt

unread,

Oct 10, 2023, 2:40:06 AM10/10/23

to

Hi:

Fresh install Debian 12. All seems well. However, when I install a new package, in this case fvwm, the package installs fine, but there is an error at the end...

dpkg: dependency problems prevent configuration of linux-image-amd64:

linux-image-amd64 depends on linux-image-6.1.0-12-amd64 (= 6.1.52-1); however:

Package linux-image-6.1.0-12-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):

dependency problems - leaving unconfigured

Processing triggers for libc-bin (2.36-9+deb12u3) ...

Processing triggers for man-db (2.11.2-2) ...

Processing triggers for initramfs-tools (0.142) ...

update-initramfs: Generating /boot/initrd.img-6.1.0-12-amd64

raspi-firmware: missing /boot/firmware, did you forget to mount it?

run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1

dpkg: error processing package initramfs-tools (--configure):

installed initramfs-tools package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:

linux-image-6.1.0-12-amd64

linux-image-amd64

initramfs-tools

E: Sub-process /usr/bin/dpkg returned an error code (1)

So far all the packages I have installed have worked fine...

Should I ignore this or do something?

Thanks

Bob Crochelt

Marco M.

unread,

Oct 10, 2023, 3:10:05 AM10/10/23

to

Am 09.10.2023 um 23:31:14 Uhr schrieb Bob Crochelt:

> raspi-firmware: missing /boot/firmware, did you forget to mount it?

Does it exist?
On Pi it does.

Run:
lsblk
cat /etc/fstab

David

unread,

Oct 10, 2023, 5:20:07 AM10/10/23

to

On Tue, 10 Oct 2023 at 06:32, Bob Crochelt <rf...@fastmail.com> wrote:

> Fresh install Debian 12. All seems well. However, when I install a new package, in this case fvwm, the package installs fine, but there is an error at the end...
>
> dpkg: dependency problems prevent configuration of linux-image-amd64:
> linux-image-amd64 depends on linux-image-6.1.0-12-amd64 (= 6.1.52-1); however:
> Package linux-image-6.1.0-12-amd64 is not configured yet.
>
> dpkg: error processing package linux-image-amd64 (--configure):
> dependency problems - leaving unconfigured
> Processing triggers for libc-bin (2.36-9+deb12u3) ...
> Processing triggers for man-db (2.11.2-2) ...
> Processing triggers for initramfs-tools (0.142) ...
> update-initramfs: Generating /boot/initrd.img-6.1.0-12-amd64
> raspi-firmware: missing /boot/firmware, did you forget to mount it?
> run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1

Hi, it seems unusual to have the raspi-firmware package installed on a
Dell desktop
computer (that you mentioned in the Subject), is there a reason for doing that?

Махно

unread,

Oct 10, 2023, 8:20:07 AM10/10/23

to

Hello.

Check this:
https://forums.debian.net/viewtopic.php?t=155245

Anders Andersson

unread,

Oct 10, 2023, 11:20:07 AM10/10/23

to

This is a bit crazy. It can't be a "fresh install" if you have the
amd64 kernel trying to configure the closed firmware for a raspberry
pi. Why is "raspi-firmware" installed? What's your actual computer and
how did you install debian?

Tixy

unread,

Oct 10, 2023, 11:40:06 AM10/10/23

to

On Tue, 2023-10-10 at 17:11 +0200, Anders Andersson wrote:
> This is a bit crazy. It can't be a "fresh install" if you have the
> amd64 kernel trying to configure the closed firmware for a raspberry
> pi.

As Махно pointed out in another reply [1], this does really seem to be
the case. If you follow the thread they linked to it occurs when
installing from the 12.0 live image and there are claims it's fixed in
12.1.

[1] https://lists.debian.org/debian-user/2023/10/msg00269.html

Andrew M.A. Cater

unread,

Oct 10, 2023, 1:40:06 PM10/10/23

to

It *was* an issue for 12.0, discovered almost immediately _after_ the
release :(

It was fixed very quickly in the release process - the workarounds given
fix it very quickly if you happen to be unfortunate.

There are good reasons why I recommend people to use the standard Debian
installer and _not_ the debian-live images and also why I recommend people
to bring their computer up to date with the latest software before raising
issues.

/me reminds people that the latest versions of supported software are 11.8
and 12.2 as of last Saturday.

All the very best, as ever,

Andy

[amac...@debian.org]

Bob Crochelt

unread,

Oct 10, 2023, 2:30:06 PM10/10/23

to

Hi,

Thanks for your help.

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

sda 8:0 0 465.8G 0 disk

├─sda1 8:1 0 464.8G 0 part /

├─sda2 8:2 0 1K 0 part

└─sda5 8:5 0 975M 0 part [SWAP]

sdb 8:16 0 931.5G 0 disk

├─sdb1 8:17 0 1M 0 part

├─sdb2 8:18 0 1G 0 part

└─sdb3 8:19 0 930.5G 0 part

sdc 8:32 0 1.8T 0 disk

├─sdc1 8:33 0 200M 0 part

├─sdc2 8:34 0 936.1G 0 part /media/bob/9c4430ba-d6b6-4ba3-af4d-01c6b2c7a167

└─sdc5 8:37 0 926.7G 0 part /media/bob/7d12182f-bf5c-4fa3-9090-306def62e9ef

sdd 8:48 1 28.9G 0 disk

└─sdd2 8:50 1 249M 0 part

sde 8:64 1 0B 0 disk

sdf 8:80 1 0B 0 disk

sdg 8:96 1 0B 0 disk

sdh 8:112 1 0B 0 disk

sr0 11:0 1 1024M 0 rom

cat /etc/fstab

# /etc/fstab: static file system information.

#

# Use 'blkid' to print the universally unique identifier for a

# device; this may be used with UUID= as a more robust way to name devices

# that works even if disks are added and removed. See fstab(5).

#

# systemd generates mount units based on this file, see systemd.mount(5).

# Please run 'systemctl daemon-reload' after making changes here.

#

# <file system> <mount point> <type> <options> <dump> <pass>

# / was on /dev/sda1 during installation

UUID=85ed3fc8-b06f-42b4-8309-8e9ccd478b72 / ext4 errors=remount-ro 0 1

# swap was on /dev/sda5 during installation

UUID=b994d00a-a1df-441a-ba31-898848c793e4 none swap sw 0 0

/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

Thanks

Bob

Bob Crochelt

unread,

Oct 10, 2023, 2:30:06 PM10/10/23

to

Hi,

No, it was not intentional. Should I remove it?

Thanks,

Bob

Marco M.

unread,

Oct 10, 2023, 2:40:06 PM10/10/23

to

Am 10.10.2023 um 11:25:13 Uhr schrieb Bob Crochelt:

> No, it was not intentional. Should I remove it?

If you don't run Debian on raspberry Pi, remove it.

Bob Crochelt

unread,

Oct 10, 2023, 2:50:06 PM10/10/23

to

Thanks to all. Followed the instructions on the Debian forums link and all is well now. Appreciate the help.

The computer is a Dell Optiplex 7020 that I got when its previous owner, my employer, decided it was junk and tossed it.

Bob Crochelt

unread,

Oct 10, 2023, 2:50:07 PM10/10/23

to

Installed Debian from Debian 12.0 disk.

Thanks

Bob

Eddie

unread,

Oct 10, 2023, 7:00:07 PM10/10/23

to

I had EXACTLY this when I installed Bookworm 12 live when it first came
out. Dumped "raspi-firmware" and purged. All started to finish their
upgrade while dpkg was running. All ok since.

Lucky Eddie !

Bob Crochelt

unread,

Oct 11, 2023, 1:50:07 PM10/11/23

to

Yes working fine here now. Appreciate all the help

Bob