Bug#1057237: debian-installer: Debian 12 (Bookworm) on Ace Magic T8Plus: Installation Report

[Charles Curley]

Package: debian-installer
Severity: normal
X-Debbugs-Cc: charlescur...@charlescurley.com

Dear Maintainer,

I took delivery of two Ace Magic T8+ computers recently. 
https://www.acemagic.com/products/t8plus I am bringing one up as a router 
running Debian 12.2 (Bookworm).

A full hardware probe of the machine is at Linux Hardware. 
https://linux-hardware.org/?probe=d0bbc73e29 Note that this was run over SSH, 
so any monitor information is incorrect. However, it does work with an NEC 
EA244WMi connected directly.

I first used a live CD to test the machine. I then used gparted to shrink the 
Windows partition to 60 G, giving me 177G for Linux, plenty for this 
application. I then booted to Windows so that it would do any necessary fixup 
on its partition.

I then installed using a netinst image (debian-12.2.0-amd64-netinst.iso) on a 
USB stick, and a second USB stick for my preseed file and some 
post-installation scripts. All has gone well, with one glitch.

The glitch was that after the installation the T8+ refused to boot to Linux, 
going directly into Windows. To make the grub bootloader active after 
installing Linux and GRUB, in the firmware:

During boot, hit escape or delete to get into the firmware.

Security -> Secure Boot -> Enabled

Boot -> UEFI BBS Priorities -> Debian boot option

Save & Exit -> Save Changes and Exit

Note: Memtest86 does not appear to work. I believe this is a problem with 
Memtest86, per emails on the Debian User list.

Power use: 5 watts when idle, .28 KWH.


-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Pascal Hambourg]

On 25/11/2023 at 22:29, David Hillman wrote:

On 11/25/23 01:37, Cyril Brulebois wrote:

Extracting /var/log/syslog would be useful to understand what's going on
there. (...)

Thanks Cyril.  This system is running Debian 12, so there is no 
/var/log/syslog.


Cyril meant the installer syslog, which is saved in /var/log/installer 
on the installed system at the end of the installation.


(Gmail will probably reject this mail though)

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Cyril Brulebois]

David Hillman  (2023-11-25):
> Thanks Cyril.  This system is running Debian 12, so there is no
> /var/log/syslog.  As I mentioned in the original report, I found nothing
> apparently related in the Journal.

I'm confused. You filed an installation report regarding a failure to
recognize network cards. I'm therefore assuming you're having issues
with the installation process, and requesting /var/log/syslog, which is
definitely where the installer logs what's going on. You also marked the
overall install with E = Error…

It'd make sense to clarify whether the problem affects the installer,
and/or the installed system.

Anyway, a copy of installer logs is available under /var/log/installer/
in the installed system.


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


signature.asc
Description: PGP signature

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[David Hillman]

On 11/25/23 01:37, Cyril Brulebois wrote:

Extracting /var/log/syslog would be useful to understand what's going on
there. A very quick search suggests this card might be supported by the
tg3 module (drivers/net/ethernet/broadcom/tg3.c), which is definitely
shipped in the installer. So maybe it's something that needs tweaking or
fixing on the firmware side (e.g. “modprobe dance”), or a missing
auxiliary bus (e.g. mhi) to make the card visible. Hard to tell without
any logs.

Thanks Cyril.  This system is running Debian 12, so there is no 
/var/log/syslog.  As I mentioned in the original report, I found nothing 
apparently related in the Journal.



--
David Hillman

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Cyril Brulebois]

Lennart Sorensen  (2023-11-25):
> I suspect you are missing the firmware file for the network port.  I think 
> this one:
> 
> firmware-misc-nonfree: /lib/firmware/tigon/tg3.bin
> 
> The installer probably does not include that.

The netinst *definitely* does ship that package:
  
https://cdimage.debian.org/cdimage/release/current/amd64/list-cd/debian-12.2.0-amd64-netinst.list.gz


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


signature.asc
Description: PGP signature

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Lennart Sorensen]

On Fri, Nov 24, 2023 at 12:34:50PM -0600, David Hillman wrote:
> 
> Package: installation-reports
> 
> Boot method: USB stick
> Image version: 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso
> Date: 2023-November-23 11PM GMT
> 
> Machine: Dell R720
> Processor: 2 x Xeon E5-2650
> Memory: 192GB
> 
> 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:   [ ]
> Load installer modules: [ ]
> Detect hard drives: [O ]
> Partition hard drives:  [O ]
> Install base system:    [ ]
> Clock/timezone setup:   [ ]
> User/password setup:    [O ]
> Install tasks:  [ ]
> Install boot loader:    [ ]
> Overall install:    [E ]
> 
> Comments/Problems:
> 
> 
> Installer completely failed to identify the presence of all four integrated
> Broadcom BCM5720 ethernet ports, and even after manually adding and
> configuring the four interfaces, no network connectivity is to be had. 
> Interfaces are allegedly "UP", but cannot ping anything nor respond to any
> communication.  IDRAC card interface works fine -- on the same subnet.  A
> half-dozen other multi-interface machines on the same subnet are working
> fine, as well.
> 
> Ubuntu 20 and 22 installers work just fine on the same hardware, so this is
> a Debian-specific issue.  All four interfaces work just fine under both
> Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.
> 
> Journal entries for NetworkManager and avahi-daemon appear to show the
> correct IP addresses being registered for all four interfaces, and "ip"
> agress, all to no avail.  No related error messages exist in the journal.

I suspect you are missing the firmware file for the network port.  I think this 
one:

firmware-misc-nonfree: /lib/firmware/tigon/tg3.bin

The installer probably does not include that.

-- 
Len Sorensen

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Diederik de Haas]

On Saturday, 25 November 2023 08:37:09 CET Cyril Brulebois wrote:
> Hard to tell without any logs.

The output of `lsmod` and `dmesg` from both Ubuntu and Debian may also help to 
figure out why it's working in one but not the other.

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

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Holger Wansing]

Hi,

Am 24. November 2023 23:54:49 MEZ schrieb David Hillman 
:
>On 11/24/23 12:59, Holger Wansing wrote:
>Thanks Holger.  I could do that, but that would completely defeat the purpose. 
> I installed Debian 12 on this machine as a test, to confirm that everything 
>necessary works, before installing it on a dozen or so other similar machines.

Trying a debian 13 image was meant as some sort of debugging. 
It would involve a newer kernel for example, in case it's a kernel issue...


Holger



-- 
Sent from /e/ OS on Fairphone3

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Cyril Brulebois]

Hi David,

David Hillman  (2023-11-24):
> Thanks Holger.  I could do that, but that would completely defeat the
> purpose.  I installed Debian 12 on this machine as a test, to confirm that
> everything necessary works, before installing it on a dozen or so other
> similar machines.
> 
> And clearly, the opposite is the case, and it isn't ready for use yet, at
> least, not on server hardware.  I have D12 running on a laptop, and a few
> virtual machines, and it doesn't suffer this problem, but I will apparently
> have to stay with Ubuntu for a while on the servers.

Extracting /var/log/syslog would be useful to understand what's going on
there. A very quick search suggests this card might be supported by the
tg3 module (drivers/net/ethernet/broadcom/tg3.c), which is definitely
shipped in the installer. So maybe it's something that needs tweaking or
fixing on the firmware side (e.g. “modprobe dance”), or a missing
auxiliary bus (e.g. mhi) to make the card visible. Hard to tell without
any logs.


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


signature.asc
Description: PGP signature

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[David Hillman]

On 11/24/23 12:59, Holger Wansing wrote:

Hi,

David Hillman  wrote (Fri, 24 Nov 2023 12:34:50 -0600):

Ubuntu 20 and 22 installers work just fine on the same hardware, so this
is a Debian-specific issue.  All four interfaces work just fine under
both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.

Maybe you could try a preview Debian 13 image?
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/



Thanks Holger.  I could do that, but that would completely defeat the 
purpose.  I installed Debian 12 on this machine as a test, to confirm 
that everything necessary works, before installing it on a dozen or so 
other similar machines.


And clearly, the opposite is the case, and it isn't ready for use yet, 
at least, not on server hardware.  I have D12 running on a laptop, and a 
few virtual machines, and it doesn't suffer this problem, but I will 
apparently have to stay with Ubuntu for a while on the servers.



--
David Hillman

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Holger Wansing]

Hi,

David Hillman  wrote (Fri, 24 Nov 2023 12:34:50 -0600):
> Ubuntu 20 and 22 installers work just fine on the same hardware, so this 
> is a Debian-specific issue.  All four interfaces work just fine under 
> both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.

Maybe you could try a preview Debian 13 image?
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/


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

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[David Hillman]

Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso

Date: 2023-November-23 11PM GMT

Machine: Dell R720
Processor: 2 x Xeon E5-2650
Memory: 192GB

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:   [ ]
Load installer modules: [ ]
Detect hard drives: [O ]
Partition hard drives:  [O ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [O ]
Install tasks:  [ ]
Install boot loader:    [ ]
Overall install:    [E ]

Comments/Problems:


Installer completely failed to identify the presence of all four 
integrated Broadcom BCM5720 ethernet ports, and even after manually 
adding and configuring the four interfaces, no network connectivity is 
to be had.  Interfaces are allegedly "UP", but cannot ping anything nor 
respond to any communication.  IDRAC card interface works fine -- on the 
same subnet.  A half-dozen other multi-interface machines on the same 
subnet are working fine, as well.


Ubuntu 20 and 22 installers work just fine on the same hardware, so this 
is a Debian-specific issue.  All four interfaces work just fine under 
both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.


Journal entries for NetworkManager and avahi-daemon appear to show the 
correct IP addresses being registered for all four interfaces, and "ip" 
agress, all to no avail.  No related error messages exist in the journal.




--
David Hillman

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#1005308: Installation Report: Crash of Debian netinst iso in Xen HVM guest

[David Brooks]

On Thu, 15 Jun 2023 18:28:51 +0100 Abhinav Praveen 
 wrote:
> This issue persists in the current Debain 12 installer: 
debian-12.0.0-amd64-netinst.iso

> --
> Abhinav Praveen
>
>

The issue is also in the latest installer, debian-12.1.0-amd64-netinst.iso

Bug#1005308: Installation Report: Crash of Debian netinst iso in Xen HVM guest

[Abhinav Praveen]

This issue persists in the current Debain 12 installer: 
debian-12.0.0-amd64-netinst.iso
-- 
Abhinav Praveen

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=bookworm=DI_rc3=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 -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Lynx Point LPC 

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Peter Ehlert]

On May 4, 2023 3:35:40 PM Pascal Hambourg  wrote:


On 04/05/2023 at 16:21, Peter Ehlert wrote:


"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/dev/sde (ata-SanDisk_SDSSDA240G_162248447811)


I selected /dev/sde and pressed the Continue button

then the GUI progress bar Installing GRUB and I see Running
"grub-install /dev/sdd" ...

in this case sdd was the install location, sde is the drive that has a
bios_grub flagged partition


OK, I think I managed to reproduce the issue and it shares the root
cause with another bug I am currently chasing (GRUB is not installed at
all). Some logic in grub-installer seems to be flawed but I still need
to understand the original intent before I can submit a patch for both bugs.

Meanwhile, a workaround is to enter the boot device manually.

Thanks. Best of luck. I appreciate your assistance




setting up BIOS to boot from a drive that does not have a bios_grub
flagged partition results in:

"GPT-formatted disk.

Legacy boot not supported. Press any key to reboot."


If this is a message from the BIOS, then it is flawed. A compliant
BIOS should not care about the partition table, even less the presence
of any kind of partition. All a BIOS should care about is the presence
of the "boot signature" 0x55, 0xAA at the end of the boot sector.


Yes, that is from the BIOS

(...)

root@z820-3:~# grub-install /dev/sda && update-grub
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot
Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for
cross-disk install.


This failure has nothing to do with the above. You are trying to install
GRUB on a GPT disk which is not the one containing /boot ("cross-disk"),
and this requires a BIOS boot partition.

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Pascal Hambourg]

On 04/05/2023 at 16:21, Peter Ehlert wrote:


"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/dev/sde (ata-SanDisk_SDSSDA240G_162248447811)


I selected /dev/sde and pressed the Continue button

then the GUI progress bar Installing GRUB and I see Running 
"grub-install /dev/sdd" ...


in this case sdd was the install location, sde is the drive that has a 
bios_grub flagged partition


OK, I think I managed to reproduce the issue and it shares the root 
cause with another bug I am currently chasing (GRUB is not installed at 
all). Some logic in grub-installer seems to be flawed but I still need 
to understand the original intent before I can submit a patch for both bugs.


Meanwhile, a workaround is to enter the boot device manually.

setting up BIOS to boot from a drive that does not have a bios_grub 
flagged partition results in:


"GPT-formatted disk.

Legacy boot not supported. Press any key to reboot."


If this is a message from the BIOS, then it is flawed. A compliant 
BIOS should not care about the partition table, even less the presence 
of any kind of partition. All a BIOS should care about is the presence 
of the "boot signature" 0x55, 0xAA at the end of the boot sector.


Yes, that is from the BIOS

(...)

root@z820-3:~# grub-install /dev/sda && update-grub
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for 
cross-disk install.


This failure has nothing to do with the above. You are trying to install 
GRUB on a GPT disk which is not the one containing /boot ("cross-disk"), 
and this requires a BIOS boot partition.

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Peter Ehlert]

On 5/2/23 11:59, Pascal Hambourg wrote:

On 02/05/2023 at 15:21, Peter Ehlert wrote:


DI asks on which drive to install GRUB
User says disk X
DI attempts to install on Drive Y
result ... GRUB does not get installed at all


This is completely different from what I understood.

The statement "GRUB does not get installed at all" is refuted by 
/var/log/syslog which indicates clearly that GRUB was successfully 
installed on /dev/sdb:


Apr 28 23:55:51 grub-installer: info: Running chroot /target 
grub-install  --force "/dev/sdb"

(...)
Apr 28 23:56:01 grub-installer: Installation finished. No error 
reported.


Can you described what happened exactly ?
Were you prompted to "Install the GRUB boot loader to your primary 
drive?" ? If yes, did you answer "yes" or "no" ?
Where you then prompted to select the "Device for boot loader 
installation" ? If yes, what option did you select exactly ?

from my initial installation-report:
"when install was finished, a list of drives was displayed, asking where 
to install GRUB.

the install drive was highlighted
I selected the drive with bios_grub
the display showed "installing GRUB on (...drive it was installed on...)"

Pardon me for not being more clear. I will elaborate from the photos I took

"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/dev/sde (ata-SanDisk_SDSSDA240G_162248447811)


I selected /dev/sde and pressed the Continue button

then the GUI progress bar Installing GRUB and I see Running 
"grub-install /dev/sdd" ...


in this case sdd was the install location, sde is the drive that has a 
bios_grub flagged partition




setting up BIOS to boot from a drive that does not have a bios_grub 
flagged partition results in:


"GPT-formatted disk.

Legacy boot not supported. Press any key to reboot."


If this is a message from the BIOS, then it is flawed. A compliant 
BIOS should not care about the partition table, even less the presence 
of any kind of partition. All a BIOS should care about is the presence 
of the "boot signature" 0x55, 0xAA at the end of the boot sector.


Yes, that is from the BIOS

running Debian, from the terminal:

peter@z820-3:~$ su -
Password:
root@z820-3:~# grub-install /dev/sda && update-grub
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for 
cross-disk install.

root@z820-3:~#

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

[James Addison]

Package: installation-reports
Followup-For: Bug #1035392

> The only customized dnsmasq setting required was:
>
>   pxe-service=0, "Raspberry Pi Boot"

Oops, I lied.  There was one other relevant dnsmasq setting:

  dhcp-boot=bootnetaa64.efi

(telling the device what EFI filename to retrieve and run from the TFTP server)

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Pascal Hambourg]

On 02/05/2023 at 15:21, Peter Ehlert wrote:


DI asks on which drive to install GRUB
User says disk X
DI attempts to install on Drive Y
result ... GRUB does not get installed at all


This is completely different from what I understood.

The statement "GRUB does not get installed at all" is refuted by 
/var/log/syslog which indicates clearly that GRUB was successfully 
installed on /dev/sdb:



Apr 28 23:55:51 grub-installer: info: Running chroot /target grub-install  --force 
"/dev/sdb"
(...)
Apr 28 23:56:01 grub-installer: Installation finished. No error reported.


Can you described what happened exactly ?
Were you prompted to "Install the GRUB boot loader to your primary 
drive?" ? If yes, did you answer "yes" or "no" ?
Where you then prompted to select the "Device for boot loader 
installation" ? If yes, what option did you select exactly ?


setting up BIOS to boot from a drive that does not have a bios_grub 
flagged partition results in:


"GPT-formatted disk.

Legacy boot not supported. Press any key to reboot."


If this is a message from the BIOS, then it is flawed. A compliant BIOS 
should not care about the partition table, even less the presence of any 
kind of partition. All a BIOS should care about is the presence of the 
"boot signature" 0x55, 0xAA at the end of the boot sector.

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

[James Addison]

Package: installation-reports
Severity: normal
Tags: d-i

Boot method: network
Image version: [2023-04-28] Bookworm Release Candidate 2 Installer
Date: 2023-05-02

Machine: Raspberry Pi 400
Partitions:

Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs   1871816   0   1871816   0% /dev
tmpfs  tmpfs   386544 704385840   1% /run
/dev/mmcblk1p2 ext4  14689724 4192988   9728736  31% /
tmpfs  tmpfs  1932704   0   1932704   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
/dev/mmcblk1p1 vfat524008  119424404584  23% /boot/efi
tmpfs  tmpfs   386540  44386496   1% /run/user/1000


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

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

Comments:

Although the list of problems in this report might seem lengthy and
arcane, I enjoyed the installation process and think that with a few
small fixes, the rough edges can be removed.  I am writing this report
from an LXDE environment on the installed system.


This was largely an experiment to determine how feasible it is to bring
up a Raspberry Pi 400 over the network and to install Debian Bookworm
from there using the standard Debian Installer process.

The TFTP server was dnsmasq with a fairly minimal configuration based on
Debian's PXE-boot wiki page[1].  In addition to Debian Bookworm's
netboot.tar.gz[2] file (for RC2 at the time of download), the EDK2 UEFI
firmware[3] v1.34 was extracted to the /srv/tftp directory.

The only customized dnsmasq setting required was:

  pxe-service=0, "Raspberry Pi Boot"


Additional firmware for use during the install session was provided by
unpacking a firmware.tar.gz[3] file onto a FAT32-formatted USB drive.


Problems:

  * Firmware for the brcmfmac kernel module was not found on the USB
drive (but is present).  This may be related to #1029843

* Workaround: extracted the .deb contents on another system, placed
  them onto the USB drive, and then used one of the available virtual
  consoles (ctrl-alt-F1 or ctrl-alt-F2) on the install host to mount
  the USB drive and copy the firmware files to /lib/firmware/brcm
  before rmmod'ing and modprobe'ing the kernel module.

  * [minor] The hw-detect/load_firmware dialog box included an
extraneous newline within the displayed filename(s) for which
loading failed.
 
  * The microSD card intended as the installation disk did not appear
under /dev/mmc* when the install began.

* Workaround: rmmod'd and modprobe'd the sdhci* kernel modules;
  after doing that, the disk was detected and available under /dev

  * After completing the installation and rebooting, the first boot from
the install disk failed.  The Raspberry Pi's diagnostics console
showed a 'Firmware not found' message.

* Fix: this seemed to be due to a lack of Pi-compatible firmware on
  the ESP (EFI System Partition) of the install disk.  To resolve
  the problem, the same EDK2 UEFI firmware used on the dnsmasq
  ntboot server was unpacked into the ESP partition from another
  system (by removing the SD card from the Pi and placing it into
  the other machine).

  * After successfully reaching the EDK2 UEFI boot manager, the system
