[SOLVED] Some Boot trouble I have. Can someone help plz?

j081 · 2026-01-11 17:00:34

Hey everyone,
Total Noob here, trying to get my feet wet.
I bought an rather old used Thinkpad E460 with Win 11 Pro on it. Because the purpose of this purchase was to get away from win, i killed win instantly and installed arch instead. Unfortunately this might have been a bit rushed, because the BIOS on this machine was very old. But at that point I couldn't use the win BIOS update anymore.
Well, so my first challenge was to update the BIOS using arch. Accepted, even though I'm a bit unsure if i did everything correctly.
Here is what i did:
I loaded the latest BIOS Update (Bootable CD) .iso from Lenovo. Because this is just flashable using a CD emulation, I installed geteltorito via AUR and somehow managed to flash a usb with it.
This was then used to update the Bios. Even though there was a warning i cannot recall anymore, the Laptop boots and works fine as far as i can tell.
Here is my current setup and the Errors/Warnings I found.
Maybe someone is able to answer one or some of the questions. Or point me to some useful resources, as I'm a bit overwhelmed right now.

             ______  ____ ___    j081@Sandbox6
            / / __ \( __ <  /    -------------
       __  / / / / / __  / /     OS: Arch Linux x86_64
      / /_/ / /_/ / /_/ / /      Host: 20ET004GGE (ThinkPad E460)
    __\____/\____/\____/_/ __    BIOS (UEFI): R00ET69W (1.44 ) (1.44)
   /   |  / __ \/ ____/ / / /    Kernel: Linux 6.18.4-arch1-1
  / /| | / /_/ / /   / /_/ /     Uptime: 3 hours, 12 mins
 / ___ |/ _, _/ /___/ __  /      Packages: 589 (pacman)
/_/  |_/_/ |_|\____/_/ /_/       Shell: bash 5.3.9
                                 Display (CMN14B1): 1920x1080 in 14", 60 Hz
                                 WM: dwm (X11)
                                 Cursor: Adwaita
                                 Terminal: st 0.9.3
                                 Terminal Font: JetBrainsMono Nerd Font (17pt)
                                 CPU: Intel(R) Core(TM) i7-6500U (4) @ 3.10 GHz
                                 GPU 1: AMD Radeon R7 M360 [Discrete]
                                 GPU 2: Intel HD Graphics 520 @ 1.05 GHz [Integrated]
                                 Memory: 1.72 GiB / 7.53 GiB (23%)
                                 Swap: 0 B / 3.76 GiB (0%)
                                 Disk (/): 6.39 GiB / 48.90 GiB (13%) - ext4
                                 Disk (/home): 413.07 MiB / 865.60 GiB (0%) - ext4
                                 Local IP (wlp1s0): 192.168.1.151/24
                                 Battery (LNV-45N1): 100% [AC Connected]
                                 Locale: en_US.UTF-8

I found the following Errors when looking into journal -b:
1)

Jan 11 14:42:20 Sandbox6 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.
Jan 11 14:42:20 Sandbox6 kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html>
Jan 11 14:42:20 Sandbox6 kernel: VMSCAPE: SMT on, STIBP is required for full protection. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/vmscape.html for more details.

Looking at the provided links, this sounds a bit like hypothetical vulnerabilities, but I could be mistaken. Do I need to do something about them?
And is there even a thing i can do as this seems hardware related.

2) I put them in the same block, as they might be related to another:

Jan 11 14:42:20 Sandbox6 kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
...
Jan 11 14:42:20 Sandbox6 kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [TBF3] at bit offset/length 262144/32768 exceeds size of target Buffer (262144 bits) (20250807/dsopcode-198)
Jan 11 14:42:20 Sandbox6 kernel: ACPI Error: Aborting method \_SB.PCI0.GFX0.GETB due to previous error (AE_AML_BUFFER_LIMIT) (20250807/psparse-529)
Jan 11 14:42:20 Sandbox6 kernel: ACPI Error: Aborting method \_SB.PCI0.GFX0.ATRM due to previous error (AE_AML_BUFFER_LIMIT) (20250807/psparse-529)
Jan 11 14:42:20 Sandbox6 kernel: [drm:amdgpu_get_bios [amdgpu]] *ERROR* failed to evaluate ATRM got AE_AML_BUFFER_LIMIT
...
Jan 11 14:42:22 Sandbox6 kernel: ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00000005A) is beyond end of object (length 0x5A) (20250807/exoparg2-393)
Jan 11 14:42:22 Sandbox6 kernel: ACPI Error: Aborting method \_SB.WMI1.WQA0 due to previous error (AE_AML_PACKAGE_LIMIT) (20250807/psparse-529)

