Bug#1080167: installation-reports: Installation programs should give an option to use ipv4 instead of ipv6

[Alexander Rusakevich]

Package: installation-reports
Severity: wishlist
Tags: d-i
X-Debbugs-Cc: mr.alexander.rusakev...@gmail.com

Boot method: USB (Ventoy)
Image version: debian-live-12.6.0-amd64-gnome.iso
Date: 

Machine: ASUS F509J
Partitions: none

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [E]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Note: this problem is not related to calamares

My wifi router has misconfigured ipv6 settings which I cannot fix. Debian tries
to use ipv6 during installation, tries to send packages, but those won't be
sent.
While trying to send packages via ipv6, my installer hangs. The only workaround
is to set ipv6.disable=1 in grub options.

I guess, a potential user who runs into this problem may find a 'ipv4/ipv6'
swtich before the "Configure network" step useful. Or the installer should show
a message about misconfigured ipv6 on the router side when failing to send data
over ipv6 multiple times. Or the program should switch to ipv4 after multiple
fails while using ipv6. There is a plenthora of options, but the installer
should not scare off a potential new user by showing him the stopped installer
with no additional info.

Bug#1078354: installation-reports: trailing '\' allowed in hostname caused exim and ssl-cert to fail

[Warren Overholt]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: overh...@gmail.com

I accidentally installed my system with a trailing \ in the fqdn.
I didn't notice until I went to install emacs, which then showed errors in
the exim install.  I prefer postfix, so installed it - which then failed on
postfix and ssl-cert installs.  At which point I noticed the hostname was wrong.


Boot method: USB
Image version: debian-12.5.0-amd64-netinst.iso
Date: Thu Aug  8 17:19:04 2024

Machine: Mac Mini
Partitions: 
root@macdeb:~# df -Tl
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs   3978940   0   3978940   0% /dev
tmpfs  tmpfs   800512 868799644   1% /run
/dev/sda3  ext4 862995256 4014580 815069252   1% /
tmpfs  tmpfs  4002548   0   4002548   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
/dev/sda1  vfat201609   29704171905  15% /boot/efi
tmpfs  tmpfs   800508   0800508   0% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect media:   [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

This was a dumb mistake on my part, but a warning about it would have been 
appreciated.

-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607+deb12u5"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux macdeb 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 
(2024-02-01) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM 
Controller [8086:0a04] (rev 09)
lspci -knn: Subsystem: Apple Inc. Device [106b:0141]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09)
lspci -knn: Subsystem: Apple Inc. Device [106b:0141]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 09)
lspci -knn: Subsystem: Apple Inc. Device [106b:0141]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI 
HC [8086:9c31] (rev 04)
lspci -knn: Subsystem: Intel Corporation Apple MacBookAir6,2 / 
MacBookPro11,1 [8086:7270]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 8 Series 
HECI #0 [8086:9c3a] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio 
Controller [8086:9c20] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series PCI Express 
Root Port 1 [8086:9c10] (rev e4)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series PCI Express 
Root Port 3 [8086:9c14] (rev e4)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series PCI Express 
Root Port 4 [8086:9c16] (rev e4)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series PCI Express 
Root Port 5 [8086:9c18] (rev e4)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC 
Controller [8086:9c43] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series SATA 
Controller 1 [AHCI mode] [8086:9c03] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series SMBus Controller 
[8086:9c22] (rev 04)
ls

Bug#1065807: marked as done (installation-reports: Verify Installtion Media Fails)

[Debian Bug Tracking System]

Your message dated Mon, 11 Mar 2024 16:37:05 +
with message-id <20240311163705.gg1697...@tack.einval.com>
and subject line Re: Bug#1065807: installation-reports: Verify Installtion 
Media Fails
has caused the Debian Bug report #1065807,
regarding installation-reports: Verify Installtion Media Fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
X-Debbugs-Cc: tombrown9...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-
cd/debian-testing-amd64-netinst.iso 2024-03-07
Date: 3/9/24

Machine: Lenovo Thinkcenter
Partitions: Failed be being set


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O ]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ O]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

It always detects a file corruption. I verified hash on download and verified
good usb stick. Same usb was used to install Debian 12 after, which correctly
verified.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="13 (trixie) - installer build 20240214-09:04:17"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 
(2024-02-04) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th 
Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD 
Graphics 620 [8086:5917] (rev 07)
lspci -knn: DeviceName:  Onboard IGD
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon 
E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 
08)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:13.0 Non-VGA unclassified device []: Intel Corporation 
Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: intel_ish_ipc
lspci -knn: Kernel modules: intel_ish_ipc
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP 
USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:15.0 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: intel-lpss
lspci -knn: Kernel modules: intel_lpss_pci
lspci -knn: 00:15.1 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: intel-lpss
lspci -knn: Kernel modules: intel_lpss_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Sunrise 
Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP 
SATA Controller [AHCI mode] [8086:9d03] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP 

Bug#1065807: installation-reports: Verify Installtion Media Fails

[Tom]

That does match my image. I cannot reproduce the error any longer, I'm
wondering if it had to do with an existing windows installation on my
device which has now been replaced with a debian install. I remember it was
a file in the grub folder but i can't remember which one.

On Sun, Mar 10, 2024 at 9:28 AM Steve McIntyre  wrote:

> Hi Neal,
>
> On Sat, Mar 09, 2024 at 08:45:28PM -0500, Neal wrote:
> >
> >(Please provide enough information to help the Debian
> >maintainers evaluate the report efficiently - e.g., by filling
> >in the sections below.)
> >
> >Boot method: USB
> >Image version:
> https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-
> >cd/debian-testing-amd64-netinst.iso 2024-03-07
> >Date: 3/9/24
> >
> >Machine: Lenovo Thinkcenter
> >Partitions: Failed be being set
> >
> >Base System Installation Checklist:
> >[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> >
> >Initial boot:   [O ]
> >Detect network card:[ ]
> >Configure network:  [ ]
> >Detect media:   [ O]
> >Load installer modules: [ ]
> >Clock/timezone setup:   [ ]
> >User/password setup:[ ]
> >Detect hard drives: [ ]
> >Partition hard drives:  [ ]
> >Install base system:[ ]
> >Install tasks:  [ ]
> >Install boot loader:[ ]
> >Overall install:[ ]
> >
> >Comments/Problems:
> >
> >It always detects a file corruption. I verified hash on download and
> verified
> >good usb stick. Same usb was used to install Debian 12 after, which
> correctly
> >verified.
>
> Hmmm. I've just grabed the latest weekly amd64 netinst and tried to
> reproduce your issue. Things work here just fine in a VM, using this
> image:
>
> e618afbebbbdf9495c74140bc87f2a4b  debian-testing-amd64-netinst.iso
>
> Does that match your image?
>
> If the integrity check fails, it should say which file is wrong. What
> did it report for please?
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> "... the premise [is] that privacy is about hiding a wrong. It's not.
>  Privacy is an inherent human right, and a requirement for maintaining
>  the human condition with dignity and respect."
>   -- Bruce Schneier
>
>

Bug#1065807: installation-reports: Verify Installtion Media Fails

[Steve McIntyre]

Hi Neal,

On Sat, Mar 09, 2024 at 08:45:28PM -0500, Neal wrote:
>
>(Please provide enough information to help the Debian
>maintainers evaluate the report efficiently - e.g., by filling
>in the sections below.)
>
>Boot method: USB
>Image version: https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-
>cd/debian-testing-amd64-netinst.iso 2024-03-07
>Date: 3/9/24
>
>Machine: Lenovo Thinkcenter
>Partitions: Failed be being set
>
>Base System Installation Checklist:
>[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
>Initial boot:   [O ]
>Detect network card:[ ]
>Configure network:  [ ]
>Detect media:   [ O]
>Load installer modules: [ ]
>Clock/timezone setup:   [ ]
>User/password setup:[ ]
>Detect hard drives: [ ]
>Partition hard drives:  [ ]
>Install base system:[ ]
>Install tasks:  [ ]
>Install boot loader:[ ]
>Overall install:[ ]
>
>Comments/Problems:
>
>It always detects a file corruption. I verified hash on download and verified
>good usb stick. Same usb was used to install Debian 12 after, which correctly
>verified.

Hmmm. I've just grabed the latest weekly amd64 netinst and tried to
reproduce your issue. Things work here just fine in a VM, using this
image:

e618afbebbbdf9495c74140bc87f2a4b  debian-testing-amd64-netinst.iso

Does that match your image?

If the integrity check fails, it should say which file is wrong. What
did it report for please?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"... the premise [is] that privacy is about hiding a wrong. It's not.
 Privacy is an inherent human right, and a requirement for maintaining
 the human condition with dignity and respect."
  -- Bruce Schneier

Bug#1065807: installation-reports: Verify Installtion Media Fails

[Neal]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: tombrown9...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-
cd/debian-testing-amd64-netinst.iso 2024-03-07
Date: 3/9/24

Machine: Lenovo Thinkcenter
Partitions: Failed be being set


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O ]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ O]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

It always detects a file corruption. I verified hash on download and verified
good usb stick. Same usb was used to install Debian 12 after, which correctly
verified.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="13 (trixie) - installer build 20240214-09:04:17"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 
(2024-02-04) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th 
Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD 
Graphics 620 [8086:5917] (rev 07)
lspci -knn: DeviceName:  Onboard IGD
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon 
E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 
08)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:13.0 Non-VGA unclassified device []: Intel Corporation 
Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: intel_ish_ipc
lspci -knn: Kernel modules: intel_ish_ipc
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP 
USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:15.0 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: intel-lpss
lspci -knn: Kernel modules: intel_lpss_pci
lspci -knn: 00:15.1 Signal processing controller [1180]: Intel Corporation 
Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: intel-lpss
lspci -knn: Kernel modules: intel_lpss_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Sunrise 
Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP 
SATA Controller [AHCI mode] [8086:9d03] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #6 [8086:9d15] (rev f1)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #9 [8086:9d18] (rev f1)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point LPC 
Controller/eSPI Controller [8086:9d4e] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise 
Point-LP PMC [8086:9d21] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:07ec]
lspci -knn: Kernel driver in use: snd_hda_int

Bug#1065048: installation-reports: partition tool in d-i remembers choices; 'delete partition' (encrypted Part.) always stays 'yes'

[Frank Weißer]

Hi Pascal,

Pascal Hambourg:

On 29/02/2024 at 08:51, Frank Weißer wrote:


Comments/Problems: 2nd NIC gets eth0 on reboot, 2nd NIC gets eth1 :-(


eth* names are no persistent and may change at any boot.
But ethernet interface should get predictable names like enpXsY or enoX.
In /proc/interrupts we can see enp1s0.


Thank you for the epiphany!


randomized encrypted partitions default to 'delete partition' 'yes';
after choosing 'no' the first time it should default to 'no'


By "randomized" do you mean "plain dm-crypt with random key" ?


yes


The only choice of extended filesystems to format the randomized
encrypted partition with is ext2, which the d-i writes to /etc/fstab.
But the d-i actually formats to ext4, so I end up in emergency mode on
reboot

the d-i also misses to write the 'tmp' parameter for the randomized
encrypted ext4 formatted partition in /etc/crypttab


These two remind me of Bug#995108 ("d-i: partman-crypto: plain dm-crypt 
device management issues").




seems so


I had submitted a patch but received no feedback so far.


:-(

Kind regards

readU
Frank

Bug#1065048: installation-reports: partition tool in d-i remembers choices; 'delete partition' (encrypted Part.) always stays 'yes'

[Pascal Hambourg]

On 29/02/2024 at 08:51, Frank Weißer wrote:


Comments/Problems: 2nd NIC gets eth0 on reboot, 2nd NIC gets eth1 :-(


eth* names are no persistent and may change at any boot.
But ethernet interface should get predictable names like enpXsY or enoX.
In /proc/interrupts we can see enp1s0.


randomized encrypted partitions default to 'delete partition' 'yes';
after choosing 'no' the first time it should default to 'no'


By "randomized" do you mean "plain dm-crypt with random key" ?


The only choice of extended filesystems to format the randomized
encrypted partition with is ext2, which the d-i writes to /etc/fstab.
But the d-i actually formats to ext4, so I end up in emergency mode on
reboot

the d-i also misses to write the 'tmp' parameter for the randomized
encrypted ext4 formatted partition in /etc/crypttab


These two remind me of Bug#995108 ("d-i: partman-crypto: plain dm-crypt 
device management issues").



I had submitted a patch but received no feedback so far.

Bug#1065048: installation-reports: partition tool in d-i remembers choices; 'delete partition' (encrypted Part.) always stays 'yes'

[Frank Weißer]

Package: installation-reports
Severity: wishlist

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: 
http://get.debian.org/cdimage/release/current/amd64/iso-bd/debian-edu-12.5.0-amd64-BD-1.iso
 2024-02-10 14:48
http://get.debian.org/cdimage/release/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso
http://get.debian.org/cdimage/release/current/amd64/iso-cd/debian-edu-12.5.0-amd64-netinst.iso
http://get.debian.org/cdimage/archive/11.0.0/i386/iso-cd/debian-11.0.0-i386-netinst.iso
and others too
Date: <2024-02-24 15:20>

Machine: Fujitsu Esprimo C710 Intel Core i3-2100T CPU @ 2.50GHz 32GB RAM 120GB 
SSD 4TB HDD
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [0]
Detect network card:[0]
Configure network:  [E]
Detect media:   [0]
Load installer modules: [0]
Clock/timezone setup:   [0]
User/password setup:[0]
Detect hard drives: [0]
Partition hard drives:  [E]
Install base system:[0]
Install tasks:  [0]
Install boot loader:[0]
Overall install:[0]

Comments/Problems: 2nd NIC gets eth0 on reboot, 2nd NIC gets eth1 :-(

randomized encrypted partitions default to 'delete partition' 'yes';
after choosing 'no' the first time it should default to 'no'

The only choice of extended filesystems to format the randomized
encrypted partition with is ext2, which the d-i writes to /etc/fstab.
But the d-i actually formats to ext4, so I end up in emergency mode on
reboot

the d-i also misses to write the 'tmp' parameter for the randomized
encrypted ext4 formatted partition in /etc/crypttab




Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==

==
Installer hardware-summary:
==
uname -a: Linux tjener.intern 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.76-1 (2024-02-01) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0100] (rev 09)
lspci -knn: DeviceName:  PCH Q75
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11b9]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd 
Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11b9]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0102] 
(rev 09)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11b9]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11d6]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11d6]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V 
Gigabit Network Connection [8086:1503] (rev 04)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11d9]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11d6]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11d8]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
lspci -knn: Subsystem: Fujitsu Technology Solutions Device [1734:11d6]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1e.0 PCI bridge [0

Bug#1063787: installation-reports: No ethernet on Cubieboard with netboot SD-card-image

[Ville Viinikka]

Package: installation-reports
Severity: important

Boot method: netboot/SD-card-images
Image version: 
https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/partition.img.gz
 2024-02-12 00:01
Date: 2024-02-12

Machine: Cubietech Cubieboard


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Can't continue network installation because the network card doesn't work:
[   50.262983] sun4i-emac 1c0b000.ethernet end0: could not find the PHY
[   50.263036] sun4i-emac 1c0b000.ethernet end0: cannot probe MDIO bus

Can be worked around by manually copying 
/lib/modules/6.6.13-armmp/kernel/drivers/net/mdio/mdio-sun4i.ko to initrd.

Should probably be fixed by adding mdio-sun4i to 
debian/installer/modules/armhf-armmp/nic-modules.

Bug#1051846: marked as done (installation-reports: gnome_flashback installation fails on openQA with daily netinst image)

[Debian Bug Tracking System]

Your message dated Sun, 11 Feb 2024 12:25:50 +0100
with message-id <20240211122550.3ac4259eb265e31ec44cf...@mailbox.org>
and subject line Re: Bug#1051846: installation-reports: gnome_flashback 
installation fails on openQA with daily netinst image
has caused the Debian Bug report #1051846,
regarding installation-reports: gnome_flashback installation fails on openQA 
with daily netinst image
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1051846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
X-Debbugs-Cc: p...@hands.com

Boot method: CD netinst image
Image version: https://get.debian.org/images/daily-builds/daily/arch-
latest/amd64/iso-cd/debian-testing-amd64-netinst.iso from 20230913_0524
Date: 

Machine: QEMU with UEFI secure boot as on openqa.debian.net, 2GB memory
Partitions: wipe all from a 10GB virtual HD


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

The installation proceeds without error.
After rebooting, the screen with 'Oh no! Something has gone wrong' is shown.

My attempts to reproduce and pinpoint the cause:
I've tested with QXL and VGA graphical cards on openQA. In both cases the 'Oh
no!' is shown.

With the netinst image from 20230909_0504, the flashback GUI started initially
with the grey top menu bar, but that got replaced by the black menu bar of the
regular GNOME desktop.

The last known good netinst image was from 20230910_0509.
The first netinst image with this issue is from 20230910_1109.
This narrows down the number of possible causes a bit.

To see more installation attempts (every 6 hours):
* Go to https://openqa.debian.net/group_overview/10
* Take a build that has no running jobs (i.e. no blue bar)
* Click on the red part of the bar
* Click on the red circle behind 'gnome_flash_flash' (before
'_graphical_wait_login' or 'complete_install')
* Installation logs and additional information can be found in the 'Logs &
Assets' tab of the test

With kind regards,
Roland Clobus


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux silent 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5000]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Intel Corporation Device [8086:2010]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5007]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Lynx Point KT 
Controller [8086:8c3d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I217-V [8086:153b] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:e000]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation L

Re: Bug#1051846: installation-reports: gnome_flashback installation fails on openQA with daily netinst image

[Holger Wansing]

Hi,

Roland Clobus  wrote (Wed, 13 Sep 2023 15:59:37 +0200):
> Comments/Problems:
> 
> The installation proceeds without error.
> After rebooting, the screen with 'Oh no! Something has gone wrong' is shown.
> 
> My attempts to reproduce and pinpoint the cause:
> I've tested with QXL and VGA graphical cards on openQA. In both cases the 'Oh
> no!' is shown.
> 

Apparently only a temporary problem; looks fine again.

Closing this bug


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1063686: installation-reports: GUI checkbox in high contrast dark mode isn't high contrast

[T. Joseph Carter]

Package: installation-reports
Severity: wishlist

Either normal/a11y or wishlist depending how you wanna call it.

I normally use the slang version of the Debian installer. Because I'm
using a 14" 1080p portable monitor here, I decided to use the GUI. In
dark mode because albino. Bright = pain. Sub-optimal install for me,
will switch to ssh as soon as the network's configured.

Went to select installer components because parted pls, but when I
selected it, I didn't see that it was selected at first. That's odd.
Then I looked closer and … oh yeah, I guess it is selected. Just this
theme/widget set uses a very small/thin checkmark inside the box.

Basically, I'd like a checkbox whose checked/unchecked states are more
visually not the same. Particularly important in the dark mode, since
that's intended to be high contrast for accessibility reasons. (Which is
why I was using it…)

Suggest a bigger/bolder checkmark might be the path of least resistance
for a fix.

Boot method: usb
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso
Date: Sat, 10 Feb 2024 17:54:18 -0800 (in the middle of installing now)

Machine: Ryzen 3000 series with B450 chipset
Partitions: 

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [?] ← Here's where I noticed the problem

Bug#1063657: installation-reports: expert install + https asks for a choice with only one option

[Simon McVittie]

Package: installation-reports
Severity: minor

Boot method: USB flash drive
Image version: reproduced on debian-12.5.0-i386-DVD-1.iso and 
debian-12.5.0-amd64-netinst.iso
Date: 2024-02-10
Machine: not relevant
Partitions: not relevant

My partner encountered an unexpected UX during point release media
testing, which #debian-cd asked me to report as a bug.

Steps to reproduce:

- boot into expert install (we used text mode)
- accept defaults until "Configure the package manager"
- asked to choose http, https or ftp for file downloads
- choose https

Expected result: maybe one of these:

- be offered a list of countries with https mirrors
- or proceed directly to entering information manually
- or a 2-way choice between https://deb.debian.org/debian or
  "enter information manually"

Actual result:

- I'm asked for "Debian archive mirror country"
- the only option is "enter information manually", which makes it look
  as though there isn't going to be any reasonable default
- but when I choose that, the default is deb.debian.org, which is good

Bug#1060325: installation-reports: Successful installation on Chrultrabooked Lenovo 300e Chromebook 2nd Gen (Intel)

[наб]

Package: installation-reports
Severity: wishlist

Boot method: cp mini.iso /dev/sda where /dev/sda is an SD card
Image version: 
https://deb.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/netboot/mini.iso
 dated 2023-12-10 00:20 bramded 20230607+deb12u4
Date: 2024-01-09

Machine: Lenovo 300e Chromebook 2nd Gen (Intel), Chrultrabooked with BIOS 
MrChromebox-4.22.0 12/22/2023
Partitions: 
  Disk /dev/mmcblk0: 29.12 GiB, 31268536320 bytes, 61071360 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: A48995AA-FF90-4540-8B6F-541E382FBCCF
  
  DeviceStart  End Sectors  Size Type
  /dev/mmcblk0p1 2048   499711  497664  243M EFI System
  /dev/mmcblk0p2 53258240 61069311 7811072  3.7G Linux swap
  /dev/mmcblk0p3 45445120 53258239 7813120  3.7G Linux filesystem
  
  Partition table entries are not in disk order.
  
  
  Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  
  
  Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

None that I found so far, works perfectly.

Post-install I see
  Jan 09 17:09:50 chrust kernel: x86/cpu: SGX disabled by BIOS.
  Jan 09 17:09:50 chrust kernel: simple-framebuffer simple-framebuffer.0: 
