Bug#1079139: Failed boot after install

[louigi 600]

Package: installation-reports

Boot method: cat debian-12.6.0-amd64-DVD-1.iso > /dev/sda  (where sda is
the where my system sees the usb stick)
 Then I proceed with normal graphical install


Image version:
https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-12.6.0-amd64-DVD-1.iso
Not sure if I got it directly from the link above in any case here is the
md5sum of what I have
462e540d1ba2ca5ecc68ab79c8e3788a

Date: 20/08/2024 was the last time I tried after changing target drive and
updating bios

Machine: Dell Optiplex 7040 micro system
Processor: Intel(R) Core(TM) i7-6700T
Memory: 16Gb
Partitions:
label: gpt
label-id: 57F1B3D2-BE5F-4F4F-8875-415984544A0C
device: /dev/sde
unit: sectors
first-lba: 34
last-lba: 976773134
sector-size: 512

/dev/sde1 : start=2048, size= 1048576,
type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B,
uuid=347C9F36-3991-41AE-B5E9-74F13A4D09FD
/dev/sde2 : start= 1050624, size=   973721600,
type=0FC63DAF-8483-4772-8E79-3D69D8477DE4,
uuid=8191A433-DF94-4157-90B5-DFD9A81BF058
/dev/sde3 : start=   974772224, size= 1998848,
type=0657FD6D-A4AB-43C4-84E5-0933C84B4F4F,
uuid=FAB1BEC7-BC34-486B-B1EF-42EC71E9042D

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500
v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor
PCIe Controller (x16) [8086:1901] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530
[8086:1912] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series
Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation 100
Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230
Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
00:16.3 Serial controller [0700]: Intel Corporation 100 Series/C230 Series
Chipset Family KT Redirection [8086:a13d] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation
Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]
[8086:a102] (rev 31)
00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset
Family PCI Express Root Port #17 [8086:a167] (rev f1)
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset
Family PCI Express Root Port #8 [8086:a117] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Q170 Chipset LPC/eSPI
Controller [8086:a146] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series
Chipset Family Power Management Controller [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series
Chipset Family HD Audio Controller [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset
Family SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection
(2) I219-LM [8086:15b7] (rev 31)
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd
NVMe SSD Controller PM9A1/PM9A3/980PRO [144d:a80a]
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565
Wireless Network Adapter [168c:0036] (rev 01)

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 installation fails to boot but only on the optiplex
7040, I took the M2 sata drive out of the dell optiplex 7040 and put it
into another PC and it boots normally.
I performed the same with nvme and normal disk drive, results were the same.
I updated bios and even tried manually configuring the boot entry in bios:
still will not boot on the 7040.
I tried booting to recovery mode from install media to reinstall boot
loader: sill no go on the 7040.
The information gouged out of the system is actually from Ubuntu 22.04 LTE
running on it at the moment ... but i would rather have Debian on it.

No point sharing the install logs because the installation is fine and
functional on another computer.
There is something Debian does not like about my Dell Optiplex 7040 but at
the same time Fedora and Ubunto seem to work fine on my 7040.
What's up with debian not liking the 7040 ? Ubuntu 22.04 LTE and Fedora 40
install and boot normally there.

Bug#1079139: Failed boot after install

[Steve McIntyre]

Hi Louigi,

On Tue, Aug 20, 2024 at 02:25:13PM +0200, louigi 600 wrote:
>Package: installation-reports
>
>Boot method: cat debian-12.6.0-amd64-DVD-1.iso > /dev/sda  (where sda is the
>where my system sees the usb stick)
>             Then I proceed with normal graphical install
>
>
>Image version: https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/
>debian-12.6.0-amd64-DVD-1.iso
>Not sure if I got it directly from the link above in any case here is the
>md5sum of what I have
>462e540d1ba2ca5ecc68ab79c8e3788a
>
>Date: 20/08/2024 was the last time I tried after changing target drive and
>updating bios
>
>Machine: Dell Optiplex 7040 micro system
>Processor: Intel(R) Core(TM) i7-6700T
>Memory: 16Gb
>Partitions:
>label: gpt
>label-id: 57F1B3D2-BE5F-4F4F-8875-415984544A0C
>device: /dev/sde
>unit: sectors
>first-lba: 34
>last-lba: 976773134
>sector-size: 512

...

>Comments/Problems: the installation fails to boot but only on the optiplex
>7040, I took the M2 sata drive out of the dell optiplex 7040 and put it into
>another PC and it boots normally.
>I performed the same with nvme and normal disk drive, results were the same.
>I updated bios and even tried manually configuring the boot entry in bios:
>still will not boot on the 7040.
>I tried booting to recovery mode from install media to reinstall boot loader:
>sill no go on the 7040.
>The information gouged out of the system is actually from Ubuntu 22.04 LTE
>running on it at the moment ... but i would rather have Debian on it.
>
>No point sharing the install logs because the installation is fine and
>functional on another computer.
>There is something Debian does not like about my Dell Optiplex 7040 but at the
>same time Fedora and Ubunto seem to work fine on my 7040.
>What's up with debian not liking the 7040 ? Ubuntu 22.04 LTE and Fedora 40
>install and boot normally there.

When you say "fails to boot" here, what *exactly* do you mean please?
Does the boot loader screen come up at all? Do you get kernel
messages? What's the last thing you see?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait:   https://www.debian.org/CD/free-linux-cd
  Debian does NOT ship free CDs. Please do NOT contact the mailing
  lists asking us to send them to you.

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

[Holger Wansing]

Hi,

Pascal Hambourg  wrote (Sun, 18 Aug 2024 23:46:13 
+0200):
> On 18/08/2024 at 16:38, Holger Wansing wrote:
> > 
> > I have uploaded some screenshots from tests with different disk sizes to
> > https://people.debian.org/~holgerw/partman-auto___new-limits/
> 
> Thank you. The /boot partition size is bigger than I expected in all LVM 
> cases, and I understand why. My previous calculations compensated the 
> LVM PV priority used by partman-auto-lvm but not the minimum size 
> (100MB) which is considerably smaller than the actual sum of lvmok 
> partition minimal sizes. According to my new calculations, it adds 
> ~260MB to /boot.
> 
> This offset can be compensated by reducing /boot minimal size 
> (ironically it almost reverts to the previous value of 512MB) in recipes 
> where /boot exists only with LVM.
> 
> But it is not possible to do the same to the EFI partition or in recipes 
>   where /boot exists in both LVM and non-LVM schemes. The only solution 
> I can think of is to replace the LVM PV fixed arbitrary minimal size 
> (and priority while we're at it) in partman-auto-lvm with the actual 
> values. But this may affect existing custom LVM recipes in unpredictable 
> ways. It is possible to apply the new behaviour only to built-in 
> recipes, but then custom recipes based on new built-in recipes may 
> produce unexpected results.

Just leave it as is, ignoring the 260MB difference?


Holger


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

Bug#1079139: Failed boot after install

[louigi 600]

I dint think it even loads the grub efi file. System bios  complains it
can't boot from that device.

On Tue, Aug 20, 2024, 17:38 Steve McIntyre  wrote:

> Hi Louigi,
>
> On Tue, Aug 20, 2024 at 02:25:13PM +0200, louigi 600 wrote:
> >Package: installation-reports
> >
> >Boot method: cat debian-12.6.0-amd64-DVD-1.iso > /dev/sda  (where sda is
> the
> >where my system sees the usb stick)
> > Then I proceed with normal graphical install
> >
> >
> >Image version:
> https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/
> >debian-12.6.0-amd64-DVD-1.iso
> >Not sure if I got it directly from the link above in any case here is the
> >md5sum of what I have
> >462e540d1ba2ca5ecc68ab79c8e3788a
> >
> >Date: 20/08/2024 was the last time I tried after changing target drive and
> >updating bios
> >
> >Machine: Dell Optiplex 7040 micro system
> >Processor: Intel(R) Core(TM) i7-6700T
> >Memory: 16Gb
> >Partitions:
> >label: gpt
> >label-id: 57F1B3D2-BE5F-4F4F-8875-415984544A0C
> >device: /dev/sde
> >unit: sectors
> >first-lba: 34
> >last-lba: 976773134
> >sector-size: 512
>
> ...
>
> >Comments/Problems: the installation fails to boot but only on the optiplex
> >7040, I took the M2 sata drive out of the dell optiplex 7040 and put it
> into
> >another PC and it boots normally.
> >I performed the same with nvme and normal disk drive, results were the
> same.
> >I updated bios and even tried manually configuring the boot entry in bios:
> >still will not boot on the 7040.
> >I tried booting to recovery mode from install media to reinstall boot
> loader:
> >sill no go on the 7040.
> >The information gouged out of the system is actually from Ubuntu 22.04 LTE
> >running on it at the moment ... but i would rather have Debian on it.
> >
> >No point sharing the install logs because the installation is fine and
> >functional on another computer.
> >There is something Debian does not like about my Dell Optiplex 7040 but
> at the
> >same time Fedora and Ubunto seem to work fine on my 7040.
> >What's up with debian not liking the 7040 ? Ubuntu 22.04 LTE and Fedora 40
> >install and boot normally there.
>
> When you say "fails to boot" here, what *exactly* do you mean please?
> Does the boot loader screen come up at all? Do you get kernel
> messages? What's the last thing you see?
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> Google-bait:   https://www.debian.org/CD/free-linux-cd
>   Debian does NOT ship free CDs. Please do NOT contact the mailing
>   lists asking us to send them to you.
>
>

Bug#1079139: Failed boot after install

[Pascal Hambourg]

On 20/08/2024 tat 18:55, louigi 600 wrote:

I dint think it even loads the grub efi file. System bios  complains it
can't boot from that device.


Did you try an expert install with GRUB in the "removable media path" 
when prompted ?



There is something Debian does not like about my Dell Optiplex 7040


Or rather something that your Optiplex does not like about Debian, if it 
complains and Debian did not.

Bug#1079139: Failed boot after install

[Rolf Reintjes]

Am 20.08.2024 um 19:28 schrieb Pascal Hambourg:

On 20/08/2024 tat 18:55, louigi 600 wrote:

I dint think it even loads the grub efi file. System bios  complains it
can't boot from that device.


Did you try an expert install with GRUB in the "removable media path" 
when prompted ?



There is something Debian does not like about my Dell Optiplex 7040


Or rather something that your Optiplex does not like about Debian, if it 
complains and Debian did not.


I googled and found this:

https://forums.debian.net/viewtopic.php?t=146225

Hey @bmc5311 , thank you very much for your post and solution! I just 
got a 2nd hand Dell Optiplex 3040 (updated to latest firmware) and after 
successfully installing Debian at the first try, I couldn't boot it, 
either with UEFI or legacy BIOS. With UEFI I got redirected to the Dell 
system check automatically.

To expand what you put in the pastebin with the right solution:
1) install Debian from USB as usual
2) reboot and it won't boot into Debian, with UEFI activated
3) reboot again in the installation media and select "Rescue mode" from 
the Grub advanced options
4) enter the rescue mode, configure keyboard etc and then choose to open 
a shell in the root partition (say yes to the /boot partition question)