I already did some research on this, and the general advise i found was not to care about it, as this is due to the old hardware. But i could be wrong. If there is anything i can do about it please let me know.

3)

Jan 11 14:42:20 Sandbox6 kernel: ata1.00: Model 'Samsung SSD 870 EVO 1TB', rev 'SVT03B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati nolpmonati

I didn't really find much about this one. Can't make sense of it. Just that the kernel is using some kind of workarounds for compatibility reasons. Whatever that means.

4)

Jan 11 14:42:20 Sandbox6 kernel: ata1.00: supports DRM functions and may not be fully accessible

This is what i found about it:
"There's an extension of the ATA protocol (the "language" spoken between your mainboard and your SATA SSDs), which allows for the storage device to reply differently, depending on whether a request was signed by the trusted platform module on the mainboard. That way, things like video player devices that only give access to the stored data when the software has proven itself to be unmodified can be implemented. (I can find much more interesting use cases, but digital rights management seems to be what the kernel authors saw as the application for this when they implemented that warning.) That also means that Linux might simply get an "incomplete" view of the SSD, hence it warns you about that, in case you wonder."
Again can and should I do something about it, and what is meant by 'incomplete view of the SSD'?

5)

Jan 11 14:42:21 Sandbox6 kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

I didn't find anything helpful for this one yet.

6)

Jan 11 14:42:21 Sandbox6 kernel: at24 8-0052: supply vcc not found, using dummy regulator

Here is what I found so far, but no clue what to do about it:
"From the sound of the error, something is missing a supply voltage."

7)

Jan 11 14:42:21 Sandbox6 kernel: Bluetooth: hci0: Reading supported features failed (-16)
Jan 11 14:42:21 Sandbox6 kernel: Bluetooth: hci0: Error reading debug features
Jan 11 14:42:21 Sandbox6 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.

rfkill gives me:

ID TYPE      DEVICE                   SOFT      HARD
 0 bluetooth tpacpi_bluetooth_sw unblocked unblocked
 1 bluetooth hci0                unblocked unblocked
 2 wlan      phy0                unblocked unblocked

Thanks for any hint, advise or classification of any of these.

Last edited by j081 (2026-01-17 10:01:04)

cryptearth · 2026-01-11 20:09:50

j081 wrote:

5)
Jan 11 14:42:21 Sandbox6 kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
I didn't find anything helpful for this one yet.

https://wiki.archlinux.org/title/Networ … ory_domain

j081 wrote:

6)
Jan 11 14:42:21 Sandbox6 kernel: at24 8-0052: supply vcc not found, using dummy regulator
Here is what I found so far, but no clue what to do about it:
"From the sound of the error, something is missing a supply voltage."

likely related to the acpi bugs

as for the cpu issues: yes, old hardware - unless intel offers some microcode update nothin to do about, maybe disable HyperThreading

seth · 2026-01-11 20:46:40

3)
https://wiki.archlinux.org/title/Solid_ … leshooting (NCQ, Trim and LPM) - but you don't have to anything about that, the kernel just informs you that some quirks are applied because of the detected model

7)
Does BT ultimately work and is this a dual-boot system?

Sanity check

cryptearth wrote:

as for the cpu issues: yes, old hardware - unless intel offers some microcode update

You do have installed the https://wiki.archlinux.org/title/Microcode patches ?

j081 · 2026-01-12 00:29:56

First of all, thank you so much for taking your time to give feedback and search and provide these links for me!!! You are gold!
I managed to resolve 5) thanks to your help. And I'm no longer concerned about 2) and 3). I'm guessing 4) might be related to 3) and therefore also not concerning?
Ah and a detail which might be of relevance: I have secure boot enabled and my root- and data partitions luks encrypted.

seth wrote:

Does BT ultimately work and is this a dual-boot system?

No, there is no dual boot. (No Linux/Win)
But, i have a lts-kernel and the normal one. Is this also considered dual boot? Then yes.
I didn't try/check bluetooth yet. Will hopefully find the time to do so tomorrow.
Maybe the vcc- and bluetooth errors/warnings are related? Just guessing at this point. Will get back to it tomorrow, later.

seth wrote:

You do have installed the https://wiki.archlinux.org/title/Microcode patches ?

No, they were not installed, but are now. Thanks.

Aaaand there is another one. I was quite sure I had this already resolved. But either this reoccurred, or I was blind and missed it before my first post:

Jan 12 00:50:33 Sandbox6 dbus-broker-launch[863]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.

:-/
Have a good start into the week you two. <3
j.