Unable to acquire aperture: -16
  Jan 09 17:09:51 chrust kernel: cros-ec-keyb GOOG0007:00: cannot register 
non-matrix inputs: -95
  Jan 09 17:09:52 chrust kernel: iwlwifi :00:0c.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
  Jan 09 17:09:52 chrust kernel: firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
  Jan 09 17:09:52 chrust kernel: iwlwifi :00:0c.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
  Jan 09 17:09:53 chrust kernel: i915 :00:02.0: firmware: failed to load 
i915/glk_dmc_ver1_04.bin (-2)
  Jan 09 17:09:53 chrust kernel: i915 :00:02.0: firmware: failed to load 
i915/glk_dmc_ver1_04.bin (-2)
  Jan 09 17:09:54 chrust kernel: sof-audio-pci-intel-apl :00:0e.0: 
firmware: failed to load intel/sof/community/sof-glk.ri (-2)
  Jan 09 17:09:54 chrust kernel: sof-audio-pci-intel-apl :00:0e.0: 
firmware: failed to load intel/sof/community/sof-glk.ri (-2)
  Jan 09 17:09:54 chrust kernel: sof-audio-pci-intel-apl :00:0e.0: error: 
sof firmware file is missing, you might need to
  Jan 09 17:09:54 chrust kernel: sof-audio-pci-intel-apl :00:0e.0:
download it from https://github.com/thesofproject/sof-bin/
  Jan 09 17:09:54 chrust kernel: sof-audio-pci-intel-apl :00:0e.0: error: 
failed to load DSP firmware -2
  Jan 09 17:09:54 chrust kernel: sof-audio-pci-intel-apl :00:0e.0: error: 
sof_probe_work failed err: -2
  Jan 09 17:09:56 chrust bluetoothd[616]: 
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
  Jan 09 17:09:56 chrust bluetoothd[616]: sap-server: Operation not permitted 
(1)
and
  Jan 09 17:09:50 chrust kernel: simple-framebuffer simple-framebuffer.0: 
Unable to acquire aperture: -16
  Jan 09 17:09:51 chrust kernel: cros-ec-keyb GOOG0007:00: cannot register 
non-matrix inputs: -95
end up in the console before logging in.

Unclear to me what those entail.


d-i calls the installation medium a "hard disk" quite often.
This machine doesn't have one, or an interface to connect one
(you've no doubt noted the 32G MMC: that's all there is to it).
This is funny more than an error I think,
calling it anything else may well be much more confusing.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607+deb12u4"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==

==
Installer firmware-summary:
==
#Package Component 

Bug#1059815: installation-reports: unmount problem on encrypted system at shutdown

[Thomas Bindewald]

Package: installation-reports
Severity: normal
Tags: d-i
X-Debbugs-Cc: zefr...@gmail.com

Boot method: DVD
Image version: 
https://laotzu.ftp.acc.umu.se/debian.cd/current/amd64/iso-dvd/debian.12.4.0-amd64-DVD-1.iso
Date: 

Machine: VirtualBox
Partitions: 

root@debian:~# df -Tl
Filesystem   Type 1K-blocksUsed Available Use% Mounted 
on
udev devtmpfs   4032336   0   4032336   0% /dev
tmpfstmpfs   813192 952812240   1% /run
/dev/mapper/LVMGRP-LVMVOLSYS ext4  20970032 426  16474372  21% /
tmpfstmpfs  4065944   0   4065944   0% /dev/shm
tmpfstmpfs 5120   8  5112   1% /run/lock
/dev/mapper/LVMGRP-LVMVOLHOM ext4   3081800  48   3033300   1% /home
/dev/mapper/LVMGRP-LVMVOLTMP ext4   3761336 104   3705816   1% /tmp
/dev/sda1ext4942764  146392770220  16% /boot
tmpfstmpfs   813188  48813140   1% 
/run/user/0

root@debian:~# fdisk --list /dev/sda
Disk /dev/sda: 35.85 GiB, 38494699520 bytes, 75184960 sectors
Disk model: VBOX HARDDISK   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe1515c34

Device Boot   Start  End  Sectors  Size Id Type
/dev/sda1  *   2048  1955839  1953792  954M 83 Linux
/dev/sda2   1955840 75184959 73229120 34.9G da Non-FS data
root@debian:~#


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

The "Expert textmode installation" went well.
Before using the installers partitioning sub-menu, i opened an 
shell and used fdisk on my own, as i wanted two PRIMARY partitions. 
I gave them the type "da".
The i went on using straight forward the installers partitioning 
program und install routines without intervening, choosing 
an encrypted system with LVM, and XFCE desktop.

After start using the fresh installed system (at least another 
reboot has been done), i investigated the 
journalctl output and found an worrying issue, reported
during a shutdown:

  Jan 01 19:54:17 debian systemd[1]: 
run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully.
  Jan 01 19:54:17 debian systemd[1]: Unmounted 
run-credentials-systemd\x2dsysctl.service.mount - 
/run/credentials/systemd-sysctl.service.
  Jan 01 19:54:17 debian systemd-cryptsetup[1199]: Device sda2_crypt is still 
in use.
  Jan 01 19:54:17 debian systemd-cryptsetup[1199]: Failed to deactivate: Device 
or resource busy
  Jan 01 19:54:17 debian systemd[1]: systemd-cryptsetup@sda2_crypt.service: 
Control process exited, code=exited, status=1/FAILURE
  Jan 01 19:54:17 debian systemd[1]: systemd-cryptsetup@sda2_crypt.service: 
Failed with result 'exit-code'.
  Jan 01 19:54:17 debian systemd[1]: Stopped 
systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt.

It wantet to unmount an filesystem still needed at that point of time?

I did some internet search on that, and found a possible solution suggested:

  root@debian:~# cat /etc/crypttab 
  sda2_crypt UUID=dd43f64e-947f-4696-b71c-dc05dc4ceb6f none luks,x-initrd.attach
  root@debian:~#

The manually added "x-initrd.attach" parameter let the error vanish.

Please evaluate, it this is an apropriate solution, which the 
installer might add at writing the /etc/crypttab file. Because 
people, who are not deeply familiar with Linux internals, 
are worried, if this error might affect filesystem integrity.

Thank you.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607+deb12u4"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 
(2023-12-09) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Kernel

Bug#1037972: marked as done (Bug on Debian 12 Bookworm - Installation reports - /etc/apt/source.list)

[Debian Bug Tracking System]

Your message dated Sat, 23 Dec 2023 02:12:33 +0100 (CET)
with message-id <2033541051.240.1703293953...@bluewin.ch>
and subject line Bug on Debian 12 Bookworm - Installation reports - 
/etc/apt/source.list
has caused the Debian Bug report #1037972,
regarding Bug on Debian 12 Bookworm - Installation reports - 
/etc/apt/source.list
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-12.0.0-amd64-DVD-1.iso
File: /etc/apt/source.list
Severity: high (security)

Bug Description :

After installation of Debian 12 with the 'debian-12.0.0-amd64-DVD-1.iso' image, 
the '/etc/apt/source.list' file contains only one entry for installing or 
upgrading the system:
deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD Binary-1 
with firmware 20230610-10:23]/ bookworm main non-free-firmware
After editing the 'source.list' file with the 'software and updates' software 
and activating all remote repositories of the first tab of this program, only 
one line is added to the 'source.list' file ':
deb https://deb.debian.org/debian/ bookworm main contrib non-free 
non-free-firmware
It therefore lacks parameters to perform updates / security repertories on this 
DVD version of 'source.list' file, while in the Live ISO version of Debian 12 
Cinnamon does not have this type of problem.
Someone who doesn't know Debian and has installed the DVD edition of Debian on 
a machine can find themselves really embarrassed some time later since the 
security updates for their machine are not done without manually updating 
update the 'source.list' file.
Thank you to correct this as soon as possible.
Best regards.
Philippe 
--- End Message ---
--- Begin Message ---
closing bug
--- End Message ---

Bug#1059167: installation-reports: installer hangs while recognizing network hardware

[Janusz S . Bień]

On Wed, Dec 20 2023 at 23:24 +01, Pascal Hambourg wrote:
> Hello Janusz,
>
> On 20/12/2023 at 20:52, Janusz Bień wrote:
>> I understand the installer now includes non-free drivers,
>
> No, only non-free firmware.
>
>> but I suspect  it missing one needed for my hardware, which is
>> Intel Ethernet Connection (7) I219-V
>> Intel Dual Band Wireless-AC 3168
>> (on the mainboard ASRock B360M-ITX/AC).
>
> How does the installer hang ? Can you switch to the installer shell in
> tty2 with Ctrl+Alt+F2 ? If yes, can you post the output of
>
> lspci -nnk
>
> and attach (compressed) /var/log/syslog ?

Thanks for your suggestion.

Today the network hardware was recognized in a second or so... Yesterday
at least two attempts failed...

Should I suspect a hardware malfunctions?

Best regards

JSB

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1059167: installation-reports: installer hangs while recognizing network hardware

[Pascal Hambourg]

Hello Janusz,

On 20/12/2023 at 20:52, Janusz Bień wrote:


I understand the installer now includes non-free drivers,


No, only non-free firmware.


but I suspect  it missing one needed for my hardware, which is
Intel Ethernet Connection (7) I219-V
Intel Dual Band Wireless-AC 3168
(on the mainboard ASRock B360M-ITX/AC).


How does the installer hang ? Can you switch to the installer shell in 
tty2 with Ctrl+Alt+F2 ? If yes, can you post the output of


lspci -nnk

and attach (compressed) /var/log/syslog ?

Bug#1059167: installation-reports: installer hangs while recognizing network hardware

[Janusz Bień]

Package: installation-reports
Severity: grave
X-Debbugs-Cc: jsb...@mimuw.edu.pl

I understand the installer now includes non-free drivers, but I suspect 
it missing one needed for my hardware, which is


Intel Ethernet Connection (7) I219-V
Intel Dual Band Wireless-AC 3168
(on the mainboard ASRock B360M-ITX/AC).

I will appreciate your help.

Best regards

JSB

Bug#1058884: installation-reports: debian testing iso install in franch: Light-DM and mate desktop are in English

[Patrick ZAJDA]

Hi again,

I forgot to mention both installation were made in accessible mode, by 
pressing s then enter on boot.


Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1056700: Package: installation-reports

[Julian Barg]

Package: installation-reports

Boot method: DVD image via USB Stick
Image version: 
https://laotzu.ftp.acc.umu.se/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
Date: 2023-11-24 5PM EST

Machine: Thinkpad P14s AMD Gen 4
Processor: AMD Ryzen™ 7 PRO 7840U
Memory: 64 GB LPDDR5X-6400MHz (Soldered)
Partitions: separate management and home partition

Output of lspci -knn (or lspci -nn): didn't try to extract, but looked
correct for Thinkpad model "21K5001JUS".

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems: Regular boot failed. Recovery mode dropped me into
shell but I could not launch gnome session. ```exec gnome``` failed,
yielding Warning: "Could not make bus activated clients aware of
XDG_CURRENT_DESKTOP=GNOME environment variable: Cannot autolaunch
D-Bus without X11 $DISPLAY"

Processed: Re: installation-reports: Installation Report: Bookworm RC2: Raspberry Pi 400 (netboot)

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #1035392 [installation-reports] installation-reports: Installation Report: 
Bookworm RC2: Raspberry Pi 400 (netboot)
Marked Bug as done

-- 
1035392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1035392: installation-reports: Installation Report: Bookworm RC2: Raspberry Pi 400 (netboot)

[James Addison]

Followup-For: Bug #1035392
Control: close -1

(closing; I'll likely re-attempt an install on the same hardware with a more
recent release of Debian in future, for comparison purposes)

Bug#1055806: installation-reports: Installer doesn't recognize laptop's SSD, but calamares does

[Pokoz Martinez]

Hi Cyril and Pascal,

Thank you both for the fast response.

Cyril, I have just tested the .iso you attached to the bug report you
referred to, and indeed that installer detects my UFS disk no problem!

Thank you again so much for the fast response and for all the work you do.
I will rest assured now that this problem is known, and hopefully this
report also contributed my small grain of sand to the Debian effort!!

I hope you have a great rest of day,

Jessie.

On Sat, Nov 11, 2023 at 10:42 PM Cyril Brulebois  wrote:

> Hi Pascal,
>
> Please use reply-all…
>
> Pascal Hambourg  (2023-11-11):
> > On 11/11/2023 à 21:43, Jessie wrote:
> > >
> > > However, when detecting disks, the only disk available for install
> > > was the usb drive I had the installer on - it did not detect the
> > > 256gb UFS SSD.
> >
> > It looks like UFS (Universal Flash Storage, not Unix filesystem) kernel
> > modules are not included in d-i initrd or udebs.
>
> Hi Jessie, and thanks for reporting.
>
> See , which I have yet to forward to
> kernel maintainers.
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
>

Bug#1055806: installation-reports: Installer doesn't recognize laptop's SSD, but calamares does

[Cyril Brulebois]

Hi Pascal,

Please use reply-all…

Pascal Hambourg  (2023-11-11):
> On 11/11/2023 à 21:43, Jessie wrote:
> > 
> > However, when detecting disks, the only disk available for install
> > was the usb drive I had the installer on - it did not detect the
> > 256gb UFS SSD.
> 
> It looks like UFS (Universal Flash Storage, not Unix filesystem) kernel
> modules are not included in d-i initrd or udebs.

Hi Jessie, and thanks for reporting.

See , which I have yet to forward to
kernel maintainers.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1055806: installation-reports: Installer doesn't recognize laptop's SSD, but calamares does

[Pascal Hambourg]

On 11/11/2023 à 21:43, Jessie wrote:


However, when detecting disks, the only disk available for install was the usb 
drive I had the installer on - it did not detect the 256gb UFS SSD.


It looks like UFS (Universal Flash Storage, not Unix filesystem) kernel 
modules are not included in d-i initrd or udebs.

Bug#1055806: installation-reports: Installer doesn't recognize laptop's SSD, but calamares does

[Jessie]

Package: installation-reports
Severity: important
X-Debbugs-Cc: pokozmarti...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: Debian Bookworm Stable Live 12.2 XFCE  
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.2.0-amd64-xfce.iso
  from 2023-10-07 11:29
Date: 2023-11-09 06:33:45.0 -0300

Machine: Laptop ASUS Vivobook GO E1504GA-NJ008W, 8-core Intel Core i3-N305
Partitions:

Output from df -a:
Filesystem 1K-blocks Used Available Use% Mounted on
sysfs  00 0- /sys
proc   00 0- /proc
udev 38251560   3825156   0% /dev
devpts 00 0- /dev/pts
tmpfs 774328 1996772332   1% /run
/dev/sda6  201300212 12421404 178580544   7% /
securityfs 00 0- /sys/kernel/security
tmpfs38716360   3871636   0% /dev/shm
tmpfs   51208  5112   1% /run/lock
cgroup200 0- /sys/fs/cgroup
pstore 00 0- /sys/fs/pstore
efivarfs 192  11276  60% /sys/firmware/efi/efivars
bpf00 0- /sys/fs/bpf
systemd-1  -- -- /proc/sys/fs/binfmt_misc
mqueue 00 0- /dev/mqueue
debugfs00 0- /sys/kernel/debug
hugetlbfs  00 0- /dev/hugepages
tracefs00 0- /sys/kernel/tracing
fusectl00 0- /sys/fs/fuse/connections
configfs   00 0- /sys/kernel/config
ramfs  00 0- 
/run/credentials/systemd-sysctl.service
ramfs  00 0- 
/run/credentials/systemd-sysusers.service
ramfs  00 0- 
/run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs3871636   16   3871620   1% /tmp
/dev/sda1 26214479652182492  31% /boot/efi
ramfs  00 0- 
/run/credentials/systemd-tmpfiles-setup.service
binfmt_misc00 0- /proc/sys/fs/binfmt_misc
tmpfs 774324   72774252   1% /run/user/1000
portal 00 0- /run/user/1000/doc

And also here below the result from lsblk:
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda  8:00 238,4G  0 disk 
├─sda1   8:10   260M  0 part /boot/efi
├─sda2   8:2016M  0 part 
├─sda3   8:30  40,9G  0 part 
├─sda4   8:40   900M  0 part 
├─sda5   8:50   260M  0 part 
└─sda6   8:60 196,1G  0 part /


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [E]
Detect media:   [E]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

When trying to install using the debian non-graphical installer, initial boot 
went fine, network card was not detected due to the kernel not supporting it 
(mediatek 7902) but using a wired connection let me connect to internet and 
pass that step.

However, when detecting disks, the only disk available for install was the usb 
drive I had the installer on - it did not detect the 256gb UFS SSD.
The SSD had a partition with windows 11 (which I shrunk to leave free space for 
the debian). I disabled Secure Boot and Fast Start on the UEFI BIOS, and still 
the debian installer didn't see the SSD.

I tried booting from the Live XFCE version of debian 12 stable, and 
surprisingly, once on the Live system it detected the windows partition (it 
showed up on the desktop as an encrypted drive) and when running the calamares 
installer, it detected the SSD. Thanks to this I was able to install debian.
So, using the same debian ISO (the one from the link I put here when prompted), 
the debian installer couldn't see the SSD, but calamares from Debian Live 
detected the SSD.

Apart from the Debian 12 Live Xfce image, I also tried the testing image 
installer, as well as the image that has the developing version of the 
installer and that installs debian 13 testing (trixie).
None of the installers, no matter the image, detected my SSD.

Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/ins

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

[Diederik de Haas]

On Wednesday, 11 October 2023 20:05:43 CEST Emanuele Rocca wrote:
> To triple-check that the needed module is in there:
> 
>  zstdcat /initrd.img | cpio -itv | grep qnoc-sc8280xp.ko

ICYDK: there's also an `lsinitramfs` command

signature.asc
Description: This is a digitally signed message part.

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

[Axel Beckert]

Hi Emanuele,

Emanuele Rocca wrote:
> On 2023-10-10 01:45, Axel Beckert wrote:
> > I tried that, installer ran through fine, grub boots from disk after
> > installation, kernel loads initramfs and then falls into the initramfs
> > prompt and fractions of a second later (sometimes even beforehand) the
> > whole screen goes black and then nothing helps then pressing the power
> > button for about 10 seconds.
> 
> This sounds like you might have missed the wiki step "Add qnoc-sc8280xp
> module to initramfs":
> https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s

I indeed missed that first, but fixed it via rescue mode of the
d-i image.

> OK then once you chroot into the installed system you should be able to
> check if qnoc-sc8280xp is in /etc/initramfs-tools/modules. If not,
> 
>  echo qnoc-sc8280xp >> /etc/initramfs-tools/modules

Was already in there.

> To triple-check that the needed module is in there:
> 
>  zstdcat /initrd.img | cpio -itv | grep qnoc-sc8280xp.ko

Was also already in there.

Additionally there are quite some messages about things being pending
due to waiting for something else from that kernel module seconds
before the screen blanks. Can send pictures I made of it, in case they
could be helpful.

And since you've mentioned /initrd.img instead of /boot/initrd.img (as
I have a single filesystem installation for now), I also added a
symlink at /initrd.img pointing to /boot/initrd.img. But it didn't
change anything either. (I later noticed that this likely was
unnecessary as GRUB also looks for kernel and initrd.img under /boot
and for a versioned file anyways.)

> In any case, the daily netinst image should now work!

Indeed. Had to use that to check the above today as the mini.iso no
more works due to the updated kernel in sid.

> There's no need to manually copy any firmware and similar
> shenanigans.

Well, still quite some shenanigans left for now.

> If you have the time, please follow the
> InstallingDebianOn/Thinkpad/X13s page again from the begingging to
> the end (quite a few things have changed) and let me know if that
> works for you.

Haven't done a reinstallation for now. (And I'm actually not that keen
on it currently, but I will have to do it at some point, because I
forgot to enable disk encryption. But I'd first like to understand
what's wrong as I seem to have followed all steps.)

Via d-i's rescue mode I have also updated the kernel to 6.5.0-2, but
the symptoms stay: Lots of "pending/waiting for" message by
qnoc-sc8280xp and then a dark, blank screen and nothing happens
anymore.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

[Emanuele Rocca]

Hi Axel,

On 2023-10-10 01:45, Axel Beckert wrote:
> I tried that, installer ran through fine, grub boots from disk after
> installation, kernel loads initramfs and then falls into the initramfs
> prompt and fractions of a second later (sometimes even beforehand) the
> whole screen goes black and then nothing helps then pressing the power
> button for about 10 seconds.

This sounds like you might have missed the wiki step "Add qnoc-sc8280xp
module to initramfs":
https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s

> And I can easily install tons of packages when I boot from the
> installer USB stick into the rescue mode and chroot into the
> installation on disk.

OK then once you chroot into the installed system you should be able to
check if qnoc-sc8280xp is in /etc/initramfs-tools/modules. If not,

 echo qnoc-sc8280xp >> /etc/initramfs-tools/modules
 update-initramfs -u -k all

To triple-check that the needed module is in there:

 zstdcat /initrd.img | cpio -itv | grep qnoc-sc8280xp.ko

In any case, the daily netinst image should now work! There's no need to
manually copy any firmware and similar shenanigans. If you have the
time, please follow the InstallingDebianOn/Thinkpad/X13s page again from
the begingging to the end (quite a few things have changed) and let me
know if that works for you.

Thanks,
  Emanuele

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

[Axel Beckert]

Hi Emanuele,

Axel Beckert wrote:
> Emanuele Rocca wrote:
> > On 2023-05-04 11:53, Axel Beckert wrote:
> > > Sure. I intend to run Debian Unstable on it anyway
> > 
> > Now you can. :-)
> 
> Hmmm, I tried a few days ago (October 1st) with the image from
> https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current/arm64/iso-cd/
> and it hang with a message saying something about "generating empty
> device tree" or so.