appeared to pause without reaching the expected next-stage GRUB
bootloader.

* Fix: this appears to be due to the default unpacked EDK2 UEFI
  bootmanager being unaware of the GRUB install on the same ESP
  partition.  That's understandable, because GRUB was installed
  before the EDK2 UEFI.

  The problem was solved by using the built-in boot menu management
  in the EDK2 UEFI to add an entry to boot into Debian.  In
  particular, this involved creating a file-boot entry that runs
  'shimaa64.efi'.

That concludes the installer-related issues; with those problems
worked-around / resolved, the system booted correctly.

There was one more problem that may not be installer-related:

  * The 'raspi-firmware' package failed to configure correctly during
'apt install', with an exit code 1 and asking whether the
/boot/firmware path had been mounted.


[1] - 
https://wiki.debian.org/PXEBootInstall?action=show=DebianInstaller%2FNetbootPXE#Another_Way_-_use_Dnsmasq

[2] - 
https://deb.debian.org/debian/dists/testing/main/installer-arm64/current/images/netboot/netboot.tar.gz

[2] - https://github.com/pftf/RPi4/releases/tag/v1.34

[3] - 
https://cdimage.debian.org/cdimage/firmware/bookworm/20230424/firmware.tar.gz


-- Package-specific 

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Peter Ehlert]

On 4/30/23 01:17, Pascal Hambourg wrote:

On 30/04/2023 at 01:47, Peter Ehlert wrote:


On 4/29/23 15:41, Pascal Hambourg wrote:

On 29/04/2023 at 16:02, Peter Ehlert wrote:


reboot gave me the Old GRUB menu, not including my new system.


What do you mean by "old GRUB menu" ? The GRUB which was previously 
installed on /dev/sdb ? 


the GRUB that was on the only disk with a bios_grub flagged partition.


Thank you for the clarification. If I understand correctly,
- the machine usually boots with some GRUB on disk X,
- you installed a new Debian system with GRUB on disk Y,
- then the machine rebooted on disk X as usual.



Correct:

to reiterate the problem...
DI asks on which drive to install GRUB
User says disk X
DI attempts to install on Drive Y
result ... GRUB does not get installed at all



The Debian installer will not add the newly installed system to 
another existing OS GRUB menu; it will only add other existing OS's to 
the new installed system GRUB menu, which will be displayed only if 
the machine boots from the disk containing the new GRUB. So what you 
describe is normal behaviour.



"normal"?
except I am not asking for the existing GRUB menu on drive X to be 
appended.


the request is Install GRUB on drive X

If you want to add the newly installed system to another OS GRUB menu, 
you need to run update-grub from that other OS. If you want to boot 
with the new installed GRUB, you need to set up the BIOS to boot from 
the disk which contains it.


setting up BIOS to boot from a drive that does not have a bios_grub 
flagged partition results in:


"GPT-formatted disk.

Legacy boot not supported. Press any key to reboot."

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Pascal Hambourg]

On 30/04/2023 at 01:47, Peter Ehlert wrote:


On 4/29/23 15:41, Pascal Hambourg wrote:

On 29/04/2023 at 16:02, Peter Ehlert wrote:


reboot gave me the Old GRUB menu, not including my new system.


What do you mean by "old GRUB menu" ? The GRUB which was previously 
installed on /dev/sdb ? 


the GRUB that was on the only disk with a bios_grub flagged partition.


Thank you for the clarification. If I understand correctly,
- the machine usually boots with some GRUB on disk X,
- you installed a new Debian system with GRUB on disk Y,
- then the machine rebooted on disk X as usual.

The Debian installer will not add the newly installed system to another 
existing OS GRUB menu; it will only add other existing OS's to the new 
installed system GRUB menu, which will be displayed only if the machine 
boots from the disk containing the new GRUB. So what you describe is 
normal behaviour.


If you want to add the newly installed system to another OS GRUB menu, 
you need to run update-grub from that other OS. If you want to boot with 
the new installed GRUB, you need to set up the BIOS to boot from the 
disk which contains it.

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Peter Ehlert]

On 4/29/23 15:41, Pascal Hambourg wrote:

Hello Peter,

On 29/04/2023 at 16:02, Peter Ehlert wrote:


Legacy aka BIOS booting
system has 4 physical disk drives, all GPT partition tables
only one drive has a partition with bios_grub

install was on a drive without bios_grub

when install was finished, a list of drives was displayed, asking 
where to install GRUB.

the install drive was highlighted
I selected the drive with bios_grub
the display showed "installing GRUB on (...drive it was installed on...)


According to /var/log/syslog, GRUB was successfully installed on 
/dev/sdb although this drive has no BIOS boot partition:


Apr 28 23:55:51 grub-installer: info: Installing grub on '/dev/sdb'
Apr 28 23:55:51 grub-installer: info: grub-install does not support
--no-floppy
Apr 28 23:55:51 grub-installer: info: Running chroot /target
grub-install  --force "/dev/sdb"
Apr 28 23:55:51 grub-installer: Installing for i386-pc platform.
Apr 28 23:56:01 grub-installer: grub-install: warning: this GPT
partition label contains no BIOS Boot Partition; embedding won't be
possible.
Apr 28 23:56:01 grub-installer: grub-install: warning: Embedding is not
possible.  GRUB can only be installed in this setup by using
blocklists.  However, blocklists are UNRELIABLE and their use is
discouraged..
Apr 28 23:56:01 grub-installer: Installation finished. No error reported.
Apr 28 23:56:01 grub-installer: info: grub-install ran successfully


(several other OS's are on that drive if that matters)

reboot gave me the Old GRUB menu, not including my new system.


What do you mean by "old GRUB menu" ? The GRUB which was previously 
installed on /dev/sdb ? 


the GRUB that was on the only disk with a bios_grub flagged partition.

That does not seem possible according to the above logs. Are you sure 
that the machine rebooted from this disk ? 

apparently so. I know of none other.
GRUB menu showed all of the other systems as before the install.
(note that /dev/sd* naming is not stable across reboots and does not 
match BIOS disk numbering/naming)

I am aware of that



boot from another OS:
# grub-install /dev/sde && update-grub
now my GRUB menu includes the new system


In chroot or directly from the other OS ?

directly from the other OS (also Bookworm), my default
Running grub-install directly from another OS just installed that 
other OS's GRUB on /dev/sde and running update-grub directly just 
added the new Debian installation to that other OS's boot menu if 
os-prober is enabled.

yes, I enabled os-prober

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Pascal Hambourg]

Hello Peter,

On 29/04/2023 at 16:02, Peter Ehlert wrote:


Legacy aka BIOS booting
system has 4 physical disk drives, all GPT partition tables
only one drive has a partition with bios_grub

install was on a drive without bios_grub

when install was finished, a list of drives was displayed, asking where 
to install GRUB.

the install drive was highlighted
I selected the drive with bios_grub
the display showed "installing GRUB on (...drive it was installed on...)


According to /var/log/syslog, GRUB was successfully installed on 
/dev/sdb although this drive has no BIOS boot partition:


Apr 28 23:55:51 grub-installer: info: Installing grub on '/dev/sdb'
Apr 28 23:55:51 grub-installer: info: grub-install does not support
--no-floppy
Apr 28 23:55:51 grub-installer: info: Running chroot /target
grub-install  --force "/dev/sdb"
Apr 28 23:55:51 grub-installer: Installing for i386-pc platform.
Apr 28 23:56:01 grub-installer: grub-install: warning: this GPT
partition label contains no BIOS Boot Partition; embedding won't be
possible.
Apr 28 23:56:01 grub-installer: grub-install: warning: Embedding is not
possible.  GRUB can only be installed in this setup by using
blocklists.  However, blocklists are UNRELIABLE and their use is
discouraged..
Apr 28 23:56:01 grub-installer: Installation finished. No error reported.
Apr 28 23:56:01 grub-installer: info: grub-install ran successfully


(several other OS's are on that drive if that matters)

reboot gave me the Old GRUB menu, not including my new system.


What do you mean by "old GRUB menu" ? The GRUB which was previously 
installed on /dev/sdb ? That does not seem possible according to the 
above logs. Are you sure that the machine rebooted from this disk ? 
(note that /dev/sd* naming is not stable across reboots and does not 
match BIOS disk numbering/naming)



boot from another OS:
# grub-install /dev/sde && update-grub
now my GRUB menu includes the new system


In chroot or directly from the other OS ?
Running grub-install directly from another OS just installed that other 
OS's GRUB on /dev/sde and running update-grub directly just added the 
new Debian installation to that other OS's boot menu if os-prober is 
enabled.

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Peter Ehlert]

On 4/29/23 09:21, Steve McIntyre wrote:

On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote:

On 4/29/23 07:23, Steve McIntyre wrote:

Hi Peter,

Could you please share a copy of the installer logs? You should be
able to find them in /var/log/installer on the installed system.

there is no file "installer" in /var/log

Right, it's a directory with multiple files in it. Could you also


Mr. McIntyre:

I sent several email Huge responses to the list.
I copied the contents of all of the files... were they received?

if not I can repeat or find a pastebin service of some sort.

Thanks, Peter


share the other files please?


I found /var/log/installer/syslog

Thanks...

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Steve McIntyre]

On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote:
>
>On 4/29/23 07:23, Steve McIntyre wrote:
>> Hi Peter,
>> 
>> Could you please share a copy of the installer logs? You should be
>> able to find them in /var/log/installer on the installed system.
>there is no file "installer" in /var/log

Right, it's a directory with multiple files in it. Could you also
share the other files please?

>I found /var/log/installer/syslog

Thanks...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Because heaters aren't purple!" -- Catherine Pitt

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Steve McIntyre]

Hi Peter,

Could you please share a copy of the installer logs? You should be
able to find them in /var/log/installer on the installed system.

On Sat, Apr 29, 2023 at 07:02:43AM -0700, Peter Ehlert wrote:
>Package: grub-installer
>Boot method: USB
>Image version: debian-bookworm-DI-rc2-amd64-netinst.iso
>download from Debian
>Date: 2023-04-28 ~17
>
>Machine: HP Z820 Workstation
>Processor: 2x 8-core model: Intel Xeon E5-2687W
>Memory: 47.06 GiB
>Partitions:
>peter@RC2net:~$ df -T
>Filesystem Type 1K-blocks    Used Available Use% Mounted on
>udev   devtmpfs  24636332   0  24636332   0% /dev
>tmpfs  tmpfs  4934304    1988   4932316   1% /run
>/dev/sda6  ext4  28660644 4485828  22693600  17% /
>tmpfs  tmpfs 24671508   0  24671508   0% /dev/shm
>tmpfs  tmpfs 5120  12  5108   1% /run/lock
>/dev/sda8  ext4  19046484 908  18052708   1% /home
>tmpfs  tmpfs  4934300  56   4934244   1% /run/user/1000
>peter@RC2net:~$
>
>Output of lspci and lspci -n:
>
>peter@RC2net:~$ lspci
>00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07)
>00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 1a (rev 07)
>00:01.1 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 1b (rev 07)
>00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 2a (rev 07)
>00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 3a in PCI Express Mode (rev 07)
>00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map,
>VTd_Misc, System Management (rev 07)
>00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status
>and Global Errors (rev 07)
>00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07)
>00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Virtual Root Port (rev 05)
>00:16.0 Communication controller: Intel Corporation C600/X79 series chipset
>MEI Controller #1 (rev 05)
>00:16.2 IDE interface: Intel Corporation C600/X79 series chipset IDE-r
>Controller (rev 05)
>00:16.3 Serial controller: Intel Corporation C600/X79 series chipset KT
>Controller (rev 05)
>00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
>Connection (Lewisville) (rev 05)
>00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2
>Enhanced Host Controller #2 (rev 05)
>00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High
>Definition Audio Controller (rev 05)
>00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Root Port 2 (rev b5)
>00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Root Port 5 (rev b5)
>00:1c.6 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Root Port 3 (rev b5)
>00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2
>Enhanced Host Controller #1 (rev 05)
>00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
>00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller
>(rev 05)
>00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA
>RAID Controller (rev 05)
>00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host
>Controller (rev 05)
>01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
>Connection
>02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express
>Fusion-MPT SAS-2 (rev 05)
>04:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset
>4-Port SATA Storage Control Unit (rev 05)
>05:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730]
>(rev a1)
>05:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev
>a1)
>08:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI
>Host Controller (rev 02)
>09:01.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a
>Controller (rev 70)
>3f:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 (rev
>07)
>3f:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0
>(rev 07)
>3f:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0
>(rev 07)
>3f:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 (rev
>07)
>3f:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1
>(rev 07)
>3f:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1
>(rev 07)
>3f:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 0 (rev 07)
>3f:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 1 (rev 07)
>3f:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 2 (rev 07)
>3f:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 3 (rev 07)
>3f:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt
>Control Registers (rev 07)
>3f:0b.3 System peripheral: 

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

[Peter Ehlert]

Package: grub-installer
Boot method: USB
Image version: debian-bookworm-DI-rc2-amd64-netinst.iso
download from Debian
Date: 2023-04-28 ~17

Machine: HP Z820 Workstation
Processor: 2x 8-core model: Intel Xeon E5-2687W
Memory: 47.06 GiB
Partitions:
peter@RC2net:~$ df -T
Filesystem Type 1K-blocks    Used Available Use% Mounted on
udev   devtmpfs  24636332   0  24636332   0% /dev
tmpfs  tmpfs  4934304    1988   4932316   1% /run
/dev/sda6  ext4  28660644 4485828  22693600  17% /
tmpfs  tmpfs 24671508   0  24671508   0% /dev/shm
tmpfs  tmpfs 5120  12  5108   1% /run/lock
/dev/sda8  ext4  19046484 908  18052708   1% /home
tmpfs  tmpfs  4934300  56   4934244   1% /run/user/1000
peter@RC2net:~$

Output of lspci and lspci -n:

peter@RC2net:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 1a (rev 07)
00:01.1 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 1b (rev 07)
00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 2a (rev 07)
00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 3a in PCI Express Mode (rev 07)
00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address 
Map, VTd_Misc, System Management (rev 07)
00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control 
Status and Global Errors (rev 07)

00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07)
00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Virtual Root Port (rev 05)
00:16.0 Communication controller: Intel Corporation C600/X79 series 
chipset MEI Controller #1 (rev 05)
00:16.2 IDE interface: Intel Corporation C600/X79 series chipset IDE-r 
Controller (rev 05)
00:16.3 Serial controller: Intel Corporation C600/X79 series chipset KT 
Controller (rev 05)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) (rev 05)
00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 
Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High 
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 2 (rev b5)
00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 5 (rev b5)
00:1c.6 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 3 (rev b5)
00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 
Enhanced Host Controller #1 (rev 05)

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC 
Controller (rev 05)
00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset 
SATA RAID Controller (rev 05)
00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host 
Controller (rev 05)
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
Connection
02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 
PCI-Express Fusion-MPT SAS-2 (rev 05)
04:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset 
4-Port SATA Storage Control Unit (rev 05)
05:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 
730] (rev a1)
05:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller 
(rev a1)
08:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
09:01.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a 
Controller (rev 70)
3f:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 
(rev 07)
3f:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 0 (rev 07)
3f:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 0 (rev 07)
3f:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 
(rev 07)
3f:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 1 (rev 07)
3f:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 1 (rev 07)
3f:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 0 (rev 07)
3f:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 1 (rev 07)
3f:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 2 (rev 07)
3f:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 3 (rev 07)
3f:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt 
Control Registers (rev 07)
3f:0b.3 System peripheral: Intel Corporation Xeon E5/Core i7 Semaphore 
and Scratchpad Configuration Registers (rev 07)
3f:0c.0 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast 
Register 0 (rev 07)
3f:0c.1 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast 
Register 0 (rev 07)

Bug#1033325: marked as done (installation-report: store and report firmware information)

[Debian Bug Tracking System]

Your message dated Wed, 22 Mar 2023 19:49:28 +
with message-id 
and subject line Bug#1033325: fixed in installation-report 2.87
has caused the Debian Bug report #1033325,
regarding installation-report: store and report firmware information
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.)


-- 
1033325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hw-detect
Severity: important
X-Debbugs-Cc: debian-rele...@lists.debian.org

Hi,

Quoting the text that was agreed to via the 2022 General Resolution
about non-free firmware:

When the installer/live system is running we will provide
information to the user about what firmware has been loaded (both
free and non-free), and we will also store that information on the
target system such that users will be able to find it later. 

During the initial brainstorming, I think it was suggested to maybe
include some kind of informational message at the end of the
installation process, like “we installed this and that” or “yay,
you're entirely free”.

That would mean extra work on the translation side, wouldn't add much
value, so that looks like something we should *not* implement.


Regarding the letter of the text, and given hw-detect's code, it's
probably easy enough to keep a file around during the installation
process, with both package name and the component it was found in.

hw-detect already has some finish-install hooks, so it would only need
to generate something like /var/log/installer/firmware-packages from
it, with “$package $component” on each line?

And maybe “# no firmware packages” (with a leading # to signal a
comment), so that people can easily iterate over it if they so wish?


I don't think that's a blocker for the next d-i release, that might be
considered a blocker for Bookworm though; debian-release@ in Cc can
comment and raise severity if that's desired.

If one wanted not to work on this at all, one could make the case that
/var/log/installer/syslog can be used to determine whether/which
firmware packages were installed; the presence of non-free-firmware in
sources.list would be another indication. (That's why I don't think
that's a short-term blocker at all.) But building a 2-column table out
of existing information shouldn't be much work anyway…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: installation-report
Source-Version: 2.87
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
installation-report, 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 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated installation-report 
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: Wed, 22 Mar 2023 20:28:35 +0100
Source: installation-report
Architecture: source
Version: 2.87
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1033325
Changes:
 installation-report (2.87) unstable; urgency=medium
 .
   * Store firmware information in /var/log/installer/firmware-summary
 (Closes: #1033325):
  - Either /var/log/firmware-summary was created by the various
hw-detect scripts, and it was copied over already; in which case,
prettify it a little (adding a descriptive header, and aligning
columns).
  - Or there was no need for firmware at all and there's no such file;
in which case, create it with a single line stating that no
firmware or microcode packages were deployed by the installer.
  - In both cases, developers wishing to process its contents can just
drop lines starting with the '#' character and iterate on the other
ones (if any).
   * Include firmware-summary in installation reports.
Checksums-Sha1:
 b8c6f39bbd2350760eab83b431fd34b8f4ab4e6f 1746 installation-report_2.

Processed: Bug#1033325 marked as pending in installation-report

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1033325 [installation-report] installation-report: store and report 
firmware information
Added tag(s) pending.

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

Bug#1005308: Installation Report: Crash of Debian netinst iso in Xen HVM guest

[Robby]

This is still a problem to this day and the bookworm freeze is right 
around the corner...

Bug#1025522: Debian successful installation report for Dell Inspiron 5482

[Ravi Dwivedi]

Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.5.0-live+nonfree/amd64/iso-hybrid/debian-live-11.5.0-amd64-kde+nonfree.iso

Date: 02 October 2022

Machine: Dell Inspiron 5482
Processor: # dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.

Handle 0x0035, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i5
Manufacturer: Intel(R) Corporation
ID: EB 06 08 00 FF FB EB BF
Signature: Type 0, Family 6, Model 142, Stepping 11
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
Voltage: 1.0 V
External Clock: 100 MHz
Max Speed: 1800 MHz
Current Speed: 1600 MHz
Status: Populated, Enabled
Upgrade: Socket BGA1528
L1 Cache Handle: 0x0032
L2 Cache Handle: 0x0033
L3 Cache Handle: 0x0034
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Core Enabled: 4
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control


Memory: 7.4 Gi
Partitions: device now.>


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

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:[O]

Comments/Problems:

The install was successful and Debian bullseye KDE was used for  months 
without any problems.


I pressed F12 on boot and used UEFI method to boot and download from the 
media.

--
Ravi Dwivedi
https://ravidwivedi.in
PGP key: FF7D B951 7CE1 E19B 6EFE 695F E0E5 BAFD 3BBF 70B3


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1025186: installation-reports: Successful Installation Report

[Spenser Pulleyking]

Package: installation-reports
Severity: wishlist
X-Debbugs-Cc: spenserpulleyk...@yahoo.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/i386/iso-cd/debian-11.5.0-i386-netinst.iso
 11/30/2022
Date: 

Machine: Asus EeePc Eee-1005HA
Partitions: 


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

Initial boot:   [ ]
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:




Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u5"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux eee 5.10.0-18-686 #1 SMP Debian 5.10.140-1 (2022-09-02) i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express 
Memory Controller Hub [8086:27ac] (rev 03)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] 
(rev 03)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
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:83ce]
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:830f]
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:830f]
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:830f]
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:830f]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family 
USB2 EHCI Controller [8086:27cc] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI 
Bridge [8086:2448] (rev e2)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC 
Interface Bridge [8086:27b9] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
lspci -knn: Kernel modules: intel_rng
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 82801GBM/GHM 
(ICH7-M Family) SATA Controller [AHCI mode] [8086:27c5] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel 