Last edited by j081 (2026-01-12 00:36:29)

j081 · 2026-01-12 00:51:44

cryptearth wrote:

likely related to the acpi bugs
as for the cpu issues: yes, old hardware - unless intel offers some microcode update nothin to do about, maybe disable HyperThreading

No, installing microcode update and disabling hyper threading didn't resolve this. But thanks for the idea.

j081 · 2026-01-12 01:52:47

seth wrote:

3)
https://wiki.archlinux.org/title/Solid_ … leshooting (NCQ, Trim and LPM) - but you don't have to anything about that, the kernel just informs you that some quirks are applied because of the detected model

Well there might be some updates out there, just not provided via this this tool. Or how should I understand this info? I just updated with the Lenovo BIOS Update (Bootable CD) r00uj31wd.iso. This is from 22 Jul 2022.

[j081@Sandbox6 ~]$ fwupdmgr get-updates
Devices with no available firmware updates:
 • Database Key
 • Key Exchange Key
 • KEK CA
 • Option ROM UEFI CA
 • SSD 870 EVO 1TB
 • System Firmware
 • UEFI Device Firmware
 • Windows UEFI CA
Devices with the latest available firmware version:
 • UEFI CA
No updates available

Will also look into this tomorrow.

seth · 2026-01-12 08:41:18

But, i have a lts-kernel and the normal one. Is this also considered dual boot? Then yes.

No. The problems arise when using two different OS (at the same time, 3rd link below and there're additional "problems" w/ bluetooth pairing)

No, installing microcode update and disabling hyper threading didn't resolve this. But thanks for the idea.

Fwwi, https://wiki.archlinux.org/title/Improv … itigations

fwupdmgr found an update for your UEFI, not for the drive and (3) isn't related to (4) - (4) is "just fyi" and you can possibly disable this in the UEFI and it should™ be gone if you disable the TPM

Edit:

 Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.

just means that you're not using systemd-resolved, which isn't necessary either.
https://wiki.archlinux.org/title/Networ … _not_found

Last edited by seth (2026-01-12 08:46:58)

j081 · 2026-01-13 00:12:28

so, here is an update:

1) resolved
2) not resolved, but as all seems to work fine and other sources as well as the comments here agree this is probably due to the rather old laptop (which works fine btw), I will file this as, is probably not of concern as long as it works. Fingers crossed.
3) nothing bad.
4) not resolved. Disabling TPM didn't change this, so I turned it back on. But as I now know what it is, I don't really mind anymore that much. Maybe because the discs are encrypted DRM cries about this?
5) resolved.
6) still no idea. But don't mind. Also just an info/warning.
7) this is still there, but bluetooth works fine with bluetoothctl. So i have no clue what this error is about. Reading the whole bluetooth block, this is just about some 'supported features', probably also due to the rather old laptop?

Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Waiting for firmware download to complete
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Firmware loaded in 1386108 usecs
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Waiting for device to boot
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Device booted in 10717 usecs
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Reading supported features failed (-16)
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: Error reading debug features
Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.

8) ok, also nothing to worry about. But nevertheless I followed the link created this file:

/etc/NetworkManager/conf.d/no-systemd-resolved.conf
.......................................................................................................
[main]
systemd-resolved=false

but the warning (only one of them) is still there after reboot.

Thanks for your help. This has already cleared the fog for me quite a bit and and I feel less unsure about these errors and warnings/infos.
The wiki is really a huge and great point of info, wow. This can feel a bit daunting at first, but also very interesting. I learned already some interesting little things on my short arch way.
Will keep digging as soon as i find some time.
Any further input is very welcome.

Thanks again. j

seth · 2026-01-13 08:56:08

Jan 13 00:14:45 Sandbox6 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.

Is a low-energy mode that's either not supported or broken

