Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #262283 > unrolled thread

apt error, fresh install Debian 12/Dell desktop

Started by"Bob Crochelt" <rfc56@fastmail.com>
First post2023-10-10 08:40 +0200
Last post2023-10-11 19:50 +0200
Articles 14 — 8 participants

Back to article view | Back to linux.debian.user

Contents

  apt error, fresh install Debian 12/Dell desktop "Bob Crochelt" <rfc56@fastmail.com> - 2023-10-10 08:40 +0200
    Re: apt error, fresh install Debian 12/Dell desktop "Marco M." <mm@dorfdsl.de> - 2023-10-10 09:10 +0200
      Re: apt error, fresh install Debian 12/Dell desktop Махно <mindaugasceliesius@gmail.com> - 2023-10-10 14:20 +0200
      Re: apt error, fresh install Debian 12/Dell desktop "Bob Crochelt" <rfc56@fastmail.com> - 2023-10-10 20:30 +0200
    Re: apt error, fresh install Debian 12/Dell desktop David <bouncingcats@gmail.com> - 2023-10-10 11:20 +0200
      Re: apt error, fresh install Debian 12/Dell desktop "Bob Crochelt" <rfc56@fastmail.com> - 2023-10-10 20:30 +0200
        Re: apt error, fresh install Debian 12/Dell desktop "Marco M." <mm@dorfdsl.de> - 2023-10-10 20:40 +0200
          Re: apt error, fresh install Debian 12/Dell desktop "Bob Crochelt" <rfc56@fastmail.com> - 2023-10-10 20:50 +0200
    Re: apt error, fresh install Debian 12/Dell desktop Anders Andersson <pipatron@gmail.com> - 2023-10-10 17:20 +0200
      Re: apt error, fresh install Debian 12/Dell desktop Tixy <tixy@yxit.co.uk> - 2023-10-10 17:40 +0200
        Re: apt error, fresh install Debian 12/Dell desktop "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-10 19:40 +0200
      Re: apt error, fresh install Debian 12/Dell desktop "Bob Crochelt" <rfc56@fastmail.com> - 2023-10-10 20:50 +0200
        Re: apt error, fresh install Debian 12/Dell desktop Eddie <eddie.seymour@gmail.com> - 2023-10-11 01:00 +0200
          Re: apt error, fresh install Debian 12/Dell desktop "Bob Crochelt" <rfc56@fastmail.com> - 2023-10-11 19:50 +0200

#262283 — apt error, fresh install Debian 12/Dell desktop

From"Bob Crochelt" <rfc56@fastmail.com>
Date2023-10-10 08:40 +0200
Subjectapt error, fresh install Debian 12/Dell desktop
Message-ID<Hnezn-eO8m-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [next] | [standalone]

#262284

From"Marco M." <mm@dorfdsl.de>
Date2023-10-10 09:10 +0200
Message-ID<Hnf2p-eOx4-5@gated-at.bofh.it>
In reply to#262283
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

[toc] | [prev] | [next] | [standalone]

#262287

FromМахно <mindaugasceliesius@gmail.com>
Date2023-10-10 14:20 +0200
Message-ID<HnjSq-eRSW-7@gated-at.bofh.it>
In reply to#262284
Hello.

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

2023-10-10, an, 10:04 Marco M. <mm@dorfdsl.de> rašė:
>
> 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
>

[toc] | [prev] | [next] | [standalone]

#262291

From"Bob Crochelt" <rfc56@fastmail.com>
Date2023-10-10 20:30 +0200
Message-ID<HnpEt-eVm8-7@gated-at.bofh.it>
In reply to#262284

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 10, 2023, at 00:04, Marco M. wrote:
> 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
> 
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

[toc] | [prev] | [next] | [standalone]

#262286

FromDavid <bouncingcats@gmail.com>
Date2023-10-10 11:20 +0200
Message-ID<Hnh4d-ePG1-3@gated-at.bofh.it>
In reply to#262283
On Tue, 10 Oct 2023 at 06:32, Bob Crochelt <rfc56@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?

[toc] | [prev] | [next] | [standalone]

#262292

