Boot Fails Before Login After New Install [SOLVED]

Help with issues regarding installation of Debian
Message
Author
debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#21 Post by debian-no »

Code: Select all

-- Journal begins at Thu 2021-08-05 19:53:18 CEST, ends at Thu 2021-08-05 23:44:48 CEST. --
Aug 05 22:48:49 debian6 kernel: secureboot: Secure boot could not be determined (mode 0)
Aug 05 22:48:49 debian6 kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Aug 05 22:48:49 debian6 kernel: TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details.
Aug 05 22:48:49 debian6 kernel:  #5 #6 #7
Aug 05 22:48:49 debian6 kernel: pci 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 05 22:48:49 debian6 kernel: r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 05 22:48:49 debian6 kernel: usb: port power management may be unreliable
Aug 05 22:48:49 debian6 kernel: CRAT table not found
Aug 05 22:48:49 debian6 kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Aug 05 22:48:49 debian6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 05 22:48:49 debian6 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 05 22:48:49 debian6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 05 22:48:49 debian6 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 05 22:48:49 debian6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 05 22:48:49 debian6 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 05 22:48:49 debian6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 05 22:48:49 debian6 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 05 22:48:49 debian6 systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Pl>
Aug 05 22:48:52 debian6 kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:08 [mem 0xfdb00000-0xfdffffff]
Aug 05 22:48:52 debian6 kernel: caller pmc_core_probe+0x7e/0x410 [intel_pmc_core] mapping multiple BARs
Aug 05 22:48:59 debian6 systemd-udevd[387]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with exit code 99.
Aug 05 22:49:06 debian6 smartd[600]: Device: /dev/sda [SAT], 13 Currently unreadable (pending) sectors
Aug 05 22:49:06 debian6 smartd[600]: Device: /dev/sda [SAT], 29 Offline uncorrectable sectors
Aug 05 22:49:08 debian6 dhclient[686]: Failed to get interface index: No such device
Aug 05 22:49:08 debian6 dhclient[686]: 
Aug 05 22:49:08 debian6 dhclient[686]: If you think you have received this message due to a bug rather
Aug 05 22:49:08 debian6 dhclient[686]: than a configuration issue please read the section on submitting
Aug 05 22:49:08 debian6 dhclient[686]: bugs on either our web page at www.isc.org or in the README file
Aug 05 22:49:08 debian6 dhclient[686]: before submitting a bug.  These pages explain the proper
Aug 05 22:49:08 debian6 dhclient[686]: process and the information we find helpful for debugging.
Aug 05 22:49:08 debian6 dhclient[686]: 
Aug 05 22:49:08 debian6 dhclient[686]: exiting.
Aug 05 22:49:08 debian6 systemd[1]: networking.service: Failed with result 'exit-code'.
Aug 05 22:49:08 debian6 systemd[1]: Failed to start Raise network interfaces.
Aug 05 22:49:10 debian6 udisksd[603]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 05 22:49:11 debian6 udisksd[603]: Failed to load the 'mdraid' libblockdev plugin
Aug 05 22:49:12 debian6 kernel: kauditd_printk_skb: 15 callbacks suppressed
Aug 05 22:49:21 debian6 blueman-mechani[586]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Aug 05 22:49:30 debian6 pipewire[1125]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Aug 05 22:49:59 debian6 pulseaudio[1126]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the messa>
Aug 05 22:50:22 debian6 lightdm[1197]: gkr-pam: unable to locate daemon control file
Aug 05 22:50:23 debian6 pulseaudio[1126]: Error opening PCM device front:0: Datei oder Verzeichnis nicht gefunden
Aug 05 22:50:23 debian6 pipewire[1222]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Aug 05 22:50:33 debian6 pipewire-media-session[1150]: error id:0 seq:158 res:-32 (Broken pipe): connection error
Aug 05 22:50:37 debian6 blueman-mechani[1676]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Aug 05 22:50:42 debian6 x-session-manager[1233]: WARNING: t+15,80066s: Detected that screensaver has appeared on the bus
Aug 05 22:50:48 debian6 pulseaudio[1223]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Aug 05 22:50:59 debian6 xdg-desktop-por[1361]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Aug 05 22:53:36 debian6 sudo[2401]:    john2 : user NOT in sudoers ; TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/bash
Aug 05 23:00:18 debian6 sudo[2525]:    john2 : user NOT in sudoers ; TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/bash
Aug 05 23:19:08 debian6 smartd[600]: Device: /dev/sda [SAT], 13 Currently unreadable (pending) sectors
Aug 05 23:19:08 debian6 smartd[600]: Device: /dev/sda [SAT], 29 Offline uncorrectable sectors
lines 1-53
Last edited by debian-no on 2021-08-05 21:50, edited 1 time in total.

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#22 Post by debian-no »

