TPM 2.0 driver missing?

Ask Fedora
, ,
1

Hello! I am having issues with TPM 2.0 on Linux in general, but I currently use Fedora so I’ll write it here. I am using Fedora 44 KDE (kernel version 7.1.3-200) on a Fujitsu Celsius H760 laptop and I am sure the laptop has TPM 2.0, and I think it worked properly on Windows

When searching for any tpm* file in /dev , I find nothing. During boot, the system tries to find a TPM device but it couldn’t so it reaches its 45 seconds timeout limit, and then after launching some another services, it tries to find TPM again and it just reaches its 45 seconds timeout limit

The output of “sudo dmesg | grep -i tpm” command is:

[ 0.000000] efi: SMBIOS=0x373fb000 ACPI 2.0=0x37ffe014 ESRT=0x3747c418 MOKvar=0x373da000 RNG=0x37fbbf98 TPMEventLog=0x37faf018
[ 0.000000] TPM Final Events table not present
[ 0.010740] ACPI: SSDT 0x0000000037FFA000 000534 (v01 Insyde TPMACPI 00001000 INTL 20130117)
[ 0.010744] ACPI: TPM2 0x0000000037FF9000 000034 (v03 FUJ PC 01230000 FUJ 00000001)
[ 0.010822] ACPI: Reserving TPM2 table memory at [mem 0x37ff9000-0x37ff9033]
[ 0.625464] tpm_crb_acpi MSFT0101:00: error -EBUSY: can’t request region for resource [mem 0x37f65000-0x37f6502f]
[ 0.625470] tpm_crb_acpi MSFT0101:00: probe with driver tpm_crb_acpi failed with error -16
[ 1.043159] ima: No TPM chip found, activating TPM-bypass!
[ 1.736014] systemd[1]: systemd 259.7-1.fc44 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +IPE +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE)
[ 1.913575] systemd[1]: Expecting device dev-tpm0.device - /dev/tpm0…
[ 1.913582] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0…
[ 47.693874] systemd[1]: systemd 259.7-1.fc44 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +IPE +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE)
[ 48.380059] systemd[1]: Expecting device dev-tpm0.device - /dev/tpm0…
[ 48.380095] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0…

As I understand, this indicates that the system sees there is TPM 2.0 but it can’t access it properly. The line with error -16 thingy apparently mostly occurs on devices with AMD CPUs, but I have an Intel CPU instead

“systemd-analyze has-tpm2” displays this:

partial
+firmware
-driver
+system
+subsystem
+libraries
+libtss2-esys.so.0
+libtss2-rc.so.0
+libtss2-mu.so.0

So, the command shows that the TPM 2.0 driver is missing? I guess yeah

Attempt to enable tpm2-abrmd service (straight after boot) shows this:

A dependency job for tpm2-abrmd.service failed. See ‘journalctl -xe’ for details.

“journalctl -xe” displays this:

░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-localed.service has successfully entered the ‘dead’ state.
июл 08 16:40:36 Palantir-surveillance-server audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-localed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’p=UNLOAD
июл 08 16:40:42 Palantir-surveillance-server kalarm[4493]: Wake from suspend: using RTC (no CAP_WAKE_ALARM capability)
июл 08 16:40:42 Palantir-surveillance-server kdeconnectd[3234]: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type.
июл 08 16:40:48 Palantir-surveillance-server systemd[1]: fprintd.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ The unit fprintd.service has successfully entered the ‘dead’ state.
июл 08 16:40:48 Palantir-surveillance-server audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=fprintd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
июл 08 16:40:48 Palantir-surveillance-server audit: BPF prog-id=84 op=UNLOAD
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start timed out.
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
░░ Subject: Ошибка юнита dev-tpm0.device (“dev-tpm0.device” unit error)
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ Произошел сбой юнита dev-tpm0.device. (“dev-tpm0.device” unit fail occured)
░░
░░ Результат: timeout. (Result: timeout)
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: Dependency failed for tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daemon.
░░ Subject: Ошибка юнита tpm2-abrmd.service (“tpm2-abrmd.service” unit error)
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ Произошел сбой юнита tpm2-abrmd.service. (“tpm2-abrmd.service” unit fail occured)
░░
░░ Результат: dependency. (Result: dependency)
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: tpm2-abrmd.service: Job tpm2-abrmd.service/start failed with result ‘dependency’.
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start failed with result ‘timeout’.
июл 08 16:41:07 Palantir-surveillance-server sudo[4420]: pam_unix(sudo:session): session closed for user root
июл 08 16:41:07 Palantir-surveillance-server audit[4420]: AUDIT1106 pid=4420 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct=“root” exe=“/usr/bin/sudo” hostname=Palantir-surveillance-server addr=? terminal=/dev/pts/1 res=succes>
июл 08 16:41:07 Palantir-surveillance-server audit[4420]: AUDIT1104 pid=4420 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg=‘op=PAM:setcred grantors=pam_unix acct=“root” exe=“/usr/bin/sudo” hostname=Palantir-surveillance-server addr=? terminal=/dev/pts/1 res=success’
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: session-c2.scope: Deactivated successfully.
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-localed.service has successfully entered the ‘dead’ state.
июл 08 16:40:36 Palantir-surveillance-server audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-localed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
июл 08 16:40:36 Palantir-surveillance-server audit: BPF prog-id=83 op=UNLOAD
июл 08 16:40:36 Palantir-surveillance-server audit: BPF prog-id=82 op=UNLOAD
июл 08 16:40:36 Palantir-surveillance-server audit: BPF prog-id=81 op=UNLOAD
июл 08 16:40:42 Palantir-surveillance-server kalarm[4493]: Wake from suspend: using RTC (no CAP_WAKE_ALARM capability)
июл 08 16:40:42 Palantir-surveillance-server kdeconnectd[3234]: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type.
июл 08 16:40:48 Palantir-surveillance-server systemd[1]: fprintd.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ The unit fprintd.service has successfully entered the ‘dead’ state.
июл 08 16:40:48 Palantir-surveillance-server audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=fprintd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
июл 08 16:40:48 Palantir-surveillance-server audit: BPF prog-id=84 op=UNLOAD
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start timed out.
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
░░ Subject: Ошибка юнита dev-tpm0.device (“dev-tpm0.device” unit error)
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ Произошел сбой юнита dev-tpm0.device. (“dev-tpm0.device” unit fail occured)
░░
░░ Результат: timeout. (Result: timeout)
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: Dependency failed for tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daemon.
░░ Subject: Ошибка юнита tpm2-abrmd.service (“tpm2-abrmd” unit error)
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ Произошел сбой юнита tpm2-abrmd.service. (“tpm2-abrmd.service” unit fail occured)
░░
░░ Результат: dependency. (Result: dependency)
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: tpm2-abrmd.service: Job tpm2-abrmd.service/start failed with result ‘dependency’.
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start failed with result ‘timeout’.
июл 08 16:41:07 Palantir-surveillance-server sudo[4420]: pam_unix(sudo:session): session closed for user root
июл 08 16:41:07 Palantir-surveillance-server audit[4420]: AUDIT1106 pid=4420 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg=‘op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct=“root” exe=“/usr/bin/sudo” hostname=Palantir-surveillance-server addr=? terminal=/dev/pts/1 res=success’
июл 08 16:41:07 Palantir-surveillance-server audit[4420]: AUDIT1104 pid=4420 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg=‘op=PAM:setcred grantors=pam_unix acct=“root” exe=“/usr/bin/sudo” hostname=Palantir-surveillance-server addr=? terminal=/dev/pts/1 res=success’
июл 08 16:41:07 Palantir-surveillance-server systemd[1]: session-c2.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░
░░ The unit session-c2.scope has successfully entered the ‘dead’ state.
июл 08 16:41:07 Palantir-surveillance-server systemd-logind[1115]: Session c2 logged out. Waiting for processes to exit.
июл 08 16:41:07 Palantir-surveillance-server systemd-logind[1115]: Removed session c2.
░░ Subject: Сеанс c2 завершен (“c2” session has ended)
░░ Defined-By: systemd
░░ Support: https[:]//lists[.]freedesktop[.]org/mailman/listinfo/systemd-devel
░░ Documentation: sd-login(3)
lines 2909-2960/2962 100%

Yes, I just pasted the output and added some translations

I just disabled TPM 2.0 in UEFI for a while but I realized I might want to eventually use it. Is there anything I can do about it?

2

On my f44 system I see this