And that image didn't contain the dtb files to copy while the mini.iso
from d-i.d.o did.

> > https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s
> 
> Ah, I see, there's much more than just the installer image needed.

I tried that, installer ran through fine, grub boots from disk after
installation, kernel loads initramfs and then falls into the initramfs
prompt and fractions of a second later (sometimes even beforehand) the
whole screen goes black and then nothing helps then pressing the power
button for about 10 seconds.

The same happens if I start the recovery mode from the grub menu when
booting from the disk.

arm64.nopauth is in there.

And I can easily install tons of packages when I boot from the
installer USB stick into the rescue mode and chroot into the
installation on disk.

Even installing the recommended packages did not change anything with
regards to the screen going black about 12 seconds after booting.

I also tried to disable any console font changes via

  dpkg-reconfigure -plow console-setup console-setup-linux

but to no avail.

Any ideas what could have gone wrong or how I can fix this? I feel I'm
_s_ close. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#594827: marked as done (installation-reports: kFreeBSD install using daily-build 20100828-3)

[Debian Bug Tracking System]

Your message dated Sat, 7 Oct 2023 14:15:24 +0300
with message-id 
and subject line kFreeBSD has been removed from Debian ports
has caused the Debian Bug report #594827,
regarding installation-reports: kFreeBSD install using daily-build 20100828-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
594827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: installation-reports
Severity: normal
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-CC: debian-...@lists.debian.org


-- Package-specific info:

Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/20100828-3/kfreebsd-i386/iso-cd/debian-testing-kfreebsd-i386-netinst.iso
Date: 2010-08-28

Machine: KVM 0.9.1
Partitions: 

Disk /dev/ad0: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b4138

Device Boot  Start End  Blocks   Id  System
/dev/ad0p1   *   1249720051968   a5  FreeBSD
Partition 1 has different physical/logical endings:
 phys=(1023, 254, 63) logical=(2496, 122, 58)
/dev/ad0p224972611  9164815  Extended
Partition 2 has different physical/logical beginnings (non-Linux?):
 phys=(1023, 254, 63) logical=(2496, 155, 26)
Partition 2 has different physical/logical endings:
 phys=(1023, 254, 63) logical=(2610, 180, 2)
/dev/ad0p524972611  916480   82  Linux swap /
Solaris

FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/ad0s1 ufs19418446   3013244  14851728  17% /
devfsdevfs   1 1 0 100% /dev
linprocfs
 linprocfs   4 4 0 100% /proc
/sys sysfs   4 4 0 100% /sys
fdescfsfdescfs   1 1 0 100% /dev/fd
tmpfstmpfs 1575252 4   1575248   1% /lib/init/rw

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

In the install menus the first character isn't highlighted when the item is
selected.

Graphical desktop install went through, although on boot gdm3 gives a black
screen as reported in http://bugs.debian.org/592549 .

Despite choosing UK keyboard on install still had to do 'dpkg-reconfigure
kbdcontrol' and choose 'uk.iso.kbd' to get correct keymap on console.

The '-k' of 'lspci -knn' doesn't work. I guess this is a Linux only
option.

lspci -nn:
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC
[Natoma] [8086:1237] (rev 02)
00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
[Natoma/Triton II] [8086:7000]
00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE
[Natoma/Triton II] [8086:7010]
00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
[8086:7113] (rev 03)
00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8]
00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ [10ec:8139] (rev 20)


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/kFreeBSD installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20100827-10:20"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: GNU/kFreeBSD debian-kfreebsd-i386-3 8.1-1-486 #0 Tue Aug 17
22:35:34 CEST 2010 i686 GNU/Linux
lspci -knn: Usage: lspci []
lspci -knn:
lspci -knn: Basic display modes:
lspci -knn: -mm Produce machine-readable outp

Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."

[Axel Beckert]

Hi Emanuele,

Emanuele Rocca wrote:
> On 2023-05-04 11:53, Axel Beckert wrote:
> > Sure. I intend to run Debian Unstable on it anyway
> 
> Now you can. :-)

Hmmm, I tried a few days ago (October 1st) with the image from
https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current/arm64/iso-cd/
and it hang with a message saying something about "generating empty
device tree" or so.

> https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s

Ah, I see, there's much more than just the installer image needed.
Thanks for that hint!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1035477: marked as done (installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services...")

[Debian Bug Tracking System]

Your message dated Fri, 6 Oct 2023 15:06:38 +0200
with message-id 
and subject line Re: Bug#1035477: installation-reports: grub or kernel of D-I 
image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."
has caused the Debian Bug report #1035477,
regarding installation-reports: grub or kernel of D-I image hangs on Thinkpad 
X13s after "EFI stub: Exiting boot services..."
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1035477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
Tags: d-i
X-Debbugs-Cc: Axel Beckert , Dimitri Ledkov , 
Debian ARM Mailing List , Manuel Traut 


Boot method: USB
Image version: 
https://cdimage.debian.org/cdimage/bookworm_di_rc2/arm64/iso-cd/debian-bookworm-DI-rc2-arm64-netinst.iso
Date: 2023-05-03, several times between noon and evening (CEST)

Machine: Thinkpad X13s (ARM)
Partitions: didn't come that far

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

[Note: Had to disable Secure Boot, to be able to boot from my USB 3.0
stick (plugged into the Thinkpad USB-C docking station). Before
disabling Secure Boot I could choose it as boot device but I was
always immediately returned to the device's boot device selection
menu.]

After choosing either "expert install" (first and prefered try) or
"graphical expert install" (second try and second choice) I saw these
three lines and then nothing more happened:

  EFI stub: Booting Linux Kernel...
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services...

Waited 10 minutes at least, i.e. left it alone, did something else and
came back later. Even adding the "debug" kernel parameter didn't bring
up any more details on what's happening.

Ubuntu seems to have had the same problem with Kinetic according to
https://www.reddit.com/r/thinkpad/comments/vh1xse/comment/is1pq78/

But Dimitri's Ubuntu Installer Live image lunar-desktop-arm64.iso from
https://people.canonical.com/~xnox/ubuntu-concept/full/daily-live/current/
as of 2023-03-07 20:08 booted fine without these issues.

It would be nice if Dimitri (xnox@d.o, Cc'ed) could tell us which fix
has been applied by him (or Ubuntu) to this image so that we can fix
this issue also in Debian, maybe even before the release of Bookworm.
(I only read in the recent D-I RC2 annoucement that there is already
some support for the X13s, so I haven't tried it beforehand.)

-- Package-specific info:
[Stripped as — for obvious reasons — the bug report has been written
on a different device.]
--- End Message ---
--- Begin Message ---
Hi Axel,

On 2023-05-04 11:53, Axel Beckert wrote:
> Sure. I intend to run Debian Unstable on it anyway

Now you can. :-)

https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s--- End Message ---

Bug#1052530: installation-reports: HP 15-ef2033dx likes bookworm w/plasma

[debian user]

Package: installation-reports
Severity: normal

Boot method: usb
Image version: Official Debian GNU/Linux Live 12.1.0 kde 2023-07-22T09:48:34Z]
Date: 27 Sep 21 12:22

Machine: HP 15-ef2033dx

Partitions:
Disk /dev/nvme0n1: 500118192 sectors, 238.5 GiB
Model: SK hynix BC711 HFM256GD3JX013N  
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): BEFEDC3E-B565-4089-86B1-A8D2EFC41469
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 500118158
Partitions will be aligned on 2048-sector boundaries
Total free space is 58722925 sectors (28.0 GiB)

Number  Start (sector)End (sector)  Size   Code  Name
   12048 1050623   512.0 MiB   EF00  
   2 105062468159487   32.0 GiB8300  bookworm
   368159488   435161087   175.0 GiB   8300  storage
   4   493881344   500117503   3.0 GiB 8200  Linux swap


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [ ]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [ ]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
It was very pleasant.  Thank you.

Too much cleanup of pkgs installed for no reason, no big deal, used to it... 

I think installer logs are attached if not I'll follow upand attach them.

The attachment file /var/log/installer/installer.tar size is bigger than the 
maximum of 10485760 
bytes: reduce its size else the report cannot be sent

Much obliged, this very brand new computer is very happy with bookworm.
I really appreciate the free os.

L8r,
bw

Bug#1051846: installation-reports: gnome_flashback installation fails on openQA with daily netinst image

[Roland Clobus]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: p...@hands.com

Boot method: CD netinst image
Image version: https://get.debian.org/images/daily-builds/daily/arch-
latest/amd64/iso-cd/debian-testing-amd64-netinst.iso from 20230913_0524
Date: 

Machine: QEMU with UEFI secure boot as on openqa.debian.net, 2GB memory
Partitions: wipe all from a 10GB virtual HD


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

The installation proceeds without error.
After rebooting, the screen with 'Oh no! Something has gone wrong' is shown.

My attempts to reproduce and pinpoint the cause:
I've tested with QXL and VGA graphical cards on openQA. In both cases the 'Oh
no!' is shown.

With the netinst image from 20230909_0504, the flashback GUI started initially
with the grey top menu bar, but that got replaced by the black menu bar of the
regular GNOME desktop.

The last known good netinst image was from 20230910_0509.
The first netinst image with this issue is from 20230910_1109.
This narrows down the number of possible causes a bit.

To see more installation attempts (every 6 hours):
* Go to https://openqa.debian.net/group_overview/10
* Take a build that has no running jobs (i.e. no blue bar)
* Click on the red part of the bar
* Click on the red circle behind 'gnome_flash_flash' (before
'_graphical_wait_login' or 'complete_install')
* Installation logs and additional information can be found in the 'Logs &
Assets' tab of the test

With kind regards,
Roland Clobus


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux silent 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5000]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Intel Corporation Device [8086:2010]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5007]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Lynx Point KT 
Controller [8086:8c3d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I217-V [8086:153b] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:e000]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #2 [8086:8c2d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5006]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Lynx Point High 
Definition Audio Controller [8086:8c20] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:a002]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Lynx Point PCI Express 
Root Port #1 [8086:8c10] (rev d4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev d4)
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #1 [8086:8c26] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5006]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Lynx Point LPC 
Controller [8086:8c4a] (rev 04)
lspci -knn:   

Bug#1051696: installation-reports

[Олег Переможець]

Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/cdimage/archive/10.13.0-live/i386/bt-hybrid/

( debian-live-10.13.0-i386-xfce.iso )


Date:  2023

Machine:  Asus P4R8L
https://www.asus.com/Barebone_PC/P_Series_0811L/PunditR350/#Specifications

Processor: Pentium 4 (0.09) 2993 MHz (32-bit)

Memory: 2GB


Partitions:

...@...-pc:~$ df -Tl

Filesystem Type 1K-blocks Used Available Use% Mounted on

udev devtmpfs 983556 0 983556 0% /dev

tmpfs tmpfs 199944 16852 183092 9% /run

/dev/sda1 ext4 302217292 83380020 203412412 30% /

tmpfs tmpfs 999704 0 999704 0% /dev/shm

tmpfs tmpfs 5120 8 5112 1% /run/lock

tmpfs tmpfs 999704 0 999704 0% /sys/fs/cgroup

tmpfs tmpfs 199940 20 199920 1% /run/user/1000



Output of

….@...-pc:~$ lspci -knn

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RS300
Host Bridge [1002:5833] (rev 02)

Subsystem: ASUSTeK Computer Inc. RS300 Host Bridge [1043:8107]

Kernel driver in use: agpgart-ati

00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RS300 AGP
Bridge [1002:5838]

00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] OHCI
USB Controller #1 [1002:4347] (rev 01)

Subsystem: ASUSTeK Computer Inc. SB200 OHCI USB Controller [1043:8108]

Kernel driver in use: ohci-pci

Kernel modules: ohci_pci

00:13.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] OHCI
USB Controller #2 [1002:4348] (rev 01)

Subsystem: ASUSTeK Computer Inc. SB200 OHCI USB Controller [1043:8108]

Kernel driver in use: ohci-pci

Kernel modules: ohci_pci

00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] EHCI
USB Controller [1002:4345] (rev 01)

Subsystem: ASUSTeK Computer Inc. SB200 EHCI USB Controller [1043:8108]

Kernel driver in use: ehci-pci

Kernel modules: ehci_pci

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SMBus
[1002:4353] (rev 1a)

Subsystem: ASUSTeK Computer Inc. SB200 SMBus Controller [1043:8108]

Kernel driver in use: piix4_smbus

Kernel modules: i2c_piix4

00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] Dual
Channel Bus Master PCI IDE Controller [1002:4349]

Subsystem: ASUSTeK Computer Inc. SB200 IDE Controller [1043:8108]

Kernel driver in use: pata_atiixp

Kernel modules: pata_atiixp, ata_generic

00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] SB200 PCI
to LPC Bridge [1002:434c]

Subsystem: ASUSTeK Computer Inc. SB200 PCI to LPC Bridge [1043:8108]

00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] IXP200
3COM 3C920B Ethernet Controller [1002:4342]

01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] RS300 [Radeon 9100 IGP] [1002:5834]

Subsystem: ASUSTeK Computer Inc. RS300 [Radeon 9100 IGP] [1043:8107]

Kernel driver in use: radeon

Kernel modules: radeonfb, radeon

02:08.0 Ethernet controller [0200]: 3Com Corporation 3Com 3C920B-EMB-WNM
Integrated Fast Ethernet Controller [10b7:9202] (rev 40)

Subsystem: ASUSTeK Computer Inc. 3Com 3C920B-EMB-WNM Integrated Fast
Ethernet Controller [1043:8108]

Kernel driver in use: 3c59x

Kernel modules: 3c59x

02:09.0 Multimedia audio controller [0401]: Creative Labs EMU10k1 [Sound
Blaster Live! Series] [1102:0002] (rev 06)

Subsystem: Creative Labs CT4832 SBLive! Value [1102:8027]

Kernel driver in use: snd_emu10k1

Kernel modules: snd_emu10k1

02:09.1 Input device controller [0980]: Creative Labs SB Live! Game Port
[1102:7002] (rev 06)

Subsystem: Creative Labs Gameport Joystick [1102:0020]

Kernel driver in use: Emu10k1_gameport

Kernel modules: emu10k1_gp





...@...-pc:~$ lspci -nn

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RS300
Host Bridge [1002:5833] (rev 02)

00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RS300 AGP
Bridge [1002:5838]

00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] OHCI
USB Controller #1 [1002:4347] (rev 01)

00:13.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] OHCI
USB Controller #2 [1002:4348] (rev 01)

00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] EHCI
USB Controller [1002:4345] (rev 01)

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SMBus
[1002:4353] (rev 1a)

00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] Dual
Channel Bus Master PCI IDE Controller [1002:4349]

00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] SB200 PCI
to LPC Bridge [1002:434c]

00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] IXP200
3COM 3C920B Ethernet Controller [1002:4342]

01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] RS300 [Radeon 9100 IGP] [1002:5834]

02:08.0 Ethernet controller [0200]: 3Com Corporation 3Com 3C920B-EMB-WNM
Integrated Fast Ethernet Controller [10b7:9202] (rev 40)

02:09.0 Multimedia audio controller [0401]: Creative Labs EMU10k1 [Sound
Blaster Live! Series] [1102:0002] (rev 06)

02:09.1 Input device

Bug#1050000: installation-reports: please install libpam-fprintd on a laptop with fingerprint reader

[Fabian Greffrath]

Package: installation-reports
Severity: wishlist


Boot method: USB
Image version: 
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 20230808

Machine: Lenovo IdeaPad 5 14IAL7
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Hi,

I don't have a bug to report, installation went smooth this time! Just
a suggestion to make: My laptop has a built-in fingerprint reader
(relevant output of lsusb below). However, after installation it is
still impossible to register a fingerprint on the user setup page of
the gnome-settings app. This possibility is only added after the
libpam-fprintd package is installed. Thus, my suggestion is that if a
fingerprint reader is detected during the hardware detection phase
during the Debian installation to install the libpam-fprintd package.

Thanks!

 - Fabian


Bus 003 Device 003: ID 04f3:0c4d Elan Microelectronics Corp. ELAN:Fingerprint


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="13 (trixie) - installer build 20230808-00:02:33"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux brainbug 6.4.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.4-2 
(2023-07-30) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4601] 
(rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:382b]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Alder 
Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
lspci -knn: Subsystem: Lenovo Device [17aa:382f]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation 
Alder Lake Innovation Platform Framework Processor Participant [8086:461d] (rev 
04)
lspci -knn: Subsystem: Lenovo Device [17aa:3832]
lspci -knn: 00:06.0 PCI bridge [0604]: Intel Corporation 12th Gen Core 
Processor PCI Express x4 Controller #0 [8086:464d] (rev 04)
lspci -knn: Subsystem: COMPAL Electronics Inc Device [14c0:013d]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation 12th Gen Core 
Processor Gaussian & Neural Accelerator [8086:464f] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:3838]
lspci -knn: 00:0d.0 USB controller [0c03]: Intel Corporation Alder Lake-P 
Thunderbolt 4 USB Controller [8086:461e] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Alder Lake PCH USB 
3.2 xHCI Host Controller [8086:51ed] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:3825]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.2 RAM memory [0500]: Intel Corporation Alder Lake PCH Shared 
SRAM [8086:51ef] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:3823]
lspci -knn: 00:15.0 Serial bus controller [0c80]: Intel Corporation Alder Lake 
PCH Serial IO I2C Controller #0 [8086:51e8] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:3814]
lspci -knn: Kernel driver in use: intel-lpss
lspci -knn: Kernel modules: intel_lpss_pci
lspci -knn: 00:15.3 Serial bus controller [0c80]: Intel Corporation Alder Lake 
PCH Serial IO I2C Controller #3 [8086:51eb] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:3821]
lspci -knn: Kernel driver in use: intel-lpss
lspci -knn: Kernel modules: intel_lpss_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Alder 
Lake PCH HECI Controller [8086:51e0] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:382d]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:51ba] 
(rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:3809]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Alder Lake PCI Express 
x1 Root Port #10 [8086:51b1] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:380d]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1e.0 Communication controller [0780]: Intel Corporation Alder 
Lake PCH UART #0 [8086:51a8] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:3818]
lspci -knn: Kernel dr

Bug#1042563: installation-reports: installation OK, screen remains blank during boot and GDM Greeter

[Dr. Axel Stammler]

Hi, Steve and Len,

Thank you for pointing this out.

On Mon 2023-07-31 09.22.35, Lennart Sorensen wrote:

On Sun, Jul 30, 2023 at 01:08:13PM +0100, Steve McIntyre wrote:



I'm a little confused here...

You say the machine is a Thinkpad X230, but the attached cpuinfo says
you have an Atom CPU and the DMI data says it's an ASUSTeK Eee
PC. What hardware are we actually looking at here please?


It also says 4.15 kernel which is clearly not bookworm.  I think the
installation log was accidentally from a much earlier install on a
different machine.


The installation report must indeed be ancient, from an installation on an Eee 
‘netbook’ some years ago, possibly Stretch or an even older release.

My bug report relates to the situation after an upgrade from Bullseye on the 
Thinkpad X230:

$ lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Address sizes:   36 bits physical, 48 bits virtual
Byte Order:  Little Endian
CPU(s):  4
On-line CPU(s) list: 0-3
Vendor ID:   GenuineIntel
Model name:  Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
CPU family:  6
Model:   58
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):   1
Stepping:9
CPU(s) scaling MHz:  55%
CPU max MHz: 3300.
CPU min MHz: 1200.
BogoMIPS:5188.29
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida 
arat pln pts md_clear flush_l1d
Virtualization:  VT-x
L1d cache:   64 KiB (2 instances)
L1i cache:   64 KiB (2 instances)
L2 cache:512 KiB (2 instances)
L3 cache:3 MiB (1 instance)
NUMA node(s):1
NUMA node0 CPU(s):   0-3
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf:  Mitigation; PTE Inversion; VMX conditional 
cache flushes, SMT vulnerable
Vulnerability Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:  Mitigation; PTI
Vulnerability Mmio stale data:   Unknown: No mitigations
Vulnerability Retbleed:  Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled 
via prctl
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Retpolines, IBPB conditional, 
IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds: Vulnerable: No microcode
Vulnerability Tsx async abort:   Not affected

$ uname -a
Linux bamboo 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) 
x86_64 GNU/Linux

$ sudo lshw
bamboo
description: Notebook
product: 23331U1 (LENOVO_MT_2333)
vendor: LENOVO
version: ThinkPad X230
serial: PK056K9
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
configuration: administrator_password=disabled chassis=notebook 
family=ThinkPad X230 power-on_password=disabled sku=LENOVO_MT_2333 
uuid=470dc001-5217-11cb-9533-a6ac2582edd3
  *-core
   description: Motherboard
   product: 23331U1
   vendor: LENOVO
   physical id: 0
   version: Not Defined
   serial: 1ZSSK37N2VP
   slot: Not Available
 *-cpu
  description: CPU
  product: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
  vendor: Intel Corp.
  physical id: 1
  bus info: cpu@0
  version: 6.58.9
  serial: None
  slot: CPU Socket - U3E1
  size: 2019MHz
  capacity: 3300MHz
  width: 64 bits
  clock: 100MHz
  capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl 
vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd 
ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq
  

Bug#1042563: installation-reports: installation OK, screen remains blank during boot and GDM Greeter

[Lennart Sorensen]

On Sun, Jul 30, 2023 at 01:08:13PM +0100, Steve McIntyre wrote:
> Hi Axel!
> 
> I'm a little confused here...
> 
> You say the machine is a Thinkpad X230, but the attached cpuinfo says
> you have an Atom CPU and the DMI data says it's an ASUSTeK Eee
> PC. What hardware are we actually looking at here please?