There is no more "user is not in the suduers-file" message anymore. I will get a new hard drive. The scan says error somewhere but I can hear it dying. .

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#23 Post by debian-no »

When i type sudo su it switches without any message so it worked right ?

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#24 Post by debian-no »

But when I type sudo su, after a reboot, it doesn't ask for the admin password. When I use sudo su it asks me for my user PW and I don't get that.

User avatar
sunrat
Global Moderator
Global Moderator
Posts: 3785
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 5 times
Been thanked: 16 times

Re: Boot Fails Before Login After New Install [SOLVED]

#25 Post by sunrat »

debian-no wrote: 2021-08-05 22:33 But when I type sudo su, after a reboot, it doesn't ask for the admin password. When I use sudo su it asks me for my user PW and I don't get that.
sudo creates elevated privileges for the user so asks the user password.
Don't use sudo su , if you want a root terminal session use su - and give root password. Having a root terminal open is more dangerous as you can inadvertently run a command as root which you didn't intend to and cause chaos.
sudo is designed to run a single command with root user privileges (and is safer than a root terminal session) so normal usage is

Code: Select all

sudo <command>
For example, say you want to edit your fstab file with nano:

Code: Select all

sudo nano /etc/fstab
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

mm3100
Posts: 255
Joined: 2020-10-21 21:39
Has thanked: 4 times
Been thanked: 7 times

Re: Boot Fails Before Login After New Install [SOLVED]

#26 Post by mm3100 »

If you are going to reinstall since you are changing your hard drive, in BIOS change few things. Enable secure boot, it will work fine with Debian.

As for those error messages I haven't found much, but it seems harmless. If system is working fine then it shouldn't be a problem.

While installing when it asks you for root password, don't write anything and just leave it blank and click on next. That will mark root password as locked, and it won't be available. So you can't login as root using su -. But then your user will be automatically added to sudo group and you will be able to use sudo from start.

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#27 Post by debian-no »

Hi,
I bought a fairly decent SSD and installed everything. Sudo shows up in groups and it went a lot faster than last time. When I install redshift for example I type this:
sudo apt install redshift
It then asks for the user pw. not the admin pw. I hope that's ok.
The same errors are there sadly. I have the log if someone wants to tell me if they have seen this before because I have very little experience with Linux.

Code: Select all