$ dnf list --installed *tpm*
Installed packages (available for reinstall, available for upgrade)
clevis-pin-tpm2.x86_64 0.5.4-1.fc44  <unknown>
libtpms.x86_64         0.10.2-3.fc44 <unknown>
swtpm.x86_64           0.10.1-3.fc44 <unknown>
swtpm-libs.x86_64      0.10.1-3.fc44 <unknown>
swtpm-selinux.noarch   0.10.1-3.fc44 <unknown>
swtpm-tools.x86_64     0.10.1-3.fc44 <unknown>
tpm2-tools.x86_64      5.7-5.fc44    <unknown>
tpm2-tss.x86_64        4.1.3-9.fc44  <unknown>
tpm2-tss-fapi.x86_64   4.1.3-9.fc44  <unknown>

All the listed packages were carried over when I upgraded from f43 to f44.

Are all or any of those installed on your system.?

3

Yeah, they are all installed

5

These lines indicate that the kernel tried to reserve some memory for the TPM chip your BIOS advertsises, but can’t as it’s already reserved. (-EBUSY or -16 = “something else is using this”)

What do you have for grep 37f65000 /proc/iomem?

6

It outputed completely nothing. Tried booting with iomem=relaxed, still no output. I try opening the iomem file with a text editor for some reason, for numbers, I just see bunch of zeros mostly, like “00000000-00000000 : Reserved” and all the next lines are starting with the same “00000000-00000000 :” thingy

7

Is this in the same boot that you took the log messages from? There’s no guarantee that a reboot will result in the same piece of memory being allocated for the same task.

8

No, the log messages were in regular mode, without the iomem=relaxed argument. And even with iomem=relaxed, TPM 2.0 couldn’t be detected properly, so I assume little to nothing changed

9

Is your BIOS/UEFI firmware the latest version? Looks like TPM2 is present but not properly configured for Linux.

10

Well, I am not really sure about if the firmware is up to date. I ran “sudo fwupdmgr update” in both regular mode and with iomem=relaxed and it found no available updates so I assume the firmware is up to date

11

Execute inxi -Fzxx and it’ll tell you your BIOS version and date is - cross-check that with your machine supplier to ensure you’re on the latest version.

12

Output of “sudo inxi -Fzxx” command for motherboard (if it’s also important) and firmware part:

Mobo: FUJITSU model: FJNB29A v: E5 serial: part-nu: SK00
Firmware: UEFI vendor: FUJITSU // Insyde v: Version 1.35 date: 01/23/2023

13

Find your kit on here and see if the BIOS can be updated - yours is from 2023 which isn’t THAT old, but I’d expect TPM to be working for something which has been around for at least 3 years.

14

So apparently, if I go to “Downloads” section and select “OS Independent”, and then go into “BIOS” section, there is a thing called “BIOS Update Utility H760 vPro” with version of 1.35, and for other versions it only shows one more version, 1.34, so only two versions available. Am I doing stuff right?
And if I need Windows operating system in order to check if the firmware is up to date (cuz all downloads for Fujitsu are strictly for Windows only), then I nuked Windows partition some time ago

15

Sounds about right; i’m not a laptop nor a Fujitsu user so it’s down to you to ensure you get the correct BIOS file your device.

To install it, you can boot Win PE (I use Ventoy for this) and run the installation software.

Alternatively many BIOS’s allow you to place the bin file onto a USB stick and apply it from within the BIOS itself. You’ll have to check if your BIOS supports this.

16

I encountered issues with WinPE so I couldn’t use Windows to be sure about firmware being up to date. From times when there was Windows 10 installed on the drive, I remember that the laptop had no new firmware updates available. Fujitsu Celsius H760 is a 2017 laptop and I only got it in 2024

17

What issues? See https://wiki.archlinux.org/title/Windows_PE for
a way to create images for WinPE with Linux.

Edit: Fujitsu has SDDM in addition to BIOS updates — not sure if it has TPM2 supports.

18

I always recommend that users who may need WinPE create a boot device using this site

19

Yeah, I tried this. But winver on the latest version shows Windows 11 22H2, which is not supported by my laptop. It means I need W10 based images. Otherwise I get ~400MB files, which are just enough to run cmd only
But I kind of think right now if it’s actually necessary to get a Windows image just to confirm if firmware version is up to date if my past experience says that I didn’t see any new firmware updates since using the laptop from 2024
edit: I guess I’ll check it anyway somehow soon. But if it’s important, from range of 2024 to until I lowkey stopped using Windows, I noticed I didn’t get any new driver updates aswell, expect NVIDIA driver updates (and still, my GPU will forever be stuck on driver version 580). I kind of assumed the laptop reached its end of life, but I am not really sure now

20

Win 10 version of Hirensbootcd is available here

However, that would only be required if you have a newer version of the firmware than was shown above (1.35) AND if the bios does not have the ability to read and flash the firmware directly from a usb device.