Processed: Re: Installation Report: Crash of Debian netinst iso in Xen HVM guest

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1005308 [installation-reports] Installation Report: Crash of Debian 
netinst iso in Xen HVM guest
Severity set to 'important' from 'normal'

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

installation-report is marked for autoremoval from testing

[Debian testing autoremoval watch]

installation-report 2.80 is marked for autoremoval from testing on 2022-06-30

It (build-)depends on packages with these RC bugs:
1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, 
CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192
 https://bugs.debian.org/1011146



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

Bug#1010272: Installation Report Debian 11.2

[Max Euer]

Package: installation-reports

Boot method:  DVD
Image version:Debian GNU/Linux 11.2.0 _Bullseye_ - Official amd64 
NETINST 20211218-11:12

Date: 31st Mar 2022

Machine:AMD A4-4000 APU with Radeon(tm) HD Graphics
BIOS: MSI FM2-A75MA-P33
Partitions: 
/dev/sda1 FAT32 - unused
 sda2 FAT16 PCDOS
 sda6 swap
 sda6 swap
 sda7 Debian ext4

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:    [E ]
Detect hard drives: [O ]
Partition hard drives:  [E ] Warning: Device 0x0800: Inconsistent 
partition table, 2nd entry

Install base system:    [O ]
Install tasks:  [O ]
Install boot loader:    [O ]
Overall install:    [E ]

Comments/Problems:
1st BOOT AFTER THE INSTALLATION I WAS UNABLE TO LOG IN AS ROOT [WRONG 
PASSWORD]

LOG IN AS A USER DID WORK.
I HAD TO DO A RESCUE REBOOT OR
BOOT WITH KERNEL CMD-LINE root=/dev/sda7 init=/bin/bash rw ,
THEN DO PASSWD , RE-ENTERING THE PASSWORD, AFTER THAT ALL WAS WELL
ONGOING PROBLEM AT LEAST SINCE DEBIAN 8

THERE WAS ANOTHER DIFFICULTY WITH THE VGA CARD: WORDS WERE SHIFTED MUCH 
TOO FAR

TO THE LEFT WHICH COULD NOT BE CORRECTED BY THE MONITOR [ACER].
EVENTUALLY ADDING A KERNEL OPTION append="video=VGA-1:800x600R-16@60"
DID THE TRICK HOWEVER HOW TO PHRASE THAT SENTENCE WAS HARD TO FIND!

--
Max Euer - Oud Lemiers 18 - NL6295AT Lemiers -
T  NL0618403128,D024079539727 - E  euer@googlemail.com

Bug#1006442: installation-report: mini-NAS v1 reinstalled with Buster 10.10 due to upgrade-failure

[andrew glaeser]

m Board Or Motherboard
dmidecode:  Use: Flash Memory
dmidecode:  Error Correction Type: None
dmidecode:  Maximum Capacity: 1 MB
dmidecode:  Error Information Handle: Not Provided
dmidecode:  Number Of Devices: 1
dmidecode: 
dmidecode: Handle 0x0020, DMI type 19, 15 bytes
dmidecode: Memory Array Mapped Address
dmidecode:  Starting Address: 0x000FFF0
dmidecode:  Ending Address: 0x000
dmidecode:  Range Size: 1 MB
dmidecode:  Physical Array Handle: 0x001F
dmidecode:  Partition Width: 1
dmidecode: 
dmidecode: Handle 0x0021, DMI type 17, 28 bytes
dmidecode: Memory Device
dmidecode:  Array Handle: 0x001F
dmidecode:  Error Information Handle: Not Provided
dmidecode:  Total Width: 8 bits
dmidecode:  Data Width: 8 bits
dmidecode:  Size: 1024 kB
dmidecode:  Form Factor: Chip
dmidecode:  Set: None
dmidecode:  Locator: Null
dmidecode:  Bank Locator: Null
dmidecode:  Type: EEPROM
dmidecode:  Type Detail: Non-Volatile
dmidecode:  Speed: 33 MT/s
dmidecode:  Manufacturer: 
dmidecode:  Serial Number:  
dmidecode:  Asset Tag:  
dmidecode:  Part Number: 
dmidecode:  Rank: Unknown
dmidecode: 
dmidecode: Handle 0x0022, DMI type 20, 19 bytes
dmidecode: Memory Device Mapped Address
dmidecode:  Starting Address: 0x000FFF0
dmidecode:  Ending Address: 0x000
dmidecode:  Range Size: 1 MB
dmidecode:  Physical Device Handle: 0x0021
dmidecode:  Memory Array Mapped Address Handle: 0x0020
dmidecode:  Partition Row Position: 1
dmidecode: 
dmidecode: Handle 0x0023, DMI type 127, 4 bytes
dmidecode: End Of Table
dmidecode: 

- -- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-18-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

installation-report depends on no packages.

Versions of packages installation-report recommends:
ii  pciutils   1:3.5.2-1
ii  reportbug  7.5.3~deb10u1

installation-report suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQTF9uNaslvnJpWt8kXn6sEfJS3nCwUCYhjexQAKCRDn6sEfJS3n
C9rzAJ9iBo0eaReVHvihMBh+6ZFd5GC8RwCdHpaKL/X4RWyCm0EmFqUiHxIZwvw=
=S8ue
-END PGP SIGNATURE-

Bug#988797: marked as done (RC1 installation report)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jan 2022 13:22:09 +0100
with message-id <20220116132209.f5d2130cc006cf61f4d0f...@mailbox.org>
and subject line Re: Bug#988797: RC1 installation report
has caused the Debian Bug report #988797,
regarding RC1 installation report
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.)


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

Package: installation-reports

I did install Debian on an Acer laptop. The installation went OK, but I 
have some things to tell:


1. After the installation the 240GB SSD was after a short period full 
with PCIe AER errors in the logs.  I think it's good to tell about 
errors in the logs, but doing that thousands of times is not OK.

After using "PCI=NOAER" the laptop works fine.

2. After the installation the sources.list had a "deb cdrom" line. 
Important to tell that I've used the official DVD ISO image. This 
problem was there too in Debian 10. I will add the sources.list.
I think most people who use a DVD-iso will use internet to install more 
packages, and will remove the DVD or stick. I sell Debian DVD's.


With regards,
Paul van der Vlis




-
# deb cdrom:[Debian GNU/Linux bullseye-DI-rc1 _Bullseye_ - Official 
Snapshot amd64 DVD Binary-1 20210415-20:26]/ bul>


deb cdrom:[Debian GNU/Linux bullseye-DI-rc1 _Bullseye_ - Official 
Snapshot amd64 DVD Binary-1 20210415-20:26]/ bulls>


deb http://ftp.nl.debian.org/debian/ bullseye main
deb-src http://ftp.nl.debian.org/debian/ bullseye main

deb http://security.debian.org/debian-security bullseye-security main 
contrib
deb-src http://security.debian.org/debian-security bullseye-security 
main contrib

-


--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/
--- End Message ---
--- Begin Message ---
Hi,

"Andrew M.A. Cater"  wrote (Thu, 20 May 2021 18:32:00 
+):
> On Thu, May 20, 2021 at 10:59:37AM +0200, Paul van der Vlis wrote:
> > Op 19-05-2021 om 20:06 schreef Cyril Brulebois:
> > > I think deactivating cdrom entries was implemented several release
> > > cycles ago. That should be the case for both buster and bullseye at the
> > > minimum (if memory serves).
> > > 
> > > Please share your /var/log/installer/syslog (compressed, due to bugs.d.o
> > > and/or lists.d.o size limits) so that we can check what happens there?
> > 
> > Attached the installer-syslog (attached) of another machine. This is
> > *always* the case with the DVD-version of the installer (not with the
> > netinstaller!).

Looking at finish-install.d/10apt-cdrom-setup in apt-setup, I see that
disabling cdrom entries is only intended for netinst, live images and
single-desktop CD image.
This is conform with the following citation from Steve:

> 
> >From a conversation with Steve McIntyre a while back: 
> 
> The netinst doesn't expect that you'll use any other medium other than
> the 'Net to continue to install.
> 
> The DVD could be used in a standalone mode with no network access: in that
> case a deb cdrom entry is useful (though latterly you get warning messages
> about apt-secure when you try ot use it).
> 
> The deb cdrom entry is deliberate, I think - though it should probably 
> come commented out.
> 
> > I am a "Debian pre install vendor" and I also sell USB-sticks with Debian,
> > so I have seen this really often.
> > 
> > With regards,
> > Paul

Anyway, having the cdrom entry active does not cause real harm, right?
If the user said Yes to the use of a network mirror during installation, he
gets the sources.list entry for that mirror, and if the mirror has later
package versions than the DVD, the version from mirror is used.

If the user does not want (or cannot) use a mirror, the active cdrom entry
is good to have any working entry at all.

So I guess it's intended as it is now.


I'm therefore closing this bug.

Holger




PS: I found in finish-install.d/10apt-cdrom-setup that disabling cdrom
entries can be preseeded. However, this is not documented in the
installation-guide appendix preseed. 
I will add it there shortly.


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

Re: Bug#988797: RC1 installation report

[Holger Wansing]

Hi,

"Andrew M.A. Cater"  wrote (Thu, 20 May 2021 18:32:00 
+):
> On Thu, May 20, 2021 at 10:59:37AM +0200, Paul van der Vlis wrote:
> > Op 19-05-2021 om 20:06 schreef Cyril Brulebois:
> > > I think deactivating cdrom entries was implemented several release
> > > cycles ago. That should be the case for both buster and bullseye at the
> > > minimum (if memory serves).
> > > 
> > > Please share your /var/log/installer/syslog (compressed, due to bugs.d.o
> > > and/or lists.d.o size limits) so that we can check what happens there?
> > 
> > Attached the installer-syslog (attached) of another machine. This is
> > *always* the case with the DVD-version of the installer (not with the
> > netinstaller!).

Looking at finish-install.d/10apt-cdrom-setup in apt-setup, I see that
disabling cdrom entries is only intended for netinst, live images and
single-desktop CD image.
This is conform with the following citation from Steve:

> 
> >From a conversation with Steve McIntyre a while back: 
> 
> The netinst doesn't expect that you'll use any other medium other than
> the 'Net to continue to install.
> 
> The DVD could be used in a standalone mode with no network access: in that
> case a deb cdrom entry is useful (though latterly you get warning messages
> about apt-secure when you try ot use it).
> 
> The deb cdrom entry is deliberate, I think - though it should probably 
> come commented out.
> 
> > I am a "Debian pre install vendor" and I also sell USB-sticks with Debian,
> > so I have seen this really often.
> > 
> > With regards,
> > Paul

Anyway, having the cdrom entry active does not cause real harm, right?
If the user said Yes to the use of a network mirror during installation, he
gets the sources.list entry for that mirror, and if the mirror has later
package versions than the DVD, the version from mirror is used.

If the user does not want (or cannot) use a mirror, the active cdrom entry
is good to have any working entry at all.

So I guess it's intended as it is now.


I'm therefore closing this bug.

Holger




PS: I found in finish-install.d/10apt-cdrom-setup that disabling cdrom
entries can be preseeded. However, this is not documented in the
installation-guide appendix preseed. 
I will add it there shortly.


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

Bug#989300: marked as done (Bullseye installation report)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jan 2022 12:41:40 +0100
with message-id <20220116124140.628d7a55b6a1101100458...@mailbox.org>
and subject line Re: #989300 Bullseye installation report
has caused the Debian Bug report #989300,
regarding Bullseye installation report
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.)


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

Boot method: USB stick/Netinst
Image version: Installer RC1
Date: 2021-05-30 20:00

Machine: ASUS Z590M-P motherboard
Processor: Intel i5-11400
Memory:16GB
Partitions:
Filesystem Type  1K-blocks    Used  Available Use% Mounted on
udev   devtmpfs    8053756   0    8053756   0% /dev
tmpfs  tmpfs   1615332    1360    1613972   1% /run
/dev/nvme0n1p2 ext4  958802032 3434596  906589248   1% /
tmpfs  tmpfs   8076648   0    8076648   0% /dev/shm
tmpfs  tmpfs  5120   4   5116   1% /run/lock
/dev/nvme0n1p1 vfat 523248    3484 519764   1% /boot/efi
/dev/sda1  ext4 7751357596  32 7360639920   1% /mnt/red1
tmpfs  tmpfs   1615328  40    1615288   1% /run/user/0
tmpfs  tmpfs   1615328  32    1615296   1% /run/user/1000



Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4c53] (rev 01)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4c8b] 
(rev 04)
    DeviceName: Onboard - Video
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
    Kernel modules: i915
00:06.0 PCI bridge [0604]: Intel Corporation Device [8086:4c09] (rev 01)
    Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:43ed] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
    Kernel driver in use: xhci_hcd
    Kernel modules: xhci_pci
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:43ef] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:43e8] (rev 
11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
    Kernel driver in use: intel-lpss
    Kernel modules: intel_lpss_pci
00:15.1 Serial bus controller [0c80]: Intel Corporation Device [8086:43e9] (rev 
11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
    Kernel driver in use: intel-lpss
    Kernel modules: intel_lpss_pci
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:43e0] 
(rev 11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
    Kernel driver in use: mei_me
    Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] (rev 11)
    DeviceName: Onboard - SATA
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
    Kernel driver in use: ahci
    Kernel modules: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:43c0] (rev 11)
    Kernel driver in use: pcieport
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:43b8] (rev 11)
    Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:43b0] (rev 11)
    Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:4385] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:43c8] (rev 11)
    DeviceName: Onboard - Sound
    Subsystem: ASUSTeK Computer Inc. Device [1043:87fb]
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel, snd_sof_pci
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:43a3] (rev 11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
    Kernel driver in use: i801_smbus
    Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:43a4] (rev 
11)
    DeviceName: Onboard - Other
    Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (14) 
I219-V [8086:15fa] (

Re: #989300 Bullseye installation report

[Holger Wansing]

> Initial boot:   [O]
> Detect network card:[E]
> Configure network:  [E]
> 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:
> Motherboard built-in NIC (Intel i219) not recognised. Installer prompted to 
> pick a driver however no i219 driver was listed. I tried some of the listed 
> Intel drivers without success. I had to install a Realtek NIC into a PCIe 
> slot in order to install. Used text-mode install. Removed Realtek NIC after 
> installation.
> 
>and ideas you had during the initial install.>
> Minor point: Installer (tasksel) defaults to Gnome desktop so the first time 
> I tried I accidentally installed Gnome. Reinstalled and remembered to 
> deselect Gnome and select my usual desktop (mate). Previous installers didn't 
> default, except to the first entry (debian desktop).
> 
> Post install and video is stuck at 1024x768 with unknown monitor listed. I'm 
> guessing Rocket Lake iGPUs aren't supported yet.


The missing support for Intel i219 and the Rocket lake iGPU is only a matter
of time. You could try a recent development image, to see if it already works
there.
Since this is not an installation issue per-se, I'm closing this bug.


Thanks for reporting anyway

Holger





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

Bug#582367: marked as done (installation-report: Unable to install grub-pc on LVM/RAID5)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #292513,
regarding installation-report: Unable to install grub-pc on LVM/RAID5
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.)


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


Boot method: CD
Image version: Daily amd64 of 16 May 2010
Date: 16 May 2010

Machine: Standard PC
Partitions:

/dev/hda1 - RAID
/dev/hdb1 - RAID
/dev/hdc1 - RAID

/dev/md0 - RAID 5 with 3 partitions above, ext3 mounted on /


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:[E]
Overall install:[ ]

Comments/Problems:

Unable to install grub-pc.

-- 
Julien Danjou
// ᐰhttp://julien.danjou.info


pgpfXUc6A7fKf.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,

similar to the installation-reports bugs, I'm closing the grub-installer 
reports 
below.

These are reports for Debian 4 / 6 / 7 / 9 where grub-installer fails (for 
various reasons).


There have been numerous changes/improvements on this topics in the past, and 
also because of the age of the reports we should consider these problems as 
being fixed (or it is even reported in the bugs that they are fixed).
They are most likely of no use anymore for recent releases.

If you know, that the issue you reported (and gets closed here) is still 
existing in recent installation images, please file a new report for that with 
up-to-date details!

Thank you for filing these bug reports, they have been very useful at the time 
they were filed!


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785149
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489005
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610116
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611713
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612420
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621923
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647267
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659116
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665856
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666552
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668923
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686955
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690515
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690592
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702731
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729411
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771467
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780115
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806164
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806849
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416986
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252009
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292513
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310798
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489006
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578338
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582367
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=229128
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463842
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497168
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500079
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516392
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520361
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544949
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549703
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557242
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580461
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587699
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588670
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596877
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612025
https://bugs.debi

Bug#982835: installation-report: doesn't set needed rootflags for flash-kernel when btrfs is used as rootfs

[Vagrant Cascadian]

On 2021-10-02, Vagrant Cascadian wrote:
> On 2021-02-15, Vieno Hakkerinen wrote:
>> I created a ext2 for /boot and luks+lvm+btrfs for /. As d-i defaults
>> to use a @rootfs subvolume for btrfs the linux bootargs need to have
>> set "rootflags=subvol=@rootfs". This was not set during configuration
>> of flash-kernel. Without this argument debian failed to boot with an
>> error that no init was found.
>
>>* What outcome did you expect instead?
>>
>> debian-installer should set "rootflags=subvol=@rootfs" in 
>> /etc/default/flash-kernel when btrfs is used for /
>
>>* What did you do to solve the problem?
>>
>> 1. I ran "setenv bootargs rootflags=subvol=@rootfs" in u-boot
>> 2. I ran "boot" in u-boot
>> 3. debian found init successfully
>> 4. I added "rootflags=subvol=@rootfs" to LINUX_KERNEL_CMDLINE_DEFAULTS in 
>> /etc/default/flash-kernel
>> 5. I ran flash-kernel
>> 6. I rebooted
>> 7. debian booted successfully
>
> So, flash-kernel-installer has a debconf question that might be useable
> for this purpose:
>
> flash-kernel-installer.postinst.in:echo flash-kernel 
> flash-kernel/linux_cmdline string $kopt_params | \
> flash-kernel-installer.postinst.in- chroot /target debconf-set-selections
>
> I'm curious how other systems handle btrfs (e.g. grub on amd64); are
> there any configuration options passed via debian-installer to set
> "rootflags=subvol=@rootfs", or does grub have any configuration that are
> set from update-grub or whatever ... or autodetected when rootfs is on
> btrfs?

To answer my own question, looks like it's autodetected in
/etc/grub.d/10_linux:

case x"$GRUB_FS" in
xbtrfs)
rootsubvol="`make_system_path_relative_to_its_root /`"
rootsubvol="${rootsubvol#/}"
if [ "x${rootsubvol}" != x ]; then
GRUB_CMDLINE_LINUX="rootflags=subvol=${rootsubvol}
${GRUB_CMDLINE_LINUX}"
fi;;


I suspect the way to handle this would be to have flash-kernel-installer
do something similar and pass it into the debconf option ... unless
someone can find a sane place to put that into flash-kernel at
run-time...

It might be easier to adapt other code, such as u-boot-menu and install
u-boot-menu instead of, or in addition to, flash-kernel... or at least,
that would be another case where this could be supported.


live well,
  vagrant




signature.asc
Description: PGP signature

Bug#982835: installation-report: doesn't set needed rootflags for flash-kernel when btrfs is used as rootfs

[Vagrant Cascadian]

On 2021-02-15, Vieno Hakkerinen wrote:
> I created a ext2 for /boot and luks+lvm+btrfs for /. As d-i defaults
> to use a @rootfs subvolume for btrfs the linux bootargs need to have
> set "rootflags=subvol=@rootfs". This was not set during configuration
> of flash-kernel. Without this argument debian failed to boot with an
> error that no init was found.

>* What outcome did you expect instead?
>
> debian-installer should set "rootflags=subvol=@rootfs" in 
> /etc/default/flash-kernel when btrfs is used for /

>* What did you do to solve the problem?
>
> 1. I ran "setenv bootargs rootflags=subvol=@rootfs" in u-boot
> 2. I ran "boot" in u-boot
> 3. debian found init successfully
> 4. I added "rootflags=subvol=@rootfs" to LINUX_KERNEL_CMDLINE_DEFAULTS in 
> /etc/default/flash-kernel
> 5. I ran flash-kernel
> 6. I rebooted
> 7. debian booted successfully

So, flash-kernel-installer has a debconf question that might be useable
for this purpose:

flash-kernel-installer.postinst.in:echo flash-kernel flash-kernel/linux_cmdline 
string $kopt_params | \
flash-kernel-installer.postinst.in- chroot /target debconf-set-selections

I'm curious how other systems handle btrfs (e.g. grub on amd64); are
there any configuration options passed via debian-installer to set
"rootflags=subvol=@rootfs", or does grub have any configuration that are
set from update-grub or whatever ... or autodetected when rootfs is on
btrfs?


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#960988: installation-report: Installation report for HP Pavillion X360 14-cd0004la

[Holger Wansing]

Hi,

Gunnar Wolf  wrote (Tue, 19 May 2020 00:33:32 -0500):
> The Buster installer could not find my wireless card (RTL 8821CE).
> 
> I performed the install using a spare external wireless interface; after
> booting to the installed system, I found an unofficial module supporting
> this hardware at:
> 
> https://github.com/tomaspinho/rtl8821ce

Maybe you could give it a try with a current Bullseye installer?


Holger



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

Bug#991899: marked as done (RC3 installation report)

[Debian Bug Tracking System]

Your message dated Sun, 29 Aug 2021 21:12:05 +0200
with message-id <20210829211205.5cf88e58c35cf70db3aa7...@mailbox.org>
and subject line Closing successful installation-reports bugs
has caused the Debian Bug report #991899,
regarding RC3 installation report
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.)


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

Boot method: 
Date: Tuesday Aug 3 3:30 PM

Machine: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03)
Subsystem: Gigabyte Technology Co., Ltd GA-EP45-DS5/GA-EG45M-DS2H Motherboard 
[1458:5000]
Processor: Intel(R) Core(TM)2 Quad CPUQ6700  @ 2.66GHz
Memory: 4GB
Partitions: 
--- End Message ---
--- Begin Message ---
Hi,

I'm closing this reports of successful installations.
They have been very useful at the time of writing.

Thanks to all reporters!


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

Bug#962802: marked as done (Installation Report)

[Debian Bug Tracking System]

Your message dated Sun, 29 Aug 2021 21:11:06 +0200
with message-id <20210829211106.6e971be92f233e38a28ea...@mailbox.org>
and subject line Closing installation-reports bugs without further information
has caused the Debian Bug report #962802,
regarding Installation Report
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.)


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

Boot method: USB
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-xfce-CD-1.iso
Date: 2020-06-14

Machine: Lenovo Yoga S730
Processor: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
Memory: 16GB
Partitions: 
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev   devtmpfs   80312240   8031224   0% /dev
tmpfs  tmpfs  1617052 1476   1615576   1% /run
/dev/nvme0n1p5 ext4  47797996  4501564  40838680  10% /
tmpfs  tmpfs  8085244   102396   7982848   2% /dev/shm
tmpfs  tmpfs 51204  5116   1% /run/lock
tmpfs  tmpfs  80852440   8085244   0% /sys/fs/cgroup
/dev/nvme0n1p1 vfat26214442100220044  17% /boot/efi
/dev/nvme0n1p7 ext4 342852932 15011212 310356052   5% /home
tmpfs  tmpfs  1617048   16   1617032   1% /run/user/1000

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c)
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 
[8086:9b41] (rev 02)
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 0c)
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
00:12.0 Signal processing controller [1180]: Intel Corporation Comet Lake 
Thermal Subsytem [8086:02f9]
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:02ed]
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:02ef]
00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host 
Controller [8086:02e8]
00:16.0 Communication controller [0780]: Intel Corporation Comet Lake 
Management Engine Interface [8086:02e0]
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:02b8] (rev f0)
00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:02bc] (rev f0)
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:02b0] (rev f0)
00:1d.1 PCI bridge [0604]: Intel Corporation Device [8086:02b1] (rev f0)
00:1d.4 PCI bridge [0604]: Intel Corporation Device [8086:02b4] (rev f0)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:0284]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:02c8]
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3]
00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) 
Controller [8086:02a4]
6c:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822CE 
802.11ac PCIe Wireless Network Adapter [10ec:c822]
6d:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe 
SSD Controller SM981/PM981/PM983 [144d:a808]

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

Initial boot:   [O]
Detect network card:[E]
Configure network:  [O]
Detect CD:  [ ]
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:

The laptop uses the relatively new Realtek 8822CE card, which the 
firmware-realtek package doesn't include yet. Running `dmesg | grep network` 
contained an error about the rtw_pci module not being able to find the driver 
(I didn't record the precise error).

I was able to get the WiFi working in the installer by downloading the latest 
linux-firmware tarball[1] from git.kernel.org, and replacing the files in 
/lib/firmware/rtw88 in a shell.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz
--- End Message ---
--- Begin Message ---
I'm closing these bugs, since they are lacking further information from the
reporters, to help for more detailed diagnosis.
Thus it's unlikely to gain some more benefit from them.


-- 
Holger Wansin

Bug#961089: marked as done (installation-report bullseye alpha2)

[Debian Bug Tracking System]

Your message dated Sun, 29 Aug 2021 21:11:06 +0200
with message-id <20210829211106.6e971be92f233e38a28ea...@mailbox.org>
and subject line Closing installation-reports bugs without further information
has caused the Debian Bug report #961089,
regarding installation-report bullseye alpha2
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.)


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

Package: installation-reports

Boot method:   Network
Image version:   
debian-bullseye-DI-alpha2-amd64-netinst.iso
Date:   05-11-2020

Machine:   VirtualBox 6.1
Processor: i7-3770 @ 3.4GHz
Memory: 2048 MB
Partitions:   lsblk

NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda  8:00   8G  0 disk
├─sda1   8:10   6G  0 part /
├─sda2   8:20   1K  0 part
└─sda5   8:50   2G  0 part [SWAP]
sr0 11:01  57M  0 rom

Output of lspci -knn (or lspci -nn):  lspci -knn   after installing VirtualBox 
Guest Additions in attempt to get clipboard to work

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 82371AB/EB/MB PIIX4 IDE 
[8086:7111] (rev 01)
Kernel driver in use: ata_piix
Kernel modules: ata_piix, ata_generic
00:02.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405]
Subsystem: VMware SVGA II Adapter [15ad:0405]
Kernel driver in use: vmwgfx
Kernel modules: vmwgfx
00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet 
Controller [8086:100e] (rev 02)
Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter [8086:001e]
Kernel driver in use: e1000
Kernel modules: e1000
00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest 
Service [80ee:cafe]
Kernel driver in use: vboxguest
Kernel modules: vboxguest
00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 
Audio Controller [8086:2415] (rev 01)
Subsystem: Dell 82801AA AC'97 Audio Controller [1028:0177]
Kernel driver in use: snd_intel8x0
Kernel modules: snd_intel8x0
00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f]
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] 
(rev 08)
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4
00:0b.0 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB2 EHCI Controller [8086:265c]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) 
SATA Controller [AHCI mode] [8086:2829] (rev 02)
Kernel driver in use: ahci
Kernel modules: ahci

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:[O]

Comments/Problems:



INSTALLATION - PROBLEM WITH UNKNOWN CAUSE: The first three times I tried to 
install bullseye alpha2, I was interrupted during
the installation process to respond to someone. When I came back, there was an 
installation failure message. The fourth time,
I stayed with the installation and the install was successful without a 
problem. I do not know at what point the install was
interrupted but I know that it was after setting user name and password. I 
tried to cause an unsuccessful install by not
responding at points in the process, but couldn't.

--- End Message ---
--- Begin Message ---
I'm closing these bugs, since they are lacking further information from the
reporters, to help for more detailed diagnosis.
Thus it's unlikely to gain some more benefit from them.


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

Bug#963755: marked as done (installation-report: fails to boot with Gnome DE)

[Debian Bug Tracking System]

Your message dated Sun, 29 Aug 2021 21:09:59 +0200
with message-id <20210829210959.f3d5b403cce267ff9e69d...@mailbox.org>
and subject line Closing bugreports related to missing/not installed firmware
has caused the Debian Bug report #963755,
regarding installation-report: fails to boot with Gnome DE
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.)


-- 
963755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Version: 2.71
Severity: grave
Justification: renders package unusable

Dear Maintainer,


   * What led up to the situation?
Booting the debian after installation, hangs at loading Gnome DE.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? 
Launched rescue mode, verified partition table and launched
interractive shell to verify logs.
   * What was the outcome of this action?
Partition table is as expected, shell works as expected, logs
indicate no obvious error.
   * What outcome did you expect instead?
Expected Debian to boot directly.



-- Package-specific info:

Boot method: USB floppy disc
Image version: 64-bit PC netinst iso, downloaded 2020/06/23, 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.4.0-amd64-netinst.iso
Date: 

Machine: GameMax desktop
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 CD:  [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:[E]

Comments/Problems:
The boot loader installed properly, detected the other OS present
(Windows 10) but failed to write the boot table correctly so that
only debian appears there.
Launching debian hangs after loading the Gnome DE in normal mode, recovery mode 
works fine.


-- 

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/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u4"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux GM-Debian 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) 
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: Subsystem: Intel Corporation Device [8086:2017]
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: Kernel driver in use: pcieport
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V 
Gigabit Network Connection [8086:1503] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
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 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -k

Bug#992774: installation-report

[lucas]

Hi Cyril,

Appreciate the swift response, hopefully the raspi team can help.

> You didn't need any extra DTB to get your CM4 to boot?

No other steps were needed just wrote the image to the eMMC with balena and 
plugged it in.

Thanks again,
Lucas


From: Cyril Brulebois
Sent: Monday, August 23, 2021 06:00
To: lucas; 992...@bugs.debian.org
Cc: pkg-raspi-maintain...@alioth-lists.debian.net
Subject: Re: Bug#992774: installation-report

Hi,

lucas  (2021-08-23):
> Installation was successful except for disabled usb port.

Thanks for your report. FWIW we deal with installations that were
performed using the Debian Installer; I'm putting the maintainers of the
relevant Raspberry Pi tooling in copy.

> Documentation for hardware (Raspi Compute Module 4) states usb ports
> disabled by default and provides a method to enable them at boot with
> raspian config.txt. The same method does not work with this Debian
> image.

You didn't need any extra DTB to get your CM4 to boot? Or did you skip
mentioning extra steps regarding the deployment of the raspi.debian.net
provided image?


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

Bug#992774: installation-report

[Cyril Brulebois]

Hi,

lucas  (2021-08-23):
> Installation was successful except for disabled usb port.

Thanks for your report. FWIW we deal with installations that were
performed using the Debian Installer; I'm putting the maintainers of the
relevant Raspberry Pi tooling in copy.

> Documentation for hardware (Raspi Compute Module 4) states usb ports
> disabled by default and provides a method to enable them at boot with
> raspian config.txt. The same method does not work with this Debian
> image.

You didn't need any extra DTB to get your CM4 to boot? Or did you skip
mentioning extra steps regarding the deployment of the raspi.debian.net
provided image?


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


signature.asc
Description: PGP signature

Bug#992774: installation-report

[lucas]

Package: installation-reports



Boot method: Flashing eMMC

Image version: 
https://raspi.debian.net/verified/20210718_raspi_4_bullseye.img.xz

Date: 20-08-2021, 15:08

Machine: Raspberry Pi Compute Module 4 IO Board

Processor: Broadcom BCM2711 quad-core Cortex-A72 (ARM v8) 64-bit SoC

Memory: 8GB SDRAM

Partitions: not possible



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



Base System Installation Checklist:

[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it



Initial boot:   [ ]

Detect network card:[ ]

Configure network:  [ ]

Detect media:   [ ]

Load installer modules: [ ]

Detect hard drives: [ ]

Partition hard drives:  [ ]

Install base system:[ ]

Clock/timezone setup:   [ ]

User/password setup:[ ]

Install tasks:  [ ]

Install boot loader:[ ]

Overall install:[ ]



Comments/Problems:

Installation was successful except for disabled usb port. Documentation for 
hardware (Raspi Compute Module 4) states usb ports disabled

 by default and provides a method to enable them at boot with raspian 
config.txt . The same method does not work with this Debian image.

Bug#991899: RC3 installation report

[Dont Reply]

Package: installation-reports

Boot method: 
Date: Tuesday Aug 3 3:30 PM

Machine: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03)
Subsystem: Gigabyte Technology Co., Ltd GA-EP45-DS5/GA-EG45M-DS2H Motherboard 
[1458:5000]
Processor: Intel(R) Core(TM)2 Quad CPUQ6700  @ 2.66GHz
Memory: 4GB
Partitions: 

Bug#990517: installation-reports: Installation report (problems)

[Filippo Rusconi]

Package: installation-reports
Severity: normal

See attached file.

Thank you for your hard work on Debian !


Filippo

Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210606"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux roma 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) 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:1918] 
(rev 07)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD 
Graphics P530 [8086:191d] (rev 06)
lspci -knn: DeviceName: Onboard IGD
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
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 
07)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
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: Hewlett-Packard Company Device [103c:80d4]
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 100 
Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: 00:15.0 Signal processing controller [1180]: Intel Corporation 100 
Series/C230 Series Chipset Family Serial IO I2C Controller #0 [8086:a160] (rev 
31)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
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: Hewlett-Packard Company Device [103c:80d4]
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: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series 
Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series 
Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series 
Chipset Family PCI Express Root Port #2 [8086:a111] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series 
Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series 
Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation CM236 Chipset LPC/eSPI 
Controller [8086:a150] (rev 31)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 
Series Chipset Family Power Management Controller [8086:a121] (rev 31)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 
Series Chipset Family HD Audio Controller [8086:a170] (rev 31)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series 
Chipset Family SMBus [8086:a123] (rev 31)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection (2) I219-LM [8086:15b7] (rev 31)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:80d4]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel 

Bug#990112: installation-report: 10.10.0-amd64-DVD-1 booted in Xen PV mode

[Lionel Elie Mamane]

Package: installation-reports
Version: 2.71
Severity: normal