-- Journal begins at Sun 2021-08-08 21:19:46 IST, ends at Sun 2021-08-08 21:28:>
Aug 08 21:28:12 deb11 kernel: secureboot: Secure boot could not be determined (>
Aug 08 21:28:12 deb11 kernel: MDS CPU bug present and SMT on, data leak possibl>
Aug 08 21:28:12 deb11 kernel: TAA CPU bug present and SMT on, data leak possibl>
Aug 08 21:28:12 deb11 kernel:  #5 #6 #7
Aug 08 21:28:12 deb11 kernel: pci 0000:05:00.0: can't disable ASPM; OS doesn't >
Aug 08 21:28:12 deb11 kernel: r8169 0000:07:00.0: can't disable ASPM; OS doesn'>
Aug 08 21:28:12 deb11 kernel: usb: port power management may be unreliable
Aug 08 21:28:12 deb11 kernel: CRAT table not found
Aug 08 21:28:12 deb11 kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone >
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [>
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._>
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [>
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._>
Aug 08 21:28:12 deb11 kernel: ata5.00: supports DRM functions and may not be fu>
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [>
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._>
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [>
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._>
Aug 08 21:28:12 deb11 kernel: ata5.00: supports DRM functions and may not be fu>
Aug 08 21:28:12 deb11 systemd[1]: /lib/systemd/system/plymouth-start.service:16>
Aug 08 21:28:12 deb11 kernel: resource sanity check: requesting [mem 0xfdffe800>
Aug 08 21:28:12 deb11 kernel: caller pmc_core_probe+0x7e/0x410 [intel_pmc_core]>
lines 1-23...skipping...
-- Journal begins at Sun 2021-08-08 21:19:46 IST, ends at Sun 2021-08-08 21:28:52 IST. --
Aug 08 21:28:12 deb11 kernel: secureboot: Secure boot could not be determined (mode 0)
Aug 08 21:28:12 deb11 kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Aug 08 21:28:12 deb11 kernel: TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details.
Aug 08 21:28:12 deb11 kernel:  #5 #6 #7
Aug 08 21:28:12 deb11 kernel: pci 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 08 21:28:12 deb11 kernel: r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 08 21:28:12 deb11 kernel: usb: port power management may be unreliable
Aug 08 21:28:12 deb11 kernel: CRAT table not found
Aug 08 21:28:12 deb11 kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 08 21:28:12 deb11 kernel: ata5.00: supports DRM functions and may not be fully accessible
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 08 21:28:12 deb11 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 08 21:28:12 deb11 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 08 21:28:12 deb11 kernel: ata5.00: supports DRM functions and may not be fully accessible
Aug 08 21:28:12 deb11 systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Plea>
Aug 08 21:28:12 deb11 kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:08 [mem 0xfdb00000-0xfdffffff]
Aug 08 21:28:12 deb11 kernel: caller pmc_core_probe+0x7e/0x410 [intel_pmc_core] mapping multiple BARs
Aug 08 21:28:13 deb11 udisksd[550]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 08 21:28:13 deb11 udisksd[550]: Failed to load the 'mdraid' libblockdev plugin
Aug 08 21:28:13 deb11 blueman-mechani[538]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Aug 08 21:28:13 deb11 NetworkManager[542]: <warn>  [1628454493.3407] Error: failed to open /run/network/ifstate
Aug 08 21:28:14 deb11 dhclient[698]: Failed to get interface index: No such device
Aug 08 21:28:14 deb11 dhclient[698]: 
Aug 08 21:28:14 deb11 dhclient[698]: If you think you have received this message due to a bug rather
Aug 08 21:28:14 deb11 dhclient[698]: than a configuration issue please read the section on submitting
Aug 08 21:28:14 deb11 dhclient[698]: bugs on either our web page at www.isc.org or in the README file
Aug 08 21:28:14 deb11 dhclient[698]: before submitting a bug.  These pages explain the proper
Aug 08 21:28:14 deb11 dhclient[698]: process and the information we find helpful for debugging.
Aug 08 21:28:14 deb11 dhclient[698]: 
Aug 08 21:28:14 deb11 dhclient[698]: exiting.
Aug 08 21:28:14 deb11 systemd[1]: networking.service: Failed with result 'exit-code'.
Aug 08 21:28:14 deb11 systemd[1]: Failed to start Raise network interfaces.
Aug 08 21:28:14 deb11 kernel: kauditd_printk_skb: 16 callbacks suppressed
Aug 08 21:28:15 deb11 pipewire[797]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Aug 08 21:28:24 deb11 lightdm[1159]: gkr-pam: unable to locate daemon control file
Aug 08 21:28:24 deb11 pulseaudio[798]: Error opening PCM device front:0: No such file or directory
Aug 08 21:28:24 deb11 pipewire[1184]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Aug 08 21:28:31 deb11 x-session-manager[1195]: WARNING: t+6.15232s: Detected that screensaver has appeared on the bus
Aug 08 21:28:40 deb11 pulseaudio[1185]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
~
~
~
~
~
~
It's greatly appreciated.

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#28 Post by debian-no »

"sudo creates elevated privileges for the user so asks the user password."
So it's normal then.

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#29 Post by debian-no »

AMD CPU is better ? They say microcode won't need an upgrade with AMD.

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#30 Post by debian-no »

I'll try the best I can to fix them on my own but thank you for being nice.

mm3100
Posts: 255
Joined: 2020-10-21 21:39
Has thanked: 4 times
Been thanked: 7 times

Re: Boot Fails Before Login After New Install [SOLVED]

#31 Post by mm3100 »

You don't have to worry about those error messages, they are harmless, just make sure that you device will go back from sleep, screen will turn on after it shuts off, fan is running when temperature gets high.

As for rest of warning messages, they are all harmless as well, don't have to worry about them, they are common. And will hopefully one day be fixed. You can already remove most of them manually by adding or changing configuration files, but there is no need, as it changes nothing in functionality of the system.

I am only interested if you have turned secure boot on? As it says it can't say if it is on or off, if it is on there shouldn't be such message. Again, no difference in functionality of the system, if you don't care for secure boot there is nothing to worry about.

AMD is also x86, so I think it will need microcode upgrades as well. And they both can share same security issues, so microcode upgrades are necessary to mitigate them.

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#32 Post by debian-no »

Enabling secure boot in the bios will give me a black screen before anything happens. During the install secure boot worked. But starting the operating system doesn't. I removed the bios battery and power before the install. There are keys you can select but I don't know how to add any more than the "factory" ones. Maybe for later. First the microcode and this one "Failed to start Raise network interfaces". I would like to use secure boot it in some way.

mm3100
Posts: 255
Joined: 2020-10-21 21:39
Has thanked: 4 times
Been thanked: 7 times

Re: Boot Fails Before Login After New Install [SOLVED]

#33 Post by mm3100 »

Secure boot should work with Debian, for that question please start new thread. Since this thread is solved.

For "Failed to start Raise network interfaces" it is because there are no configuration files in /etc/network/interfaces.d/*. Ifupdown is looking there but can't find anything. To 'solve' that you can comment out source /etc/network/interfaces.d/* with # in /etc/network/interfaces. But there is no need to do that really. As it isn't really an error.

As for microcode you don't have to worry about it, if you have intel-microcode and or amd64-microcode installed you are all set.

debian-no
Posts: 33
Joined: 2021-08-04 14:08

Re: Boot Fails Before Login After New Install [SOLVED]

#34 Post by debian-no »

The one from the bios doesn't work. I updated the microcode with this method

Code: Select all

Build your own intel-microcode package

    Add your favorite mirror to/etc/apt/sources.list:

deb-src https://mirrors.kernel.org/debian/ sid main non-free

2. Update apt, build the package, install it, reboot

sudo apt-get update
sudo apt-get build-dep intel-microcode
sudo apt-get -b source intel-microcode
sudo dpkg -i imicrocode(your version cd: /home)64.deb
sudo reboot
And for the other mds error I disabled hyper threading. This is the log now and thank you for helping.

Code: Select all

-- Journal begins at Mon 2021-08-09 16:36:01 IST, ends at Tue 2021-08-10 12:08:32 IST. --
Aug 10 11:50:02 debian12 kernel: secureboot: Secure boot could not be determined (mode 0)
Aug 10 11:50:02 debian12 kernel: pci 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 10 11:50:02 debian12 kernel: r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 10 11:50:02 debian12 kernel: usb: port power management may be unreliable
Aug 10 11:50:02 debian12 kernel: CRAT table not found
Aug 10 11:50:02 debian12 kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Aug 10 11:50:02 debian12 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 10 11:50:02 debian12 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 10 11:50:02 debian12 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 10 11:50:02 debian12 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 10 11:50:02 debian12 kernel: ata5.00: supports DRM functions and may not be fully accessible
Aug 10 11:50:02 debian12 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 10 11:50:02 debian12 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 10 11:50:02 debian12 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Aug 10 11:50:02 debian12 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Aug 10 11:50:02 debian12 kernel: ata5.00: supports DRM functions and may not be fully accessible
Aug 10 11:50:02 debian12 systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process l>
Aug 10 11:50:02 debian12 kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:08 [mem 0xfdb00000-0xfdffffff]
Aug 10 11:50:02 debian12 kernel: caller pmc_core_probe+0x7e/0x410 [intel_pmc_core] mapping multiple BARs
Aug 10 11:50:02 debian12 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201]>
Aug 10 11:50:02 debian12 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201]>
Aug 10 11:50:03 debian12 udisksd[523]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 10 11:50:03 debian12 udisksd[523]: Failed to load the 'mdraid' libblockdev plugin
Aug 10 11:50:03 debian12 blueman-mechani[509]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Aug 10 11:50:03 debian12 NetworkManager[514]: <warn>  [1628592603.5849] Error: failed to open /run/network/ifstate
Aug 10 11:50:03 debian12 dhclient[655]: Failed to get interface index: No such device
Aug 10 11:50:03 debian12 dhclient[655]: 
Aug 10 11:50:03 debian12 dhclient[655]: If you think you have received this message due to a bug rather
Aug 10 11:50:03 debian12 dhclient[655]: than a configuration issue please read the section on submitting
Aug 10 11:50:03 debian12 dhclient[655]: bugs on either our web page at www.isc.org or in the README file
Aug 10 11:50:03 debian12 dhclient[655]: before submitting a bug.  These pages explain the proper
Aug 10 11:50:03 debian12 dhclient[655]: process and the information we find helpful for debugging.
Aug 10 11:50:03 debian12 dhclient[655]: 
Aug 10 11:50:03 debian12 dhclient[655]: exiting.
Aug 10 11:50:03 debian12 systemd[1]: networking.service: Failed with result 'exit-code'.
Aug 10 11:50:03 debian12 systemd[1]: Failed to start Raise network interfaces.
Aug 10 11:50:03 debian12 kernel: kauditd_printk_skb: 17 callbacks suppressed
Aug 10 11:50:04 debian12 pipewire[749]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop':>
Aug 10 11:50:30 debian12 pulseaudio[750]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote appli>
Aug 10 11:50:33 debian12 lightdm[1105]: gkr-pam: unable to locate daemon control file
lines 2-41

Post Reply