IME I don’t think hirencbootcd image requires the TPM chip which is required when using windows 11. If it will boot on your machine it should perform all that would be needed for flashing the firmware.

Unfortunately I cannot verify the latest firmware since you did not provide the model nor serial number of the device, nor have you shown whether it is a laptop or desktop. The limited info from inxi that you did provide is inadequate and you should provide us the full output of inxi -Fzxx so we may be able to provide better assistance.

EDIT
I had not tried that site, but relied on google search to provide the link
When I tried the link I had to edit the link to provide a direct download page..

21

alphaMountain.ai and CRDF detected “progs[.]online” (the final link for download for WInPE image) as malicious on VirusTotal. This is a false positive, right?

Oh, wait. full “sudo inxi -Fzxx” output:

System:
Kernel: 7.1.3-200.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Console: pty pts/4 wm: kwin_wayland Distro: Fedora Linux 44 (KDE Plasma
Desktop Edition)
Machine:
Type: Laptop System: FUJITSU product: CELSIUS H760 v: 10601736746
serial: Chassis: type: 10 v: CELSIUS H760 serial:
Mobo: FUJITSU model: FJNB29A v: E5 serial: part-nu: SK00
Firmware: UEFI vendor: FUJITSU // Insyde v: Version 1.35 date: 01/23/2023
CPU:
Info: quad core model: Intel Core i5-6440HQ bits: 64 type: MCP
arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 2700 min/max: 800/3500 cores: 1: 2700 2: 2700 3: 2700
4: 2700 bogomips: 20799
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Skylake-H GT2 [HD Graphics 530] vendor: Fujitsu driver: i915
v: kernel arch: Gen-9 ports: active: DP-1,eDP-1 empty: DP-2,DP-3,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:191b
Device-2: NVIDIA GM107GLM [Quadro M600M] vendor: Fujitsu driver: nvidia
v: 580.173.02 arch: Maxwell pcie: speed: 2.5 GT/s lanes: 16 ports:
active: none empty: DP-4,DP-5 bus-ID: 01:00.0 chip-ID: 10de:13b2
Display: unspecified server: X.Org v: 24.1.12 with: Xwayland v: 24.1.12
compositor: kwin_wayland driver: dri: iris gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96
Monitor-1: DP-1 pos: right model: BOE Display 21CT5000AK res: 1920x1080
hz: 60 dpi: 85
Monitor-2: eDP-1 pos: primary,left model: LG Display 0x046f res: 1920x1080
hz: 60 dpi: 142 diag: 395mm (15.5")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: iris
device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11:
drv: iris inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 26.1.4 glx-v: 1.4
direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL GT2)
device-ID: 8086:191b
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: integrated-gpu
driver: mesa intel device-ID: 8086:191b device: 1 type: discrete-gpu
driver: nvidia device-ID: 10de:13b2 device: 2 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 100/C230 Series Family HD Audio vendor: Fujitsu
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX]
vendor: Fujitsu driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fbc
API: ALSA v: k7.1.3-200.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.7 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
Device-1: Intel Ethernet I219-LM vendor: Fujitsu driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b7
IF: enp0s31f6 state: down mac:
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel pcie:
speed: 2.5 GT/s lanes: 1 bus-ID: 0d:00.0 chip-ID: 8086:24f3
IF: wlp13s0 state: up mac:
IF-ID-1: wwan0 state: down mac:
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-7:4 chip-ID: 8087:0a2b
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: bt-v: 4.2 lmp-v: 8
Drives:
Local Storage: total: 950.16 GiB used: 377.95 GiB (39.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVKW512HMJP-00000
size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 36.9 C
ID-2: /dev/sda vendor: Toshiba model: MQ01ABD050V -63 size: 465.76 GiB
type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial:
ID-3: /dev/sdb vendor: Silicon Power model: UFD 2.0 8G size: 7.46 GiB
type: USB rev: 2.0 spd: 480 Mb/s lanes: 1 serial:
Partition:
ID-1: / size: 411.44 GiB used: 194.77 GiB (47.3%) fs: btrfs
dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 1022 MiB used: 194 MiB (19.0%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 173.3 MiB (2.1%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 60.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.46 GiB used: 6.88 GiB (44.5%)
igpu: 64 MiB
Processes: 351 Power: uptime: 3h 31m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 16.1.1 alt: 15
Shell: Sudo v: 1.9.17p2 running-in: konsole inxi: 3.3.40