If you want a comment on the resolved invocation (since it's apparently not NM) you'll have to post the entire journal.

As a rule of thumb you'll see a lot of comments logged from the system that might seem like something you need to address but are just FYI (sometimes about the hardware, sometimes about bugs in userspace code that get caught and handled) - so it's necessary to assess the situation and not freak out about some red line because it's read.
Information overflow is an inherent downside of transparent systems (but some Desktop Environment will also happily show you a sad picture and tell you that it made an ooopsie with absolutely no further details nor where to look for them)
The upside is that you're not limited to the binary state of "works" and "please reinstall"

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

j081 · 2026-01-13 20:33:20

Thanks again.
No no, don't get me wrong, I'm totally happy with all the info about things. That's what I'm here for! It probably is a Noob thing, that you want to do everything as clean as possible.
The reason why I didn't post the whole boot journal is because I don't expect that anyone would read a wall of text (~1298 lines atm). That's why I tried to narrow it down to the things I am curious about to make it more accessible. Maybe the wrong approach.
And the reason why I didn't mark this 'solved' yet is because I'd like to investigate further. For example I applied some configs and settings to see if they will have an effect or not in combination with changes to the BIOS... that also might have effect on another. There are quite some things I need to revert and or try in different combinations to learn what actually has effect on what... But i only have a limited amount of time each day to do so.

Next time I have a question, I will narrow it down so it is more clear if that (one) issue is resolved or not.
You guys already have been a very big help. <3

seth wrote:

If you want a comment on the resolved invocation (since it's apparently not NM) you'll have to post the entire journal.

What is 'NM'?
Do you want me to post the whole 1298 lines? Or was this meant as a general note?
best j.

Last edited by j081 (2026-01-13 20:37:55)

seth · 2026-01-13 20:46:06

N|etworkM|anager

~1298 lines atm

That's almost nothing
For reference: There's another thread were someone struggles with an ath11k adapter (producing a lot of errors) - his initial journal was 89MB and the subsequent ones are 10k+ lines

sudo journalctl -b | curl -F 'file=@-' 0x0.st

j081 · 2026-01-14 00:00:15

seth wrote:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

ooooh, this is fancy !!!

seth · 2026-01-14 13:03:50

The resolved spam is gone, what's there is

Jan 14 00:44:21 Sandbox6 dbus-broker-launch[887]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.

which is likewise spam.
This is https://wiki.archlinux.org/title/Systemd-homed and you can suppress the spam by commenting the module references in /etc/pam.d/*

PSA: when messing around w/ the PAM config ALWAYS KEEP A ROOT SHELL OPEN! so you can undo your mistakes online (ie. w/o having to edit the files from some live distro boot)

j081 · 2026-01-14 20:26:51

Hey. Thanks again.
Will do.
But not today. Unfortunately too tired today to edit any spicy pam configs rn.

Last edited by j081 (2026-01-14 20:27:20)

j081 · 2026-01-17 09:57:36

Hey, just for the record. Found a way easier fix. systemd-homed.service wasn't running for some reason. After enabling it with

sudo systemctl enable systemd-homed.service

the error was gone. Sry for not checking this earlier.
Only thing unclear is this bluetooth vcc thingy. But as you said and other sources in the net also pointed this is most likely due to the old laptop. Also tied several different power configs in the BIOS without any success.
Possible solutions are probably trying an older kernel, what i don't really want to do as for now everything work fine nevertheless.
Or using an older BIOS, what i tried and didn't fix it.

So I will mark this as solved. Thanks a lot for your help. <3

seth · 2026-01-17 10:55:19

Make sure to read https://wiki.archlinux.org/title/Systemd-homed - it implies a completely different way of user management.
It's not advisable to engage it merely o shut down some systemd spam.

j081 · 2026-01-17 14:30:57

Aah. ok. I did actually read it. Also this: https://man.archlinux.org/man/systemd-homed.8
But I still thought the service needs to run as part of systemd weather I use homed or not. This wasn't clear to me.
So I switched it back off and the spam reappeared.
But looking at the message:

Jan 14 00:44:21 Sandbox6 dbus-broker-launch[887]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.

This raises the question why is there even an activation request, if it isn't being used nor enabled?

Nevertheless I edited my /etc/pam.d/system-auth and commented out the lines beginning with the minus '-' and now the spam is gone.
Also added a comment reminding my future self that I did this change to silence some spam.
Even though I don't plan to use homed on this machine anyways. So I hope this is a legit way of silencing this spam. :fingerscrossed:

Thanks again. j

Arch Linux

#1 2026-01-11 17:00:34

[SOLVED] Some Boot trouble I have. Can someone help plz?

#2 2026-01-11 20:09:50

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#3 2026-01-11 20:46:40

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#4 2026-01-12 00:29:56

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#5 2026-01-12 00:51:44

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#6 2026-01-12 01:52:47

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#7 2026-01-12 08:41:18

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#8 2026-01-13 00:12:28

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#9 2026-01-13 08:56:08

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#10 2026-01-13 20:33:20

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#11 2026-01-13 20:46:06

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#12 2026-01-14 00:00:15

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#13 2026-01-14 13:03:50

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#14 2026-01-14 20:26:51

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#15 2026-01-17 09:57:36

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#16 2026-01-17 10:55:19

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

#17 2026-01-17 14:30:57

Re: [SOLVED] Some Boot trouble I have. Can someone help plz?

Board footer