5) at the prompt, execute `grub-install`
6) at the prompt, execute now `grub-install --removable`
7) poweroff, remove the USB key and reboot into Debian and enjoy it!

TBH I'm not sure step 5 is needed, I think that it is 6 that did the 
trick, but anyway it won't hurt.

Again, thanks for your help bmc5311!


May be this helps.

Rolf

Bug#1079139: Failed boot after install

[Matthew Dyer]

Hi,


I just happened to run in to this this morning on my asus desktop using 
debian testing.  Fedora works just fine.  The only difference is that I 
am using an external hard drive which is from cgate.  Just pointing this 
but have not tried a debaian stable image.  Intresting.



Matthew



On 8/20/2024 8:25 AM, louigi 600 wrote:

Package: installation-reports

Boot method: cat debian-12.6.0-amd64-DVD-1.iso > /dev/sda  (where sda 
is the where my system sees the usb stick)

             Then I proceed with normal graphical install


Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-12.6.0-amd64-DVD-1.iso
Not sure if I got it directly from the link above in any case here is 
the md5sum of what I have

462e540d1ba2ca5ecc68ab79c8e3788a

Date: 20/08/2024 was the last time I tried after changing target drive 
and updating bios


Machine: Dell Optiplex 7040 micro system
Processor: Intel(R) Core(TM) i7-6700T
Memory: 16Gb
Partitions:
label: gpt
label-id: 57F1B3D2-BE5F-4F4F-8875-415984544A0C
device: /dev/sde
unit: sectors
first-lba: 34
last-lba: 976773134
sector-size: 512