From"Bob Crochelt" <rfc56@fastmail.com>
Date2023-10-10 20:30 +0200
Message-ID<HnpEt-eVm8-11@gated-at.bofh.it>
In reply to#262286

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 10, 2023, at 02:13, David wrote:
> On Tue, 10 Oct 2023 at 06:32, Bob Crochelt <rfc56@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?
> 
Hi,
No, it was not intentional.  Should I remove it?
Thanks,
Bob

[toc] | [prev] | [next] | [standalone]

#262293

From"Marco M." <mm@dorfdsl.de>
Date2023-10-10 20:40 +0200
Message-ID<HnpO9-eVpz-11@gated-at.bofh.it>
In reply to#262292
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.

[toc] | [prev] | [next] | [standalone]

#262294

From"Bob Crochelt" <rfc56@fastmail.com>
Date2023-10-10 20:50 +0200
Message-ID<HnpXP-eVsT-1@gated-at.bofh.it>
In reply to#262293

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 10, 2023, at 11:31, Marco M. wrote:
> 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.
> 

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

[toc] | [prev] | [next] | [standalone]

#262288

FromAnders Andersson <pipatron@gmail.com>
Date2023-10-10 17:20 +0200
Message-ID<HnmGB-eTxJ-9@gated-at.bofh.it>
In reply to#262283
On Tue, Oct 10, 2023 at 1:19 PM Bob Crochelt <rfc56@fastmail.com> wrote:
>
> 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?

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?

[toc] | [prev] | [next] | [standalone]

#262289

FromTixy <tixy@yxit.co.uk>
Date2023-10-10 17:40 +0200
Message-ID<HnmZX-eTDD-7@gated-at.bofh.it>
In reply to#262288
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

[toc] | [prev] | [next] | [standalone]

#262290

From"Andrew M.A. Cater" <amacater@einval.com>
Date2023-10-10 19:40 +0200
Message-ID<HnoS5-eUQU-3@gated-at.bofh.it>
In reply to#262289
On Tue, Oct 10, 2023 at 04:31:15PM +0100, Tixy wrote:
> 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
>

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

[amacater@debian.org]

[toc] | [prev] | [next] | [standalone]

#262295

From"Bob Crochelt" <rfc56@fastmail.com>
Date2023-10-10 20:50 +0200
Message-ID<HnpXP-eVsT-3@gated-at.bofh.it>
In reply to#262288

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 10, 2023, at 08:11, Anders Andersson wrote:
> On Tue, Oct 10, 2023 at 1:19 PM Bob Crochelt <rfc56@fastmail.com> wrote:
> >
> > 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?
> 
> 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?
Installed Debian from Debian 12.0 disk.  
Thanks
Bob

[toc] | [prev] | [next] | [standalone]

#262296

FromEddie <eddie.seymour@gmail.com>
Date2023-10-11 01:00 +0200
Message-ID<HntRL-eXOm-1@gated-at.bofh.it>
In reply to#262295

On 10/10/23 14:41, Bob Crochelt wrote:
> 
> 
> On Tue, Oct 10, 2023, at 08:11, Anders Andersson wrote:
>> On Tue, Oct 10, 2023 at 1:19 PM Bob Crochelt <rfc56@fastmail.com 
>> <mailto:rfc56@fastmail.com>> wrote:
>> >
>> > 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?
>>
>> 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?
> Installed Debian from Debian 12.0 disk.
> Thanks
> Bob
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 !

[toc] | [prev] | [next] | [standalone]

#262306

From"Bob Crochelt" <rfc56@fastmail.com>
Date2023-10-11 19:50 +0200
Message-ID<HnLvk-f8YO-11@gated-at.bofh.it>
In reply to#262296

[Multipart message — attachments visible in raw view] — view raw

On Tue, Oct 10, 2023, at 15:52, Eddie wrote:
> 
> 
> On 10/10/23 14:41, Bob Crochelt wrote:
> > 
> > 
> > On Tue, Oct 10, 2023, at 08:11, Anders Andersson wrote:
> >> On Tue, Oct 10, 2023 at 1:19 PM Bob Crochelt <rfc56@fastmail.com 
> >> <mailto:rfc56@fastmail.com>> wrote:
> >> >
> >> > 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?
> >>
> >> 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?
> > Installed Debian from Debian 12.0 disk.
> > Thanks
> > Bob
> 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 !
> 
Yes working fine here now. Appreciate all the help
Bob

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web