Boot method: Loading iso and put it on an USB-Stick with 'USB-
Abbilderstellung' (ministick.py)
Image version: debian-12.4.0-amd64-DVD-1.iso
(https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-12.4.0-amd64-DVD-1.iso
)
Date: 23.12.23, 19:00

Machine: <Dell xps-13 9380, BIOS 1.26.0 9/11/2023
Processor: amd64
Memory: 8GB
Partitions: created by debian installer: p1: EFI, p2: system, p3:swap,
p4: /home

Output of lspci -knn (or lspci -nn): not possible, system goes into
kernel panic

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 (graphical installer) went fine. I allowed to use the
whole disk.
Reboot after successful installation:
Start in a start screen with selection of 3 items.
When booting (first item), message on Debian screen: "Arbeitsspeicher
erschöpft" ("Memory exhausted").
Then start in a black terminal screen with Kernel panic: "Kernel panic
- not syncing: VHS Unable to mount root fs on unknown-block(0,0)"
I found no logs on the usb-stick

It matches the German translation for "out of memory" in GRUB.

It looks like a consequence of GRUB failure to load the initramfs properly.

Le 26/12/2023 à 20:35, Christian Kirsch wrote:

Basically, the Debian installer just installs required grub packages and
runs grub-install and update-grub in the target system environment so if
GRUB loads and displays the menu, it is unlikely that the installer did
something wrong.

After booting into Debian through Ubuntu's GRUB menu, you can try to
re-run these commands and reboot with Debian GRUB. If it does not fix
the error, then the issue probably lies in GRUB itself and the bug may
be reassigned to grub2.

I forgot to mention it, but please also reply to the bug report address,
not only me.

I wonder which one was actually needed. I should have suggested to run
one and reboot, then run the other one only if the issue persisted.

So maybe GRUB was not properly installed after all. But I am failing to
figure out what could have gone wrong. Can you compress and attach the
installation log (/var/log/installer/syslog) please ?

That's right. I always run an 'update-grub' first to check whether
everything is running correctly and is recognized properly. In doing
so, I came across the message that the 'OS-prober' is missing.
Probably grub-install would have sufficed.

However:
syslog is attached


Am Mittwoch, dem 27.12.2023 um 12:40 +0100 schrieb Pascal Hambourg: