I Would Like to Clean Install Debian 13 and Wandering...

[Trml]

--More--

There is a LOT more. But I do not know how much to post/is needed.

You posted the beginning of the kernel messages while it boots. There is absolutely nothing going wrong in the lines you posted. The kernel will prefix warnings, errors, etc and the command lets you view its last boot log, i.e. no need to make screenshots unless it crashes booting.

What I forgot suggesting dmesg |more is that the piped "| more" removes the coloured output which makes it easier to spot severe errors. If you omit it, you can simply scroll back and look for red lines. These are ones you may want to have a look at.

 

[ZennMystic]

I did not see any red lines at all.

I also seemed to have fixed the slow boot when USB drive it in by re-formatting the drive and putting the data I want to keep back on it.

I re-took some screen shoot of the issues I am having at boot time. Hopefully something can been seen this time.
I think as long as you do not zoom in to far.

Chat GPT told me to try a grep command instead of image I go this:
$ sudo dmesg | grep -iE 'ACPI BIOS Error|AE_ALREADY_EXISTS|During name lookup/catalog|XHCI\.RHUB\.HS14'
[sudo] password for zenn:
[ 0.208466] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.SADX], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208474] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208478] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.SADS], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208481] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208484] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14._DSM], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208486] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208488] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.BTRT], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208490] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208507] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14._PRR], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208509] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208511] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.BRDY], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208513] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208516] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.BGAP], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208519] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208522] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.BRDS], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208526] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.ECKY], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208528] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208531] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.ECKV], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208533] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208535] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.GPCX], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208537] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208541] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.GPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208544] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208546] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.GLAX], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208548] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208551] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.GLAI], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208553] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208555] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.BTLY], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208557] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.208561] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS14.BTLC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[ 0.208563] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[ 0.249204] ACPI: \SB.PC00.XHCI.RHUB.HS14.BTRT: New power resource


Additional Adturquoise warning lines visible below the ACPI block (best effort):
i915 0000:00:02.0: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]
sd 8:0:0:0: [sda] No Caching mode page found
sd 8:0:0:0: [sda] Assuming drive cache: write through
nvme nvme0: using unchecked data buffer
platform INT3515:01: deferred probe pending: Serial bus multi instantiate pseudo device driver: Error creating i2c-client, idx 0

I am sight impaired so I am not sure, is the best I can do to show the issues/warning/errors I am getting.
I did not have any of this issue with Debian 12.I know.

Chat GPT said it is a effi/bios issue and to update my bios. I did that and my bios is now up to date as far as know. But it did not solve this issue.

 

[Trml]

I re-took some screen shoot of the issues I am having at boot time.

Yes, these are easy to read, thanks!
Just saying: you can trust dmesg has all of them. So, if you later scroll through them in terminal, you can also screenshot snippets more easily than at boot.

As for the messages:

Additional Adturquoise warning lines visible below the ACPI block (best effort):
i915 0000:00:02.0: disabling ...

These are no issue.

[\_SB.PC00.XHCI.RHUB.HS14.SADS], AE_ALREADY_EXISTS (20240827/dswload2-326)

These may hint to a misconfiguration of USB options in Bios, or simply its bugs. The prefix "_SB" stands for the ACPI (power management) subsystem. I'd be surprised if these messages are new with Debian 13, but it is something its newer kernel can indeed produce. Nothing fatal, it can deteriorate throughput to USB devices, for example.

Have a look at the Bios options for USB, Harddrive (ACPI/AHCI/SATA keywords) and power management configuration. Perhaps make a screenshot of the ones you have set for USB/HDD to discuss, and also state the motherboard model (ideally a link to manufacturer support for the handbook, if exists).

 

[ZennMystic]

I have not been able to find the manual for my computer. It was something I spent time looking for when all this started.
I did after I started having issues got to the MSI site/support and update my bios. Did not help with the warning though.

I am not sure what menus/sub menus you want screen shots of, so here are a few.

 

[Brickwizard]

I have not been able to find the manual for my computer.

what is the Make and full model number?

 

[ZennMystic]

Good question! I have know idea!
It was built from parts bought at the MicroCenter store, a few years ago.

~$ hostnamectl
Static hostname: debian13-PC
Icon name: computer-desktop
Chassis: desktop ️
Machine ID: 7b5e83721a2e42d4a69eb38dba6774ea
Boot ID: 2a378cce9ecd4290b2d513cd1afb2875
Operating System: Debian GNU/Linux 13 (trixie)
Kernel: Linux 6.12.74+deb13+1-amd64
Architecture: x86-64
Hardware Vendor: Micro-Star International Co., Ltd.
Hardware Model: MS-7D25
Firmware Version: 1.M0
Firmware Date: Fri 2025-08-08
Firmware Age: 7month 1w 5d

 

[Brickwizard]

Here is a link to the MSI motherboard docs...
https://www.manualslib.com/manual/3507083/Msi-Pro-Z690-A-Wifi-Ddr4.html#product-PRO Z690-A WIFI DDR4

 

[ZennMystic]

Good question! I have know idea!
It was built from parts bought at the MicroCenter store, a few years ago.

~$ hostnamectl
Static hostname: debian13-PC
Icon name: computer-desktop
Chassis: desktop ️
Machine ID: 7b5e83721a2e42d4a69eb38dba6774ea
Boot ID: 2a378cce9ecd4290b2d513cd1afb2875
Operating System: Debian GNU/Linux 13 (trixie)
Kernel: Linux 6.12.74+deb13+1-amd64
Architecture: x86-64
Hardware Vendor: Micro-Star International Co., Ltd.
Hardware Model: MS-7D25
Firmware Version: 1.M0
Firmware Date: Fri 2025-08-08
Firmware Age: 7month 1w 5d

Thank You
I will read.

 

[Trml]

I am not sure what menus/sub menus you want screen shots of, so here are a few.

Your second screenshot lists the keywords I mentioned (top menus up to USB). Best is you reset it to Bios defaults and have another boot first though. I think that's a mainboard with excellent Linux support. You can even get some coreboot supported bios for this mainboard model, which is testament of its support.

I'd say you should simply disregard the messages, unless you experience issues and see red messages. It's much easier to follow up on something specific rather than kernel messages that appear just informational. By the way, rather than going back to Debian 12, I'm sure the Debian repo has the Deb12 kernel. You could just install that and see if it makes a difference to the messages. Yet, this is all a lot of fishing around when there is nothing obvious going wrong.

 

[ZennMystic]

Your second screenshot lists the keywords I mentioned (top menus up to USB). Best is you reset it to Bios defaults and have another boot first though. I think that's a mainboard with excellent Linux support. You can even get some coreboot supported bios for this mainboard model, which is testament of its support.

I'd say you should simply disregard the messages, unless you experience issues and see red messages. It's much easier to follow up on something specific rather than kernel messages that appear just informational. By the way, rather than going back to Debian 12, I'm sure the Debian repo has the Deb12 kernel. You could just install that and see if it makes a difference to the messages. Yet, this is all a lot of fishing around when there is nothing obvious going wrong.

I am not clear on what you are saying.

You are saying:

#1 Load bios defaults? I did this.
#2 Change the boot order? Yes No? To?
#3 Otherwise ignore all the messages?
#4 Try/Do something else?

Ignoring is doable I guess. But it does mean that at boot up and shut down, my screen is literally completely filed with warning and such.
While boot up still seems very fast, shut down can sometimes take a fair bit of time (but not always.)

It just would have been nice to have everything setup so their are not warnings. I read I can disable the messages but would prefer not to in case that one time something serious does happen.

I just wonder if there is something I have not setup right, that if I flick this switch or tweak this knob all will be fixed.
Anyway as it is right now anything more than loading the defaults is beyond me and would need the assist of someone who understands all this a lot better than I do.

Chat GPT says some kind of table/USB table is being loaded twice and the is what is causing the warning/issues. For whatever that is worth/means.

 

[GatorsFan]

The AE_ALREADY_EXISTS error is an ACPI (Advanced Configuration and Power Interface) BIOS error that indicates a failure in creating a named object during the system's boot process. which are often harmless and can be ignored. These errors are common and usually do not affect system stability, but if you experience other issues, it may be worth investigating further.

 

[GatorsFan]

Did you encrypt your drive? did you use LUKS Encryption? did you make a backup of your LUKS Headers?

 

[ZennMystic]

Did you encrypt your drive? did you use LUKS Encryption? did you make a backup of your LUKS Headers?

No after starting to get warnings I want back and reformatted the drive and chose the most general option to install Debian (The use whole drive, for new/most users option.)

No I haven't experienced any other issues one the OS is up, all seems to be fine.

 

[Trml]

Chat GPT says some kind of table/USB table is being loaded twice and the is what is causing the warning/issues. For whatever that is worth/means.

Chat GPT just munges the messages you prompt and churns them into complete paragraphs. I'm actually impressed just how bad that model (free one) stays for Linux (in general) - total waste of time.

#1 Load bios defaults? I did this.
#2 Change the boot order? Yes No? To?
#3 Otherwise ignore all the messages?
#4 Try/Do something else?

1. Ok. I asked that because Bios updates may mess up previous settings, e.g. MSI moves items around but existing settings get lost. Defaults are the best base.
2. If you regular boot order is from HDD/SDD/NVME, no. My point was: What you see are kernel messages and if you experience problems, installing the Debian 12 kernel to test is easier than ditching the whole install of Debian 13. Installing the old kernel will create new Grub entries for it, letting you choose at boot.
3. Yes, only do 2. or troubleshoot if you notice errors.
4.1. As said, you can have a look at the Bios menus for ACPI etc (the first entries up to USB). If unsure an entry is good, post it so others can have a look
4.2. Once you experienced a slow shutdown, note the date/time so you can have a look at the journal the next time. For example, with journalctl -b -1 --no-pager | tail -100 output you see last 100 journal entries of the last shutdown with timestamps. It may tell you what took long.

 

[ZennMystic]

OK TY I will look.