It also says 4.15 kernel which is clearly not bookworm.  I think the
installation log was accidentally from a much earlier install on a
different machine.

-- 
Len Sorensen

Bug#1042563: installation-reports: installation OK, screen remains blank during boot and GDM Greeter

[Steve McIntyre]

Hi Axel!

I'm a little confused here...

You say the machine is a Thinkpad X230, but the attached cpuinfo says
you have an Atom CPU and the DMI data says it's an ASUSTeK Eee
PC. What hardware are we actually looking at here please?

On Sun, Jul 30, 2023 at 01:48:47PM +0200, Axel Stammler wrote:
>Package: installation-reports
>Severity: important
>X-Debbugs-Cc: a...@users.sourceforge.net
>
>(Please provide enough information to help the Debian
>maintainers evaluate the report efficiently - e.g., by filling
>in the sections below.)
>
>Everything work well _after_ I remove the computer from the docking station 
>and put it
>back.
>
>- boots into visible Grub menu (including background picture)
>- Grub works well
>- kernel starts without any output (except that the screen is first grey = 
>lit-up and
>  turns totally dark a few seconds later)
>- password prompt for encrypted disk (if used) is not visible but password can 
>be entered
>  blindly; password prompt and all other output becomes visible when computer 
> is briefly
>  removed from docking station
>- GDM is started, Greeter screen remains invisible if computer has not been 
>removed from
>  station, becomes visible then
>- Greeter screen is visible after logging out
>
>Boot method: network
>Image version: 
>https://www.debian.org/releases/bookworm/amd64/ch05s01.en.html#boot-initrd
>Date: 
>
>Machine: Think Pad X 230 with docking station
>Partitions: 
>
>
>Base System Installation Checklist:
>[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
>Initial boot:   [O]
>Detect network card:[O]
>Configure network:  [O]
>Detect media:   [O]
>Load installer modules: [O]
>Clock/timezone setup:   [O]
>User/password setup:[O]
>Detect hard drives: [O]
>Partition hard drives:  [O]
>Install base system:[O]
>Install tasks:  [O]
>Install boot loader:[O]
>Overall install:[O]
>
>Comments/Problems:
>
>see above
>
>Please make sure that any installation logs that you think would
>be useful are attached to this report. (You can find them in the
>installer system in /var/log/ and later on the installed system
>under /var/log/installer.) Please compress large files using gzip.
>
>
>-- Package-specific info:
>
>==
>Installer lsb-release:
>==
>DISTRIB_ID=Debian
>DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
>DISTRIB_RELEASE="10 (buster) - installer build 20180430-00:04"
>X_INSTALLATION_MEDIUM=cdrom
>
>==
>Installer hardware-summary:
>==
>uname -a: Linux bamboo-w 4.15.0-3-amd64 #1 SMP Debian 4.15.17-1 (2018-04-19) 
>x86_64 GNU/Linux
>lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
>D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010] (rev 02)
>lspci -knn:Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
>lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom 
>Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 
>02)
>lspci -knn:Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
>lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Atom 
>Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012] (rev 
>02)
>lspci -knn:Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
>lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family 
>High Definition Audio Controller [8086:27d8] (rev 02)
>lspci -knn:Subsystem: ASUSTeK Computer Inc. Device [1043:84d3]
>lspci -knn:Kernel driver in use: snd_hda_intel
>lspci -knn:Kernel modules: snd_hda_intel
>lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
>Express Port 1 [8086:27d0] (rev 02)
>lspci -knn:Kernel driver in use: pcieport
>lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
>Express Port 2 [8086:27d2] (rev 02)
>lspci -knn:Kernel driver in use: pcieport
>lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
>Express Port 4 [8086:27d6] (rev 02)
>lspci -knn:Kernel driver in use: pcieport
>lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
>USB UHCI Controller #1 [8086:27c8] (rev 02)
>lspci -knn:Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
>lspci -knn:Kernel driver in use: uhci_hcd
>lspci -knn:Kernel modules: uhci_hcd
>lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
>USB UHCI Controller #2 [8086:27c9] (rev 02)
>lspci -knn:S

Bug#1042563: installation-reports: installation OK, screen remains blank during boot and GDM Greeter

[Axel Stammler]

Package: installation-reports
Severity: important
X-Debbugs-Cc: a...@users.sourceforge.net

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Everything work well _after_ I remove the computer from the docking station and 
put it
back.

- boots into visible Grub menu (including background picture)
- Grub works well
- kernel starts without any output (except that the screen is first grey = 
lit-up and
  turns totally dark a few seconds later)
- password prompt for encrypted disk (if used) is not visible but password can 
be entered
  blindly; password prompt and all other output becomes visible when computer 
is briefly
  removed from docking station
- GDM is started, Greeter screen remains invisible if computer has not been 
removed from
  station, becomes visible then
- Greeter screen is visible after logging out

Boot method: network
Image version: 
https://www.debian.org/releases/bookworm/amd64/ch05s01.en.html#boot-initrd
Date: 

Machine: Think Pad X 230 with docking station
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

see above

Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20180430-00:04"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux bamboo-w 4.15.0-3-amd64 #1 SMP Debian 4.15.17-1 (2018-04-19) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom 
Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 
02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family 
High Definition Audio Controller [8086:27d8] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:84d3]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 1 [8086:27d0] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 2 [8086:27d2] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI 
Express Port 4 [8086:27d6] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #1 [8086:27c8] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #2 [8086:27c9] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #3 [8086:27ca] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB UHCI Controller #4 [8086:27cb] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.7 USB controller [0c03]: In

Bug#1042070: installation-reports: on apt-get update; apt-get upgrade; errors appear about firmware /lib/firmware/amdgpu/ip_discovery.bin

[Hammad Rauf]

Thanks for the feedback. I ended up reinstalling with
the debian-12.1.0-amd64-netinst.iso image. No issues so far.

Thanks for looking into this.

Hammad Rauf

On Wed, Jul 26, 2023 at 2:04 PM Cyril Brulebois  wrote:

> Hi,
>
> rauf.hammad  (2023-07-25):
> > On doing apt-get update; apt-get upgrade; warnings about missing
> firmware /lib/firmware/amdgpu/* appeared.
>
> Those are really not a problem.
>
> > Excrept from console messages during: apt install <>; is given
> below:
> > 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-10-amd64
> >  linux-image-amd64
> >  initramfs-tools
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > root@peace-homes:~#
>
> The raspi-firmware thing is a grave problem instead (fixed in the 12.1
> live images: raspi-firmware is no longer installed by mistake):
>  - delete z50 hooks;
>  - then purge the raspi-firmware package.
>
> Something like this should help:
>
> rm /etc/initramfs/post-update.d/z50-raspi-firmware
> rm /etc/kernel/postrm.d/z50-raspi-firmware
> rm /etc/kernel/postinst.d/z50-raspi-firmware
> dpkg -P raspi-firmware
>
> Afterwards, you should be able to configure other packages with:
>
> dpkg --configure -a
>
> And the package manager (apt, apt-get, etc.) should be happier at this
> point.
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
>

Bug#1042070: marked as done (installation-reports: on apt-get update; apt-get upgrade; errors appear about firmware /lib/firmware/amdgpu/ip_discovery.bin)

[Debian Bug Tracking System]

Your message dated Wed, 26 Jul 2023 20:59:06 +
with message-id 
and subject line Bug#1042070: fixed in raspi-firmware 1.20230405+ds-2
has caused the Debian Bug report #1042070,
regarding installation-reports: on apt-get update; apt-get upgrade; errors 
appear about firmware /lib/firmware/amdgpu/ip_discovery.bin
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: important
X-Debbugs-Cc: rauf.ham...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: debian-live-12.0.0-amd64-cinnamon.iso 
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
Date: 

Machine: HP Thin Client t630, cpu: AMD GX-420GI (SOC), Integrated GPU Radeon 
R7E, 8GB RAM, USB Attached 500GB Boot HDD
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

On doing apt-get update; apt-get upgrade; warnings about missing firmware 
/lib/firmware/amdgpu/* appeared.

Excrept from console messages during: apt install <>; is given below:

run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure):
 installed linux-image-6.1.0-10-amd64 package post-installation script 
subprocess returned error exit status 1
Setting up python3-pycurl (7.45.2-3) ...
Setting up python3-pysimplesoap (1.16.2-5) ...
Setting up python3-debianbts (4.0.1) ...
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); however:
  Package linux-image-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up python3-reportbug (12.0.0) ...
Setting up reportbug (12.0.0) ...
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-10-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module 
amdgpu
I: The initramfs will attempt to resume from /dev/sda3
I: (UUID=b497c0e6-7e96-4da8-acf4-e86d985eebdb)
I: Set the RESUME variable to override this.
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return 

Bug#1042070: installation-reports: on apt-get update; apt-get upgrade; errors appear about firmware /lib/firmware/amdgpu/ip_discovery.bin

[Cyril Brulebois]

Hi,

rauf.hammad  (2023-07-25):
> On doing apt-get update; apt-get upgrade; warnings about missing firmware 
> /lib/firmware/amdgpu/* appeared.

Those are really not a problem.

> Excrept from console messages during: apt install <>; is given 
> below:
> 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-10-amd64
>  linux-image-amd64
>  initramfs-tools
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> root@peace-homes:~#

The raspi-firmware thing is a grave problem instead (fixed in the 12.1
live images: raspi-firmware is no longer installed by mistake):
 - delete z50 hooks;
 - then purge the raspi-firmware package.

Something like this should help:

rm /etc/initramfs/post-update.d/z50-raspi-firmware
rm /etc/kernel/postrm.d/z50-raspi-firmware
rm /etc/kernel/postinst.d/z50-raspi-firmware
dpkg -P raspi-firmware

Afterwards, you should be able to configure other packages with:

dpkg --configure -a

And the package manager (apt, apt-get, etc.) should be happier at this
point.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1042070: installation-reports: on apt-get update; apt-get upgrade; errors appear about firmware /lib/firmware/amdgpu/ip_discovery.bin

[rauf.hammad]

Package: installation-reports
Severity: important
X-Debbugs-Cc: rauf.ham...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: debian-live-12.0.0-amd64-cinnamon.iso 
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
Date: 

Machine: HP Thin Client t630, cpu: AMD GX-420GI (SOC), Integrated GPU Radeon 
R7E, 8GB RAM, USB Attached 500GB Boot HDD
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

On doing apt-get update; apt-get upgrade; warnings about missing firmware 
/lib/firmware/amdgpu/* appeared.

Excrept from console messages during: apt install <>; is given below:

run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure):
 installed linux-image-6.1.0-10-amd64 package post-installation script 
subprocess returned error exit status 1
Setting up python3-pycurl (7.45.2-3) ...
Setting up python3-pysimplesoap (1.16.2-5) ...
Setting up python3-debianbts (4.0.1) ...
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); however:
  Package linux-image-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up python3-reportbug (12.0.0) ...
Setting up reportbug (12.0.0) ...
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-10-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module 
amdgpu
I: The initramfs will attempt to resume from /dev/sda3
I: (UUID=b497c0e6-7e96-4da8-acf4-e86d985eebdb)
I: Set the RESUME variable to override this.
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-10-amd64
 linux-image-amd64
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@peace-homes:~#


-- Package-specific info:

Bug#1042059: installation-reports: success

[Axel Stammler]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: a...@users.sourceforge.net

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: network
Image version: 
https://www.debian.org/releases/bookworm/amd64/ch05s01.en.html#boot-initrd
Date: 

Machine: Lenovo Think Pad X 230
Partitions: 
Filesystem Type 1K-blocks  Used Available Use% Mounted on
udev   devtmpfs   3878408 0   3878408   0% /dev
tmpfs  tmpfs   782380  1644780736   1% /run
/dev/sdd1  ext4   2808488127452   2518220   5% /
/dev/sdd6  ext4  19047080   4867716  13186496  27% /usr
tmpfs  tmpfs  3911880 0   3911880   0% /dev/shm
tmpfs  tmpfs 5120 8  5112   1% /run/lock
/dev/sdd5  ext4   1307744   228   1222832   1% /tmp
/dev/sdd9  ext4978972141860770040  16% /home
/dev/sdd7  ext4   4720160762808   3696900  18% /var
tmpfs  tmpfs   782376   148782228   1% /run/user/1001

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O] SD card
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: boots & works correctly & very fast (on different machines, 
too), probably due to better firmware




Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux bookworm-sd 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.27-1 (2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core 
processor DRAM Controller [8086:0154] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen 
Core processor Graphics Controller [8086:0166] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 
Series Chipset Family KT Controller [8086:1e3d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM 
Gigabit Network Connection (Lewisville) [8086:1502] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 3 [8086:1e14] (rev c4)

Processed: tagging 1030328, reassign 1040712 to installation-reports, tagging 1030346, tagging 1040746 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1030328 + sid trixie
Bug #1030328 [src:quelcom] quelcom: FTBFS with TeXInfo 7.0.x
Added tag(s) sid and trixie.
> reassign 1040712 installation-reports
Bug #1040712 [installation-reports debian 12] installation-reports Debian 12
Warning: Unknown package 'debian'
Warning: Unknown package '12'
Bug reassigned from package 'installation-reports debian 12' to 
'installation-reports'.
Ignoring request to alter found versions of bug #1040712 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1040712 to the same values 
previously set
> tags 1030346 + sid trixie
Bug #1030346 {Done: David Bremner } [src:elpa-transient] 
elpa-transient: FTBFS with TeXInfo 7.0.x
Added tag(s) sid and trixie.
> tags 1040746 + experimental
Bug #1040746 [src:gnome-photos] ftbfs in gnome-photos with recent babl
Added tag(s) experimental.
> tags 1030322 + sid trixie experimental
Bug #1030322 [src:gnushogi] gnushogi: FTBFS with TeXInfo 7.0.x
Added tag(s) trixie, experimental, and sid.
> tags 1040801 + sid trixie
Bug #1040801 [mcomix] mcomix: pillow 10.0.0 not recognized as higher than 6.0.0
Added tag(s) sid and trixie.
> tags 1030350 + sid trixie
Bug #1030350 [src:fweb] fweb: FTBFS with TeXInfo 7.0.x
Added tag(s) trixie and sid.
> tags 1030367 + sid trixie
Bug #1030367 [src:festival] festival: FTBFS with TeXInfo 7.0.x
Added tag(s) sid and trixie.
> tags 1030375 + sid trixie
Bug #1030375 [src:proofgeneral] proofgeneral: FTBFS with TeXInfo 7.0.x
Added tag(s) trixie and sid.
> tags 1030385 + sid trixie
Bug #1030385 {Done: Samuel Thibault } [src:flite] flite: 
FTBFS with TeXInfo 7.0.x
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1030322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030322
1030328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030328
1030346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030346
1030350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030350
1030367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030367
1030375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030375
1030385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030385
1040712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040712
1040746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040746
1040801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:dbus 1.12.20-3
Bug #1040790 [installation-reports] installation-reports: ID in /etc/machine-id 
and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation
Bug reassigned from package 'installation-reports' to 'src:dbus'.
Ignoring request to alter found versions of bug #1040790 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1040790 to the same values 
previously set
Bug #1040790 [src:dbus] installation-reports: ID in /etc/machine-id and 
/var/lib/dbus/machine-id mismatch on fresh debian 12 installation
Marked as found in versions dbus/1.12.20-3.

-- 
1040790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[Simon McVittie]

Control: reassign -1 src:dbus 1.12.20-3

On Mon, 10 Jul 2023 at 18:43:06 +0100, Luca Boccassi wrote:
> As a wild guess, maybe the split of src:dbus into multiple packages
> affected the order in which the postinsts run, and now systemd's runs
> first and creates /etc/machine-id, and then dbus-daemon's runs and
> creates /var/lib/dbus/machine-id.

The ordering here is not *meant* to matter, because dbus-uuidgen is meant
to copy /etc/machine-id if it already exists and has suitable contents,
and systemd-machine-id-setup is meant to copy /var/lib/dbus/machine-id
if *that* already exists and has suitable contents.

> mkdir -p "${DPKG_ROOT:-/}var/lib/dbus"
> dbus-uuidgen --ensure="${DPKG_ROOT:-/}var/lib/dbus/machine-id"

I think the regression here is that in attempting to respect DPKG_ROOT,
I replaced dbus-uuidgen --ensure (which copies an existing systemd
machine ID if one exists) with dbus-uuidgen --ensure=PATH (which doesn't).
This was at the same time as the split into dbus.deb / dbus-daemon.deb,
but it was an orthogonal change. bullseye is unaffected, bookworm is the
first release with this.

I'm sorry that it took so long to notice this. I should have had test
coverage that would have detected this error.

> There is a tmpfiles.d shipped by dbus-daemon that creates
> /var/lib/dbus/machine-id as a symlink to /etc/machine-id if it exists,
> but this snippet runs _after_ the dbus-uuidgen so effectively it is
> always a no-op on package install:

As an upstream, this is clearly the right thing to do, but as a
downstream, I'm intentionally not relying on it as load-bearing by
default. There is nothing in Debian that guarantees that /etc/machine-id
will be created, unless we happen to be booting with systemd, which
isn't guaranteed; and if it did get created, as far as I can see, there
is technically also nothing that guarantees that it won't subsequently
be deleted.

https://bugs.debian.org/745876 proposed creating the machine ID in
base-files as a basic Debian feature that any package can rely on,
but it was closed as wontfix.

See also https://bugs.debian.org/783716 for more background.

Of course, d-i doesn't provide a way to not install systemd-sysv, but
a vocal minority of users and developers use non-default installation
mechanisms to get a different init system and consider that to be
a critically important use-case; and I'm concerned that even if these
users got a machine ID generated during installation, they would delete
it as a perceived systemd'ism, and then complain loudly in the form of
RC bugs when D-Bus doesn't work because /var/lib/dbus/machine-id is now
a dangling symlink.

smcv

Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[Luca Boccassi]

On Mon, 10 Jul 2023 17:14:48 +0100 Steve McIntyre 
wrote:
> Hi, and thanks for your bug report!
> 
> On Mon, Jul 10, 2023 at 05:27:50PM +0200, yogg wrote:
> >Package: installation-reports
> >Severity: serious
> >Tags: d-i
> >Justification: https://wiki.debian.org/MachineId
> >
> 
> ...
> 
> >After installation was finished and the system has been restarted
the
> >files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not
linked
> >in any way (no soft or hardlink) and the ID inside the files differ
> >from each other.
> 
> I've confirmed this bug just now, doing a clean installation from the
> 12.0.0 amd64 netinst.

As a wild guess, maybe the split of src:dbus into multiple packages
affected the order in which the postinsts run, and now systemd's runs
first and creates /etc/machine-id, and then dbus-daemon's runs and
creates /var/lib/dbus/machine-id.

There is a tmpfiles.d shipped by dbus-daemon that creates
/var/lib/dbus/machine-id as a symlink to /etc/machine-id if it exists,
but this snippet runs _after_ the dbus-uuidgen so effectively it is
always a no-op on package install:

$ cat /var/lib/dpkg/info/dbus-daemon.postinst 
#!/bin/sh

set -e

if [ "$1" = configure ]; then
# This is idempotent, so it's OK to do every time. The system bus' init
# script does this anyway, but you also have to do this before a session
# bus will work on non-systemd systems, so we do this here for the
# benefit of people starting a temporary session bus in a chroot.
mkdir -p "${DPKG_ROOT:-/}var/lib/dbus"
dbus-uuidgen --ensure="${DPKG_ROOT:-/}var/lib/dbus/machine-id"
fi

# Automatically added by dh_installtmpfiles/13.11.4
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -x "$(command -v systemd-tmpfiles)" ]; then
systemd-tmpfiles ${DPKG_ROOT:+--root="$DPKG_ROOT"} --create 
dbus.conf >/dev/null || true
fi
fi
# End automatically added section

It seems to me a safe way to fix this and do the right thing is to swap
the #DEBHELPER# token and the manual dbus-uuidgen block in dbus-
daemon's postinst. Then on systemd systems the tmpfiles will win and on
other systems dbus-uuidgen will do its job.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[Steve McIntyre]

Hi, and thanks for your bug report!

On Mon, Jul 10, 2023 at 05:27:50PM +0200, yogg wrote:
>Package: installation-reports
>Severity: serious
>Tags: d-i
>Justification: https://wiki.debian.org/MachineId
>

...

>After installation was finished and the system has been restarted the
>files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked
>in any way (no soft or hardlink) and the ID inside the files differ
>from each other.

I've confirmed this bug just now, doing a clean installation from the
12.0.0 amd64 netinst.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall

Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation

[yogg]

Package: installation-reports
Severity: serious
Tags: d-i
Justification: https://wiki.debian.org/MachineId

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: CD/network
Image version: http://ftp.debian.org/debian/dists/bookworm/main/installer-amd64/
Date: 2023-07-10

Machine: Virtual-Maschine
Partitions:
Disk /dev/vda: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xcf0c07c3

Device Boot   Start  End  Sectors  Size Id Type
/dev/vda1  2048  2000895  1998848  976M 82 Linux swap / Solaris
/dev/vda2  *2000896 20969471 189685769G 83 Linux



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]?

Comments/Problems:

After installation was finished and the system has been restarted the files 
"/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked in any way (no 
soft or hardlink) and the ID inside the files differ from each other.

Expected:
"cat /etc/machine-id /var/lib/dbus/machine-id" should return the same ID two 
times

Workaround:
rm /etc/machine-id /var/lib/dbus/machine-id && dbus-uuidgen 
--ensure=/etc/machine-id && dbus-uuidgen --ensure


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux debian-test 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.27-1 (2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 
[1013:00b8]
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: cirrus
lspci -knn: Kernel modules: cirrus
lspci -knn: 00:03.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:04.0 Communication controller [0780]: Red Hat, Inc. Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:05.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:06.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory 
balloon [1af4:1002]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0005]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:07.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG 
[1af4:1005]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0004]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lsmod: Module  Size  Used by
lsmod: fuse  176128  0
lsmod: battery28672  0
lsmod: dm_mod184320  0
lsmod: md_mod192512  0
lsmod: xfs  1945600  0
lsmod: jfs   221184  0
lsmod: btrfs  

Bug#1040759: installation-reports: "out of memory" message at boot, then unable to update processor microcode, and kernel panic

[Ari Fryxell]

Package: installation-reports
Severity: important
Tags: d-i
X-Debbugs-Cc: ari.fryx...@proton.me

Boot method: USB
Image version: Debian 12.0.0-amd64-netist downloaded from July 3rd (i.e. a week 
old build)
Date: July 9, 2023

Machine: System76 serw10 laptop with an Intel Core i7-7700K CPU (CPU family 6, 
model 158, stepping 9)
Partitions: 
Filesystem  Type 1K-blocksUsed Available Use% Mounted on
udevdevtmpfs  32815780   0  32815780   0% /dev
tmpfs   tmpfs  65670041732   6565272   1% /run
/dev/nvme1n1p3  ext4  28660644   10988  27168440   1% /
/dev/nvme1n1p4  ext4 114760836 6898996 101986080   7% /usr
tmpfs   tmpfs 32835012   0  32835012   0% /dev/shm
tmpfs   tmpfs 5120  12  5108   1% /run/lock
/dev/nvme1n1p2  ext4989032  117276804172  13% /boot
/dev/nvme1n1p8  ext4  23854928  24  22617812   1% /opt
/dev/nvme1n1p12 ext4   9510080 220   9005184   1% /tmp
/dev/nvme1n1p13 ext4  28660644 120  27179308   1% /usr/local
/dev/nvme1n1p14 ext4  47745772  24  45287944   1% /usr/src
/dev/nvme1n1p5  ext4 256921924   27736 243770604   1% /home
/dev/nvme1n1p7  ext4  81121736  433584  76521396   1% /var
/dev/nvme1n1p1  vfat   10219846112   1015872   1% /boot/efi
tmpfs   tmpfs  6567000 144   6566856   1% /run/user/1000

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

During the first boot, the system displays an "out of memory" message (this
seems to be during the initramfs stage).  Nevertheless after pressing a key
it presents two successive screens of a failure to load microcode message.
After the second message, the boot stops and the power button has to be
pressed.  The OS doesn't reach login.

For some reason, I've have been able to reach login and to successfully login
on the second boot after my initial install and my re-install today.
(This current successful boot is running the 6.1.0-9-amd64 kernel but the
6.1.0-10-amd64 didn't boot minutes before.)

Here is the output from
# dmesg | grep microcode 



[0.046049] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please 
update microcode to version: 0x52 (or later)
[0.113466] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
[0.113467] TAA: Vulnerable: Clear CPU buffers attempted, no microcode
[0.113467] MMIO Stale Data: Vulnerable: Clear CPU buffers attempted, no 
microcode
[0.113468] SRBDS: Vulnerable: No microcode
[1.023465] microcode: sig=0x906e9, pf=0x2, revision=0x48
[1.023543] microcode: Microcode Update Driver: v2.2.

~

If I do
# cat /var/log/installer/syslog | grep microcode

then the block of lines above is followed by:

~

Jul 10 02:40:59 install-firmware: queuing intel-microcode installation 
(GenuineIntel)
Jul 10 03:12:25 hw-detect: installing intel-microcode
Jul 10 03:12:26 in-target:   intel-microcode iucode-tool
Jul 10 03:12:26 in-target: Get:2 cdrom://[Debian GNU/Linux 12.0.0 _Bookworm_ - 
Official amd64 NETINST with firmware 20230610-10:21] bookworm/non-free-firmware 
amd64 intel-microcode amd64 3.20230512.1 [6,124 kB]
Jul 10 03:12:26 in-target: Selecting previously unselected package 
intel-microcode.^M
Jul 10 03:12:26 in-target: Preparing to unpack 
.../intel-microcode_3.20230512.1_amd64.deb ...^M
Jul 10 03:12:26 in-target: Unpacking intel-microcode (3.20230512.1) ...^M
Jul 10 03:12:27 in-target: Setting up intel-microcode (3.20230512.1) ...^M
Jul 10 03:12:27 in-target: intel-microcode: microcode will be updated at next 
boot

~

However, on the (more-frequent) occasions when the kernel panics at boot and
the OS doesn't load the final output to my display has been:

~

[0.047755] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please 
update microcode to version: 0x52 (or later)
[0.117586] RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to
 RETBleed attacks, data leaks possible!
[1.140611] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[1.140697] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.1.0-10-amd64 #1  
Debian 6.1.37-1
[1.140777] Hardware name: System76  
Serval WS   /Serval WS
[1.140902] Call Trace:
[1.140929]  
[1.140952]  dump_stack_lvl+0x44/0x5c
[1.140995]  panic+0x118/0x2ed
[1.14

Bug#1040712: installation-reports Debian 12

[Cyril Brulebois]

Salut Jacques,

Jacques Rubin  (2023-07-09):
> #
> Comments/Problems: Problems with package installation (alien, gdm3,
> default-jre, etc...). Example of installing alien with the command line: $
> sudo apt-get install alien . Problem with the linux-image-6.1.0-10-amd64
> package when the installed package is linux-image-6.1.0-9-amd64.
> #
> Parameter setting for linux-image-6.1.0-10-amd64 (6.1.37-1) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64
> I: The initramfs will attempt to resume from /dev/sda3
> I: (UUID=eafc18cf-23e3-43e6-8bce-6784d60e3a92)
> I: Set the RESUME variable to override this.
> 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
> run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> dpkg: erreur de traitement du paquet linux-image-6.1.0-10-amd64
> (--configure) :
>  le sous-processus paquet linux-image-6.1.0-10-amd64 script
> post-installation installé a renvoyé un état de sortie d'erreur 1

I suppose this is an installation done from the live image? In that case
that's a known bug that will be fixed for 12.1 (to be released in 2
weeks).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1040712: installation-reports Debian 12

[Jacques Rubin]

Package: installation-reports Debian 12

Boot method: USB key - amd64
Image version:  Debian 12 Bookworm - Last updated: Sat, 10 Jun 2023
08:51:17 +
Date: sunday 9 july 2023, 20:05

Machine: Dell Latitude 5580 intel core i5 7th Gen.
Processor: Intel© Core™ i5-7440HQ CPU @ 2.80GHz × 4
Memory: 8.0 Go
Partitions: df -Tl
Sys. of filesType blocs of 1K Used Availability Use% Mounted on
udev devtmpfs 395650003956500   0% /dev
tmpfstmpfs 800244 1700 798544   1% /run
/dev/sda2ext4   470208136 17089220  429160168   4% /
tmpfstmpfs400121604001216   0% /dev/shm
tmpfstmpfs   5120   12   5108   1% /run/lock
/dev/sda1vfat  306572 5976 300596   2% /boot/efi
tmpfstmpfs 800240   80 800160   1%
/run/user/1000


Result of lspci -knn (or lspci -nn) :
#
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM
Registers [1028:07d1]
Kernel driver in use: skl_uncore
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor
PCIe Controller (x16) [8086:1901] (rev 05)
Subsystem: Dell 6th-10th Gen Core Processor PCIe Controller (x16)
[1028:07d1]
Kernel driver in use: pcie
port
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630
[8086:591b] (rev 04)
DeviceName:  Onboard IGD
Subsystem: Dell HD Graphics 630 [1028:07d1]
Kernel driver in use: i915
Kernel modules: i915
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 05)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal
Subsystem [1028:07d1]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series
Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
Subsystem: Dell 100 Series/C230 Series Chipset Family USB 3.0 xHCI
Controller [1028:07d1]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation 100
Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
Subsystem: Dell 100 Series/C230 Series Chipset Family Thermal Subsystem
[1028:07d1]
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller [1180]: Intel Corporation 100
Series/C230 Series Chipset Family Serial IO I2C Controller #0 [8086:a160]
(rev 31)
Subsystem: Dell 100 Series/C230 Series Chipset Family Serial IO I2C
Controller [1028:07d1]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:15.1 Signal processing controller [1180]: Intel Corporation 100
Series/C230 Series Chipset Family Serial IO I2C Controller #1 [8086:a161]
(rev 31)
Subsystem: Dell 100 Series/C230 Series Chipset Family Serial IO I2C
Controller [1028:07d1]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230
Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
Subsystem: Dell 100 Series/C230 Series Chipset Family MEI Controller
[1028:07d1]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation
Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]
[8086:a102] (rev 31)
Subsystem: Dell Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller
[AHCI Mode] [1028:07d1]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset
Family PCI Express Root Port #2 [8086:a111] (rev f1)
Subsystem: Dell 100 Series/C230 Series Chipset Family PCI Express Root Port
[1028:07d1]
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset
Family PCI Express Root Port #3 [8086:a112] (rev f1)
Subsystem: Dell 100 Series/C230 Series Chipset Family PCI Express Root Port
[1028:07d1]
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset
Family PCI Express Root Port #5 [8086:a114] (rev f1)
Subsystem: Dell 100 Series/C230 Series Chipset Family PCI Express Root Port
[1028:07d1]
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation CM238 Chipset LPC/eSPI
Controller [8086:a154] (rev 31)
Subsystem: Dell CM238 Chipset LPC/eSPI Controller [1028:07d1]
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series
Chipset Family Power Management Controller [8086:a121] (rev 31)
Subsystem: Dell 100 Series/C230 Series Chipset Family Power Management
Controller [1028:07d1]
00:1f.3 Audio device [0403]: Intel Corporation CM238 HD Audio Controller

Processed: Re: Bug#1038419: installation-reports: [arm64] Installation hangs on "Configuring grub-efi-arm64 (arm64)"

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 6.1.27-1
Bug #1038419 [installation-reports] installation-reports: [arm64] Installation 
hangs on "Configuring grub-efi-arm64 (arm64)"
Bug reassigned from package 'installation-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #1038419 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1038419 to the same values 
previously set
Bug #1038419 [src:linux] installation-reports: [arm64] Installation hangs on 
"Configuring grub-efi-arm64 (arm64)"
Marked as found in versions linux/6.1.27-1.
> affects -1 debian-installer installation-reports
Bug #1038419 [src:linux] installation-reports: [arm64] Installation hangs on 
"Configuring grub-efi-arm64 (arm64)"
Added indication that 1038419 affects debian-installer and installation-reports

-- 
1038419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1038419: installation-reports: [arm64] Installation hangs on "Configuring grub-efi-arm64 (arm64)"

[Cyril Brulebois]

Control: reassign -1 src:linux 6.1.27-1
Control: affects -1 debian-installer installation-reports

Hi Joel,

Joel May  (2023-06-25):
> This bug was fixed in kernel version 6.1.33 by commit
> e8631d84c01ece34670af0d300a6f88d86d12f70.  I compiled from source and
> confirm that the problem is indeed fixed in 6.1.33.
> 
> The root of the problem is that the "family" in the SMBIOS is "Lenovo
> ThinkSystem HR330A/HR350A" not "eMAG", so a workaround broken
> SetVirtualAddressMap() is not applied.

Oh wow, thanks for tracking this down.

> I now see that this bug applies to more than installer, that just
> happened to be where I first was blocked by it.  I'm not sure if I
> can/should reclassify this bug report to the kernel package.

Let's reassign so that it can be documented as fixed in a further
upload, to be included into stable via a point release, at which point
the installer will be rebuilt against it… while leaving some pointers
for others to find.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1038419: installation-reports: [arm64] Installation hangs on "Configuring grub-efi-arm64 (arm64)"

[Joel May]

This bug was fixed in kernel version 6.1.33 by commit 
e8631d84c01ece34670af0d300a6f88d86d12f70.  I compiled from source and confirm 
that the problem is indeed fixed in 6.1.33.

The root of the problem is that the "family" in the SMBIOS is "Lenovo 
ThinkSystem HR330A/HR350A" not "eMAG", so a workaround broken 
SetVirtualAddressMap() is not applied.

I now see that this bug applies to more than installer, that just happened to 
be where I first was blocked by it.  I'm not sure if I can/should reclassify 
this bug report to the kernel package.

Bug#1038958: installation-reports: gnome-control-center very slow to start - modemmanager timeout

[Alessandro De Zorzi]

Package: installation-reports
Severity: normal

After a Debian11 to Debian12 upgrade on my Desktop NUC Intel
gnome-control-center very slow to start, I discover with

gnome-control-center -v

a modemmanager timeout, after modemmanager removed problem seems solved on my 
system

HTH
Alessandro - Lota

==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u4"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux nuc 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core 
Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD 
Graphics [8086:9a49] (rev 01)
lspci -knn: DeviceName: Onboard - Video
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: 00:06.0 PCI bridge [0604]: Intel Corporation 11th Gen Core 
Processor PCIe Controller [8086:9a09] (rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP 
Thunderbolt PCI Express Root Port #1 [8086:9a25] (rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:07.2 PCI bridge [0604]: Intel Corporation Tiger Lake-LP 
Thunderbolt PCI Express Root Port #2 [8086:9a27] (rev 01)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation Device 
[8086:9a11] (rev 01)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: 00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP 
Thunderbolt USB Controller [8086:9a13] (rev 01)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:0d.2 USB controller [0c03]: Intel Corporation Tiger Lake-LP 
Thunderbolt NHI #0 [8086:9a1b] (rev 01)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Device [:]
lspci -knn: 00:0d.3 USB controller [0c03]: Intel Corporation Tiger Lake-LP 
Thunderbolt NHI #1 [8086:9a1d] (rev 01)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Device [:]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 
3.2 Gen 2x1 xHCI Host Controller [8086:a0ed] (rev 20)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-LP Shared 
SRAM [8086:a0ef] (rev 20)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: 00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 
[8086:a0f0] (rev 20)
lspci -knn: DeviceName: Onboard - Ethernet
lspci -knn: Subsystem: Intel Corporation Device [8086:0070]
lspci -knn: Kernel modules: iwlwifi
lspci -knn: 00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger 
Lake-LP Serial IO I2C Controller #0 [8086:a0e8] (rev 20)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: 00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger 
Lake-LP Serial IO I2C Controller #1 [8086:a0e9] (rev 20)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Tiger 
Lake-LP Management Engine Interface [8086:a0e0] (rev 20)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Device 
[8086:a0e3] (rev 20)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Device 
[8086:a0d3] (rev 20)
lspci -knn: DeviceName: Onboard - SATA
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:a0b1] 
(rev 20)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Tiger Lake-LP LPC 
Controller [8086:a082] (rev 20)
lspci -knn: DeviceName: Onboard - Other
lspci -knn: Subsystem: Intel Corporation Device [8086:3003]
lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Tiger Lake-LP Smart 
So

Bug#1035588: marked as done (installation-reports: Installation of GNOME desktop fails (in openQA))

[Debian Bug Tracking System]

Your message dated Fri, 23 Jun 2023 13:15:41 +0200
with message-id <87zg4qsa3m@nimble.hk.hands.com>
and subject line Re: Bug#1035588: installation-reports: Installation of GNOME 
desktop fails (in openQA)
has caused the Debian Bug report #1035588,
regarding installation-reports: Installation of GNOME desktop fails (in openQA)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1035588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
User: debian...@lists.debian.org
X-Debbugs-Cc: p...@hands.com

Boot method: CD
Image version: daily netinst 20230505_1104 from
https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/
Date: 2023-05-05T15:57:23

Machine: qemu running on AMD64 server osuosl3.debian.net
See: https://openqa.debian.net/tests/144783
Partitions:

https://openqa.debian.net/tests/144783/logfile?filename=complete_install-
gdisk.txt

--
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***

Disk /dev/vda: 31457280 sectors, 15.0 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 71C86CFF-DC9F-4BC4-B99D-DB5CF15F1DB3
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 31457246
Partitions will be aligned on 2048-sector boundaries
Total free space is 6077 sectors (3.0 MiB)

Number  Start (sector)End (sector)  Size   Code  Name
   1204829456383   14.0 GiB8300  Linux filesystem
   52945843231455231   975.0 MiB   8200  Linux swap
--

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

After the reboot the GNOME login screen is not shown, instead the screen stays
black.

Judging from the output of `journalctl -b`, sddm-greeter causes a core dump
https://openqa.debian.net/tests/144783/logfile?filename=_graphical_wait_login-
journal.txt
systemd-coredump[917]: Process 873 (sddm-greeter) of user 113 dumped core.

I've used the same ISO file on my Intel-based hardware, with a similar
invocation of qemu, and there the ISO images worked fine.

With kind regards,
Roland Clobus

PS: The netinst-RC2 image has the same issue


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux silent 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5000]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Intel Corporation Device [8086:2010]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5007]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Lynx Point KT 
Controller [8086:8c3d] (rev 04)

Processed: reassign 1038612 to installation-reports

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1038612 installation-reports
Bug #1038612 [debian installer] Reporting a unworkable / bug
Warning: Unknown package 'debian'
Warning: Unknown package 'installer'
Bug reassigned from package 'debian installer' to 'installation-reports'.
Ignoring request to alter found versions of bug #1038612 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1038612 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1038612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1038419: installation-reports: [arm64] Installation hangs on "Configuring grub-efi-arm64 (arm64)"

[Joel May]

Upon further investigation, this problem appears to be related to the kernel 
version (6.1.0-9-arm64).

After booting into my new Debian 12 installation, efibootmgr hung with no 
output when I attempted to delete a boot entry (`sudo efibootmgr -Bb 0006`).  I 
downloaded the Bullseye kernel deb package and downgraded to 5.10.0-23-arm64.  
Using the older kernel with Debian 12 allowed me to delete the boot entry with 
efibootmgr.

After a few seconds of efibootmgr hanging with kernel 6.1.0-9-arm64, dmesg 
starts logging:
[  220.565406] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  220.571320] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=2582
[  220.580182]  (detected by 28, t=5255 jiffies, g=2537, q=452 ncpus=32)
[  220.580186] Task dump for CPU 31:
[  220.580188] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  220.580194] Workqueue: efi_rts_wq efi_call_rts
[  220.580203] Call trace:
[  220.580204]  __switch_to+0xf0/0x170
[  220.580211]  0x0
[  283.592504] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  283.598416] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=10186
[  283.607364]  (detected by 18, t=21013 jiffies, g=2537, q=644 ncpus=32)
[  283.607368] Task dump for CPU 31:
[  283.607369] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  283.607376] Workqueue: efi_rts_wq efi_call_rts
[  283.607382] Call trace:
[  283.607383]  __switch_to+0xf0/0x170
[  283.607388]  0x0
[  346.620541] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  346.626453] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=16943
[  346.635401]  (detected by 22, t=36771 jiffies, g=2537, q=1673 ncpus=32)
[  346.635404] Task dump for CPU 31:
[  346.635405] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  346.635411] Workqueue: efi_rts_wq efi_call_rts
[  346.635417] Call trace:
[  346.635419]  __switch_to+0xf0/0x170
[  346.635424]  0x0
[  363.463544] INFO: task khugepaged:188 blocked for more than 120 seconds.
[  363.470242]   Not tainted 6.1.0-9-arm64 #1 Debian 6.1.27-1
[  363.476069] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  363.483894] task:khugepaged  state:D stack:0 pid:188   ppid:2  
flags:0x0008
[  363.483901] Call trace:
[  363.483902]  __switch_to+0xf0/0x170
[  363.483909]  __schedule+0x340/0x940
[  363.483913]  schedule+0x58/0xf0
[  363.483916]  schedule_timeout+0x14c/0x180
[  363.483919]  __wait_for_common+0xd4/0x254
[  363.483922]  wait_for_completion+0x28/0x3c
[  363.483926]  __flush_work.isra.0+0x180/0x2dc
[  363.483931]  flush_work+0x18/0x2c
[  363.483934]  __lru_add_drain_all+0x1a0/0x260
[  363.483938]  lru_add_drain_all+0x1c/0x30
[  363.483941]  khugepaged+0xa4/0x9d0
[  363.483945]  kthread+0xe0/0xe4
[  363.483948]  ret_from_fork+0x10/0x20
[  363.483986] INFO: task efibootmgr:956 blocked for more than 120 seconds.
[  363.490681]   Not tainted 6.1.0-9-arm64 #1 Debian 6.1.27-1
[  363.496510] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  363.504335] task:efibootmgr  state:D stack:0 pid:956   ppid:955
flags:0x0004
[  363.504341] Call trace:
[  363.504342]  __switch_to+0xf0/0x170
[  363.504347]  __schedule+0x340/0x940
[  363.504351]  schedule+0x58/0xf0
[  363.504354]  schedule_timeout+0x14c/0x180
[  363.504357]  __wait_for_common+0xd4/0x254
[  363.504360]  wait_for_completion+0x28/0x3c
[  363.504363]  virt_efi_set_variable+0x134/0x1b0
[  363.504367]  efivar_set_variable_locked+0x7c/0xfc
[  363.504370]  efivar_entry_delete+0x5c/0xec [efivarfs]
[  363.504380]  efivarfs_unlink+0x28/0x5c [efivarfs]
[  363.504385]  vfs_unlink+0x124/0x300
[  363.504390]  do_unlinkat+0x19c/0x2c0
[  363.504393]  __arm64_sys_unlinkat+0x44/0x90
[  363.504396]  invoke_syscall+0x78/0x100
[  363.504401]  el0_svc_common.constprop.0+0x4c/0xf4
[  363.504405]  do_el0_svc+0x34/0xd0
[  363.504408]  el0_svc+0x34/0xd4
[  363.504411]  el0t_64_sync_handler+0xf4/0x120
[  363.504414]  el0t_64_sync+0x18c/0x190
[  409.648706] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  409.654617] rcu: 31-...0: (1 GPs behind) idle=de3c/1/0x4000 
softirq=453/453 fqs=22740
[  409.663565]  (detected by 20, t=52529 jiffies, g=2537, q=1895 ncpus=32)
[  409.663568] Task dump for CPU 31:
[  409.663570] task:kworker/u64:5   state:R  running task stack:0 
pid:378   ppid:2  flags:0x000a
[  409.663576] Workqueue: efi_rts_wq efi_call_rts
[  409.663582] Call trace:
[  409.663583]  __switch_to+0xf0/0x170
[  409.663589]  0x0

Bug#1038419: installation-reports: [arm64] Installation hangs on "Configuring grub-efi-arm64 (arm64)"

[Joel May]

Package: installation-reports
Severity: important

Boot method: USB
Image version: 
https://cdimage.debian.org/debian-cd/current/arm64/bt-cd/debian-12.0.0-arm64-netinst.iso.torrent
Date: 2023-06-17

Machine: Lenovo HR350A server
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
rootfs rootfs   263117412  216724 262900688   1% /
tmpfs  tmpfs 26311744 144  26311600   1% /run
devtmpfs   devtmpfs 131020564   0 131020564   0% /dev
/dev/sdc1  iso9660 612352  612352 0 100% /cdrom
/dev/sdb2  ext4 237753112 1161200 224441896   1% /target
/dev/sdb1  vfat5240006224517776   2% /target/boot/efi


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[ ]

Comments/Problems:

Installation hangs on "Configuring grub-efi-arm64 (arm64)".

When the installer is stuck in this state, other commands from the shell also 
hang, such as
`efibootmgr`
`cat /sys/firmware/efi/efivars/Boot-...`
`modprobe` (called by `reportbug installation-report`).

Using the expert install to disable updating NVRAM variables works around the 
problem.
For reference, Debian Bullseye, Ubuntu 22.04.2, and RHEL 9.2 successfully 
install the UEFI bootloader on this system.

-- Package-specific info:
- dmesg
[  396.440480] Adding 1000444k swap on /dev/sda3.  Priority:-2 extents:1 
across:1000444k SSFS
[  398.952999] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota 
mode: none.
[  398.963417] FAT-fs (sda1): Volume was not properly unmounted. Some data may 
be corrupt. Please run fsck.
[  850.581829] fuse: init (API version 7.37)
[  887.150168] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  887.150177] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=2163
[  887.150185]  (detected by 7, t=5252 jiffies, g=68329, q=166 ncpus=32)
[  887.150188] Task dump for CPU 1:
[  887.150190] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[  887.150197] Workqueue: efi_rts_wq efi_call_rts
[  887.150206] Call trace:
[  887.150208]  __switch_to+0xf0/0x170
[  887.150214]  0x0
[  950.170167] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  950.170173] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=7867
[  950.170180]  (detected by 16, t=21007 jiffies, g=68329, q=296 ncpus=32)
[  950.170183] Task dump for CPU 1:
[  950.170184] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[  950.170190] Workqueue: efi_rts_wq efi_call_rts
[  950.170196] Call trace:
[  950.170198]  __switch_to+0xf0/0x170
[  950.170203]  0x0
[ 1013.190168] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1013.190173] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=13685
[ 1013.190180]  (detected by 0, t=36762 jiffies, g=68329, q=343 ncpus=32)
[ 1013.190183] Task dump for CPU 1:
[ 1013.190184] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[ 1013.190191] Workqueue: efi_rts_wq efi_call_rts
[ 1013.190197] Call trace:
[ 1013.190198]  __switch_to+0xf0/0x170
[ 1013.190204]  0x0
[ 1076.210168] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1076.210173] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=19448
[ 1076.210179]  (detected by 11, t=52517 jiffies, g=68329, q=373 ncpus=32)
[ 1076.210182] Task dump for CPU 1:
[ 1076.210183] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[ 1076.210189] Workqueue: efi_rts_wq efi_call_rts
[ 1076.210195] Call trace:
[ 1076.210196]  __switch_to+0xf0/0x170
[ 1076.210201]  0x0
[ 1088.482198] INFO: task khugepaged:188 blocked for more than 120 seconds.
[ 1088.482205]   Not tainted 6.1.0-9-arm64 #1 Debian 6.1.27-1
[ 1088.482207] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1088.482209] task:khugepaged  state:D stack:0 pid:188   ppid:2  
flags:0x0008
[ 1088.482214] Call trace:
[ 1088.482215]  __switch_to+0xf0/0x170
[ 1088.482221]  __schedule+0x340/0x940
[ 1088.482225]  schedule+0x58/0xf0
[ 1088.482228]  schedule_timeout+0x14c/0x180
[ 1088.482231]  __wait_for_common+0xd4/0x254
[ 1088.482234]  wait_for_completion+0x28/0x3c
[ 1088.482238]  __flush_work.isra.0+0x180/0x2dc
[ 1088.482244]  flush_work+0x18/0x2c
[ 1088.482246]  __lru_add_drain_all+0x1a0/0x260
[ 1088.482250]  lru_add_drain_all+0x1c/0x30
[ 1

Bug#1037550: installation-reports: Command /usr/sbin/bootloader-config failed to finish in 600 seconds.

[Chris Turner]

Thank you for the clarification.

On Wed, Jun 14, 2023 at 12:50 PM Cyril Brulebois  wrote:

> Chris Turner  (2023-06-14):
> > I beg your pardon, it was
> >
> >
> https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/debian-live-12.0.0-amd64-cinnamon.iso
> >
> > Does that make sense?
>
> That looks much more plausible, yes. :)
>
> As you can see in that directory, live images exist in several variants,
> and it's always best to know exactly which image one is reporting issues
> against (sometimes it doesn't matter which desktop environment is used,
> sometimes this means huge differences at run-time).
>
> Putting back the bug report and the live team in the loop (for further
> reference, using reply-all is best).
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
>

Bug#1037550: installation-reports: Command /usr/sbin/bootloader-config failed to finish in 600 seconds.

[Cyril Brulebois]

Chris Turner  (2023-06-14):
> I beg your pardon, it was
> 
> https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/debian-live-12.0.0-amd64-cinnamon.iso
> 
> Does that make sense?

That looks much more plausible, yes. :)

As you can see in that directory, live images exist in several variants,
and it's always best to know exactly which image one is reporting issues
against (sometimes it doesn't matter which desktop environment is used,
sometimes this means huge differences at run-time).

Putting back the bug report and the live team in the loop (for further
reference, using reply-all is best).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1037550: installation-reports: Command /usr/sbin/bootloader-config failed to finish in 600 seconds.

[Cyril Brulebois]

Hi,

wizardfromoz  (2023-06-14):
> Boot method: USB
> Image version: 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-12.0.0-amd64-DVD-1.iso
> Date: Mon Jun 12 10:36:38 2023

Are you sure about the image you're using?

> Install went fine to 68% then Error Installation Failed - Command 
> /usr/sbin/bootloader-config failed to finish in 600 seconds
> 
> SUGGESTION - extend timeout for bootloader-config from 10 minutes to 60 
> minutes
> 
> Please make sure that any installation logs that you think would
> be useful are attached to this report. (You can find them in the
> installer system in /var/log/ and later on the installed system
> under /var/log/installer.) Please compress large files using gzip.

As far as I can see, bootloader-config is a calamares-specific command,
so is shipped on live images, and not on the installer images. The one
you linked to is about the latter.

Cc-ing debian-live@ as a heads-up.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1037550: installation-reports: Command /usr/sbin/bootloader-config failed to finish in 600 seconds.

[wizardfromoz]

Package: installation-reports
Severity: important
X-Debbugs-Cc: christurner1...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-12.0.0-amd64-DVD-1.iso
Date: Mon Jun 12 10:36:38 2023

Machine: Dell Inspiron 5770 Laptop
Partitions: 

Filesystem Type  1K-blocks  Used  Available Use% Mounted on
udev   devtmpfs8088576 08088576   0% /dev
tmpfs  tmpfs   1627092  20841625008   1% /run
/dev/sda13 ext4   29754436  11586460   16631160  42% /
tmpfs  tmpfs   8135448 08135448   0% /dev/shm
tmpfs  tmpfs  5120 8   5112   1% /run/lock
/dev/sda1  vfat1045784518720 527064  50% /boot/efi
tmpfs  tmpfs   1627088961626992   1% /run/user/1000
/dev/sdc9  ext4   20466388  134297365971692  70% 
/media/chris/MJRO-KDE-WD
/dev/sdc6  ext4   2046638824   19401404   1% 
/media/chris/DistroReady1
/dev/sdc8  ext4   2046638824   19401404   1% 
/media/chris/DistroReady
/dev/sdc48 ext4   1954888444   18483884   1% 
/media/chris/Photorec
/dev/sdc5  ext4   20466388  138591925542236  72% 
/media/chris/MJRO18.4-Xfce-WD
/dev/sdc44 ext4  360126524 812928378772  98% 
/media/chris/FutureLinux-WD
/dev/sdc45 ext4  566548024 493761944   43933856  92% 
/media/chris/TS-HDD2-dev-sda
/dev/sdc7  ext4   20335316  154179043852460  81% 
/media/chris/2wayAdataDocs
/dev/sdc42 ext4   40973776   8434044   30426196  22% 
/media/chris/TSNitruxOriginal
/dev/sdc47 ext4  102101944  31031296   65811388  33% 
/media/chris/VeraMATE4VMs-WD
/dev/sdc41 ext4  102626052  32503136   64863664  34% 
/media/chris/Voyager4VMs-WD
/dev/sdc43 ext4  103023292  909350526828728  94% 
/media/chris/Ex-Adata-1
/dev/sdc46 ext4  145451076 1329227885067068  97% 
/media/chris/TS-SSD2-dev-sdb
/dev/sdc49 ext4 145212510028 1378288068   1% 
/media/chris/DistroReady35GiB
/dev/sdc40 ext4   20466388 8   19401420   1% 
/media/chris/DistroReady2
/dev/sdc38 ext4   30787492  11722248   17475996  41% 
/media/chris/Mageia9Alpha-Fix
/dev/sdc37 ext4   2046638824   19401404   1% 
/media/chris/DistroReady3
/dev/sdc32 ext4   20466256  120369407364356  63% 
/media/chris/LubuntuKudu-WD
/dev/sdc33 ext4   20466256  148986804502616  77% 
/media/chris/LinuxLite6.0-WD
/dev/sdc30 ext4   3078766824   29198396   1% 
/media/chris/Leave4PhotoRec
/dev/sdc36 ext4   2046638856   19401372   1% 
/media/chris/TestingTimeshift
/dev/sdc3  ext4   2046638824   19401404   1% 
/media/chris/DistroReady5
/dev/sdc28 ext4   30787668   7192480   22005940  25% 
/media/chris/SpiralCinn-WD
/dev/sdc39 ext4   25627028  153805608919364  64% 
/media/chris/UlyanaCinn-WD
/dev/sdc31 ext4   20466256  117949247606372  61% 
/media/chris/XubuntuJammy-WD
/dev/sdc34 ext4   20466256   8774700   10626596  46% 
/media/chris/BunsenlabsHelium
/dev/sdc35 ext4   20466256  129487366452560  67% 
/media/chris/Jammy-GNOME-WD
/dev/sdc27 ext4   2046638824   19401404   1% 
/media/chris/DistroReady6
/dev/sdc24 ext4   2046638824   19401404   1% 
/media/chris/DistroReady7
/dev/sdc25 ext4   40973776  12348412   26511828  32% 
/media/chris/Swagarch
/dev/sdc4  ext4   2046638824   19401404   1% 
/media/chris/DistroReady4
/dev/sdc26 ext4   20466388   9376144   10025284  49% 
/media/chris/Peppermint10-WD
/dev/sdc23 ext4   20466256   8955384   10445912  47% 
/media/chris/TrisquelMATE-WD
/dev/sdc29 btrfs  62914560  24299884   35962196  41% 
/media/chris/Garuda-Cinn-WD
/dev/sdc20 ext4   20466256   6770404   12630892  35% 
/media/chris/Gecko-Xfce-WD
/dev/sdc22 ext4   20466256  123024167098880  64% 
/media/chris/EmmabuntusXfceWD
/dev/sdc21 ext4   40973536  12503260   26356740  33% 
/media/chris/VanessaCinn-WD
/dev/sdc17 ext4   2046638824   19401404   1% 
/media/chris/DistroReady8
/dev/sdc18 ext4   35942016  20946392   13144232  62% 
/media/chris/CLDC-22.0.1
/dev/sdc12 ext4   20466256   9210872   10190424  48% 
/media/chris/ParrotHOME-WD
/dev/sdc13 ext4   2046638824   19401404   1% 
/media/chris/DistroReady9
/dev/sdc15 ext4   4097377624   38860216   1% 
/media/chris/DistroReady40GiB
/dev/sdc1  ext4   2046638824   19401404   1% 
/media/chris/DistroReady11
/dev/sdc10 ext4   20466388  126144326786996  66% 
/media/chris/MJRO-Cinn-WD
/dev/sdc11 ext4   2046638824   19401404   1% 
/media/chris

Processed: Re: Bug#1037350: Package: installation-reports

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 installation-reports: grub not installed (correctly)
Bug #1037350 [installation-reports] Package: installation-reports
Changed Bug title to 'installation-reports: grub not installed (correctly)' 
from 'Package: installation-reports'.

-- 
1037350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037350: Package: installation-reports

[Holger Wansing]

Control: retitle -1 installation-reports: grub not installed (correctly)



-- 
Sent from /e/ OS on Fairphone3

Bug#1037350: Package: installation-reports

[Holger Wansing]

Control: rename -1 installation-reports: grub not installed (correctly)



Am 11. Juni 2023 22:45:34 MESZ schrieb Peter Ehlert :
>Package: installation-reports
>
>Boot method: USB
>Image version: debian-12.0.0-amd64-netinst.iso
>Date: 2023-06-11 9-16-23
>
>Machine: Type: Desktop System: Hewlett-Packard product: HP Z820 Workstation
>Processor: CPU: 2x 8-core Intel Xeon E5-2687W 0 (-MT MCP SMP-)
>Memory: Mem: 1310.8/48189.1 MiB (2.7%) Storage: 9.32 TiB (3.2% used)
>Partitions: 
>
>$ df -Tl
>Filesystem Type 1K-blocks    Used Available Use% Mounted on
>udev   devtmpfs  24639364   0  24639364   0% /dev
>tmpfs  tmpfs  4934568    2036   4932532   1% /run
>/dev/sdb24 ext4  28660644 4437152  22742276  17% /
>tmpfs  tmpfs 24672828   0  24672828   0% /dev/shm
>tmpfs  tmpfs 5120  12  5108   1% /run/lock
>/dev/sdb26 ext4  19046484    1228  18052388   1% /home
>tmpfs  tmpfs  4934564  80   4934484   1% /run/user/1000
>
>
>
>Output of lspci -knn (or lspci -nn):
>
>$ lspci -knn
>00:00.0 Host bridge [0600]: Intel Corporation Xeon E5/Core i7 DMI2 [8086:3c00] 
>(rev 07)
>    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 DMI2 [103c:158b]
>00:01.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
>Root Port 1a [8086:3c02] (rev 07)
>    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express Root 
>Port 1a [103c:158b]
>    Kernel driver in use: pcieport
>00:01.1 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
>Root Port 1b [8086:3c03] (rev 07)
>    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express Root 
>Port 1b [103c:158b]
>    Kernel driver in use: pcieport
>00:02.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
>Root Port 2a [8086:3c04] (rev 07)
>    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express Root 
>Port 2a [103c:158b]
>    Kernel driver in use: pcieport
>00:03.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
>Root Port 3a in PCI Express Mode [8086:3c08] (rev 07)
>    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express Root 
>Port 3a in PCI Express Mode [103c:158b]
>    Kernel driver in use: pcieport
>00:05.0 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 Address 
>Map, VTd_Misc, System Management [8086:3c28] (rev 07)
>    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 Address Map, VTd_Misc, 
>System Management [103c:158b]
>00:05.2 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 Control 
>Status and Global Errors [8086:3c2a] (rev 07)
>    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 Control Status and 
>Global Errors [103c:158b]
>00:05.4 PIC [0800]: Intel Corporation Xeon E5/Core i7 I/O APIC [8086:3c2c] 
>(rev 07)
>    Subsystem: Intel Corporation Xeon E5/Core i7 I/O APIC [8086:3c2c]
>00:11.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI 
>Express Virtual Root Port [8086:1d3e] (rev 05)
>    Subsystem: Hewlett-Packard Company C600/X79 series chipset PCI Express 
>Virtual Root Port [103c:158b]
>    Kernel driver in use: pcieport
>00:16.0 Communication controller [0780]: Intel Corporation C600/X79 series 
>chipset MEI Controller #1 [8086:1d3a] (rev 05)
>    Subsystem: Hewlett-Packard Company C600/X79 series chipset MEI Controller 
>[103c:158b]
>    Kernel driver in use: mei_me
>    Kernel modules: mei_me
>00:16.2 IDE interface [0101]: Intel Corporation C600/X79 series chipset IDE-r 
>Controller [8086:1d3c] (rev 05)
>    Subsystem: Hewlett-Packard Company C600/X79 series chipset IDE-r 
>Controller [103c:158b]
>    Kernel driver in use: ata_generic
>    Kernel modules: ata_generic
>00:16.3 Serial controller [0700]: Intel Corporation C600/X79 series chipset KT 
>Controller [8086:1d3d] (rev 05)
>    Subsystem: Hewlett-Packard Company C600/X79 series chipset KT Controller 
>[103c:158b]
>    Kernel driver in use: serial
>00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
>Connection (Lewisville) [8086:1502] (rev 05)
>    DeviceName: Onboard LAN
>    Subsystem: Hewlett-Packard Company 82579LM Gigabit Network Connection 
>(Lewisville) [103c:158b]
>    Kernel driver in use: e1000e
>    Kernel modules: e1000e
>00:1a.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset USB2 
>Enhanced Host Controller #2 [8086:1d2d] (rev 05)
>    Subsystem: Hewlett-Packard Company C600/X79 series chipset USB2 Enhanced 
>Host Controller [103c:158b]
>    Kernel driver in use: ehci-pci
>    Kernel modules: ehci_pci
>00:1b.0 Audio device [0403]: Intel Corporation C600/X79 series chipset High 
>Definition Audio Controller 

Bug#1037350: Package: installation-reports

[Peter Ehlert]

Package: installation-reports

Boot method: USB
Image version: debian-12.0.0-amd64-netinst.iso
Date: 2023-06-11 9-16-23

Machine: Type: Desktop System: Hewlett-Packard product: HP Z820 Workstation
Processor: CPU: 2x 8-core Intel Xeon E5-2687W 0 (-MT MCP SMP-)
Memory: Mem: 1310.8/48189.1 MiB (2.7%) Storage: 9.32 TiB (3.2% used)
Partitions: 

$ df -Tl
Filesystem Type 1K-blocks    Used Available Use% Mounted on
udev   devtmpfs  24639364   0  24639364   0% /dev
tmpfs  tmpfs  4934568    2036   4932532   1% /run
/dev/sdb24 ext4  28660644 4437152  22742276  17% /
tmpfs  tmpfs 24672828   0  24672828   0% /dev/shm
tmpfs  tmpfs 5120  12  5108   1% /run/lock
/dev/sdb26 ext4  19046484    1228  18052388   1% /home
tmpfs  tmpfs  4934564  80   4934484   1% /run/user/1000



Output of lspci -knn (or lspci -nn):

$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E5/Core i7 DMI2 
[8086:3c00] (rev 07)

    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 DMI2 [103c:158b]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 1a [8086:3c02] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 1a [103c:158b]

    Kernel driver in use: pcieport
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 1b [8086:3c03] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 1b [103c:158b]

    Kernel driver in use: pcieport
00:02.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 2a [8086:3c04] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 2a [103c:158b]

    Kernel driver in use: pcieport
00:03.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO PCI 
Express Root Port 3a in PCI Express Mode [8086:3c08] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 IIO PCI Express 
Root Port 3a in PCI Express Mode [103c:158b]

    Kernel driver in use: pcieport
00:05.0 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 
Address Map, VTd_Misc, System Management [8086:3c28] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 Address Map, 
VTd_Misc, System Management [103c:158b]
00:05.2 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 
Control Status and Global Errors [8086:3c2a] (rev 07)
    Subsystem: Hewlett-Packard Company Xeon E5/Core i7 Control Status 
and Global Errors [103c:158b]
00:05.4 PIC [0800]: Intel Corporation Xeon E5/Core i7 I/O APIC 
[8086:3c2c] (rev 07)

    Subsystem: Intel Corporation Xeon E5/Core i7 I/O APIC [8086:3c2c]
00:11.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI 
Express Virtual Root Port [8086:1d3e] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset PCI 
Express Virtual Root Port [103c:158b]

    Kernel driver in use: pcieport
00:16.0 Communication controller [0780]: Intel Corporation C600/X79 
series chipset MEI Controller #1 [8086:1d3a] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset MEI 
Controller [103c:158b]

    Kernel driver in use: mei_me
    Kernel modules: mei_me
00:16.2 IDE interface [0101]: Intel Corporation C600/X79 series chipset 
IDE-r Controller [8086:1d3c] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset IDE-r 
Controller [103c:158b]

    Kernel driver in use: ata_generic
    Kernel modules: ata_generic
00:16.3 Serial controller [0700]: Intel Corporation C600/X79 series 
chipset KT Controller [8086:1d3d] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset KT 
Controller [103c:158b]

    Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit 
Network Connection (Lewisville) [8086:1502] (rev 05)

    DeviceName: Onboard LAN
    Subsystem: Hewlett-Packard Company 82579LM Gigabit Network 
Connection (Lewisville) [103c:158b]

    Kernel driver in use: e1000e
    Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset 
USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset USB2 
Enhanced Host Controller [103c:158b]

    Kernel driver in use: ehci-pci
    Kernel modules: ehci_pci
00:1b.0 Audio device [0403]: Intel Corporation C600/X79 series chipset 
High Definition Audio Controller [8086:1d20] (rev 05)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset High 
Definition Audio Controller [103c:158b]

    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 2 [8086:1d12] (rev b5)
    Subsystem: Hewlett-Packard Company C600/X79 series chipset PCI 
Express Root Port 2 [103c:158b]

    Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation

Bug#1037328: Bug on Debian 12 Bookworm - Installation-reports - EFI partition installation

[pham...@bluewin.ch]

Package: Installation-reports - EFI partition installation
Severity: High

Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with 
Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI 
partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI 
partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of 
the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost 
full, I have no possibility of installing other OSes ;-( This 100 MB partition 
being ridiculously small and not expandable, it does not also cannot benefit 
from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe

Bug#1037325: marked as done (Bug on Debian 11 Bookworm - Installation-reports - EFI partition installation)

[Debian Bug Tracking System]

Your message dated Sun, 11 Jun 2023 13:48:26 +0200 (CEST)
with message-id <1749396002.7565.1686484106...@bluewin.ch>
and subject line 
has caused the Debian Bug report #1037325,
regarding Bug on Debian 11 Bookworm - Installation-reports - EFI partition 
installation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: Installation-reports - EFI partition installation
Severity: Hight

Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with 
Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI 
partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI 
partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of 
the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost 
full, I have no possibility of installing other OSes ;-( This 100 MB partition 
being ridiculously small and not expandable, it does not also cannot benefit 
from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe--- End Message ---
--- Begin Message ---
Redaction error.
Regards.--- End Message ---

Bug#1037325: Bug on Debian 11 Bookworm - Installation-reports - EFI partition installation

[pham...@bluewin.ch]

Package: Installation-reports - EFI partition installation
Severity: Hight

Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with 
Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI 
partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI 
partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of 
the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost 
full, I have no possibility of installing other OSes ;-( This 100 MB partition 
being ridiculously small and not expandable, it does not also cannot benefit 
from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe

Bug#1037118: installation-reports: booting to d-i does not complete on Samsung Galaxy Book (arm64 laptop)

[Jonathan Carter]

Package: installation-reports
Severity: normal

Boot method: USB
Image version: 
https://cdimage.debian.org/cdimage/bookworm_di_rc4/arm64/iso-cd/debian-bookworm-DI-rc4-arm64-netinst.iso
Date: 2023-06-05

Machine: Samsung Galaxy Book Go 5G
Partitions: n/a

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]

GRUB starts fine, when selecting either Install or Graphical Install,
booting halts with just a static "_" on the display.

I'll try to troubleshoot this a bit further and attach more info to the bug, 
this is
a student's laptop so I'm not sure how long I'll have access to it.

Bug#1036895: installation-reports: successful installation on X1 Carbon gen 1

[Étienne Mollier]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: emoll...@debian.org

Boot method: netinst
Image version: debian installer 12 RC 4
Date: 2023-05-28

Machine: Lenovo X1 Carbon generation 1 (2012)
Partitions:
$ df -Tl
Filesystem   Type 1K-blocks Used Available Use% Mounted 
on
udev devtmpfs   39372440   3937244   0% /dev
tmpfstmpfs   794508 1344793164   1% /run
/dev/mapper/charbon--vg-root xfs   29229056  4625584  24603472  16% /
tmpfstmpfs  39725240   3972524   0% /dev/shm
tmpfstmpfs 51208  5112   1% 
/run/lock
/dev/mapper/charbon--vg-home xfs  218615508 15372176 203243332   8% /home
/dev/sda2ext445781682293346442  20% /boot
/dev/sda1vfat523244 5972517272   2% 
/boot/efi
tmpfstmpfs   794504   48794456   1% 
/run/user/1000
$ lsblk
NAME MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda8:00 238.5G  0 disk  
├─sda1 8:10   512M  0 part  /boot/efi
├─sda2 8:20   488M  0 part  /boot
└─sda3 8:30 237.5G  0 part  
  └─sda3_crypt   254:00 237.5G  0 crypt 
├─charbon--vg-root   254:10  27.9G  0 lvm   /
├─charbon--vg-swap_1 254:20   976M  0 lvm   [SWAP]
└─charbon--vg-home   254:30 208.6G  0 lvm   /home

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
The install went overall boringly great, which is how it should
be.  :)

One thing worth mentionning is that I proceeded to the install
on the Wifi, and that the connectivity went flaky.  This caused
the mirror selection and scanning to error with a message about
the bookworm release to not be supported by all the mirrors I
selected.  I had to investigate via the system console to
identify the network drop.  I'm not sure that I have a good idea
to improve how to feed this back through the d-i interface, but
Paul Gevers, who was is the vicinity, suggested that I raise the
issue anyway.

-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230526"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux charbon 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 
(2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core 
processor DRAM Controller [8086:0154] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21f9]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen 
Core processor Graphics Controller [8086:0166] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21f9]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f9]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f9]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f9]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f9]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
lspci -knn: Subsystem: Lenovo Device [17aa:21f9]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
lspci -knn

Bug#1036215: marked as done (installation-reports: PXE netboot x86_64 libvirt guest on aarch64 host)

[Debian Bug Tracking System]

Your message dated Fri, 26 May 2023 07:34:31 +
with message-id 
and subject line Bug#1036215: fixed in debian-installer 20230526
has caused the Debian Bug report #1036215,
regarding installation-reports: PXE netboot x86_64 libvirt guest on aarch64 host
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1036215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: PXE netboot
Image version: netboot.tar.gz from 
https://deb.debian.org/debian/dists/testing/main/installer-amd64/20230515/images/netboot/

Machine: QEMU TCG x86_64 libvirt guest on aarch64 host

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

This report is about the successful installation of Bookworm on a x86_64 guest
running on a aarch64 host. The guest was installed with virt-manager using PXE
boot and UEFI Secure Boot enabled. Everything went smoothly except:

(A) some troubles with the UEFI PXE boot device to choose
(B) failure to load the grub splash screen

(A)
At VM startup I've entered the UEFI firmware and booted selecting the first
PXEv4 option, see [0].

Choosing the first one *seemed* to work fine, but it ended up in a Secure Boot
error (see [1]). Disabling Secure Boot did not fix the problem, I still got a
"Invalid Parameter" error. It eventually became clear that I had to boot with
[2] instead. I'm not really sure what the difference between the two may be,
and if this is an issue in the Tianocore firmware.

At any rate, [2] worked fine with and without Secure Boot enabled. I went on
with a preseeded installation, which finished uneventfully.

I then noticed the following errors in the libvirtd logs on the host (B):

 sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/isolinux/splash.png not 
found for 192.168.122.7
 sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/splash.png not found for 
192.168.122.7

The grub.cfg file under /debian-installer/amd64/grub/grub.cfg has the following
conditionals:

 if background_image /isolinux/splash.png; then
[...]
 elif background_image /splash.png; then

The splash screen is loaded correctly replacing either of those with
/debian-installer/amd64/boot-screens/splash.png instead.

[0] https://people.debian.org/~ema/RC3-x86_64-uefi-firmware.png
[1] https://people.debian.org/~ema/RC3-x86_64-uefi-firmware-sb-error.png
[2] https://people.debian.org/~ema/RC3-x86_64-uefi-firmware-right-entry.png

PS:

To test PXE boot with libvirt I've edited the default network with:

 $ sudo virsh net-edit default

Here's what the  part looks like:



  
  

I've untarred netboot.tar.gz under /srv/tftp/bookworm/.

After editing the network, I re-created it with:

 $ sudo virsh net-destroy default && sudo virsh net-start default

Although I'm not 100% sure it was necessary, I've also restarted libvirt and
shot a couple of dnsmasq processes that seemed to want to stick around: 

 $ sudo systemctl stop libvirtd && sudo pkill dnsmasq && sudo systemctl start 
libvirtd
--- End Message ---
--- Begin Message ---
Source: debian-installer
Source-Version: 20230526
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
debian-installer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1036...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated debian-installer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 May 2023 09:08:23 +0200
Source: debian-installer
Architecture: source
Version: 20230526
Distribution: u

Bug#1036659: installation-reports: LUKs Prompt Splash Screen and Console Prompt Disappears After Installing Nvidia Drivers

[Cyril Brulebois]

Control: reassign -1 nvidia-driver

Hi,

and thanks for your report.

Asmodean  (2023-05-23):
> Package: installation-reports
> Severity: normal
> X-Debbugs-Cc: place4...@gmail.com
> 
> (Please provide enough information to help the Debian
> maintainers evaluate the report efficiently - e.g., by filling
> in the sections below.)
> 
> Boot method: USB
> Image version: debian-bookworm-DI-rc3-amd64-DVD-1.iso
> Date: 05/23/23
> 
> Machine: i7-6700k, Nvidia 980 Ti, HDMI lik to monitor, 1080p monitor
> Partitions: `df -Tl`:
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% 
> /snapshots
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /swap
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /var
> /dev/nvme0n1p2  ext2515668 80388409068  17% /boot
> /dev/nvme0n1p1  vfat54 11096511128   3% 
> /boot/efi
> /dev/mapper/sda1_crypt  btrfs488368128 380438904 107203864  79% /home
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [O]
> Detect network card:[O]
> Configure network:  [O]
> Detect media:   [O]
> Load installer modules: [O]
> Clock/timezone setup:   [O]
> User/password setup:[O]
> Detect hard drives: [O]
> Partition hard drives:  [O]
> Install base system:[O]
> Install tasks:  [O]
> Install boot loader:[O]
> Overall install:[O]
> 
> Comments/Problems:
> `initrd` was installed with the general option, and no extra modules
> were loaded when prompted to do so in the expert installer. After
> finishing the installation, the system rebooted correctly, albeit there
> being no splash screen for the LUKs prompt, only a console text prompt
> to enter the encryption passphrase. After decrypting everything and
> loading the graphical environment, i.e. XFCE, the `non-free` component was
> added to `/etc/apt/sources.list`, the package `linux-headers-amd64` was
> installed, and lastly the command `apt install nvidia-driver
> firmware-misc-nonfree` was run to install the proprietary Nvidia drivers
> for my GPU. At reboot time, bootloader GRUB appeared without problem,
> but after selecting the kernel and the initial loading that follows, the
> console only displayed the line "XDG something disabled" instead of
> showing the LUKs prompt. Though after waiting a few moments, supposedly
> for the keyboard modules to load, the passphrase can be entered without
> any visual feedback, with only the "XDG..." line on the screen. Pressing
>  following the passphrase boots the system into graphical target
> without problems. The questions are: 1. Why was the GUI splash screen 
> unavailable
>  after the reboot following installation?

That I don't know but I'm not going to consider a big issue. I've added
debian-xfce@ to cc so that they can give some feedback if they want to.

> 2. Why did the prompt disappear after
> installing Nvidia drivers? 3. Is there a way to fix this?
> Note: I installed the same system on the W550s Thinkpad which has a
> Nvidia GPU. The splash screen displayed correctly after pressing
>  following the initial boot, and loaded correctly too after
> installing the Nvidia drivers with identical steps detailed above. 

Reassigning to nvidia-driver for this part that seems much more
worrying.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#1036659: installation-reports: LUKs Prompt Splash Screen and Console Prompt Disappears After Installing Nvidia Drivers

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 nvidia-driver
Bug #1036659 [installation-reports] installation-reports: LUKs Prompt Splash 
Screen and Console Prompt Disappears After Installing Nvidia Drivers
Bug reassigned from package 'installation-reports' to 'nvidia-driver'.
Ignoring request to alter found versions of bug #1036659 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1036659 to the same values 
previously set

-- 
1036659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1036659: installation-reports: LUKs Prompt Splash Screen and Console Prompt Disappears After Installing Nvidia Drivers

[Asmodean]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: place4...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: debian-bookworm-DI-rc3-amd64-DVD-1.iso
Date: 05/23/23

Machine: i7-6700k, Nvidia 980 Ti, HDMI lik to monitor, 1080p monitor
Partitions: `df -Tl`:
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% 
/snapshots
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /swap
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /var
/dev/nvme0n1p2  ext2515668 80388409068  17% /boot
/dev/nvme0n1p1  vfat54 11096511128   3% 
/boot/efi
/dev/mapper/sda1_crypt  btrfs488368128 380438904 107203864  79% /home


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
`initrd` was installed with the general option, and no extra modules
were loaded when prompted to do so in the expert installer. After
finishing the installation, the system rebooted correctly, albeit there
being no splash screen for the LUKs prompt, only a console text prompt
to enter the encryption passphrase. After decrypting everything and
loading the graphical environment, i.e. XFCE, the `non-free` component was
added to `/etc/apt/sources.list`, the package `linux-headers-amd64` was
installed, and lastly the command `apt install nvidia-driver
firmware-misc-nonfree` was run to install the proprietary Nvidia drivers
for my GPU. At reboot time, bootloader GRUB appeared without problem,
but after selecting the kernel and the initial loading that follows, the
console only displayed the line "XDG something disabled" instead of
showing the LUKs prompt. Though after waiting a few moments, supposedly
for the keyboard modules to load, the passphrase can be entered without
any visual feedback, with only the "XDG..." line on the screen. Pressing
 following the passphrase boots the system into graphical target
without problems. The questions are: 1. Why was the GUI splash screen 
unavailable
 after the reboot following installation? 2. Why did the prompt disappear after
installing Nvidia drivers? 3. Is there a way to fix this?
Note: I installed the same system on the W550s Thinkpad which has a
Nvidia GPU. The splash screen displayed correctly after pressing
 following the initial boot, and loaded correctly too after
installing the Nvidia drivers with identical steps detailed above. 


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230515"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux 6700k 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 
(2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] 
(rev 07)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core 
Processor PCIe Controller (x16) [8086:1901] (rev 07)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD 
Graphics 530 [8086:1912] (rev 06)
lspci -knn: DeviceName:  Onboard IGD
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 
Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 100 
Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation 
Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] 
[8086:a102] (rev 31)
lspci -knn

Bug#1036215: installation-reports: PXE netboot x86_64 libvirt guest on aarch64 host

[Emanuele Rocca]

Hello,

following up here on the BTS for the benefit of those not reading #debian-boot.

On Wed, May 17, 2023 at 05:37:07PM +0200, Cyril Brulebois wrote:
> Emanuele Rocca  (2023-05-17):
> > (B) failure to load the grub splash screen

[...] 

> >  sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/isolinux/splash.png 
> > not found for 192.168.122.7
> >  sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/splash.png not found 
> > for 192.168.122.7
> > 
> > The grub.cfg file under /debian-installer/amd64/grub/grub.cfg has the 
> > following
> > conditionals:
> > 
> >  if background_image /isolinux/splash.png; then
> > [...]
> >  elif background_image /splash.png; then
> > 
> > The splash screen is loaded correctly replacing either of those with
> > /debian-installer/amd64/boot-screens/splash.png instead.
> 
> Adding an extra conditional in there really doesn't seem appropriate at
> this point. Seeing how images/netboot/ is 745M, and how splash.png is
> 58K, I think I'd rather have it duplicated in a way that it's found in
> /splash.png for both text and gtk installers (/isolinux/splash.png could
> would be a weird location given the booting happens via GRUB).

Even better than duplicating the image, we can use a symlink instead, see:
https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/32

Bug#1036471: installation-reports: Bookworm RC3 installs in MBR but hangs in UEFI, goes to gray screen

[Lee Wulff]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: lewu...@retiredtechie.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: ISO
Image version: debian-bookworm-DI-rc3-amd64-netinstall
Date: 21 May 2023 3:00 PM EST

Machine: VirtualVox version 7.0.6
Partitions: None, system does not install, so storage disk is not partioned or 
formated


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Attempted to install bookwork rc3 as guest on in Virtual machine (Virtual Box); 
4 CPUS, 
4 GB RAM, 20 GB drive, bridge network, UEFI enabled. Host compiuter MSI Raider 
GE76 running 
Windows 11.

Boot menu comes up. When selecting install option, goes to gray screen with 
flashing cursor
in nupper left corner.

Was able to install without issue using same setup, but with UEFI disabled 
(legacy mode).


Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230427"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian12 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-2 
(2023-04-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:02.0 VGA compatible controller [0300]: VMware SVGA II Adapter 
[15ad:0405]
lspci -knn: Subsystem: VMware SVGA II Adapter [15ad:0405]
lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM 
Gigabit Ethernet Controller [8086:100e] (rev 02)
lspci -knn: Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter 
[8086:001e]
lspci -knn: Kernel driver in use: e1000
lspci -knn: Kernel modules: e1000
lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH 
VirtualBox Guest Service [80ee:cafe]
lspci -knn: 00:05.0 Multimedia audio controller [0401]: Intel Corporation 
82801AA AC'97 Audio Controller [8086:2415] (rev 01)
lspci -knn: Subsystem: Dell Device [1028:0177]
lspci -knn: 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB 
[106b:003f]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: Kernel modules: ohci_pci
lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 08)
lspci -knn: 00:0b.0 USB controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM 
(ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 6.1.0-7-amd64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: OHCI PCI host controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 6.1.0-7-amd64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
lsmod: Module  Size  Used by
lsmod: fuse  176128  0
lsmod: dm_mod184320  0
lsmod: md_mod192512  0
lsmod: xfs  1945600  0
lsmod: jfs   221184  0
lsmod: btrfs1777664  0
lsmod: xor24576  1 btrfs
lsmod: raid6_pq  122880

Bug#1036397: Package: installation-reports

[thomas . chandesris]

Package: installation-reports

Boot method: USB key
Image version: debian-bookworm-DI-alpha2-amd64-netinst.iso
Date: 05/19/2023 8:00 PM

Machine: HP HP Stream Notebook
Processor: Intel® Celeron® N2840  × 2
Memory: 2,0 Gio
Partitions:
Sys. de fichiers Type blocs de 1K Utilisé Disponible Uti% Monté sur
udev devtmpfs  921424   0 921424   0% /dev
tmpfstmpfs 1902841552 188732   1% /run
/dev/mmcblk0p2   ext428378028 5997764   20913384  23% /
tmpfstmpfs 951416   0 951416   0% /dev/shm
tmpfstmpfs   5120   8   5112   1% /run/lock
/dev/mmcblk0p1   vfat  5232486112 517136   2% /boot/efi
tmpfstmpfs 190280 120 190160   1%
/run/user/1000

Résultat de lspci -knn :
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series SoC Transaction Register [103c:817b]
Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom
Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)
DeviceName: Intel(R) HD Graphics
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series Graphics & Display [103c:817b]
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation Atom Processor
Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [103c:817b]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:1a.0 Encryption controller [1080]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series Trusted Execution Engine [103c:817b]
Kernel driver in use: mei_txe
Kernel modules: mei_txe
00:1b.0 Audio device [0403]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series High Definition Audio Controller [8086:0f04] (rev
0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series High Definition Audio Controller [103c:817b]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Atom Processor E3800
Series PCI Express Root Port 1 [8086:0f48] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800 Series
PCI Express Root Port 1 [103c:817b]
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Atom Processor E3800
Series PCI Express Root Port 2 [8086:0f4a] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800 Series
PCI Express Root Port 2 [103c:817b]
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation Atom Processor E3800
Series PCI Express Root Port 4 [8086:0f4e] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800 Series
PCI Express Root Port 4 [103c:817b]
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor
Z36xxx/Z37xxx Series Power Control Unit [103c:817b]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.3 SMBus [0c05]: Intel Corporation Atom Processor E3800/CE2700
Series SMBus Controller [8086:0f12] (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor E3800/CE2700
Series SMBus Controller [103c:817b]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries
BCM43142 802.11b/g/n [14e4:4365] (rev 01)
DeviceName: Broadcom WLAN Broadcom Nami 43142 bgn 1x1 + BT 4
LE PCIe+USB NGFF 1630 MOW
Subsystem: Hewlett-Packard Company BCM43142 802.11b/g/n
[103c:804a]
Kernel driver in use: wl
Kernel modules: bcma, wl
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
RTS5229 PCI Express Card Reader [10ec:5229] (rev 01)
Subsystem: Hewlett-Packard Company RTS5229 PCI Express Card
Reader [103c:817b]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci

Installation du système de base :
[O] = OK, [E] = Error, [ ] = non essayé

Initial boot:   [O]
Detect network card:[E] for wifi then use USB ethernet [O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Still missing non free kernel drive

Bug#1036319: installation-reports: Multiple Installation report for RC3 on openQA

[Roland Clobus]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: p...@hands.com


Boot method: CD in openQA
Image version:
https://cdimage.debian.org/cdimage/bookworm_di_rc3/amd64/iso-cd/debian-
bookworm-DI-rc3-amd64-netinst.iso
Date: 

Machine: openQA x86_64 qemu video: qxl memory: 2GB. SeaBIOS and Tianocore UEFI
(non-secure)

Comments/Problems:

See
https://openqa.debian.net/tests/overview?distri=debian&version=bookworm&build=DI_rc3&groupid=10

On the page 'Logs & Assets' the file '_graphical_wait_login-journal.txt'
contains the output of journalctl.

The following issues are detected:
Cinnamon: For BIOS boot, on first boot, a dialog is shown 'You are currently
running in fallback mode'. The UEFI installation works fine.

GNOME: For BIOS boot, on first boot, a dialog is shown 'On no! Something has
gone wrong'. The UEFI installation works fine.
The journalctl file has the following suspect snippet:

May 18 17:16:17 debian org.gnome.Shell.desktop[610]: LLVM ERROR: 64-bit code
requested on a subtarget that doesn't support it!
May 18 17:16:17 debian org.gnome.Shell.desktop[610]: == Stack trace for context
0x55aacc0f37c0 ==


KDE: For BIOS boot, on first boot, the screen stays black (no plymouth splash
screen is shown). The UEFI installation works fine.
The journalctl file has the following suspect snippet:

May 18 18:14:03 debian systemd-coredump[584]: Process 536 (sddm-greeter) of
user 110 dumped core.


LXQt: For BIOS boot, on first boot, the screen stays black (no plymouth splash
screen is shown). Due to #1023472, this might be the same issue as for KDE.
The UEFI installation shows the KDE login, as reported in #1023472.

The other desktops (LXDE, Mate and XFCE) install correctly in both BIOS and
UEFI installations.

In all cases, the installation itself runs fine. (Even though a screensaver
might not be ideal -> #787279). It is 'only' the first boot that causes issues.

Note that some issues on the public openQA server (running on AMD hardware)
were not reproducible on my local openQA server (running on Intel hardware)

With kind regards,
Roland Clobus


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux silent 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5000]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Intel Corporation Device [8086:2010]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5007]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Lynx Point KT 
Controller [8086:8c3d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I217-V [8086:153b] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:e000]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #2 [8086:8c2d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5006]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Lynx Point High 
Definition Audio Controller [8086:8c20] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:a002]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Lynx Point PCI Express 
Root Port #1 [8086:8c10] (rev d4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev d4)
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #1 [8086:8c26] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5006]
lspci -kn

Bug#1036215: installation-reports: PXE netboot x86_64 libvirt guest on aarch64 host

[Cyril Brulebois]

Hi!

Emanuele Rocca  (2023-05-17):
> This report is about the successful installation of Bookworm on a x86_64 guest
> running on a aarch64 host. The guest was installed with virt-manager using PXE
> boot and UEFI Secure Boot enabled. Everything went smoothly except:
> 
> (A) some troubles with the UEFI PXE boot device to choose

Oh, wow. I'm skipping this as I still have some GRUB/OVMF debugging on
my own to finish. :)

> (B) failure to load the grub splash screen
> 
> (A)
> At VM startup I've entered the UEFI firmware and booted selecting the first
> PXEv4 option, see [0].
> 
> Choosing the first one *seemed* to work fine, but it ended up in a Secure Boot
> error (see [1]). Disabling Secure Boot did not fix the problem, I still got a
> "Invalid Parameter" error. It eventually became clear that I had to boot with
> [2] instead. I'm not really sure what the difference between the two may be,
> and if this is an issue in the Tianocore firmware.
> 
> At any rate, [2] worked fine with and without Secure Boot enabled. I went on
> with a preseeded installation, which finished uneventfully.
> 
> I then noticed the following errors in the libvirtd logs on the host (B):
> 
>  sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/isolinux/splash.png not 
> found for 192.168.122.7
>  sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/splash.png not found for 
> 192.168.122.7
> 
> The grub.cfg file under /debian-installer/amd64/grub/grub.cfg has the 
> following
> conditionals:
> 
>  if background_image /isolinux/splash.png; then
> [...]
>  elif background_image /splash.png; then
> 
> The splash screen is loaded correctly replacing either of those with
> /debian-installer/amd64/boot-screens/splash.png instead.

Adding an extra conditional in there really doesn't seem appropriate at
this point. Seeing how images/netboot/ is 745M, and how splash.png is
58K, I think I'd rather have it duplicated in a way that it's found in
/splash.png for both text and gtk installers (/isolinux/splash.png could
would be a weird location given the booting happens via GRUB).

Two words of caution though:

(1) Many archs, many builds for each, make sure not to break any when
tweaking the code. :) That being said, it should be seen via daily
builds, and worst case it happens on the buildds after uploading
debian-installer, and I need to either revert or fix on the spot and
re-upload an hour later.

(2) We should make sure the possible duplication doesn't interfere with
debian-installer--netboot-'s co-installability. It looks
like each of them uses a separate  top-level directory
anyway, but I thought I'd mention it anyway.

debian-installer-12-netboot-amd64: 
/usr/lib/debian-installer/images/12/amd64/gtk/pxelinux.0
debian-installer-12-netboot-amd64: 
/usr/lib/debian-installer/images/12/amd64/gtk/pxelinux.cfg

debian-installer-12-netboot-amd64: 
/usr/lib/debian-installer/images/12/amd64/text/pxelinux.0
debian-installer-12-netboot-amd64: 
/usr/lib/debian-installer/images/12/amd64/text/pxelinux.cfg


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1036215: installation-reports: PXE netboot x86_64 libvirt guest on aarch64 host

[Emanuele Rocca]

Package: installation-reports

Boot method: PXE netboot
Image version: netboot.tar.gz from 
https://deb.debian.org/debian/dists/testing/main/installer-amd64/20230515/images/netboot/

Machine: QEMU TCG x86_64 libvirt guest on aarch64 host

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

This report is about the successful installation of Bookworm on a x86_64 guest
running on a aarch64 host. The guest was installed with virt-manager using PXE
boot and UEFI Secure Boot enabled. Everything went smoothly except:

(A) some troubles with the UEFI PXE boot device to choose
(B) failure to load the grub splash screen

(A)
At VM startup I've entered the UEFI firmware and booted selecting the first
PXEv4 option, see [0].

Choosing the first one *seemed* to work fine, but it ended up in a Secure Boot
error (see [1]). Disabling Secure Boot did not fix the problem, I still got a
"Invalid Parameter" error. It eventually became clear that I had to boot with
[2] instead. I'm not really sure what the difference between the two may be,
and if this is an issue in the Tianocore firmware.

At any rate, [2] worked fine with and without Secure Boot enabled. I went on
with a preseeded installation, which finished uneventfully.

I then noticed the following errors in the libvirtd logs on the host (B):

 sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/isolinux/splash.png not 
found for 192.168.122.7
 sarzana dnsmasq-tftp[7413]: file /srv/tftp/bookworm/splash.png not found for 
192.168.122.7

The grub.cfg file under /debian-installer/amd64/grub/grub.cfg has the following
conditionals:

 if background_image /isolinux/splash.png; then
[...]
 elif background_image /splash.png; then

The splash screen is loaded correctly replacing either of those with
/debian-installer/amd64/boot-screens/splash.png instead.

[0] https://people.debian.org/~ema/RC3-x86_64-uefi-firmware.png
[1] https://people.debian.org/~ema/RC3-x86_64-uefi-firmware-sb-error.png
[2] https://people.debian.org/~ema/RC3-x86_64-uefi-firmware-right-entry.png

PS:

To test PXE boot with libvirt I've edited the default network with:

 $ sudo virsh net-edit default

Here's what the  part looks like:



  
  

I've untarred netboot.tar.gz under /srv/tftp/bookworm/.

After editing the network, I re-created it with:

 $ sudo virsh net-destroy default && sudo virsh net-start default

Although I'm not 100% sure it was necessary, I've also restarted libvirt and
shot a couple of dnsmasq processes that seemed to want to stick around: 

 $ sudo systemctl stop libvirtd && sudo pkill dnsmasq && sudo systemctl start 
libvirtd

Processed: Re: Bug#1035824: installation-reports: unable to detect Realtek RTL8188EUS 802.11n USB WiFi adapter

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux
Bug #1035824 [installation-reports] installation-reports: unable to detect 
Realtek RTL8188EUS 802.11n USB WiFi adapter
Bug reassigned from package 'installation-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #1035824 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1035824 to the same values 
previously set
> tag -1 patch
Bug #1035824 [src:linux] installation-reports: unable to detect Realtek 
RTL8188EUS 802.11n USB WiFi adapter
Added tag(s) patch.

-- 
1035824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1035824: installation-reports: unable to detect Realtek RTL8188EUS 802.11n USB WiFi adapter

[Cyril Brulebois]

Control: reassign -1 src:linux
Control: tag -1 patch

Hi,

Cyril Brulebois  (2023-05-09):
> Fabian Greffrath  (2023-05-09):
> > Sadly, another failed attempt to install Debian on my brand-new Lenovo
> > IdeaPad 5, this time using a USB dongle equiped with the Realtek
> > RTL8188EUS chip set.
> > 
> > The installer failed to detect the network adapter and presented me
> > with a list of kernel modules, none of which got my device to work.
> > This is what dmesg reports after I plug the adapter into a USB port on
> > my current device, which is obviously not the same one as the report
> > applies to  (which is why I removed all of the appended logs):
> > 
> > [42871.476218] usb 1-4: new high-speed USB device number 19 using xhci_hcd
> > [42871.624725] usb 1-4: New USB device found, idVendor=0bda, 
> > idProduct=8179, bcdDevice= 0.00
> > [42871.624729] usb 1-4: New USB device strings: Mfr=1, Product=2, 
> > SerialNumber=3
> > [42871.624731] usb 1-4: Product: 802.11n NIC
> > [42871.624732] usb 1-4: Manufacturer: Realtek
> > [42871.624733] usb 1-4: SerialNumber: 00E04C0001
> > [42871.936975] r8188eu: module is from the staging directory, the quality 
> > is unknown, you have been warned.
> > [42871.970033] usbcore: registered new interface driver r8188eu
> > [42872.005633] r8188eu 1-4:1.0 wlx482254c71aaf: renamed from wlan0
> > [42872.597812] r8188eu 1-4:1.0: firmware: direct-loading firmware 
> > rtlwifi/rtl8188eufw.bin
> > [42872.597825] r8188eu 1-4:1.0: Firmware Version 11, SubVersion 1, 
> > Signature 0x88e1
> > [42881.731472] r8188eu 1-4:1.0: firmware: direct-loading firmware 
> > rtlwifi/rtl8188eufw.bin
> > 
> > Interstingly, calling dmesg on the system where the installation
> > attempt failed, the line starting with 42871.936975,i.e. where the
> > actual kernel module is loaded, and all following ones are omitted.
> 
> Please share the full /var/log/syslog (compressed).

Nevermind, as spotted by Pascal Hambourg, the staging driver isn't shipped
in nic-wireless-modules (name that's slightly different from the usual
drivers/staging/rtl8**).

Reassigning to src:linux and tagging accordingly.

Merge request coming up (once Salsa upgrades are over), but the r8188eu-udeb
branch is already available in my fork:
  https://salsa.debian.org/kibi/linux/

Tested locally by hotpatching the relevant linux-support file, with the same
line addition, resulting in the following debdiff:

Files in second .deb but not in first
-
-rw-r--r--  root/root   
/lib/modules/6.1.0-8-amd64/kernel/drivers/staging/r8188eu/r8188eu.ko

Unlikely to appear in time for RC 3, chances should be better for RC 4 (but
it really depends on whether we'll need or want another linux upload in the
next few days).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035824: installation-reports: unable to detect Realtek RTL8188EUS 802.11n USB WiFi adapter

[Cyril Brulebois]

Hi Fabian,

Fabian Greffrath  (2023-05-09):
> Sadly, another failed attempt to install Debian on my brand-new Lenovo
> IdeaPad 5, this time using a USB dongle equiped with the Realtek
> RTL8188EUS chip set.
> 
> The installer failed to detect the network adapter and presented me
> with a list of kernel modules, none of which got my device to work.
> This is what dmesg reports after I plug the adapter into a USB port on
> my current device, which is obviously not the same one as the report
> applies to  (which is why I removed all of the appended logs):
> 
> [42871.476218] usb 1-4: new high-speed USB device number 19 using xhci_hcd
> [42871.624725] usb 1-4: New USB device found, idVendor=0bda, idProduct=8179, 
> bcdDevice= 0.00
> [42871.624729] usb 1-4: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [42871.624731] usb 1-4: Product: 802.11n NIC
> [42871.624732] usb 1-4: Manufacturer: Realtek
> [42871.624733] usb 1-4: SerialNumber: 00E04C0001
> [42871.936975] r8188eu: module is from the staging directory, the quality is 
> unknown, you have been warned.
> [42871.970033] usbcore: registered new interface driver r8188eu
> [42872.005633] r8188eu 1-4:1.0 wlx482254c71aaf: renamed from wlan0
> [42872.597812] r8188eu 1-4:1.0: firmware: direct-loading firmware 
> rtlwifi/rtl8188eufw.bin
> [42872.597825] r8188eu 1-4:1.0: Firmware Version 11, SubVersion 1, Signature 
> 0x88e1
> [42881.731472] r8188eu 1-4:1.0: firmware: direct-loading firmware 
> rtlwifi/rtl8188eufw.bin
> 
> Interstingly, calling dmesg on the system where the installation
> attempt failed, the line starting with 42871.936975,i.e. where the
> actual kernel module is loaded, and all following ones are omitted.

Please share the full /var/log/syslog (compressed).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035824: installation-reports: unable to detect Realtek RTL8188EUS 802.11n USB WiFi adapter

[Fabian Greffrath]

Package: installation-reports
Severity: normal

Boot method: USB
Image version: debian-bookworm-DI-rc2-amd64-netinst.iso (downloaded 2023-05-05)

Machine: Lenovo IdeaPad 5


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[E]

Comments/Problems:

Sadly, another failed attempt to install Debian on my brand-new Lenovo
IdeaPad 5, this time using a USB dongle equiped with the Realtek
RTL8188EUS chip set.

The installer failed to detect the network adapter and presented me
with a list of kernel modules, none of which got my device to work.
This is what dmesg reports after I plug the adapter into a USB port on
my current device, which is obviously not the same one as the report
applies to  (which is why I removed all of the appended logs):

[42871.476218] usb 1-4: new high-speed USB device number 19 using xhci_hcd
[42871.624725] usb 1-4: New USB device found, idVendor=0bda, idProduct=8179, 
bcdDevice= 0.00
[42871.624729] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[42871.624731] usb 1-4: Product: 802.11n NIC
[42871.624732] usb 1-4: Manufacturer: Realtek
[42871.624733] usb 1-4: SerialNumber: 00E04C0001
[42871.936975] r8188eu: module is from the staging directory, the quality is 
unknown, you have been warned.
[42871.970033] usbcore: registered new interface driver r8188eu
[42872.005633] r8188eu 1-4:1.0 wlx482254c71aaf: renamed from wlan0
[42872.597812] r8188eu 1-4:1.0: firmware: direct-loading firmware 
rtlwifi/rtl8188eufw.bin
[42872.597825] r8188eu 1-4:1.0: Firmware Version 11, SubVersion 1, Signature 
0x88e1
[42881.731472] r8188eu 1-4:1.0: firmware: direct-loading firmware 
rtlwifi/rtl8188eufw.bin

Interstingly, calling dmesg on the system where the installation
attempt failed, the line starting with 42871.936975,i.e. where the
actual kernel module is loaded, and all following ones are omitted.


Hope this helps!

Cheers,

 - Fabian

Bug#1035588: installation-reports: Installation of GNOME desktop fails (in openQA)

[Roland Clobus]

On 05/05/2023 22:26, Roland Clobus wrote:

Sorry, I mixed up KDE and GNOME reports...

Fixing the URLs to point to the GNOME issue


Boot method: CD
Image version: daily netinst 20230505_1104 from
https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/
Date: 2023-05-05T15:57:23

Machine: qemu running on AMD64 server osuosl3.debian.net

See: https://openqa.debian.net/tests/144876

Partitions:

https://openqa.debian.net/tests/144876/logfile?filename=complete_install-gdisk.txt 


--
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***

Disk /dev/vda: 20971520 sectors, 10.0 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 2E91D03B-B669-42AF-9A53-D4DD7C273F31
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 20971486
Partitions will be aligned on 2048-sector boundaries
Total free space is 6077 sectors (3.0 MiB)

Number  Start (sector)End (sector)  Size   Code  Name
   1204818970623   9.0 GiB 8300  Linux filesystem
   51897267220969471   975.0 MiB   8200  Linux swap
--


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]


Comments/Problems:

After the reboot the GNOME login screen is not shown, instead the screen 
shows 'Oh no! Something has gone wrong'.


This is a suspicious parts from `journalctl -b`:
https://openqa.debian.net/tests/144876/logfile?filename=_graphical_wait_login-journal.txt

May 05 13:59:35 debian org.gnome.Shell.desktop[610]: LLVM ERROR: 64-bit 
code requested on a subtarget that doesn't support it!
May 05 13:59:35 debian org.gnome.Shell.desktop[610]: == Stack trace for 
context 0x5560643b27d0 ==


I've used the same ISO file on my Intel-based computer, that worked fine.

With kind regards,
Roland Clobus


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035588: installation-reports: Installation of GNOME desktop fails (in openQA)

[Roland Clobus]

Package: installation-reports
Severity: normal
User: debian...@lists.debian.org
X-Debbugs-Cc: p...@hands.com

Boot method: CD
Image version: daily netinst 20230505_1104 from
https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/
Date: 2023-05-05T15:57:23

Machine: qemu running on AMD64 server osuosl3.debian.net
See: https://openqa.debian.net/tests/144783
Partitions:

https://openqa.debian.net/tests/144783/logfile?filename=complete_install-
gdisk.txt

--
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***

Disk /dev/vda: 31457280 sectors, 15.0 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 71C86CFF-DC9F-4BC4-B99D-DB5CF15F1DB3
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 31457246
Partitions will be aligned on 2048-sector boundaries
Total free space is 6077 sectors (3.0 MiB)

Number  Start (sector)End (sector)  Size   Code  Name
   1204829456383   14.0 GiB8300  Linux filesystem
   52945843231455231   975.0 MiB   8200  Linux swap
--

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

After the reboot the GNOME login screen is not shown, instead the screen stays
black.

Judging from the output of `journalctl -b`, sddm-greeter causes a core dump
https://openqa.debian.net/tests/144783/logfile?filename=_graphical_wait_login-
journal.txt
systemd-coredump[917]: Process 873 (sddm-greeter) of user 113 dumped core.

I've used the same ISO file on my Intel-based hardware, with a similar
invocation of qemu, and there the ISO images worked fine.

With kind regards,
Roland Clobus

PS: The netinst-RC2 image has the same issue


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux silent 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5000]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Intel Corporation Device [8086:2010]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5007]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Lynx Point KT 
Controller [8086:8c3d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I217-V [8086:153b] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:e000]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #2 [8086:8c2d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5006]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Lynx Point High 
Definition Audio Controller [8086:8c20] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:a002]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Lynx Point PCI Express 
Root Port #1 [8086:8c10] (rev d4)
lspci -knn: Kernel driver in use: pcieport

Processed: Re: Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux
Bug #1035569 [installation-reports] installation-reports: failed to detect 
Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter
Bug reassigned from package 'installation-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #1035569 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1035569 to the same values 
previously set
> retitle -1 please enable CONFIG_RTW89_8852BE
Bug #1035569 [src:linux] installation-reports: failed to detect Realtek 
RTL8852BE WiFi 6 802.11ax PCIe adapter
Changed Bug title to 'please enable CONFIG_RTW89_8852BE' from 
'installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe 
adapter'.
> affects -1 installation-reports
Bug #1035569 [src:linux] please enable CONFIG_RTW89_8852BE
Added indication that 1035569 affects installation-reports

-- 
1035569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Cyril Brulebois]

Control: reassign -1 src:linux
Control: retitle -1 please enable CONFIG_RTW89_8852BE
Control: affects -1 installation-reports

Hi,

Fabian Greffrath  (2023-05-05):
> Today I attempted to install Debian bookworm on a brand new Lenovo
> IdeaPad 5 14IAL7 with an i5-1235U CPU, 16GB RAM and 512GB SDD.
> 
> The installation failed to proceed at the network card detection
> stage. Apparently, the machine has a Realtek RTL8852BE adapter, which
> *should* be supported by recent kernels.

As mentioned in follow-ups (by Diederik and me), that module only appeared
in v6.2-rc1 (v6.2-rc1~99^2~345^2~3), so no it's not available in Bookworm.

Reassigning to the kernel accordingly, so that it gets enabled in some
future upload.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Cyril Brulebois]

fab...@greffrath.com  (2023-05-05):
> When will be the earliest chance for a D-I image with kernel >= 6.2?

One prerequisite is having said kernel in unstable/testing.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[fabian]

Am 05.05.2023 18:23, schrieb Cyril Brulebois:

Right, initial support seems to have been merged in time for v6.2-rc1
only.


Oh, no!

When will be the earliest chance for a D-I image with kernel >= 6.2?

Cheers,

 - Fabian

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Cyril Brulebois]

Diederik de Haas  (2023-05-05):
> Too recent for Bookworm as it appears that it was added in 6.2, while
> Bookworm has 6.1.

Right, initial support seems to have been merged in time for v6.2-rc1
only.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Diederik de Haas]

On Friday, 5 May 2023 17:45:34 CEST Fabian Greffrath wrote:
> Today I attempted to install Debian bookworm on a brand new Lenovo
> IdeaPad 5 14IAL7 with an i5-1235U CPU, 16GB RAM and 512GB SDD.
> 
> The installation failed to proceed at the network card detection
> stage. Apparently, the machine has a Realtek RTL8852BE adapter, which
> *should* be supported by recent kernels.

Too recent for Bookworm as it appears that it was added in 6.2,
while Bookworm has 6.1.

signature.asc
Description: This is a digitally signed message part.