I encountered the problem several times while installing grub or using efibootmgr, until I was able to free up space in the efivars storage on my Dell laptop.
Because df /sys/firmware/efi/efivars showed a usage of 100%, I searched and found a solution.
The directory /boot/efi/EFI/dell/SOS contained a large number of language support subfolders for various languages that are of no relevance to me.
Mod edit:- Removed duplication of content. No charge.
Solution with doubts:
After having deleted the majority of the EFI/dell/SOS language subfolders (except for en-US, en-GB, and my regional language) and restarting the system, the usage rate of /sys/firmware/efi/efivars had fallen from 100% to 34%. Since then, the system freeze issue has not recurred, and fwupdmgr get-devices no longer shows any Not enough efivarfs space errors.
After @Teo’s doubts, I now have doubts myself that deleting the files had triggered the reduction in NVRAM usage. I cannot prove it. Perhaps some kind of automatic garbage collection by the boot firmware occurred during the startup of the computer. That remains an open question. However, I rule out an interplay of several actions of my own. The problem has disappeared nonetheless.
Don’t want to hurt your enthusiasm, but it is a coincidence. The /sys… Is on the nvram, the /boot…is on the hard drive. So if you had efivars error you cannot fix it by freeing space on the ESP.
You probably had both of those problems (lack of space in nvram and esp), you fixed the esp space and around that time you did something else that fixed your nvram without you realizing it (like updating the bios, resetting it, deleting boot entries, turning off or changing secure boot mode, manipulation on the dbx with fwupdate, etc) and now you think the 2 are connected. I also can understand why you have this impression - install grub writes to both of this places at the same time and i can imagine the error messages are not exactly precise so it will error out regardless where exactly it cannot write.
But it is a coincidence and if you think and remember what else did you do around the time you will find what truly fixed the nvram space.
That was my opinion before, too. But it happened exactly as I described (delete files and reboot). And I didn’t do anything else – I didn’t even go into the BIOS. It might be specific to Dell computers that data from the ESP causes efivars to bloat during boot.
A few quick questions:
$esp and /sys/firmware/efi/efivars?/?brtfs?
Please provide a link to that solution. 
System information might be helpful: 
Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.
Output of the inxi command will generate more useful and detailed information for those who may wish to help:
Suggested inxi command (use either):
inxi -zv8 |
(short-form) |
inxi --filter --verbosity=8 |
(long-form) |
inxi manual)Command output should be presented as pre-formatted text in accordance with forum guidelines.
Running inxi within a chroot environment
--color=0 to the long-form command, or…inxi -zv8c0Your privacy is respected
**#** df -Th / /sys/firmware/efi/efivars /boot/efi
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p10 ext4 79G 43G 32G 58% /
efivarfs efivarfs 148K 50K 94K 35% /sys/firmware/efi/efivars
/dev/nvme0n1p1 vfat 196M 94M 103M 48% /boot/efi
It seems you missed:
Add it to post #2 so it may benefit others.
The solution is my description in this post. What I found by searching the web was an AI hit of Google.
Thank you for explaining.
@Teo : It’s strange. I wanted to restore the ‘bad state’ from a tar backup as proof, but I didn’t succeed.
# date
Fr 11. Sep 17:45:12 CEST 2026
# pwd
/boot/efi/EFI
# ls -Fd ./dell/SOS/??-??
./dell/SOS/de-DE/ ./dell/SOS/en-GB/ ./dell/SOS/en-US/
#
# tar -xf ~/boot_efi_EFI_dell.tar ./dell/SOS
#
# ls -Fd ./dell/SOS/??-??
./dell/SOS/bg-BG/ ./dell/SOS/el-GR/ ./dell/SOS/es-MX/ ./dell/SOS/fr-FR/ ./dell/SOS/ja-JP/ ./dell/SOS/nb-NO/ ./dell/SOS/pt-PT/ ./dell/SOS/sl-SI/ ./dell/SOS/zh-CN/
./dell/SOS/cs-CZ/ ./dell/SOS/en-GB/ ./dell/SOS/et-EE/ ./dell/SOS/hr-HR/ ./dell/SOS/ko-KR/ ./dell/SOS/nl-NL/ ./dell/SOS/ro-RO/ ./dell/SOS/sv-SE/ ./dell/SOS/zh-TW/
./dell/SOS/da-DK/ ./dell/SOS/en-US/ ./dell/SOS/fi-FI/ ./dell/SOS/hu-HU/ ./dell/SOS/lt-LT/ ./dell/SOS/pl-PL/ ./dell/SOS/ru-RU/ ./dell/SOS/tr-TR/
./dell/SOS/de-DE/ ./dell/SOS/es-ES/ ./dell/SOS/fr-CA/ ./dell/SOS/it-IT/ ./dell/SOS/lv-LV/ ./dell/SOS/pt-BR/ ./dell/SOS/sk-SK/ ./dell/SOS/uk-UA/
#
#
# df -Th / /sys/firmware/efi/efivars /boot/efi
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p10 ext4 79G 43G 32G 58% /
efivarfs efivarfs 148K 50K 94K 35% /sys/firmware/efi/efivars
/dev/nvme0n1p1 vfat 196M 100M 97M 51% /boot/efi
#
# reboot
...
...
...
# date
Fr 11. Sep 17:50:16 CEST 2026
#
# df -Th / /sys/firmware/efi/efivars /boot/efi
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p10 ext4 79G 43G 32G 58% /
efivarfs efivarfs 148K 50K 94K 35% /sys/firmware/efi/efivars
/dev/nvme0n1p1 vfat 196M 100M 97M 51% /boot/efi
#
# cd /boot/efi/EFI
# ls -Fd ./dell/SOS/??-??
./dell/SOS/bg-BG/ ./dell/SOS/el-GR/ ./dell/SOS/es-MX/ ./dell/SOS/fr-FR/ ./dell/SOS/ja-JP/ ./dell/SOS/nb-NO/ ./dell/SOS/pt-PT/ ./dell/SOS/sl-SI/ ./dell/SOS/zh-CN/
./dell/SOS/cs-CZ/ ./dell/SOS/en-GB/ ./dell/SOS/et-EE/ ./dell/SOS/hr-HR/ ./dell/SOS/ko-KR/ ./dell/SOS/nl-NL/ ./dell/SOS/ro-RO/ ./dell/SOS/sv-SE/ ./dell/SOS/zh-TW/
./dell/SOS/da-DK/ ./dell/SOS/en-US/ ./dell/SOS/fi-FI/ ./dell/SOS/hu-HU/ ./dell/SOS/lt-LT/ ./dell/SOS/pl-PL/ ./dell/SOS/ru-RU/ ./dell/SOS/tr-TR/
./dell/SOS/de-DE/ ./dell/SOS/es-ES/ ./dell/SOS/fr-CA/ ./dell/SOS/it-IT/ ./dell/SOS/lv-LV/ ./dell/SOS/pt-BR/ ./dell/SOS/sk-SK/ ./dell/SOS/uk-UA/
#
After having restored the dell/SOS language file to the original ESP path /sys/firmware/efi/efivars is still OK (35% usage) and not 100% as I expected.
Exactly as expected 
But one sees from the df the esp space shrinked with about 6 MB so the restore was successful.
It just has nothing to do with the 150k nvram. Of which you now have plenty.
In my experience the biggest 
on the nvram ever were the misco$oft .dbx files, one of which was over 30 kb. That is how i managed to fill my nvram once. Resetting secure boot deleted it.
That is also an option that i thought of but i do not have experience with dell.
Anyways, be happy the problem is solved. You should be fine for years to come with 100kb free.
I own a Dell laptop too and I also have 100% usage there. But I never encountered any problems, and Manjaro rolls on it since 2020.
There is no such directory on my system, still df /sys/firmware/efi/efivars shows 100% without problem.
So now we are even talking about Dell computers in general? Honestly, I can’t see how this topic could help anyone, unless further system information is provided. For a start inxi -zv8, and as @Teo already noted I agree we have to consider that the given solution isn’t a real solution but some sort of fluke.
I have seen laptops with firmwares that incorrectly report the used nvram as the total to the OS. At 80k it was 100% used and writing was possible, at next boot it was 100kb 100% and still everything worked. Maybe this is the case here too. And after some firmware update or driver update this was just fixed and it now shows the real value. Who knows. (But of course if you had writing errors this was not your case).
If it helps:
# inxi -zv8
System:
Kernel: 7.2.3-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-7.2-x86_64
root=UUID=e606c908-01e8-11f1-bbaf-4da1686e5bf4 rw udev.log_priority=3
lsm=landlock,lockdown,yama,integrity,apparmor,bpf
Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Manjaro base: Arch Linux
Machine:
Type: Laptop System: Dell product: Inspiron 16 5625 v: 1.28.1
serial: <filter> Chassis: type: 10 v: 1.28.1 serial: <filter>
Mobo: Dell model: 0J9C2M v: A00 serial: <filter> part-nu: 0B47
uuid: 4c4c4544-0059-3210-8053-b9c04f445833 Firmware: UEFI vendor: Dell
v: 1.28.1 date: 05/12/2026
Battery:
ID-1: BAT0 charge: 54 Wh (100%) condition: 54/54 Wh (100%) volts: 16.38
min: 15 model: SMP-COS3.66 DELL XDY9K35 type: Li-poly serial: <filter>
charging: status: full cycles: N/A
Memory:
System RAM: total: 16 GiB available: 14.97 GiB used: 6.73 GiB (44.9%)
Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
max-module-size: 32 GiB note: est.
Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2
max: 1.2 width (bits): data: 64 total: 64 manufacturer: 80AD000080AD
part-no: HMAA1GS6CJR6N-XN firmware: HMAA1GS6CJR6N-XN serial: <filter>
Device-2: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2
max: 1.2 width (bits): data: 64 total: 64 manufacturer: 80AD000080AD
part-no: HMAA1GS6CJR6N-XN firmware: HMAA1GS6CJR6N-XN serial: <filter>
PCI Slots:
Slot: 2 type: PCIe status: available info: J10 length: short volts: 3.3
bus-ID: 0200:00:02.2
Slot: 3 type: PCIe status: available info: J3600 length: short volts: 3.3
bus-ID: 0200:00:02.2
Slot: 3 type: PCIe status: available info: J3707 length: short volts: 3.3
bus-ID: 0200:00:02.2
Slot: 3 type: PCIe status: available info: J3700 length: short volts: 3.3
bus-ID: 0200:00:02.2
Slot: 3 type: PCIe status: available info: J3702 length: short volts: 3.3
bus-ID: 0200:00:02.2
Slot: 3 type: PCIe status: available info: J3703 length: short volts: 3.3
bus-ID: 0200:00:02.2
Slot: N/A type: N/A status: available info: J3701 length: short volts: 3.3
bus-ID: 0200:00:02.5
CPU:
Info: model: AMD Ryzen 7 5825U with Radeon Graphics socket: FP6 bits: 64
type: MT MCP arch: Zen 3 gen: 3 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA500014
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 411 min/max: 411/2000 boost: enabled
base/boost: 2000/4550 scaling: driver: amd-pstate-epp governor: powersave
volts: 1.2 V ext-clock: 100 MHz cores: 1: 411 2: 411 3: 411 4: 411 5: 411
6: 411 7: 411 8: 411 9: 411 10: 411 11: 411 12: 411 13: 411 14: 411
15: 411 16: 411 bogomips: 63885
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
vpclmulqdq wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
xtopology
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: ghostwrite status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: old_microcode status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds status: Not affected
Type: tsa mitigation: Clear CPU buffers
Type: tsx_async_abort status: Not affected
Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Barcelo vendor: Dell
driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: eDP-1
empty: DP-1,HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:15e7 class-ID: 0300
temp: 42.0 C
Device-2: Microdia Integrated_Webcam_FHD driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:3 chip-ID: 0c45:6739
class-ID: 0e02
Display: unspecified server: X.Org v: 24.1.13 with: Xwayland v: 24.1.13
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.00x12.48")
s-diag: 599mm (23.57") monitors: <missing: xrandr>
Monitor-1: eDP-1 model: BOE Display 0x0a34 built: 2021 res: 1920x1200
dpi: 141 gamma: 1.2 chroma: red: x: 0.580 y: 0.365 green: x: 0.345 y: 0.580
blue: x: 0.165 y: 0.129 white: x: 0.314 y: 0.329
size: 345x215mm (13.58x8.46") diag: 407mm (16") ratio: 16:10
modes: 1920x1200, 1920x1080, 1600x1200, 1680x1050, 1280x1024, 1440x900,
1280x800, 1280x720, 1024x768, 800x600, 640x480
EDID-Warnings: 1: parse_edid: unknown flag 0
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 vendor: amd mesa v: 26.2.2-arch1.1 glx-v: 1.4
direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM
3.64 7.2.3-2-MANJARO) device-ID: 1002:15e7 memory: 500 MiB unified: yes
API: Vulkan v: 1.4.357 layers: 2 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RENOIR) driver: mesa radv v: 26.2.2-arch1.1
device-ID: 1002:15e7 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
vendor: Dell driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Dell
driver: snd_rn_pci_acp3x v: kernel alternate: snd_pci_acp3x, snd_pci_acp5x,
snd_pci_acp6x, snd_acp_pci, snd_pci_ps, snd_sof_amd_renoir,
snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63,
snd_sof_amd_acp70 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.5
chip-ID: 1022:15e2 class-ID: 0480
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Dell
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k7.2.3-2-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.6.8 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
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: MEDIATEK MT7921 802.11ax PCIe Wireless Network Adapter [Filogic
330] vendor: Foxconn driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 03:00.0 chip-ID: 14c3:7961 class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
IF-ID-1: virbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-2: vnet0 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
Info: services: NetworkManager, sshd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Foxconn / Hon Hai MediaTek MT7921 Bluetooth driver: btusb v: 0.8
type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:2
chip-ID: 0489:e0c8 class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c010c
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 931.51 GiB used: 300.83 GiB (32.3%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000P310SSD8
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: VACR001 temp: 32.9 C
scheme: GPT
SMART: yes health: PASSED on: 17d 13h cycles: 491
read-units: 17,850,313 [9.13 TB] written-units: 4,287,331 [2.19 TB]
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 80 GiB size: 78.19 GiB (97.74%) used: 43.17 GiB (55.2%)
fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p10 maj-min: 259:10
label: Manjaro uuid: e606c908-01e8-11f1-bbaf-4da1686e5bf4
ID-2: /boot/efi raw-size: 200 MiB size: 196 MiB (98.00%)
used: 99.1 MiB (50.6%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1 label: ESP uuid: 90DC-4AF6
ID-3: /home raw-size: 150 GiB size: 146.59 GiB (97.72%)
used: 110.22 GiB (75.2%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p11
maj-min: 259:11 label: Home uuid: 5a96eae4-6622-40a3-8e1f-d7b55719287c
ID-4: /local-backups raw-size: 224.57 GiB size: 219.99 GiB (97.96%)
used: 147.45 GiB (67.0%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p12
maj-min: 259:12 label: Local_Backups
uuid: 86895c4c-cbdd-4bbc-8fea-da1213d5b3de
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 28.13 GiB used: 0 KiB (0.0%)
priority: -1 dev: /dev/nvme0n1p4 maj-min: 259:4 label: N/A
uuid: 222db0df-e653-4309-8a12-64df0fc3f2ae
Unmounted:
ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 128 MiB fs: N/A label: N/A
uuid: N/A
ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 180.72 GiB fs: ntfs label: OS
uuid: 9656F3A756F385F1
ID-3: /dev/nvme0n1p5 maj-min: 259:5 size: 220 GiB fs: ext4 label: N/A
uuid: 53b68390-ec6d-4d9c-a340-89ca70d563da
ID-4: /dev/nvme0n1p6 maj-min: 259:6 size: 27.07 GiB fs: ext4 label: N/A
uuid: b5d4ddac-bf44-4034-a2da-88aaea57e09e
ID-5: /dev/nvme0n1p7 maj-min: 259:7 size: 990 MiB fs: ntfs
label: WINRETOOLS uuid: 6CB81D12B81CDC80
ID-6: /dev/nvme0n1p8 maj-min: 259:8 size: 18.29 GiB fs: ntfs label: Image
uuid: 6AA81D45A81D10E5
ID-7: /dev/nvme0n1p9 maj-min: 259:9 size: 1.45 GiB fs: ntfs
label: DELLSUPPORT uuid: B090CAD090CA9BEA
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-2:2 info: Dell Universal Receiver type: keyboard,mouse,HID
driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 100mA chip-ID: 413c:2514 class-ID: 0300
Device-2: 1-4:3 info: Microdia Integrated_Webcam_FHD type: video
driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 power: 500mA chip-ID: 0c45:6739 class-ID: 0e02
Hub-2: 2-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 3-3:2 info: Foxconn / Hon Hai MediaTek MT7921 Bluetooth
type: bluetooth driver: btusb interfaces: 3 rev: 2.1
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 0489:e0c8 class-ID: e001 serial: <filter>
Device-2: 3-4:3 info: Shenzhen Goodix USB2.0 MISC type: <vendor specific>
driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
mode: 1.1 power: 100mA chip-ID: 27c6:639c class-ID: ef00 serial: <filter>
Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 44.9 C mobo: 36.0 C sodimm: 40.0 C gpu: amdgpu
temp: 43.0 C
Fan Speeds (rpm): cpu: 0
Repos:
Packages: 2236 pm: pacman pkgs: 2221 libs: 392 tools: pamac pm: rpm pkgs: 0
pm: flatpak pkgs: 15
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
2: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
3: https://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
4: https://mirror.bakertelekom.fr/manjaro/stable/$repo/$arch
5: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
6: https://mirror.informatik.tu-freiberg.de/manjaro/stable/$repo/$arch
7: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
8: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 364
1: cpu: 100% command: ps pid: 5316 mem: 3.83 MiB (0.0%)
2: cpu: 11.5% command: qemu-system-x86_64 pid: 1140
mem: 3169.0 MiB (20.6%)
3: cpu: 5.9% command: firefox pid: 3569 mem: 477.4 MiB (3.1%)
4: cpu: 2.1% command: firefox pid: 3997 mem: 274.1 MiB (1.7%)
5: cpu: 1.9% command: kwin_wayland pid: 1423 mem: 280.4 MiB (1.8%)
Memory top: 5 of 364
1: mem: 3169.0 MiB (20.6%) command: qemu-system-x86_64 pid: 1140
cpu: 11.5%
2: mem: 961.5 MiB (6.2%) command: clamd pid: 603 cpu: 0.5%
3: mem: 477.4 MiB (3.1%) command: firefox pid: 3569 cpu: 5.9%
4: mem: 383.4 MiB (2.5%) command: plasmashell pid: 1561 cpu: 0.8%
5: mem: 365.2 MiB (2.3%) command: plasma-discover pid: 3324 cpu: 1.1%
Info:
Processes: 364 Power: uptime: 19m states: freeze,mem,disk suspend: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 5.91 GiB services: org_kde_powerdevil, power-profiles-daemon,
upowerd Init: systemd v: 261 default: graphical tool: systemctl
Compilers: clang: 22.1.8 gcc: 16.2.1 Shell: Bash (sudo) v: 5.3.15
running-in: konsole inxi: 3.3.41
By the way, efivars usage has climbed back up to 80% in the meantime. That is presumably because I ran updates using fwupdmgr.
If you don’t dual boot with windows or something using secure boot you can skip the humongous dbx. Those are revoked hacked Microsoft signatures…which show how secure is the secure boot.
Thanks! Good hint! I put DisabledPlugins=uefi_dbx into /etc/fwupd/fwupd.conf.
I hope the system freezing won’t happen again in the future on my Dell Inspiron 5625. I performed a BIOS firmware update today.
Please provide information that might be helpful to others – the basic point of a User to User Support forum.
By marking your post (immediately above) as the solution, perhaps you were attempting to infer that updating your BIOS firmware had solved your issues, however, it is unclear; you need to actually state it to leave no doubt.
If you are uncertain what actually solved your issue, please say as much, and the topic can be closed without a confirmed solution.
The marked solution has been removed.