Reboot failed on Garuda KDE Dr460nized Gaming Edition

Hi to all ,

I'm new in Garuda. Great distro !

My problem is, every time I reboot the PC I get this error:

[FAILED] Failed to start Wait for Network to be Configured. Broadcast message from [email protected] on pts/3 (Wed 2023-02-15 21:06:19 CET):

The system will reboot now!

[20965.367803] watchdog: watchdog0: watchdog did not stop! [20970.4353301 reboot: Restarting system

[20966.338528] watchdog: [email protected]: watchdog did not stop! [20969.071835] watchdog: watchdog0: watchdog did not stop!21:40

I attach the garuda-inxi output in the next link:

  Kernel: 6.1.11-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=db8f597f-ee34-448c-9e7e-43615296aac6 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=37068b2e-2770-4abb-872e-c7824dbda90a loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock
    wm: kwin_x11 vt: 1 dm: 1: GDM v: 43.0 note: stopped 2: SDDM note: stopped
    Distro: Garuda Linux base: Arch Linux
  Type: Desktop Mobo: Micro-Star model: MS-B9331 v: 1.0 serial: <filter>
    UEFI: American Megatrends v: 8.00 date: 06/15/2020
  Info: model: Intel Core i5-10400F socket: U3E1 bits: 64 type: MT MCP
    arch: Comet Lake gen: core 10 level: v3 note: check built: 2020
    process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 3
    microcode: 0xF4
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 3631 high: 4002 min/max: 800/4300 base/boost: 2871/8300
    scaling: driver: intel_pstate governor: performance volts: 0.8 V
    ext-clock: 100 MHz cores: 1: 4000 2: 4000 3: 4002 4: 4000 5: 4000 6: 1335
    7: 4002 8: 3999 9: 4001 10: 4001 11: 3999 12: 2243 bogomips: 69597
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
  Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: Micro-Star MSI
    driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
    status: current (as of 2023-02) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:1f06 class-ID: 0300
  Device-2: Logitech C922 Pro Stream Webcam type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1- chip-ID: 046d:085c
    class-ID: 0102 serial: <filter>
  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: 3840x1080 s-dpi: 80 s-size: 1219x343mm (47.99x13.50")
    s-diag: 1266mm (49.86")
  Monitor-1: DP-3 pos: left res: 1920x1080 hz: 60 dpi: 92
    size: 530x300mm (20.87x11.81") diag: 609mm (23.98") modes: N/A
  Monitor-2: DP-4 pos: primary,right res: 1920x1080 dpi: 82
    size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX 2060
    SUPER/PCIe/SSE2 direct-render: Yes
  Device-1: Intel Comet Lake PCH-V cAVS vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 1-1.2:4 chip-ID: 045e:083c
    alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3 class-ID: 0300
    chip-ID: 8086:a3f0 serial: <filter> class-ID: 0403
  Device-2: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Device-3: Microsoft USB Link type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Device-4: Logitech C922 Pro Stream Webcam type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1- chip-ID: 046d:085c
    class-ID: 0102 serial: <filter>
  Sound API: ALSA v: k6.1.11-zen1-1-zen running: yes
  Sound Interface: sndio v: N/A running: no
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.65 running: yes
  Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
    v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d55 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp4s0 state: down mac: <filter>
  IF-ID-1: anbox0 state: down mac: <filter>
  IF-ID-2: wgivpn state: unknown speed: N/A duplex: N/A mac: N/A
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-9:14 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
  Local Storage: total: 5.01 TiB used: 132.72 GiB (2.6%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 PRO 512GB
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 1B2QEXP7 temp: 44.9 C scheme: GPT
  SMART: yes health: PASSED on: 1y 115d 22h cycles: 2,853
    read-units: 114,207,698 [58.4 TB] written-units: 86,262,296 [44.1 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000BX500SSD1
    family: Micron Client SSDs size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.3 speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 061 temp: 35 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 31d 15h cycles: 176
    written: 8.77 TiB
  ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate model: Expansion
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: N/A
    serial: <filter> rev: 0708 scheme: GPT
  SMART Message: A mandatory SMART command failed. Various possible causes.
  ID-1: / raw-size: 888.2 GiB size: 888.2 GiB (100.00%)
    used: 132.72 GiB (14.9%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 612 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 888.2 GiB size: 888.2 GiB (100.00%)
    used: 132.72 GiB (14.9%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-4: /var/log raw-size: 888.2 GiB size: 888.2 GiB (100.00%)
    used: 132.72 GiB (14.9%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-5: /var/tmp raw-size: 888.2 GiB size: 888.2 GiB (100.00%)
    used: 132.72 GiB (14.9%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 43.01 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
  ID-2: swap-2 type: zram size: 39.1 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  System Temperatures: cpu: 53.0 C mobo: N/A gpu: nvidia temp: 43 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 31%
  Processes: 421 Uptime: 16m wakeups: 1 Memory: 39.1 GiB
  used: 11.22 GiB (28.7%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 2745 libs: 643 tools: gnome-software,octopi,pamac,paru,yay pm: flatpak
  pkgs: 0 Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.25
Garuda (2.6.14-1):
  System install date:     2023-02-10
  Last full system update: 2023-02-15
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
  Windows dual boot:       Yes
  Failed units:            anbox-container-manager.service systemd-networkd-wait-online.service 

Any idea ?

Thanks in advance !

Welcome to the Forum!

Does this error prevent you from rebooting or slows down the reboot process?

Hi @FGD ,

Yes, it prevent to me to rebooting.

Thanks for your interest.

Try adding the nowatchdog kernel parameter.

An easy way to do add it is with Garuda Boot Options, where you can simply add it to the end of the "Kernel parameters" line:

Make sure you click "Apply" (bottom right corner), then reboot.

The kernel parameter won't do anything until your next boot, because it gets loaded with the kernel at boot. So to test if it works, you will actually need to reboot twice.


Hi @BluishHumility ,

I rebooted some times, and it seems it is SOLVED now.


Hi to all,

After trying this solution, some days, it does not work always, work sometimes randomly only. Very curiously ...

More ideas ?


Edit this file:

sudo micro /etc/systemd/system.conf

Find the line that says RebootWatchdogSec, uncomment it by removing the #, and set the value to 0 so it looks like this:


Save and exit, then reboot again.

After that, I have no more ideas. :wink:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.