Error in systemctl, systemd, kernel etc

[mtsbh]

System:
Kernel: 6.1.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=ed32595a-d211-4658-b067-e481188b5b26 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.0 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK MAX II (MS-7C02) v: 3.0
serial: <superuser required> UEFI: American Megatrends LLC. v: H.90
date: 07/25/2022
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3691 high: 3700 min/max: 2200/4650 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3700 2: 3700
3: 3700 4: 3700 5: 3700 6: 3700 7: 3700 8: 3700 9: 3700 10: 3599 11: 3700
12: 3700 bogomips: 88801
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: PNY driver: nvidia
v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
status: current (as of 2023-02) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 26:00.0 chip-ID: 10de:2487
class-ID: 0300
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 6960x1920 s-dpi: 109 s-size: 1622x447mm (63.86x17.60")
s-diag: 1682mm (66.24")
Monitor-1: DP-0 pos: bottom-r res: 1920x1080 hz: 60 dpi: 92
size: 531x299mm (20.91x11.77") diag: 609mm (23.99") modes: N/A
Monitor-2: DP-2 pos: primary,top-left res: 1200x1920 hz: 60 dpi: 94
size: 324x518mm (12.76x20.39") diag: 611mm (24.05") modes: N/A
Monitor-3: DP-4 pos: top-center res: 3840x1600 hz: 60 dpi: 111
size: 879x366mm (34.61x14.41") diag: 952mm (37.49") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX
3060/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GA104 High Definition Audio vendor: PNY
driver: snd_hda_intel v: kernel bus-ID: 5-1.1:4 chip-ID: 0499:170f pcie:
gen: 3 class-ID: 0103 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s bus-ID: 26:00.1 chip-ID: 10de:228b class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 28:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Yamaha Steinberg UR22mkII type: USB driver: snd-usb-audio
Device-4: Intel USB PnP Sound Device type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:3 chip-ID: 8086:0808
class-ID: 0300
Sound API: ALSA v: k6.1.12-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.65 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
Bluetooth:
Device-1: TP-Link UB500 Adapter type: USB driver: btusb v: 0.8
bus-ID: 3-1.4:3 chip-ID: 2357:0604 class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 4.1 TiB used: 1.58 TiB (38.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN520
SDAPNUW-512G-1014 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter>
rev: 20110000 temp: 42.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2FR102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD120 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD
rpm: 7200 serial: <filter> rev: ACF0 scheme: GPT
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 23.76 GiB (5.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 23.76 GiB (5.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 23.76 GiB (5.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 23.76 GiB (5.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.27 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 36.8 C mobo: N/A gpu: nvidia temp: 56 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 354 Uptime: 4m wakeups: 0 Memory: 31.27 GiB
used: 4.82 GiB (15.4%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 1715 libs: 446 tools: octopi,pamac,paru Shell: fish v: 3.6.0
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.25
Garuda (2.6.14-1):
System install date:     2023-02-18
Last full system update: 2023-02-18
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:            anbox-container-manager.service systemd-networkd-wait-online.service

Hello! I received a couple of errors after $ systemctl --failed and # journalctl -p 3 -b
Anyone with better knowledge knows how to procedure now?

╭─ahbh@linux in ~
╰─λ systemctl --failed
UNIT                            LOAD   ACTIVE SUB    DESCRIPTION
● anbox-container-manager.service loaded failed failed Anbox Container Manager

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel: blacklist: Problem blacklisting hash (-13)
фев 18 23:01:27 linux-desktop kernel:
фев 18 23:01:27 linux-desktop kernel: usb 3-1.4: device descriptor read/64, error -32
фев 18 23:01:27 linux-desktop systemd-modules-load[383]: Failed to find module 'ashmem_linux'
фев 18 23:01:27 linux-desktop systemd-modules-load[383]: Failed to find module 'binder_linux'
фев 18 23:01:27 linux-desktop systemd-modules-load[383]: Failed to find module 'vboxpci'
фев 18 23:01:27 linux-desktop systemd-udevd[417]: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:57 Unknown group 'uaccess', ignoring
фев 18 23:01:28 linux-desktop (udev-worker)[488]: hiddev0: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:57 Only network interfaces can be re>
фев 18 23:01:28 linux-desktop bluetoothd[758]: src/plugin.c:plugin_init() Failed to init vcp plugin
фев 18 23:01:28 linux-desktop bluetoothd[758]: src/plugin.c:plugin_init() Failed to init mcp plugin
фев 18 23:01:28 linux-desktop bluetoothd[758]: src/plugin.c:plugin_init() Failed to init bap plugin
фев 18 23:01:42 linux-desktop systemd[3848]: Failed to start Initial Bashrc setup.
фев 18 23:01:42 linux-desktop systemd[3848]: Failed to start BTRFS Assistant Snapper check.
фев 18 23:01:42 linux-desktop systemctl[4582]: Failed to enable unit: Unit file gamemoded\x3bsetup_dxvk.service does not exist.
фев 18 23:02:40 linux-desktop konsole[10789]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with QAction::setShortcut()! Use KAct>
фев 18 23:02:40 linux-desktop konsole[10789]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with QAction::setShortcut()! Use KAction>
фев 18 23:02:40 linux-desktop sudo[10837]:     ahbh : a password is required ; TTY=pts/0 ; PWD=/home/ahbh ; USER=root ; COMMAND=/usr/bin/true
фев 18 23:02:41 linux-desktop sudo[10874]:     ahbh : a password is required ; TTY=pts/0 ; PWD=/home/ahbh ; USER=root ; COMMAND=/usr/bin/true

[BluishHumility]

@mtsbh

Anbox

Anbox is all done I think, see Austin’s post here with links and alternative recommendations:

Ultimate Guide to install Anbox in any Arch-based distro(especially Garuda)

Anbox is deprecated now as its development has stalled, and its founding developer has acknowledged this. There are other alternatives: Anbox Cloud (for cloud) Waydroid (for desktop use) You can check out our Waydroid installation guide: The guide will be available here for any references. While trying to get Anbox running, you would probably get stuck somewhere and find it all confusing, just like it was for me before getting it running. I have made this guide so that it would be…

[mtsbh]

So u think that other errors are as a result of that anbox error?

[BluishHumility]

No, the Anbox thing is the only failed unit. The rest of the output is unrelated to that.

If you want to chase down these errors and clean up your log a bit, do a web search for the journal message and try to figure out what it means. For example:

@mtsbh

linux-desktop kernel: blacklist: Problem blacklisting hash

The very first result in a search query leads me to this thread, which provides an explanation and an additional thread you can follow for updates if you wish:

These kernel messages should be treated as warning, not error. You should not remove blacklisted hashes (i.e. do not clear secure boot keys), this is a security measure to protect against malicious signatures. These kernel messages now show because we hardened this security mechanism, and it now reveals issues with some firmwares. There is an ongoing kernel patch to update this error message: https://lore.kernel.org/lkml/3b997266-0 … gikod.net/

If you are no longer using Windows you can delete the secure boot keys and that will clear up the warning messages, but that guy says they are working on a kernel patch that will suppress the messages without deleting anything.

Long story short: the Anbox thing you should take care of as soon as you get a chance (I would just uninstall it/disable the service). The rest is not critical, but if you care and have time it’s worthy of investigation. Probably some of those would be easy to resolve.

[mtsbh]

@BluishHumility

If you are no longer using Windows you can delete the secure boot keys

I thought that I did that before, but it seems not.

@BluishHumility

the Anbox thing you should take care of

Yeah, already uninstalled it and I think there’s no more failed units.

Thank you!