(report done from another macn

-- Package-specific info:

Boot method: DVD (Xen PV mode)
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-10.10.0-amd64-DVD-1.iso.torrent
 2021-06-19 19:20
Date: 2021-06-20 evening

Machine: Xen PV DomU


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:  [E]
Load installer modules: [E]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [E]
Install boot loader:[E]
Overall install:[E]

Comments/Problems:


Problem 1: The CD is not recognised as a valid source of package, and
thus grub installation fails; my assumption is that it requires
grub-common from the CD but doesn't have it.

So I loaded the extra installer module pppoe in order to get an
Internet connection and use a network mirror to get packages. That
failed to work, because the pppoe kernel module failed to load, which
is:

Problem 2: the ppoe installer module needs "depmod" but doesn't run it

"depmod" run from the shell fixed that.

Then I selected a network mirror, namely http / Luxembourg / deb.debian.org

Problem 3: the selected network mirror is not used.

I ended up going to the shell again, chrooting into /target, editing
/etc/sources.lst with nano to put the requested deb.debian.org mirror
source, and after "apt-get update && apt-get install grub-xen" the
installer finished correctly. Note also that the "security updates"
and "updates" lines in source.list were commented out "because they
failed to validate".

"Install tasks" worked OK, but the only task available was "basic
system utilities" or something like that, again that's because nothing
in sources.list, not the CD and not the network mirror.

Bug#989987: installation-report Bullseye rc2

[Oliver Psotta]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Cyril,

you are welcome.

On Thu, 17 Jun 2021 15:23:02 +0200
Cyril Brulebois  wrote:

> Hallo Oliver,
> 
> And thanks for your report.
> 
> Oliver Psotta  (2021-06-17):
> > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> > 
> > Initial boot:   [O ]
> > Detect network card:[E ]
> > Configure network:  [O ]
> > Detect media:   [E ]
> > Load installer modules: [E ]
> > 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: Graphical Install did not find ethernet, because
> > laptop is not equipped with it. But it did not try to search for
> > wireless. Instead I was able to choose my wireless Realtek chip in
> > ethernet window.  
> 
> I do have some laptops around that I'm testing firmware-related issues
> with, and I think I've noticed this (to be confirmed):
>  - on a laptop without wired Ethernet, I'm getting a prompt for the
>wireless card and its firmware.
>  - when booting it with a USB→Ethernet adapter, I'm getting a prompt
> for the (possibly missing but actually unimportant) firmware for the
>USB→Ethernet adapter, but no mention of the wireless card or
> missing firmware.

If you want I can send you a screenshot of the Ethernet screen, where I
can select WIFI drivers.
When I plugged in the USB-Ethernet adapter, I will not be asked
anything. Installation then automatically configures network, IP, time
and so on.
> 
> > It could not activate the supplied driver from 2nd USB drive.
> > Mounting of 2nd USB drive was unreliable. Installation worked well
> > after using USB-Ethernet adapter.  
> 
> OK, that part I'm not familiar with, and I cannot really comment.
> 
> You could have used one of the unofficial/non-free images that come
> with all firmware packages:
>   
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
> 
Good to know, thank you. I will use it for the next installation.

> > Installation process of install via ethernet worked well. Gnome
> > desktop not useable on built in screen because resolution and
> > brightness not changeable, no sound, no BT.  
> 
> Alright, I'm currently chasing that kind of issues. You can double
> check you're using a software-based rendering by installing the
> mesa-utils package, running `glxinfo | grep renderer` should give you
> llvmpipe.
> 
> Wild guess, you're lacking:
>  - firmware-iwlwifi for bluetooth support (I do have a realtek
> wireless card here, but the kernel complains about files that are
> shipped in that package instead).
>  - firmware-amd-graphics for proper display support.
>  - firmware-sof-signed for sound support.
> 
> All those wouldn't have been solved by using the firmware-enabled
> images because we're currently lacking some detection, but I'm
> working on this.
> 
> For users of official installation images (main-only), I'm wondering
> whether to advertise something like this in the installation guide:
> 
> sudo apt install isenkram-cli
> sudo isenkram-autoinstall-firmware
> sudo reboot
> 
> Please note that due to #989884, one should install isenkram-cli from
> unstable to make sure the firmware file to firmware package lookup
> works.
> 
> More on such issues on #989863 and follow-up bug reports when I get a
> chance to sum up my findings.
> 
The situation right now is:
- - Screen resolution, brightness controls and sound are working.
  Probably because of the AMD firmware I've installed. Also the laptop
  is not getting warm anymore.
- - BT is working with the non-free Realtek firmware. WiFi chip cannot be
  activated because of the known bug: "rtw88 / rtl_8821ce: rfe 2 is not
supported". This bug is fixed on Ubuntu, but the range of WiFi is only
2 meters (also known). On Ubuntu there's a proprietary driver for this
which works well. I'm not sure if it is possible to install that on
Bullseye.
- - Suspend is not working, also known bug. I was reading somewhere that
  will be fixed in the next main linux kernel.
- - Now my renderer is GLX_MESA_query_renderer and for OpenGL it's AMD
  Renoir.
> 
> Tschüss,
Tschüss,
Oliver
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsG582PEz+8y62k/U1tubkH9v9PMFAmDLdpEACgkQ1tubkH9v
9PP4Jw/+KBmCXqtJLFVm1LF8AA92WYju+Hb3o1alr0Xm++DrkR24LY5mvAL9Le6A
T9WekudaSMZPp73TBHa2l4UxA1hmHabgQ7b6BeyKEaADLvIWyqlZbcKs8oMCZYKD
vaut0VPi0ylNKYt/U6LL2axwO9JMdiI1Hu4XFDvtNNDhP2fi4mo6yy5v6VYO/87u
Kl5fRcsqKVIWZ9cGtN7/pT22P0WVApBYmilbG3i4pzLLHyhGJLSNfQY+3O96rn4E
cccX7oU8iBzmWxa5jXzPIzSikyOkWJtqD6yPiUQz+m1x4P//zh+/yspmjtsuiSyn
Yq9Q+D+EpKKf8GeyccLyPXERZOtOZV8gsAIiB6mEIF62MzcbHCHCerofdG2T+xd8
7D152I6UUk+5xCmf320vVEvOT8NaDsjJIUB28WnA/+amf8eMjL7AOumEIa0MPAEM
XxAQAwaNDBfxxOKhl8wCIfBnNDGE7W5T06a85W5ltK1uyebmdVvgQifTGK27+Ish

Bug#989987: installation-report Bullseye rc2

[Oliver Psotta]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

PS: I forgot to mention that Gnome forgets the settings of screen
brightness after restarts. Same bug with Ubuntu. I could file a bug
report. Could you point me to the package that is relevant here? Thanks!
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsG582PEz+8y62k/U1tubkH9v9PMFAmDLd94ACgkQ1tubkH9v
9PNqnBAAs2ttJNc0VxCoYz1ZVefa/7RzNWSYDQSZ+BM6AZppb8POeyTnYlUZYRjw
Qm2i3e3g1kzIVdIAUHJbT5triMJHMxDLIyh21b4h+6/vZ3qOmclXV3JVd0nlSgMA
OyzDYJjXAtiUgfuxhVa8XAtPUZMZbYtizXtqB754CpT1VLYUR399m0c41lc/aY1i
PfujsXtdR+ozjQ1jRyBl8S0oVzQUEU12gdhNn7uNUMv4JzcNnApiAy6B849JWv/3
CziWIBkxeZK7Puw5ADjLsk7PlsERrf53jeMbLN8VKhXcb39H/wtMCEzZBWwPgV+d
nlv8So6qty/HVLrK0BOFDSXrCTxVoQH31BGyxdRHRQ0IpZAUJ1L0K78jSTc8SgVG
zoBqYX1jLmLY1qrQHy3rBIuzBfmsbHedvs3tAgn/U19lmSN6UR+ADnI4eWn0Adv0
cm3SiCAuyhA2Ze4naFR2iEDzX4sn+LWSAnkjJ7XYLybi2cXPZQlttgUFFELFMkQw
nF7BmK1UaEo5d+qNv4sXdJtYHWYYfKcjlNSTDB9pBzpzuH4V0Wr1TX+Z3a9IcCPd
a1F4vjNQBySwHkgSN0756yGaJpsNAQHnJSEXculGErJkMLzMaTooLgbTJfhWppuG
z4udK2sA5FSTR93KOypAGxWbvnqfztC/O1GNDtpvMAlGljQwC/w=
=8pzZ
-END PGP SIGNATURE-

Bug#989987: installation-report Bullseye rc2

[Cyril Brulebois]

Hallo Oliver,

And thanks for your report.

Oliver Psotta  (2021-06-17):
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [O ]
> Detect network card:[E ]
> Configure network:  [O ]
> Detect media:   [E ]
> Load installer modules: [E ]
> 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: Graphical Install did not find ethernet, because
> laptop is not equipped with it. But it did not try to search for
> wireless. Instead I was able to choose my wireless Realtek chip in
> ethernet window.

I do have some laptops around that I'm testing firmware-related issues
with, and I think I've noticed this (to be confirmed):
 - on a laptop without wired Ethernet, I'm getting a prompt for the
   wireless card and its firmware.
 - when booting it with a USB→Ethernet adapter, I'm getting a prompt for
   the (possibly missing but actually unimportant) firmware for the
   USB→Ethernet adapter, but no mention of the wireless card or missing
   firmware.

> It could not activate the supplied driver from 2nd USB drive. Mounting
> of 2nd USB drive was unreliable. Installation worked well after using
> USB-Ethernet adapter.

OK, that part I'm not familiar with, and I cannot really comment.

You could have used one of the unofficial/non-free images that come with
all firmware packages:
  https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

> Installation process of install via ethernet worked well. Gnome
> desktop not useable on built in screen because resolution and
> brightness not changeable, no sound, no BT.

Alright, I'm currently chasing that kind of issues. You can double check
you're using a software-based rendering by installing the mesa-utils
package, running `glxinfo | grep renderer` should give you llvmpipe.

Wild guess, you're lacking:
 - firmware-iwlwifi for bluetooth support (I do have a realtek wireless
   card here, but the kernel complains about files that are shipped in
   that package instead).
 - firmware-amd-graphics for proper display support.
 - firmware-sof-signed for sound support.

All those wouldn't have been solved by using the firmware-enabled images
because we're currently lacking some detection, but I'm working on this.

For users of official installation images (main-only), I'm wondering
whether to advertise something like this in the installation guide:

sudo apt install isenkram-cli
sudo isenkram-autoinstall-firmware
sudo reboot

Please note that due to #989884, one should install isenkram-cli from
unstable to make sure the firmware file to firmware package lookup
works.

More on such issues on #989863 and follow-up bug reports when I get a
chance to sum up my findings.


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


signature.asc
Description: PGP signature

Bug#989987: installation-report Bullseye rc2

[Oliver Psotta]

Package: installation-reports

Severity: normal

(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/bullseye_di_rc2/amd64/iso-cd/debian-bullseye-DI-rc2-amd64-netinst.iso
Date: June 16 2021, 22:00

Machine: HP Pavilion Laptop 15-eh1557ng
Partitions: 
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev   devtmpfs   78330720   7833072   0% /dev
tmpfs  tmpfs  1577796 1704   1576092   1% /run
/dev/nvme0n1p5 ext4 199490896  4304316 184980220   3% /
tmpfs  tmpfs  788897263320   7825652   1% /dev/shm
tmpfs  tmpfs 51204  5116   1% /run/lock
/dev/nvme0n1p1 vfat26214472160189984  28% /boot/efi
tmpfs  tmpfs  1577792  152   1577640   1% /run/user/1000



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

Initial boot:   [O ]
Detect network card:[E ]
Configure network:  [O ]
Detect media:   [E ]
Load installer modules: [E ]
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: Graphical Install did not find ethernet, because
laptop is not equipped with it. But it did not try to search for
wireless. Instead I was able to choose my wireless Realtek chip in
ethernet window. It could not activate the supplied driver from 2nd USB
drive. Mounting of 2nd USB drive was unreliable. Installation worked
well after using USB-Ethernet adapter.

Installation process of install via ethernet worked well. Gnome desktop
not useable on built in screen because resolution and brightness not
changeable, no sound, no BT.


Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210606"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux bullseye 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1
(2021-05-28) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]:
Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630]
lspci -knn: Subsystem: Hewlett-Packard Company Device
[103c:88d0] lspci -knn: 00:00.2 IOMMU [0806]: Advanced Micro Devices,
Inc. [AMD] Renoir IOMMU [1022:1631] lspci -knn: Subsystem:
Hewlett-Packard Company Device [103c:88d0] lspci -knn: 00:01.0 Host
bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy
Host Bridge [1022:1632] lspci -knn: 00:01.3 PCI bridge [0604]: Advanced
Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] lspci
-knn:   Kernel driver in use: pcieport lspci -knn: 00:02.0 Host
bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy
Host Bridge [1022:1632] lspci -knn: 00:02.2 PCI bridge [0604]: Advanced
Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] lspci
-knn:   Kernel driver in use: pcieport lspci -knn: 00:02.4 PCI
bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP
Bridge [1022:1634] lspci -knn:  Kernel driver in use: pcieport
lspci -knn: 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc.
[AMD] Renoir PCIe Dummy Host Bridge [1022:1632] lspci -knn: 00:08.1 PCI
bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe
GPP Bridge to Bus [1022:1635] lspci -knn:   Kernel driver in use:
pcieport lspci -knn: 00:08.2 PCI bridge [0604]: Advanced Micro Devices,
Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] lspci
-knn:   Kernel driver in use: pcieport lspci -knn: 00:14.0 SMBus
[0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
[1022:790b] (rev 51) lspci -knn:Subsystem: Advanced Micro
Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] lspci -knn:
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC
Bridge [1022:790e] (rev 51) lspci -knn: Subsystem: Advanced
Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] lspci -knn:
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir
Device 24: Function 0 [1022:1448] lspci -knn: 00:18.1 Host bridge
[0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1
[1022:1449] lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro
Devices, Inc. [AMD] Renoir Device 24: Function 2 [1022:144a] lspci
-knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD]
Renoir Device 24: 

Bug#989593: installation report Raspberry Pi 4 UEFI

[Marc Haber]

Hi Cyril,

thanks for the analysis.

On Thu, Jun 10, 2021 at 05:16:31PM +0200, Cyril Brulebois wrote:
> May 25 11:15:32 localechooser: info: System locale 
> (debian-installer/locale) = 'en_US.UTF-8'
> May 25 11:15:32 localechooser: info: Set debian-installer/language = 
> 'en_US:en'
> May 25 11:15:32 debconf: Setting debconf/language to en_US:en
> May 25 11:15:32 main-menu[261]: INFO: Falling back to the package 
> description for brltty-udeb
> May 25 11:15:32 main-menu[261]: INFO: Falling back to the package 
> description for brltty-udeb
> May 25 11:15:34 main-menu[261]: INFO: Falling back to the package 
> description for brltty-udeb
> May 25 11:15:34 main-menu[261]: INFO: Menu item 'console-setup-udeb' 
> selected
> May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
> accessible. Will not save cached keyboard map.
> May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
> accessible. Will not save cached keyboard map.
> May 25 11:15:37 main-menu[261]: (process:1290): ckbcomp-mini: 
> /usr/share/console-setup/pc105.ekmap.gz does not exist
> May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
> accessible. Will not save cached keyboard map.
> May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
> accessible. Will not save cached keyboard map.
> May 25 11:15:37 main-menu[261]: (process:1290): /bin/setupcon: line 722: 
> can't create /etc/console-setup/cached_setup_keyboard.sh: nonexistent 
> directory
> May 25 11:15:37 main-menu[261]: (process:1290): /bin/setupcon: line 730: 
> can't create /etc/console-setup/cached_setup_font.sh: nonexistent directory
> May 25 11:15:37 main-menu[261]: (process:1290): /bin/setupcon: line 748: 
> can't create /etc/console-setup/cached_setup_terminal.sh: nonexistent 
> directory
> May 25 11:15:37 main-menu[261]: (process:1290): chmod: 
> /etc/console-setup/cached_setup_keyboard.sh: No such file or directory
> May 25 11:15:37 main-menu[261]: (process:1290): chmod: 
> /etc/console-setup/cached_setup_font.sh: No such file or directory
> May 25 11:15:37 main-menu[261]: (process:1290): chmod: 
> /etc/console-setup/cached_setup_terminal.sh: No such file or directory
> May 25 11:15:37 main-menu[261]: (process:1290): ckbcomp-mini: 
> /usr/share/console-setup/pc105.ekmap.gz does not exist
> 
> and might explain why your keyboard settings don't work right after
> selecting the layout.

Where would the Installer look for gzip? I can check at this stage
whether gzip is there.

> This seems also strange (even if I must confess I've never grepped for
> s-s-d lines before):
> 
> Jun  9 16:20:40 base-installer: Using CD-ROM mount point /media/cdrom/
> Jun  9 16:20:40 base-installer: Identifying...
> Jun  9 16:20:40 base-installer: [27dc08d5c910ea7df2dee6e03e127e52-2]
> Jun  9 16:20:40 base-installer: Scanning disc for index files...
> Jun  9 16:20:41 base-installer: Found 1 package indexes, 0 source 
> indexes, 1 translation indexes and 0 signatures
> Jun  9 16:20:41 base-installer: Found label 'Debian GNU/Linux testing 
> _Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56'
> Jun  9 16:20:41 base-installer: This disc is called:
> Jun  9 16:20:41 base-installer: 'Debian GNU/Linux testing _Bullseye_ - 
> Official Snapshot arm64 NETINST 20210607-08:56'
> Jun  9 16:20:41 base-installer: Copying package lists...
> Jun  9 16:20:41 base-installer: ^MReading Package Indexes... 0%^M
> Jun  9 16:20:41 base-installer: ^MReading Package Indexes... 0%^M
> Jun  9 16:20:41 base-installer: ^MReading Package Indexes... Done^M
> Jun  9 16:20:41 base-installer: ^MReading Translation Indexes... 0%^M
> Jun  9 16:20:41 base-installer: ^MReading Translation Indexes... Done^M
> Jun  9 16:20:41 base-installer: Writing new source list
> Jun  9 16:20:41 base-installer: Source list entries for this disc are:
> Jun  9 16:20:41 base-installer: deb cdrom:[Debian GNU/Linux testing 
> _Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56]/ bullseye main
> Jun  9 16:20:41 base-installer: Repeat this process for the rest of the 
> CDs in your set.
> Jun  9 16:20:41 base-installer: Ign:1 cdrom://[Debian GNU/Linux testing 
> _Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56] bullseye 
> InRelease
> Jun  9 16:20:41 base-installer: Err:2 cdrom://[Debian GNU/Linux testing 
> _Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56] bullseye Release
> Jun  9 16:20:41 base-installer:   Please use apt-cdrom to make this 
> CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
> Jun  9 16:20:41 base-installer: Reading package lists...
> Jun  9 16:20:41 base-installer:
> Jun  9 16:20:41 base-installer: E: The repository 'cdrom://[Debian 
> GNU/Linux testing _Bullseye_ - Official Snapshot arm64 NETINST 
> 20210607-08:56] bullseye Release' does 

Bug#989593: installation report Raspberry Pi 4 UEFI

[Cyril Brulebois]

Marc Haber  (2021-06-09):
> I have attached the installer's syslog of a new installation. All
> issues that I reported were observed during this installation.

Thanks, this sticks out:

May 25 11:15:32 localechooser: info: System locale 
(debian-installer/locale) = 'en_US.UTF-8'
May 25 11:15:32 localechooser: info: Set debian-installer/language = 
'en_US:en'
May 25 11:15:32 debconf: Setting debconf/language to en_US:en
May 25 11:15:32 main-menu[261]: INFO: Falling back to the package 
description for brltty-udeb
May 25 11:15:32 main-menu[261]: INFO: Falling back to the package 
description for brltty-udeb
May 25 11:15:34 main-menu[261]: INFO: Falling back to the package 
description for brltty-udeb
May 25 11:15:34 main-menu[261]: INFO: Menu item 'console-setup-udeb' 
selected
May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
accessible. Will not save cached keyboard map.
May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
accessible. Will not save cached keyboard map.
May 25 11:15:37 main-menu[261]: (process:1290): ckbcomp-mini: 
/usr/share/console-setup/pc105.ekmap.gz does not exist
May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
accessible. Will not save cached keyboard map.
May 25 11:15:37 main-menu[261]: (process:1290): setupcon: gzip is not 
accessible. Will not save cached keyboard map.
May 25 11:15:37 main-menu[261]: (process:1290): /bin/setupcon: line 722: 
can't create /etc/console-setup/cached_setup_keyboard.sh: nonexistent directory
May 25 11:15:37 main-menu[261]: (process:1290): /bin/setupcon: line 730: 
can't create /etc/console-setup/cached_setup_font.sh: nonexistent directory
May 25 11:15:37 main-menu[261]: (process:1290): /bin/setupcon: line 748: 
can't create /etc/console-setup/cached_setup_terminal.sh: nonexistent directory
May 25 11:15:37 main-menu[261]: (process:1290): chmod: 
/etc/console-setup/cached_setup_keyboard.sh: No such file or directory
May 25 11:15:37 main-menu[261]: (process:1290): chmod: 
/etc/console-setup/cached_setup_font.sh: No such file or directory
May 25 11:15:37 main-menu[261]: (process:1290): chmod: 
/etc/console-setup/cached_setup_terminal.sh: No such file or directory
May 25 11:15:37 main-menu[261]: (process:1290): ckbcomp-mini: 
/usr/share/console-setup/pc105.ekmap.gz does not exist

and might explain why your keyboard settings don't work right after
selecting the layout.

This seems also strange (even if I must confess I've never grepped for
s-s-d lines before):

Jun  9 16:20:40 base-installer: Using CD-ROM mount point /media/cdrom/
Jun  9 16:20:40 base-installer: Identifying...
Jun  9 16:20:40 base-installer: [27dc08d5c910ea7df2dee6e03e127e52-2]
Jun  9 16:20:40 base-installer: Scanning disc for index files...
Jun  9 16:20:41 base-installer: Found 1 package indexes, 0 source indexes, 
1 translation indexes and 0 signatures
Jun  9 16:20:41 base-installer: Found label 'Debian GNU/Linux testing 
_Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56'
Jun  9 16:20:41 base-installer: This disc is called:
Jun  9 16:20:41 base-installer: 'Debian GNU/Linux testing _Bullseye_ - 
Official Snapshot arm64 NETINST 20210607-08:56'
Jun  9 16:20:41 base-installer: Copying package lists...
Jun  9 16:20:41 base-installer: ^MReading Package Indexes... 0%^M
Jun  9 16:20:41 base-installer: ^MReading Package Indexes... 0%^M
Jun  9 16:20:41 base-installer: ^MReading Package Indexes... Done^M
Jun  9 16:20:41 base-installer: ^MReading Translation Indexes... 0%^M
Jun  9 16:20:41 base-installer: ^MReading Translation Indexes... Done^M
Jun  9 16:20:41 base-installer: Writing new source list
Jun  9 16:20:41 base-installer: Source list entries for this disc are:
Jun  9 16:20:41 base-installer: deb cdrom:[Debian GNU/Linux testing 
_Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56]/ bullseye main
Jun  9 16:20:41 base-installer: Repeat this process for the rest of the CDs 
in your set.
Jun  9 16:20:41 base-installer: Ign:1 cdrom://[Debian GNU/Linux testing 
_Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56] bullseye InRelease
Jun  9 16:20:41 base-installer: Err:2 cdrom://[Debian GNU/Linux testing 
_Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56] bullseye Release
Jun  9 16:20:41 base-installer:   Please use apt-cdrom to make this CD-ROM 
recognized by APT. apt-get update cannot be used to add new CD-ROMs
Jun  9 16:20:41 base-installer: Reading package lists...
Jun  9 16:20:41 base-installer:
Jun  9 16:20:41 base-installer: E: The repository 'cdrom://[Debian 
GNU/Linux testing _Bullseye_ - Official Snapshot arm64 NETINST 20210607-08:56] 
bullseye Release' does not have a Release file.
Jun  9 16:20:41 base-installer: warning: apt update failed: 100
Jun  9 16:20:41 base-installer: dpkg-divert: warning: diverting file 

Bug#989593: installation report Raspberry Pi 4 UEFI

[Marc Haber]

On Wed, Jun 09, 2021 at 12:24:33AM +0200, Geert Stappers wrote:
> Repeating this:

I apologize for waiting for delivery of a new usb stick so that the
new installation would not be a complete waste of time.

> If you were to retry the installation, saving /var/log/syslog manually
> before rebooting into the installed system would be useful. Without it,
> I fear much guessing would be needed to try and figure out what happened
> on that system specifically. Unless someone else has better ideas of
> course.

I have attached the installer's syslog of a new installation. All issues
that I reported were observed during this installation.

Let me know if I can be of additional help. I appreciate the swiftness
of your reactions, this is very helpful.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421


syslog.xz
Description: application/xz

Bug#989593: installation report Raspberry Pi 4 UEFI

[Holger Wansing]

Hi,

Cyril Brulebois  wrote (Tue, 8 Jun 2021 17:07:52 +0200):
> Marc Haber  (2021-06-08):
> > Since my default domain types differently with US and DE keyboard, I
> > guess this might be an actual regression, I would have noticed this in
> > earlier versions of the installer.
> 
> I guess someone could try various images outside the Pi 4 setup and see
> whether/when that regressed. Given the following issue (ssd), I wouldn't
> rule out some Pi-specific, but such a trivial thing seems a little
> strange… That being said, I test the graphical installer most of the
> time, and I don't know the specifics of the text version by heart.

I checked with rc1 and the *brandnew* rc2 netinst images on amd64 qemu
VM machine (text installer), and I cannot reproduce such issue with wrong 
keyboard layout; German is correctly available immediately after the 
"Configure keyboard" step.

So, I guess that a Pi-specific thingy somehow.


Holger


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

Bug#989593: installation report Raspberry Pi 4 UEFI

[Geert Stappers]

On Tue, Jun 08, 2021 at 09:49:15PM +0200, Marc Haber wrote:
>
> The more pressing issue IMO is the deletion of /sbin/start-stop-daemon.
>

Repeating this:

If you were to retry the installation, saving /var/log/syslog manually
before rebooting into the installed system would be useful. Without it,
I fear much guessing would be needed to try and figure out what happened
on that system specifically. Unless someone else has better ideas of
course.


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

Bug#989593: installation report Raspberry Pi 4 UEFI

[Marc Haber]

On Tue, Jun 08, 2021 at 09:27:57PM +0200, Holger Wansing wrote:
> I checked with rc1 and the *brandnew* rc2 netinst images on amd64 qemu
> VM machine (text installer), and I cannot reproduce such issue with wrong 
> keyboard layout; German is correctly available immediately after the 
> "Configure keyboard" step.
> 
> So, I guess that a Pi-specific thingy somehow.

On the Pi, keyboard-configuration, console-data etc only seem to get
installed at the end of the "installing the base system" step, after
which the keyboard setting works.

The more pressing issue IMO is the deletion of /sbin/start-stop-daemon.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#989593: installation report Raspberry Pi 4 UEFI

[Cyril Brulebois]

Marc Haber  (2021-06-08):
> The Raspi 4 has both Wifi and Ethernet interfaces named brcmsomething,
> so it's still kind of guessing, but I have verified in the mean time
> that it's actually really the Wifi firmware.

Alright, thanks for confirming.

> Text installer ("expert"). I have used the graphical installer just a
> handful of times in two decades.

OK, good guess then, but checking never hurts.

> Since my default domain types differently with US and DE keyboard, I
> guess this might be an actual regression, I would have noticed this in
> earlier versions of the installer.

I guess someone could try various images outside the Pi 4 setup and see
whether/when that regressed. Given the following issue (ssd), I wouldn't
rule out some Pi-specific, but such a trivial thing seems a little
strange… That being said, I test the graphical installer most of the
time, and I don't know the specifics of the text version by heart.

> > Simply /var/log/syslog for the main log. Other files are mentioned
> > there:
> >   
> > https://salsa.debian.org/installer-team/installation-report/-/blob/master/debian/installation-report.postinst
> 
> Is there anything you need from me to go on?

If you were to retry the installation, saving /var/log/syslog manually
before rebooting into the installed system would be useful. Without it,
I fear much guessing would be needed to try and figure out what happened
on that system specifically. Unless someone else has better ideas of
course.


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


signature.asc
Description: PGP signature

Bug#989593: installation report Raspberry Pi 4 UEFI

[Marc Haber]

On Tue, Jun 08, 2021 at 11:17:51AM +0200, Cyril Brulebois wrote:
> Marc Haber  (2021-06-08):
> > I followed the instructions given on
> > https://www.raspberrypi.org/forums/viewtopic.php?t=282839
> > to install Debian on a Raspberry Pi using the UEFI firmware
> > available for the raspi.
> > 
> > This involves unpacking the official Debian 11 image into an ESP
> > partition on an USB medium and using the Rasberry Pi UEFI firmware
> > to boot the installer via UEFI => grub => Linux. Once the
> > installe has started, this feels 100 % like a standard Debian
> > installation.
> 
> Fun!

Yes!

> > I experienced the following issues:
> > 
> > "Detecting Hardware" complains about missing firmware. I guess
> > that's Wifi related, since the Wifi Interface doesn't work in the
> > installed system and the 1000Base-TX interface works fine without.
> 
> AFAICR (I'll get back to that soon enough) you should get a message
> indicating which files were expected, so that you don't have to guess.

The Raspi 4 has both Wifi and Ethernet interfaces named brcmsomething,
so it's still kind of guessing, but I have verified in the mean time
that it's actually really the Wifi firmware.

> > Requesting German keyboard layout does not work in the beginning of
> > installation, domain name and user name configuration still happens
> > with the default US keyboard layout. Later, when configuring the
> > network mirror, the keyboard layout has been changed to the requested
> > german layout. I guess this happens during base system installation.
> 
> Was that with the text or graphical installer?

Text installer ("expert"). I have used the graphical installer just a
handful of times in two decades.

Since my default domain types differently with US and DE keyboard, I
guess this might be an actual regression, I would have noticed this in
earlier versions of the installer.

> > For very strange reasons, the installed system ends up without
> > /sbin/start-stop-daemon despite the dpkg package being in state "ii".
> > This is reproducible. In the installer, I see a temporary diversion of
> > /sbin/start-stop-daemon, but in the installed system, dpkg-divert
> > --list doesn't show that.
> > 
> > /var/lib/dpkg/diversions-old has those three lines:
> > /sbin/start-stop-daemon
> > /sbin/start-stop-daemon.REAL
> > :
> > 
> > There is no /sbin/start-stop-daemon.REAL though.
> 
> A quick grep across our source packages show 3 possibilities:
>  - debootstrap
>  - debian-installer-utils
>  - apt-setup (code apparently copied from d-i-utils until some clean-up
>happens, which never did)
> 
> > And, the installed system does neither have /var/log/installer nor
> > /var/log/debian-installer. This is also reproducible :-(   Where would
> > I find the files that get copied to /target/var/log/installer in the
> > still running installer?
> 
> Simply /var/log/syslog for the main log. Other files are mentioned
> there:
>   
> https://salsa.debian.org/installer-team/installation-report/-/blob/master/debian/installation-report.postinst

Is there anything you need from me to go on?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#989593: installation report Raspberry Pi 4 UEFI

[Cyril Brulebois]

Hallo Marc,

Marc Haber  (2021-06-08):
> I followed the instructions given on
> https://www.raspberrypi.org/forums/viewtopic.php?t=282839
> to install Debian on a Raspberry Pi using the UEFI firmware
> available for the raspi.
> 
> This involves unpacking the official Debian 11 image into an ESP
> partition on an USB medium and using the Rasberry Pi UEFI firmware
> to boot the installer via UEFI => grub => Linux. Once the
> installe has started, this feels 100 % like a standard Debian
> installation.

Fun!

> I experienced the following issues:
> 
> "Detecting Hardware" complains about missing firmware. I guess
> that's Wifi related, since the Wifi Interface doesn't work in the
> installed system and the 1000Base-TX interface works fine without.

AFAICR (I'll get back to that soon enough) you should get a message
indicating which files were expected, so that you don't have to guess.

> Requesting German keyboard layout does not work in the beginning of
> installation, domain name and user name configuration still happens
> with the default US keyboard layout. Later, when configuring the
> network mirror, the keyboard layout has been changed to the requested
> german layout. I guess this happens during base system installation.

Was that with the text or graphical installer?

> For very strange reasons, the installed system ends up without
> /sbin/start-stop-daemon despite the dpkg package being in state "ii".
> This is reproducible. In the installer, I see a temporary diversion of
> /sbin/start-stop-daemon, but in the installed system, dpkg-divert
> --list doesn't show that.
> 
> /var/lib/dpkg/diversions-old has those three lines:
> /sbin/start-stop-daemon
> /sbin/start-stop-daemon.REAL
> :
> 
> There is no /sbin/start-stop-daemon.REAL though.

A quick grep across our source packages show 3 possibilities:
 - debootstrap
 - debian-installer-utils
 - apt-setup (code apparently copied from d-i-utils until some clean-up
   happens, which never did)

> And, the installed system does neither have /var/log/installer nor
> /var/log/debian-installer. This is also reproducible :-(   Where would
> I find the files that get copied to /target/var/log/installer in the
> still running installer?

Simply /var/log/syslog for the main log. Other files are mentioned
there:
  
https://salsa.debian.org/installer-team/installation-report/-/blob/master/debian/installation-report.postinst


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


signature.asc
Description: PGP signature

Bug#989593: installation report Raspberry Pi 4 UEFI

[Marc Haber]

Package: installation-reports
Version: 2.78
Severity: normal
Tags: d-i

Hi,

I followed the instructions given on
https://www.raspberrypi.org/forums/viewtopic.php?t=282839
to install Debian on a Raspberry Pi using the UEFI firmware
available for the raspi.

This involves unpacking the official Debian 11 image into an ESP
partition on an USB medium and using the Rasberry Pi UEFI firmware
to boot the installer via UEFI => grub => Linux. Once the
installe has started, this feels 100 % like a standard Debian
installation.

I experienced the following issues:

"Detecting Hardware" complains about missing firmware. I guess
that's Wifi related, since the Wifi Interface doesn't work in the
installed system and the 1000Base-TX interface works fine without.

Requesting German keyboard layout does not work in the beginning
of installation, domain name and user name configuration still happens
with the default US keyboard layout. Later, when configuring the
network mirror, the keyboard layout has been changed to the requested
german layout. I guess this happens during base system installation.

For very strange reasons, the installed system ends up without
/sbin/start-stop-daemon despite the dpkg package being in state "ii".
This is reproducible. In the installer, I see a temporary diversion of
/sbin/start-stop-daemon, but in the installed system, dpkg-divert --list
doesn't show that.

/var/lib/dpkg/diversions-old has those three lines:
/sbin/start-stop-daemon
/sbin/start-stop-daemon.REAL
:

There is no /sbin/start-stop-daemon.REAL though.

And, the installed system does neither have /var/log/installer nor
/var/log/debian-installer. This is also reproducible :-(   Where would I
find the files that get copied to /target/var/log/installer in the
still running installer?

Greetings
Marc

-- Package-specific info:

installation-report depends on no packages.

Versions of packages installation-report recommends:
ii  pciutils   1:3.7.0-5
ii  reportbug  7.10.3

installation-report suggests no packages.

-- no debconf information

Re: Bug#988797: RC1 installation report

[Andrew M.A. Cater]

On Thu, May 20, 2021 at 10:59:37AM +0200, Paul van der Vlis wrote:
> Op 19-05-2021 om 20:06 schreef Cyril Brulebois:
> > Goedendag Paul,
> > 
> > and thanks for your report.
> > 
> > Paul van der Vlis  (2021-05-19):
> 
> Correction, I did use: "pci=noaer", no capitals.
> 
> I guess this will become a problem on some machines.
> 
> > > 2. After the installation the sources.list had a "deb cdrom" line.
> > > Important to tell that I've used the official DVD ISO image. This
> > > problem was there too in Debian 10. I will add the sources.list.  I
> > > think most people who use a DVD-iso will use internet to install more
> > > packages, and will remove the DVD or stick. I sell Debian DVD's.
> > 
> > I think deactivating cdrom entries was implemented several release
> > cycles ago. That should be the case for both buster and bullseye at the
> > minimum (if memory serves).
> > 
> > Please share your /var/log/installer/syslog (compressed, due to bugs.d.o
> > and/or lists.d.o size limits) so that we can check what happens there?
> 
> Attached the installer-syslog (attached) of another machine. This is
> *always* the case with the DVD-version of the installer (not with the
> netinstaller!).
> 

>From a conversation with Steve McIntyre a while back: 

The netinst doesn't expect that you'll use any other medium other than
the 'Net to continue to install.

The DVD could be used in a standalone mode with no network access: in that
case a deb cdrom entry is useful (though latterly you get warning messages
about apt-secure when you try ot use it).

The deb cdrom entry is deliberate, I think - though it should probably 
come commented out.

All best,

Andy Cater


> I am a "Debian pre install vendor" and I also sell USB-sticks with Debian,
> so I have seen this really often.
> 
> With regards,
> Paul
> 
> -- 
> Paul van der Vlis Linux systeembeheer Groningen
> https://www.vandervlis.nl/

Bug#988797: RC1 installation report

[Cyril Brulebois]

Goedendag Paul,

and thanks for your report.

Paul van der Vlis  (2021-05-19):
> I did install Debian on an Acer laptop. The installation went OK, but
> I have some things to tell:
> 
> 1. After the installation the 240GB SSD was after a short period full
> with PCIe AER errors in the logs.  I think it's good to tell about
> errors in the logs, but doing that thousands of times is not OK.
> After using "PCI=NOAER" the laptop works fine.

Looks like something that might be worth reporting against src:linux?

> 2. After the installation the sources.list had a "deb cdrom" line.
> Important to tell that I've used the official DVD ISO image. This
> problem was there too in Debian 10. I will add the sources.list.  I
> think most people who use a DVD-iso will use internet to install more
> packages, and will remove the DVD or stick. I sell Debian DVD's.

I think deactivating cdrom entries was implemented several release
cycles ago. That should be the case for both buster and bullseye at the
minimum (if memory serves).

Please share your /var/log/installer/syslog (compressed, due to bugs.d.o
and/or lists.d.o size limits) so that we can check what happens there?


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


signature.asc
Description: PGP signature

Bug#988797: RC1 installation report

[Paul van der Vlis]

Package: installation-reports

I did install Debian on an Acer laptop. The installation went OK, but I 
have some things to tell:


1. After the installation the 240GB SSD was after a short period full 
with PCIe AER errors in the logs.  I think it's good to tell about 
errors in the logs, but doing that thousands of times is not OK.

After using "PCI=NOAER" the laptop works fine.

2. After the installation the sources.list had a "deb cdrom" line. 
Important to tell that I've used the official DVD ISO image. This 
problem was there too in Debian 10. I will add the sources.list.
I think most people who use a DVD-iso will use internet to install more 
packages, and will remove the DVD or stick. I sell Debian DVD's.


With regards,
Paul van der Vlis




-
# deb cdrom:[Debian GNU/Linux bullseye-DI-rc1 _Bullseye_ - Official 
Snapshot amd64 DVD Binary-1 20210415-20:26]/ bul>


deb cdrom:[Debian GNU/Linux bullseye-DI-rc1 _Bullseye_ - Official 
Snapshot amd64 DVD Binary-1 20210415-20:26]/ bulls>


deb http://ftp.nl.debian.org/debian/ bullseye main
deb-src http://ftp.nl.debian.org/debian/ bullseye main

deb http://security.debian.org/debian-security bullseye-security main 
contrib
deb-src http://security.debian.org/debian-security bullseye-security 
main contrib

-


--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Bug#985832: marked as done (installation report: netboot debian-installer kernel too old)

[Debian Bug Tracking System]

Your message dated Fri, 23 Apr 2021 23:25:23 +0200
with message-id <20210423212523.ifn6kdifh3rk3...@mraw.org>
and subject line Re: Bug#985832: installation report: netboot debian-installer 
kernel too old
has caused the Debian Bug report #985832,
regarding installation report: netboot debian-installer kernel too old
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.)


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

Boot method: network
Image version:
http://ftp.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
Date: 2021-03-11 ++

Machine: KVM
Processor: x86_64
Memory: 2 GB
Partitions: does not matter

Output of lspci -knn (or lspci -nn): does not matter

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: [E]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Installing bullseye via network fails since the (directory named)
_current_ debian-installer at

http://ftp.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux

is a kernel 5.9.0-4-amd64:

# file linux
linux: Linux kernel x86 boot executable bzImage, version 5.9.0-4-amd64
(debian-ker...@lists.debian.org) #1 SMP Debian 5.9.11-1 (2020-11-27),
RO-rootFS, swap_dev 0x5, Normal VGA

... which does not match the more recent kernel (modules) in

http://ftp.debian.org:80/debian/dists/bullseye/main/debian-installer/binary-amd64/Packages.xz
.

which rather fit kernel-image-5.10.0-3-amd64.

The installation fails after 'download-installer' succeeded:

"WARNNG **: no packages matching running kernel 5.9.0-4-amd64 in archive"

Since we use Foreman for automatic installation, this bug blocks testing
of debian bullseye in our environment. Is it possible to automatically
create the netboot installer whenever a new kernel is available? Thanks!
--- End Message ---
--- Begin Message ---
Anhu  (2021-03-24):
> Installing bullseye via network fails since the (directory named)
> _current_ debian-installer at
> 
> http://ftp.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
> 
> is a kernel 5.9.0-4-amd64

Fixed with the D-I Bullseye RC 1 release:
  https://lists.debian.org/debian-devel-announce/2021/04/msg00011.html

> Since we use Foreman for automatic installation, this bug blocks testing
> of debian bullseye in our environment. Is it possible to automatically
> create the netboot installer whenever a new kernel is available? Thanks!

We have daily builds so that you don't have to wait for a new release of
the installer:
  https://d-i.debian.org/daily-images/daily-build-overview.html


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


signature.asc
Description: PGP signature
--- End Message ---

Bug#986894: marked as done (installation report)

[Debian Bug Tracking System]

Your message dated Thu, 15 Apr 2021 14:19:57 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #986894,
regarding installation report
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.)


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

Boot method: DVD 1
Image version: 
https://cdimage.debian.org/cdimage/bullseye_di_alpha3/amd64/iso-dvd/
Date: 04/12/2021 23:00 UTC-5

Machine: Desktop
Processor: Intel Core i5-8600k
Memory: 16.0 GiB
Partitions:
S.ficheros Tipo bloques de 1KUsados Disponibles Uso% Montado en
udev   devtmpfs   8109116 0 8109116   0% /dev
tmpfs  tmpfs  1626412  1648 1624764   1% /run
/dev/sda5  ext4 102687492   496792492460316   6% /
tmpfs  tmpfs  8132048142952 7989096   2% /dev/shm
tmpfs  tmpfs 5120 45116   1% /run/lock
/dev/sda7  ext4 648173624 111246536   530314948  18% /media/datos
tmpfs  tmpfs  1626408   168 1626240   1% /run/user/1000
/dev/sdb1  iso96603875424   3875424   0 100%
/media/snt/Debian bullseye-DI-a3 amd64 1

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor
Host Bridge/DRAM Registers [8086:3ec2] (rev 07)
Subsystem: Gigabyte Technology Co., Ltd 8th Gen Core Processor Host
Bridge/DRAM Registers [1458:5000]
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:02.0 VGA compatible controller [0300]: Intel Corporation
CometLake-S GT2 [UHD Graphics 630] [8086:3e92]
DeviceName:  Onboard IGD
Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) 
[1458:d000]
Kernel driver in use: i915
Kernel modules: i915
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6
/ E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
[8086:1911]
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/v6 / E3-1500
v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [1458:5000]
00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370
Chipset Family USB 3.0 xHCI Controller [8086:a2af]
Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller [1458:5007]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 200 Series
PCH CSME HECI #1 [8086:a2ba]
Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH CSME HECI 
[1458:1c3a]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA
controller [AHCI mode] [8086:a282]
Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH SATA
controller [AHCI mode] [1458:b005]
Kernel driver in use: ahci
Kernel modules: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #17 [8086:a2e7] (rev f0)
Kernel driver in use: pcieport
00:1b.2 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #19 [8086:a2e9] (rev f0)
Kernel driver in use: pcieport
00:1b.3 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #20 [8086:a2ea] (rev f0)
Kernel driver in use: pcieport
00:1b.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #21 [8086:a2eb] (rev f0)
Kernel driver in use: pcieport
00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #1 [8086:a290] (rev f0)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #5 [8086:a294] (rev f0)
Kernel driver in use: pcieport
00:1c.6 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #7 [8086:a296] (rev f0)
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #9 [8086:a298] (rev f0)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Z370 Chipset LPC/eSPI
Controller [8086:a2c9]
Subsystem: Gigabyte Technology Co., Ltd Z370 Chipset LPC/eSPI
Controller [1458:5001]
00:1f.2 Memory controller [0580]: Intel Corporation 200 Series/Z370
Chipset Family Power Management Controller [8086:a2a1]
Subsystem: Gigabyte

Bug#973530: marked as done (installation-report: successful installation on SD card on EEE PC, runs on X230)

[Debian Bug Tracking System]

Your message dated Thu, 15 Apr 2021 14:09:26 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #973530,
regarding installation-report: successful installation on SD card on EEE PC, 
runs on X230
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.)


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

