#1136213 Can't re-install Debian after previous installation broke

#1136213#5
Date:
2026-05-10 20:42:41 UTC
From:
To:
Boot method: <Ventoy USB Stick>
Image version: <https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-13.4.0-amd64-kde.iso>
Date: <May 10, 10 PM>

Machine: <Laptop HP 350 G2>
Processor: i5-5200U
Memory: 16 GB RAM
Partitions: <1 TB SSD, partitioned as MBR>

Output of lspci -knn (or lspci -nn): Not sure what this is.

Base System Installation Checklist:
Can't do this step.



Comments/Problems:

<
Hi,

I can't install debian for a second time after breaking the previous
installation.

- My main OS is Windows, and I wanted to try Linux, so I installed
Linux Mint first, then installed Debian, as a dual-boot system, and
formatted the previous Linux Mint partition in the process.
- Using the Live Debian ISO, the first installation worked fine. The
Live ISO booted, and then I installed it successfully.
- However, video playback had stuttering issues. So I used Claude.AI
to try and fix them. Specifically I used some terminal commands, these
are some of the ones I used:
"sudo nano /etc/modprobe.d/i915.conf", then I wrote there "options
i915 enable_psr=0 enable guc=2" then save, enter, exit.)
- More commands have been used, and I don't remember which ones I
used, and I don't know exactly which ones caused the issue.
- The issue: after applying these commands and restarting the PC - the
bootloader was broke, and could not load any OS.
- After some Claude.AI suggestions (pressing E at bootup, adding some
commands after Linux) Debian booted, but it shut down abruptly after
loading the desktop.
- Seeing that I can't fix it, I loaded a Zorin Live OS from the same
Ventoy USB and installed it.
- This way, I regained access to Windows, my files, and currently have
Zorin OS installed.
- But I want to install Debian instead.
- The current issue: After plugging in the Ventoy USB stick, selecting
the Live ISO from the USB stick, the laptop shows a black screen
error: "[ 0.018339] [Firmware Bug]:
TSC_Deadline disabled due to Errata; please update microcode to
version: 0x25 (or later)" - which is not shown when booting any other
OS, installed, or from the Ventoy stick - then Debian continues
loading, it shows the desktop for 2-3 seconds, and then it shows a
black screen error: "Broadcast message from root@debian (current date)
The system will power off now!" and it shuts down abruptly! So the
issue is I can't install Debian, even though I installed it before
from the same USB stick, on the same laptop.
- Other details: The ventoy USB stick is installed/formatted as MBR
because my SSD drive is also formatted as MBR, and the laptop is using
legacy BIOS. So when trying to install, I select the non-UEFI Ventoy
stick, and make sure at every step needed I choose MBR/legacy BIOS
installation. I do not use an EFI partition.
- I tried deleting the ISO from the USB stick thinking it may have
gotten corrupted, and downloaded a new one - same issue.
- I checked the checksum number - it is correct.
- Other ISOs from the same Ventoy USB stick load fine (mint, Zorin,
Hiren's Boot CD PE, etc.) only specifically the Debian Live ISO
doesn't boot.
- The only theory I could think of is that some GRUB / bootloader
files remained either on the bootloader partition on the internal SSD
or the USB stick, and it loads those wrong settings from the broken
Debian installation.
- I am going to try: testing a different Debian DESKTOP (gnome instead
of KDE) Live ISO, possibly re-format the Ventoy USB stick and re-add
the Live ISOs. These are the only things I can think of.
- What else could be the issue, and how can I fix it?

Thank you.

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

#1136213#10
Date:
2026-05-10 22:13:25 UTC
From:
To:
Hi,

Is sending an email to this unique address the right way to reply to a
ticket? I didn't know and sent another ticket.

Here is the update:

In the ticket number #1136213 -  I said I would try:

- Add Debian Gnome Live ISO to the Ventoy USB stick and try booting it
- Format the Ventoy USB stick and add the Debian KDE Live ISO again and try
it.

I have tried both. None have worked.

So right now the situation is:

- Debian ISOs worked on this PC, from this Ventoy USB stick before.
- Other Operating Systems ISOs work currently on this Ventoy USB stick, on
this PC.
- The issue is not in the Ventoy USB stick, or the ISOs, or in the general
PC hardware/BIOS.

It is specifically something that I broke in the previous Debian
installation, perhaps it broke something in BIOS, or the bootloader, or
there are some broken settings leftover in the System Reserved partition of
Windows that remember Debian as a broken ISO.

Please help me fix this issue.

If it is of any help, here are links to the Claude Chats I had, and the
commands it was telling me to input.

Chat 1: (mostly unrelated, I was dealing with other issues):
https://claude.ai/share/fabedd0c-9c0d-424b-a5c8-dd3bf4f6006b

Chat 2: (The MAIN chat which dealt with the boot up issue):
https://claude.ai/share/36901de2-7691-41cf-993f-4d454e132f7f

Thank you!

#1136213#15
Date:
2026-05-10 23:41:05 UTC
From:
To:
Hi,

I was able to fix part of the issue with a VERY COMPLETE shut down, however
the other issues persist.

I turned off fast start up in Windows, I shut down the PC, I unplugged
every single cable, the MicroSD adapter with the SD card, the laptop
battery, and let it sit like this for about 5 minutes.

After this I plugged in the Ventoy USB, selected the Live Debian ISO, and
it showed me the black screen error with the firmware, microcode, etc.

However this time Debian booted and stayed booted.

The second error appeared also: When I click to shut down Debian/ the PC, a
black screen appeared with the text "power will be turned off now!",
however, I could tell that the PC did not shut down abruptly like before,
but shut down normally.

So these 2 black screen errors still persist, and they did not exist before.

Any idea what could be causing them and how to fix them?

Thank you.