/dev/sde1 : start=        2048, size=     1048576, 
type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, 
uuid=347C9F36-3991-41AE-B5E9-74F13A4D09FD
/dev/sde2 : start=     1050624, size=   973721600, 
type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, 
uuid=8191A433-DF94-4157-90B5-DFD9A81BF058
/dev/sde3 : start=   974772224, size=     1998848, 
type=0657FD6D-A4AB-43C4-84E5-0933C84B4F4F, 
uuid=FAB1BEC7-BC34-486B-B1EF-42EC71E9042D


Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core 
Processor PCIe Controller (x16) [8086:1901] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD 
Graphics 530 [8086:1912] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 
Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation 100 
Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation 100 
Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
00:16.3 Serial controller [0700]: Intel Corporation 100 Series/C230 
Series Chipset Family KT Redirection [8086:a13d] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation 
Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI 
Mode] [8086:a102] (rev 31)
00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series 
Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1)
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series 
Chipset Family PCI Express Root Port #8 [8086:a117] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Q170 Chipset LPC/eSPI 
Controller [8086:a146] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 
Series Chipset Family Power Management Controller [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series 
Chipset Family HD Audio Controller [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset 
Family SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection (2) I219-LM [8086:15b7] (rev 31)
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co 
Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO [144d:a80a]
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 
Wireless Network Adapter [168c:0036] (rev 01)


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 installation fails to boot but only on the 
optiplex 7040, I took the M2 sata drive out of the dell optiplex 7040 
and put it into another PC and it boots normally.
I performed the same with nvme and normal disk drive, results were the 
same.
I updated bios and even tried manually configuring the boot entry in 
bios: still will not boot on the 7040.
I tried booting to recovery mode from install media to reinstall boot 
loader: sill no go on the 7040.
The information gouged out of the system is actually from Ubuntu 22.04 
LTE running on it at the moment ... but i would rather have Debian on it.


No point sharing the install logs because the installation is fine and 
functional on another computer.
There is something Debian does not like about my Dell Optiplex 7040 
but at the same time Fedora an

Bug#1079139: Failed boot after install

[Matthew Dyer]

Hi,


Also, i in my case, when trying to booot on my asus desktop, the system 
shutsdown when selected from the boot meenu.  Again this happens on the 
latest wekly image from testing.




On 8/20/2024 1:28 PM, Pascal Hambourg wrote:

On 20/08/2024 tat 18:55, louigi 600 wrote:

I dint think it even loads the grub efi file. System bios  complains it
can't boot from that device.


Did you try an expert install with GRUB in the "removable media path" 
when prompted ?



There is something Debian does not like about my Dell Optiplex 7040


Or rather something that your Optiplex does not like about Debian, if 
it complains and Debian did not.

Bug#1079175: python3-pkg-resources: pkg_resources cannot be imported: No module named 'packaging'

[Emanuele Rocca]

Package: python3-pkg-resources
Version: 72.2.0-1
Severity: serious
X-Debbugs-CC: debian-boot@lists.debian.org

[debian-boot added to CC as this issue breaks d-i builds]

Importing pkg_resources fails with the following error:

  (sid-amd64-sbuild)ema@ariel:~$ python3
  Python 3.12.5 (main, Aug  7 2024, 13:49:14) [GCC 14.2.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import pkg_resources
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 95, 
in 
  import packaging.specifiers
  ModuleNotFoundError: No module named 'packaging'

This is a regression in version 72.2.0-1, whereas 70.3.0-2 worked fine.

For an example of d-i build failure caused by this problem, see:
https://salsa.debian.org/installer-team/debian-installer/-/jobs/6155545 

It seems that installing python3-packaging, python3-jaraco.text, and
python3-platformdirs fixes it.

Re: Bug#1079175: python3-pkg-resources: pkg_resources cannot be imported: No module named 'packaging'

[Cyril Brulebois]

Control: affects -1 depthcharge-tools

Ciao ema,

Emanuele Rocca  (2024-08-20):
> Package: python3-pkg-resources
> Version: 72.2.0-1
> Severity: serious
> X-Debbugs-CC: debian-boot@lists.debian.org
> 
> [debian-boot added to CC as this issue breaks d-i builds]

Thanks for the heads-up, much appreciated.

> Importing pkg_resources fails with the following error:
> 
>   (sid-amd64-sbuild)ema@ariel:~$ python3
>   Python 3.12.5 (main, Aug  7 2024, 13:49:14) [GCC 14.2.0] on linux
>   Type "help", "copyright", "credits" or "license" for more information.
>   >>> import pkg_resources
>   Traceback (most recent call last):
> File "", line 1, in 
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 95, 
> in 
>   import packaging.specifiers
>   ModuleNotFoundError: No module named 'packaging'
> 
> This is a regression in version 72.2.0-1, whereas 70.3.0-2 worked fine.
> 
> For an example of d-i build failure caused by this problem, see:
> https://salsa.debian.org/installer-team/debian-installer/-/jobs/6155545 
> 
> It seems that installing python3-packaging, python3-jaraco.text, and
> python3-platformdirs fixes it.

I couldn't replicate the FTBFS within a devel sid chroot that has tons of
extra packages, including python3-packaging, and python3-platformdirs, but
not python3-jaraco.text.

Purging python3-platformdirs still gives me a successful build.

And from the error/call site quoted above, it seems python3-packaging
could be sufficient? (It doesn't list anything but python3:any in
Depends or Recommends…)

I haven't tried just adding python3-packaging under sbuild though, I'm
merely a little curious why the two other packages would be necessary.



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


signature.asc
Description: PGP signature