Dear Maintainer,

Everything went extremely well, just sending you this because the
installer asked me to.


-- Package-specific info:

Boot method: netinst/linux on hd
Image version: 
https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/ 
(downloaded 2020-10-31)
Date: 

Machine: installation: EEE PC X101H; runs on: X230
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] via network (netinst)
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:



-- 

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/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20201031-00:08:02"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux debian-sd 5.9.0-1-amd64 #1 SMP Debian 5.9.1-1 (2020-10-17) 
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. Eee PC 1015PX [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. Eee PC 1015PX [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. Eee PC 1015PX [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: 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. Eee PC 1015PX [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. Eee PC 1015PX [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. Eee PC 1015PX [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. Eee PC 1015PX [1043:83ad]
lspci -kn

Bug#984727: marked as done (installation-reports: just an installation report)

[Debian Bug Tracking System]

Your message dated Thu, 15 Apr 2021 14:02:00 +0200 (CEST)
with message-id 
and subject line closing successfull installation report
has caused the Debian Bug report #984727,
regarding installation-reports: just an installation report
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.)


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

-- Package-specific info:

Boot method: USB
Image version: debian-mac-10.8.0-amd64-netinst.iso 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ 2021-02-06
Date: 

Machine: MacBook3,1 (Nov 2007)
Partitions: 


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

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
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:




-- 

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/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u8"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (secondary) [8086:2a03] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) 
HD Audio Controller [8086:284b] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 5 [8086:2847] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 6 [8086:2849] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #2 [8086:2831] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Inte

Bug#986894: installation report

[Shigueru Nagata]

Package: installation-reports

Boot method: DVD 1
Image version: 
https://cdimage.debian.org/cdimage/bullseye_di_alpha3/amd64/iso-dvd/
Date: 04/12/2021 23:00 UTC-5

Machine: Desktop
Processor: Intel Core i5-8600k
Memory: 16.0 GiB
Partitions:
S.ficheros Tipo bloques de 1KUsados Disponibles Uso% Montado en
udev   devtmpfs   8109116 0 8109116   0% /dev
tmpfs  tmpfs  1626412  1648 1624764   1% /run
/dev/sda5  ext4 102687492   496792492460316   6% /
tmpfs  tmpfs  8132048142952 7989096   2% /dev/shm
tmpfs  tmpfs 5120 45116   1% /run/lock
/dev/sda7  ext4 648173624 111246536   530314948  18% /media/datos
tmpfs  tmpfs  1626408   168 1626240   1% /run/user/1000
/dev/sdb1  iso96603875424   3875424   0 100%
/media/snt/Debian bullseye-DI-a3 amd64 1

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor
Host Bridge/DRAM Registers [8086:3ec2] (rev 07)
Subsystem: Gigabyte Technology Co., Ltd 8th Gen Core Processor Host
Bridge/DRAM Registers [1458:5000]
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:02.0 VGA compatible controller [0300]: Intel Corporation
CometLake-S GT2 [UHD Graphics 630] [8086:3e92]
DeviceName:  Onboard IGD
Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) 
[1458:d000]
Kernel driver in use: i915
Kernel modules: i915
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6
/ E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
[8086:1911]
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/v6 / E3-1500
v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [1458:5000]
00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370
Chipset Family USB 3.0 xHCI Controller [8086:a2af]
Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller [1458:5007]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 200 Series
PCH CSME HECI #1 [8086:a2ba]
Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH CSME HECI 
[1458:1c3a]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA
controller [AHCI mode] [8086:a282]
Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH SATA
controller [AHCI mode] [1458:b005]
Kernel driver in use: ahci
Kernel modules: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #17 [8086:a2e7] (rev f0)
Kernel driver in use: pcieport
00:1b.2 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #19 [8086:a2e9] (rev f0)
Kernel driver in use: pcieport
00:1b.3 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #20 [8086:a2ea] (rev f0)
Kernel driver in use: pcieport
00:1b.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #21 [8086:a2eb] (rev f0)
Kernel driver in use: pcieport
00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #1 [8086:a290] (rev f0)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #5 [8086:a294] (rev f0)
Kernel driver in use: pcieport
00:1c.6 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #7 [8086:a296] (rev f0)
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI
Express Root Port #9 [8086:a298] (rev f0)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Z370 Chipset LPC/eSPI
Controller [8086:a2c9]
Subsystem: Gigabyte Technology Co., Ltd Z370 Chipset LPC/eSPI
Controller [1458:5001]
00:1f.2 Memory controller [0580]: Intel Corporation 200 Series/Z370
Chipset Family Power Management Controller [8086:a2a1]
Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset
Family Power Management Controller [1458:5001]
00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio
[8086:a2f0]
Subsystem: Gigabyte Technology Co., Ltd 200 Series PCH HD Audio 
[1458:a182]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1f.4 SMBus [0c05]: Intel Corporation 200 Series/Z370 Chipset Family
SMBus Controller [8086:a2a3]
Subsystem: Gigabyte Technology Co., Ltd 200 Series/Z370 Chipset
Family SMBus Controller [1458:5001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet
Connection (2) I219-V [8086:15b8]
Subsystem: Gigabyte Technology Co., Ltd Ethernet Connection (2)
I219-V 

Bug#985956: Installation Report - Bullseye 2021-03-15

[Butch Kemper]

Package: installation-reports 

Boot method: SSD built with Rufus using this installation guide:

 https://www.raspberrypi.org/forums/viewtopic.php?f=50=282839

Image version: Debian 11 ARM64 net install ISO 
   Debian-testing-arm64-netinst.iso 2021-03-15 04:03

Date: 2021-03-25 1109

Machine: Raspberry Pi 
Processor: Broadcom BCM2711 - Quad-core Cortex-A72 (ARM v8) 64-bit SoC
Memory: 4GB
Partitions: 
FilesystemType 1K-blocks   Used Available Use% Mounted on
udev  devtmpfs   1438812  0   1438812   0% /dev
tmpfs tmpfs   297504536296968   1% /run
/dev/sda4 ext4   1883580   3724   1765836   1% /
/dev/sda5 ext4   3764408 961688   2591008  28% /usr
tmpfs tmpfs  1487504  0   1487504   0% /dev/shm
tmpfs tmpfs 5120  0  5120   0% /run/lock
/dev/sda8 ext4  99027088 241836  93708724   1% /var
/dev/sda7 ext4   1883580 44   1769516   1% /home
/dev/sda6 ext4   1883580 72   1769488   1% /usr/local
/dev/sda2 ext4   3764408 118432   3434264   4% /boot
/dev/sda1 vfat391408 342172 49236  88% /boot/efi
tmpfs tmpfs   297500  0297500   0% /run/user/1000

Output of lspci -knn (or lspci -nn): Command produces no output  here is the 
output from lsusb-tv:

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/4p, 5000M
   ID 1d6b:0003 Linux Foundation 3.0 root hub
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, 
ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s 
bridge
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
   ID 1d6b:0002 Linux Foundation 2.0 root hub
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   ID 2109:3431 VIA Labs, Inc. Hub
   |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
   ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   |__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
   ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory

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:   [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: Other than the not detecting the builtin ethernet adapter, 
the installation went okay.  The result of the install was a functioning system 
which when booted would detect and initialize the ethernet adapter.

When the Install process failed to find a dhcp server, I used Alt-F2 to 
activate a console and searched through the syslog for the error.  I found that 
the module mdio-bcm-unimac.ko failed to load.  When the newly built system was 
booted, I copied mdio-bcm-unimac.ko from 
/lib/modules/5.10.0-5-arm64/kernel/drivers/net/mdio to a usb stick.  

I rebuilt the SSD using Rufus and started the installation process from the 
beginning.  When the network setup failed to find the dhcp server, I opened the 
Alt-F2 console, mounted the usb stick, copied the mdio-bcm-unimac.ko module to
/lib/modules/5.10.0-5-arm64/kernel/drivers/net/mdio, and then issued the 
command insmod to install the module in the kernel.

I used  Alt-F1 to return to the installation process and selected go-back to 
restart the network configuration process.  The network adapter was 
initialized, the dhcp server found, and the installation was completed 
successfully.

This problem has been present in the Bullseye Weekly Builds: 2021-03-01, 
2021-03-08, and 2021-03-15.

The problem summary is: mdio-bcm-unimac.ko module is not installed in the 
kernel.

The problem solution is: install the mdio-bcm-unimac.ko module in the kernel.

   

Bug#985832: installation report: netboot debian-installer kernel too old

[Anhu]

Package: installation-reports

Boot method: network
Image version:
http://ftp.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
Date: 2021-03-11 ++

Machine: KVM
Processor: x86_64
Memory: 2 GB
Partitions: does not matter

Output of lspci -knn (or lspci -nn): does not matter

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: [E]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Installing bullseye via network fails since the (directory named)
_current_ debian-installer at

http://ftp.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux

is a kernel 5.9.0-4-amd64:

# file linux
linux: Linux kernel x86 boot executable bzImage, version 5.9.0-4-amd64
(debian-ker...@lists.debian.org) #1 SMP Debian 5.9.11-1 (2020-11-27),
RO-rootFS, swap_dev 0x5, Normal VGA

... which does not match the more recent kernel (modules) in

http://ftp.debian.org:80/debian/dists/bullseye/main/debian-installer/binary-amd64/Packages.xz
.

which rather fit kernel-image-5.10.0-3-amd64.

The installation fails after 'download-installer' succeeded:

"WARNNG **: no packages matching running kernel 5.9.0-4-amd64 in archive"

Since we use Foreman for automatic installation, this bug blocks testing
of debian bullseye in our environment. Is it possible to automatically
create the netboot installer whenever a new kernel is available? Thanks!

Bug#984727: installation-reports: just an installation report

[Joseph Livesey]

Package: installation-reports
Severity: wishlist

-- Package-specific info:

Boot method: USB
Image version: debian-mac-10.8.0-amd64-netinst.iso 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ 2021-02-06
Date: 

Machine: MacBook3,1 (Nov 2007)
Partitions: 


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

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
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:




-- 

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/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u8"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (secondary) [8086:2a03] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) 
HD Audio Controller [8086:284b] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 5 [8086:2847] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 6 [8086:2849] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #2 [8086:2831] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #3 [8086:2832] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #1 [8086:2836] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI 
Bridge [8086:2448] (rev f3)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HM (ICH8M) LPC 
Interface Controller [8086:2815] (rev 03)
lspci -knn: Subsystem: Apple Inc. Device [106b:00a1]
lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 

Bug#980929: marked as done (reportbug and installation-report)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2021 18:33:26 +
with message-id 
and subject line Bug#980929: fixed in installation-report 2.78
has caused the Debian Bug report #980929,
regarding reportbug and installation-report
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.)


-- 
980929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-report
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-report...@lists.debian.org

What do you think about including the installation-report message
template directly in reportbug?

In reportbug's GTK interface, the output of bugscripts is not handed to
the user for editing, since it is seen as additional information and not
essential to the report. This view is incompatible with using the bug
script to generate a message template, which is what the
installation-report bug script is doing.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931438

So instead of changing the reportbug GTK ui, I'm proposing a pair of
changes to the installation-report package:
https://salsa.debian.org/installer-team/installation-report/-/merge_requests/1
and to reportbug:
https://salsa.debian.org/reportbug-team/reportbug/-/commit/15d209f4cf899f76749200899218e37c48a8f5a7
--- End Message ---
--- Begin Message ---
Source: installation-report
Source-Version: 2.78
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
installation-report, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated installation-report 
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: Wed, 24 Feb 2021 19:07:33 +0100
Source: installation-report
Architecture: source
Version: 2.78
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 980929
Changes:
 installation-report (2.78) unstable; urgency=medium
 .
   * Team upload
 .
   [ Nis Martensen ]
   * bugscript: do not include template in script output. Closes: #980929
 .
   [ Updated translations ]
   * Tamil (ta.po) by Vasudevan Tirumurti
Checksums-Sha1:
 503537ad5a483885761f45e473060821bc6050fa 1777 installation-report_2.78.dsc
 d01ad7da3a1841ac3cea292dc600c0863d4a694d 84572 installation-report_2.78.tar.xz
 2550ac981795b0a08cfb2fbe5aad113b3cee8eda 6104 
installation-report_2.78_amd64.buildinfo
Checksums-Sha256:
 ee3d9ce5ae38516ca14b75d710e032eea1347d6087da0aa9d37d643b32966356 1777 
installation-report_2.78.dsc
 ecf0640a01b4107831003384249a0a3d6172bea4b002056429d26c4642ddf70a 84572 
installation-report_2.78.tar.xz
 3b7a3c2b2301858e3a6ca431fbba8422c7083c9ef0963d87f659efdcc22be54a 6104 
installation-report_2.78_amd64.buildinfo
Files:
 59e2f8d2f7afa87c6088f75a52447f93 1777 debian-installer optional 
installation-report_2.78.dsc
 ae6c4e9b55e5057a72c659ff9eb01a6f 84572 debian-installer optional 
installation-report_2.78.tar.xz
 6f9189971ab22928a5dc80376e752769 6104 debian-installer optional 
installation-report_2.78_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmA2mGoVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2rKcQAIj5uYwTTxfEecHAozGG6GQToCjF
Xfb2zx3wITg4dMxgPdnnES1IU+nMq8K064KNwQtniT8LnNmzQMo+VUdGaJ6Pa2SS
3UpAB6SA8NSC7FYPSMMAbzWVVzM9n5pEPd2QZXEOJMDTjKMTWu0sk5M7GW5zIwkw
YR26JZ6cgR9DwtNVDn+vsqrZoLCsu2rpCszSM50wQMICU7AZt+WHFHDYzxJJe4Mm
gitJFPIUzu0ZDqFjn9K633L6qNtObZATKdvuOHTgBa8Ef1JJD6thFDeNmVV14VSR
Paluf7TVB/fDJg+cNUlZmhmCeoC4UdsqNMpYN4aIGcN8rg9zCWxcKD5QPqyW3D93
rnTC6UsDa9pHFmy5e7ECxY63ddvzIH61kFPwbYL6WGD6lffm4dC1UUXG0VJR996F
UeISEWBBFBdWmJA+7LtFjvHgpxrCshK6nrq6FMVQWRHXlaNwQB1zBFluQaBLyLH0
xsBxSIfO5akkOwmTETNZcrS3wZgk6lzy+X1I9Nh8cO+CBfA/lCm+OiE7lzgJUns2
bOFssMlMZpbJtLU0fwwYJXewrlapt2CCswsPzwjRWWsa/cEDlr/Z7GThpwYViuuc
/ydDjxQR5I0tq0OJCHgTvsFT9Tvc1YbbgHgt9IeqI9Rvo7SDhK7x6Uvi+6nb7ais
H28HnBAyO+5aj+2e
=wma2
-END PGP SIGNATURE End Message ---

Bug#980929: reportbug and installation-report

[Nis Martensen]

Hi,

On 18.02.2021 18.04, Holger Wansing wrote:
> Now merged.

Thanks!

> Will upload at the weekend, I think.

A new reportbug upload will follow within 24 hours after you upload.

 Nis

Bug#980929: reportbug and installation-report

[Holger Wansing]

Hi,

Holger Wansing  wrote (Sat, 6 Feb 2021 16:50:40 +0100):
> Hi,
> 
> Nis Martensen  wrote:
> > What do you think about including the installation-report message
> > template directly in reportbug?
> > 
> > In reportbug's GTK interface, the output of bugscripts is not handed to
> > the user for editing, since it is seen as additional information and not
> > essential to the report. This view is incompatible with using the bug
> > script to generate a message template, which is what the
> > installation-report bug script is doing.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931438
> > 
> > So instead of changing the reportbug GTK ui, I'm proposing a pair of
> > changes to the installation-report package:
> > https://salsa.debian.org/installer-team/installation-report/-/merge_requests/1
> > and to reportbug:
> > https://salsa.debian.org/reportbug-team/reportbug/-/commit/15d209f4cf899f76749200899218e37c48a8f5a7
> 
> Any objections against merging the above MR against installation-report?
> Are there some drawbacks to expect?

Now merged.
Will upload at the weekend, I think.


Holger


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

Bug#982995: Installation Report

[Raymond Burkholder]

On 2/17/21 3:20 PM, Jeff Forsyth wrote:

Comments/Problems:

RPI4 with 4GiB Ram.  This system is netbooted using RPI-UEFI 1.22 and
iPXE 1.2.x.

DNSMASQ send the RPI-UEFI to the RPI.  The RPI-UEFI pulls the arm64
EFI/ipxe.  The iPXE

shows a menu for booting into the Debian Installer.  The Installer
loads and starts the

interactive menu installation system.  Everything seems good until
input is required.  The

keyboard is dead.


You are probably using a serial port to monitor progress?

If so, you need the following appended on the kernel line to redirect to 
the serial console:


kernel debian-installer/amd64/linux TERM=linux ..  yadda yadda ... 
console=ttyS0,115200n -- console=ttyS0,115200n8

Bug#982995: Installation Report

[Jeff Forsyth]

Package: installation-reports

Boot method: 
Image version: 
https://d-i.debian.org/daily-images/arm64/daily/netboot/debian-installer/arm64/linux
2021-02-17 02:07
Date: 2021-02-17 19:14

Machine: RPI4
Processor:
Memory: 4G
Partitions:

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

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:   [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[E]

Comments/Problems:

RPI4 with 4GiB Ram.  This system is netbooted using RPI-UEFI 1.22 and
iPXE 1.2.x.

DNSMASQ send the RPI-UEFI to the RPI.  The RPI-UEFI pulls the arm64
EFI/ipxe.  The iPXE

shows a menu for booting into the Debian Installer.  The Installer
loads and starts the

interactive menu installation system.  Everything seems good until
input is required.  The

keyboard is dead.

Bug#982835: installation-report: doesn't set needed rootflags for flash-kernel when btrfs is used as rootfs

[Vieno Hakkerinen]

/proc/meminfo: Inactive: 455084 kB
/proc/meminfo: Active(anon): 102924 kB
/proc/meminfo: Inactive(anon):91012 kB
/proc/meminfo: Active(file): 817040 kB
/proc/meminfo: Inactive(file):   364072 kB
/proc/meminfo: Unevictable:   0 kB
/proc/meminfo: Mlocked:   0 kB
/proc/meminfo: SwapTotal:974844 kB
/proc/meminfo: SwapFree: 972540 kB
/proc/meminfo: Dirty:  1260 kB
/proc/meminfo: Writeback: 0 kB
/proc/meminfo: AnonPages: 36356 kB
/proc/meminfo: Mapped: 5224 kB
/proc/meminfo: Shmem:157332 kB
/proc/meminfo: KReclaimable:  74584 kB
/proc/meminfo: Slab: 123168 kB
/proc/meminfo: SReclaimable:  74584 kB
/proc/meminfo: SUnreclaim:48584 kB
/proc/meminfo: KernelStack:2368 kB
/proc/meminfo: PageTables: 1164 kB
/proc/meminfo: NFS_Unstable:  0 kB
/proc/meminfo: Bounce:0 kB
/proc/meminfo: WritebackTmp:  0 kB
/proc/meminfo: CommitLimit: 1959280 kB
/proc/meminfo: Committed_AS: 205100 kB
/proc/meminfo: VmallocTotal:   135290159040 kB
/proc/meminfo: VmallocUsed:   26092 kB
/proc/meminfo: VmallocChunk:  0 kB
/proc/meminfo: Percpu:  624 kB
/proc/meminfo: HardwareCorrupted: 0 kB
/proc/meminfo: AnonHugePages: 18432 kB
/proc/meminfo: ShmemHugePages:0 kB
/proc/meminfo: ShmemPmdMapped:0 kB
/proc/meminfo: FileHugePages: 0 kB
/proc/meminfo: FilePmdMapped: 0 kB
/proc/meminfo: CmaTotal:  65536 kB
/proc/meminfo: CmaFree:   45644 kB
/proc/meminfo: HugePages_Total:   0
/proc/meminfo: HugePages_Free:0
/proc/meminfo: HugePages_Rsvd:0
/proc/meminfo: HugePages_Surp:0
/proc/meminfo: Hugepagesize:   2048 kB
/proc/meminfo: Hugetlb:   0 kB

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-3-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

installation-report depends on no packages.

Versions of packages installation-report recommends:
ii  pciutils   1:3.7.0-5
ii  reportbug  7.9.0

installation-report suggests no packages.

-- no debconf information

Bug#980929: reportbug and installation-report

[Holger Wansing]

Hi,

Nis Martensen  wrote:
> What do you think about including the installation-report message
> template directly in reportbug?
> 
> In reportbug's GTK interface, the output of bugscripts is not handed to
> the user for editing, since it is seen as additional information and not
> essential to the report. This view is incompatible with using the bug
> script to generate a message template, which is what the
> installation-report bug script is doing.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931438
> 
> So instead of changing the reportbug GTK ui, I'm proposing a pair of
> changes to the installation-report package:
> https://salsa.debian.org/installer-team/installation-report/-/merge_requests/1
> and to reportbug:
> https://salsa.debian.org/reportbug-team/reportbug/-/commit/15d209f4cf899f76749200899218e37c48a8f5a7

Any objections against merging the above MR against installation-report?
Are there some drawbacks to expect?


Holger


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

Bug#971984: marked as done (installation-reports: installation report)

[Debian Bug Tracking System]

Your message dated Sun, 31 Jan 2021 23:43:25 +0100
with message-id <20210131224324.hguvf6n4cwlts...@percival.namespace.at>
and subject line Re: Bug#971984: installation-reports: installation report
has caused the Debian Bug report #971984,
regarding installation-reports: installation report
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- Package-specific info:

Boot method: usb
Image version: debian 10.0 iso
Date: 

Machine: Dell Inspiron 15-3567
Partitions: 


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

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
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:




-- 

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/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux zues 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] 
(rev 02)
lspci -knn: Subsystem: Dell Device [1028:078b]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:5916] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:078b]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation 
Skylake Processor Thermal Subsystem [8086:1903] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:078b]
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:078b]
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:078b]
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:078b]
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:078b]
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:078b]
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:078b]
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 #5 [8086:9d14] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI 
Express Root Port #6 [8086:9d15] (rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d4e] 
(rev 21)
lspci -knn: Subsystem: Dell Device [1028:078b]
lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise 
Point-LP PMC [8086

Bug#980929: reportbug and installation-report

[Nis Martensen]

Package: installation-report
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-report...@lists.debian.org

What do you think about including the installation-report message
template directly in reportbug?

In reportbug's GTK interface, the output of bugscripts is not handed to
the user for editing, since it is seen as additional information and not
essential to the report. This view is incompatible with using the bug
script to generate a message template, which is what the
installation-report bug script is doing.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931438

So instead of changing the reportbug GTK ui, I'm proposing a pair of
changes to the installation-report package:
https://salsa.debian.org/installer-team/installation-report/-/merge_requests/1
and to reportbug:
https://salsa.debian.org/reportbug-team/reportbug/-/commit/15d209f4cf899f76749200899218e37c48a8f5a7

Bug#980271: #980271 installation-reports: Toshiba Tecra 8000 Installation report Bullseye

[Holger Wansing]

Control: reassign -1 pcmciautils
Control: tags -1 + patch


Charles Curley  wrote:
> I tried a Xircom CreditCard Ethernet adapter, CE38-100BTX, which uses
> the xirc2ps_cs driver. It runs, if slowly, on an installed system. But
> on installation, the software fails to detect it also.
> 
> I noticed in the log on console F4 a message:
> 
> pcmcia-socket-startup: chdir to /etc/pcmcia failed: no such file or
> directory.
> 
> Possibly this is because the directory actually is /etc/pcmciautils on
> the installer. It is /etc/pcmcia on the installed system.
> 
> I then made a symlink, rmmod yenta_socket, modprobe yenta_socket.
> Messages indicate that yenta_socket picked up the configuration file.
> 
> I then inserted the card. Messages indicate that the card was detected
> and set up. I then went back to the installatio software, had it detect
> the network. It detected it correctly, and auto-configuration worked
> correctly.

I have verified that on a current testing installation system, there is
still /etc/pcmciautils/ existing, and no /etc/pcmcia/.

So re-assigning to pcmciautils package.

Also, I attached a patch, which should hopefully fix this for the udeb.


Thanks
Holger




-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/debian/changelog b/debian/changelog
index 44560d6..0c86fc6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pcmciautils (018-13) UNRELEASED; urgency=medium
+
+  * Update /etc/pcmciautils/ dir to /etc/pcmcia/ in udeb.
+
+ -- Holger Wansing   Thu, 21 Jan 2021 18:17:41 +0100
+
 pcmciautils (018-12) unstable; urgency=medium
 
   [ Bor Grošelj Simić ]
diff --git a/debian/pcmciautils-udeb.install b/debian/pcmciautils-udeb.install
index 6e4bf21..2010958 100644
--- a/debian/pcmciautils-udeb.install
+++ b/debian/pcmciautils-udeb.install
@@ -1,2 +1,2 @@
 lib/udev lib/
-usr/lib/pcmciautils/config.opts etc/pcmciautils/
+usr/lib/pcmciautils/config.opts etc/pcmcia/

Processed: Re: #980271 installation-reports: Toshiba Tecra 8000 Installation report Bullseye

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pcmciautils
Bug #980271 [installation-reports] installation-reports: Toshiba Tecra 8000 
Installation report Bullseye
Bug reassigned from package 'installation-reports' to 'pcmciautils'.
Ignoring request to alter found versions of bug #980271 to the same values 
previously set
Ignoring request to alter fixed versions of bug #980271 to the same values 
previously set
> tags -1 + patch
Bug #980271 [pcmciautils] installation-reports: Toshiba Tecra 8000 Installation 
report Bullseye
Added tag(s) patch.

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

Bug#980271: installation-reports: Toshiba Tecra 8000 Installation report Bullseye

[Charles Curley]

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

Dear Maintainer,

-- Package-specific info:

Boot method: CD-ROM
Image version: debian-bullseye-DI-alpha3-i386-netinst.iso
Date: 14 January 2021

Machine: Toshiba Tecra 8000
Partitions: 

Filesystem Type  Size  Used Avail Use% Mounted on
udev   devtmpfs  110M 0  110M   0% /dev
tmpfs  tmpfs  25M  560K   24M   3% /run
/dev/sda6  ext4  6.8G  1.1G  5.4G  17% /
tmpfs  tmpfs 121M 0  121M   0% /dev/shm
tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
tmpfs  tmpfs 4.0M 0  4.0M   0% /sys/fs/cgroup
/dev/sda2  ext4   95M   35M   53M  40% /boot
tmpfs  tmpfs  25M 0   25M   0% /run/user/1000
tmpfs  tmpfs  25M 0   25M   0% /run/user/0

Disk /dev/sda: 7.63 GiB, 8195604480 bytes, 16007040 sectors
Disk model: IBM-DYLA-28100  
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: 0x000ce2ac

Device Boot   Start  End  Sectors   Size Id Type
/dev/sda1  * 63   208844   208782 101.9M  b W95 FAT32
/dev/sda2208845   417689   208845   102M 83 Linux
/dev/sda3417751 16000739 15582989   7.4G  5 Extended
/dev/sda5417753  1461914  1044162 509.8M 82 Linux swap / Solaris
/dev/sda6   1461978 16000739 14538762   6.9G 83 Linux



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:   [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:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Installed via debian-bullseye-DI-alpha3-i386-netinst.iso. Expert
install via text using a RW-CD. Due to low memory, language and
keyboard are US English, which is fine for me.

The d-i kernel gets hung up for a while on "probing EDD". I haven't
tried adding "edd=off" to the command line yet.

For obvious reasons, d-i used low memory mode. Also, the installer is
*slow*. If you must install on this machine, have patience.

d-i does not detect the Ethernet card. This machine has a Netgear FA411
Ethernet card in a PCMCIA; it seems to like the axnet_cs driver. Even
after I selected it in the menu, d-i didn't use it. It worked in
Stretch. Once the installation was complete, all I had to do was add it
to /etc/network/interfaces, and run "ifup eth0".

However, it does not continue to work smoothly, so it may be a a
hardware issue. I get a lot of dropped packets, frame errors, and
errors on RX; none on TX. Misconfiguration of the Ethernet
configuration???

I got an entirely bogus question about installing GRUB in the EFI
fallback. Would a machine this old have EFI on it?

According to d-i, the BIOS has corrupted hw-PMU resources (MSR-186 is
40002e). Whatever that means.

The graphical installer bombed. I don't think it could launch X. I did
not investigate.

fdisk seems to think it has a floppy disk at fd0. It doesn't.

-- 

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/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20201202"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux (none) 5.9.0-4-686 #1 SMP Debian 5.9.11-1 (2020-11-27) i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 
82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 02)
lspci -knn: Subsystem: Toshiba Corporation Satellite 4010 [1179:0001]
lspci -knn: 00:04.0 VGA compatible controller [0300]: Neomagic Corporation 
NM2200 [MagicGraph 256AV] [10c8:0005] (rev 20)
lspci -knn: Subsystem: Toshiba Corporation Device [1179:0001]
lspci -knn: 00:05.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ISA 
[8086:7110] (rev 02)
lspci -knn: 00:05.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:05.2 USB controller [0c03]: Intel Corporation 82371AB/EB/MB 
PIIX4 USB [8086:7112] (rev 01)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB 

Bug#975367: installation-report

[Steve McIntyre]

On Sat, Nov 21, 2020 at 10:38:07AM +0330, Sayed Hadi Rastgou Haghi wrote:
>Package: installation-reports
>
>Partitions:
>/dev/sda1  /        ext4 [formated]
>/dev/sda2  swap
>/dev/sda3  /home    ext4 [kept old partiotin]
>/dev/sda4  /var     ext4 [kept old partiotin]
>
>Comments/Problems:
>
>We were trying to install fresh debain on old debian 8 installed machine and
>wanted to keep old /var partiton as new /var partition. But this made base
>system to fail with bootstrap errors on install.
>
>Content of /var/log/syslog :
>base-installer: error: exiting on error base-installer /debootstrap-failed
>main-menu[620]: WARNING ** : configuring "bootstrap-base" failed with error
>code 3
>main-menu[620]: WARNING ** : Menu Item "bootstrap-base" failed
>base-installer: warning: attempting to install to unclean target
>debootstrap: tar: can't open './usr/share/doc/gcc-8-base/
>README.Debian.amd64.gz' File exists
>debootstrap: xscat: write: Broken pipe
>debootstrap: ar: write error: Broken pipe

This isn't going to work - you can't just install over an existing
system like this.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer

Bug#975367: installation-report

[Sayed Hadi Rastgou Haghi]

Package: installation-reports

Boot method: CD, USB Stick
Image
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.6.0-amd64-netinst.iso
Date: Wed Nov 18 16:23:27 +0330 2020

Machine:HP Proliant Gen9
Processor:  Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz
Memory: 48GB

Partitions:
/dev/sda1  /ext4 [formated]
/dev/sda2  swap
/dev/sda3  /homeext4 [kept old partiotin]
/dev/sda4  /var ext4 [kept old partiotin]

Output of lspci -knn (or lspci -nn): N.A

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:[E]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

We were trying to install fresh debain on old debian 8 installed machine
and wanted to keep old /var partiton as new /var partition. But this made
base system to fail with bootstrap errors on install.

Content of /var/log/syslog :
base-installer: error: exiting on error base-installer /debootstrap-failed
main-menu[620]: WARNING ** : configuring "bootstrap-base" failed with error
code 3
main-menu[620]: WARNING ** : Menu Item "bootstrap-base" failed
base-installer: warning: attempting to install to unclean target
debootstrap: tar: can't open
'./usr/share/doc/gcc-8-base/README.Debian.amd64.gz' File exists
debootstrap: xscat: write: Broken pipe
debootstrap: ar: write error: Broken pipe

-- 
Sincerely,

Sayed Hadi Rastgou Haghi

Bug#973530: installation-report: successful installation on SD card on EEE PC, runs on X230

[Axel Stammler]

ader Start Offset: 0x
dmidecode:  Header Length: 2 bytes
dmidecode:  Data Start Offset: 0x0002
dmidecode:  Access Method: Indexed I/O, one 16-bit index port, one 8-bit 
data port
dmidecode:  Access Address: Index 0x046A, Data 0x046C
dmidecode:  Status: Invalid, Not Full
dmidecode:  Change Token: 0x
dmidecode:  Header Format: No Header
dmidecode:  Supported Log Type Descriptors: 6
dmidecode:  Descriptor 1: End of log
dmidecode:  Data Format 1: OEM-specific
dmidecode:  Descriptor 2: End of log
dmidecode:  Data Format 2: OEM-specific
dmidecode:  Descriptor 3: End of log
dmidecode:  Data Format 3: OEM-specific
dmidecode:  Descriptor 4: End of log
dmidecode:  Data Format 4: OEM-specific
dmidecode:  Descriptor 5: End of log
dmidecode:  Data Format 5: OEM-specific
dmidecode:  Descriptor 6: End of log
dmidecode:  Data Format 6: OEM-specific
dmidecode: 
dmidecode: Handle 0x0015, DMI type 16, 15 bytes
dmidecode: Physical Memory Array
dmidecode:  Location: System Board Or Motherboard
dmidecode:  Use: System Memory
dmidecode:  Error Correction Type: None
dmidecode:  Maximum Capacity: 2 GB
dmidecode:  Error Information Handle: Not Provided
dmidecode:  Number Of Devices: 1
dmidecode: 
dmidecode: Handle 0x0016, DMI type 19, 15 bytes
dmidecode: Memory Array Mapped Address
dmidecode:  Starting Address: 0x000
dmidecode:  Ending Address: 0x0007FFF
dmidecode:  Range Size: 2 GB
dmidecode:  Physical Array Handle: 0x0015
dmidecode:  Partition Width: 4
dmidecode: 
dmidecode: Handle 0x0017, DMI type 17, 28 bytes
dmidecode: Memory Device
dmidecode:  Array Handle: 0x0015
dmidecode:  Error Information Handle: Not Provided
dmidecode:  Total Width: 64 bits
dmidecode:  Data Width: 64 bits
dmidecode:  Size: 2048 MB
dmidecode:  Form Factor: SODIMM
dmidecode:  Set: None
dmidecode:  Locator: DIMM0
dmidecode:  Bank Locator: BANK0
dmidecode:  Type: DDR3
dmidecode:  Type Detail: Synchronous
dmidecode:  Speed: 667 MT/s
dmidecode:  Manufacturer: Manufacturer00
dmidecode:  Serial Number: SerNum00
dmidecode:  Asset Tag: AssetTagNum0
dmidecode:  Part Number: ModulePartNumber00
dmidecode:  Rank: Unknown
dmidecode: 
dmidecode: Handle 0x0018, DMI type 20, 19 bytes
dmidecode: Memory Device Mapped Address
dmidecode:  Starting Address: 0x000
dmidecode:  Ending Address: 0x0007FFF
dmidecode:  Range Size: 2 GB
dmidecode:  Physical Device Handle: 0x0017
dmidecode:  Memory Array Mapped Address Handle: 0x0016
dmidecode:  Partition Row Position: 1
dmidecode:  Interleaved Data Depth: 1
dmidecode: 
dmidecode: Handle 0x0019, DMI type 32, 20 bytes
dmidecode: System Boot Information
dmidecode:  Status: No errors detected
dmidecode: 
dmidecode: Handle 0x001A, DMI type 41, 11 bytes
dmidecode: Onboard Device
dmidecode:  Reference Designation: To Be Filled By O.E.M.
dmidecode:  Type: Video
dmidecode:  Status: Enabled
dmidecode:  Type Instance: 0
dmidecode: 
dmidecode: Handle 0x001B, DMI type 41, 11 bytes
dmidecode: Onboard Device
dmidecode:  Reference Designation: To Be Filled By O.E.M.
dmidecode:  Type: SCSI Controller
dmidecode:  Status: Disabled
dmidecode:  Type Instance: 0
dmidecode: 
dmidecode: Handle 0x001C, DMI type 127, 4 bytes
dmidecode: End Of Table
dmidecode: 

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

installation-report depends on no packages.

Versions of packages installation-report recommends:
ii  pciutils   1:3.7.0-4
ii  reportbug  7.7.0

installation-report suggests no packages.

-- no debconf information

Processed: Re: Bug#971984: installation-reports: installation report

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #971984 [installation-reports] installation-reports: installation report
Added tag(s) moreinfo.

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

Bug#971984: installation-reports: installation report

[Geert Stappers]

Control: tag -1 moreinfo


On Sun, Oct 11, 2020 at 01:42:17AM -0400, WK Burke wrote:
> Package: installation-reports
> 
> Boot method: usb
> Image version: debian 10.0 iso
> 
> Machine: Dell Inspiron 15-3567
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [ ]
> Detect network card:[ ]
> Configure network:  [ ]
> Detect CD:  [ ]
> 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:
> 
>and ideas you had during the initial install.>
> 
> 
> 
> 
> 
> ==
> Installer lsb-release:
> ==
> DISTRIB_ID=Debian
> DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
> DISTRIB_RELEASE="10 (buster) - installer build 20190702"
> X_INSTALLATION_MEDIUM=cdrom
> 
> uname -a: Linux zues 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) 
> x86_64 GNU/Linux



Please tell more about the installation success.

And that includes a message like "the install went just fine"   :-)




Regards
Geert Stappers
-- 
Silence is hard to parse