Unresponsive kb/m after boot


Hi, I just installed manjaro-kde and I noticed that after each boot my kb/m are unresponsive for a minute, not even the lights are on. Once the lights turn on on both they work normally without any issues. Any idea what could be causing this? Thanks.
Keyboard G910 Orion Spark Mouse G502 Hero

System: Host: pr0xyw0rm-manjaro Kernel: 4.19.13-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: KDE Plasma 5.14.4
Distro: Manjaro Linux
Machine: Type: Desktop Mobo: ASUSTeK model: MAXIMUS IX CODE v: Rev 1.xx serial: UEFI: American Megatrends v: 1301
date: 03/14/2018
CPU: Topology: Quad Core model: Intel Core i7-7700K bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 8192 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 67224
Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
Graphics: Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: ASUSTeK driver: nvidia v: 415.25 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.3 driver: nvidia tty: N/A
OpenGL: renderer: GeForce GTX 1080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 415.25 direct render: Yes
Audio: Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Device-2: NVIDIA GP102 HDMI Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1
Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-3:3
Device-4: Logitech type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-4:5
Device-5: Logitech type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-5:7
Device-6: C-Media Blue Snowball type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-6.1:12
Sound Server: ALSA v: k4.19.13-1-MANJARO
Network: Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: f000 bus ID: 00:1f.6
IF: enp0s31f6 state: down mac:
Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: ASUSTeK driver: ath10k_pci v: kernel
port: e000 bus ID: 04:00.0
IF: wlp4s0 state: up mac:
Drives: Local Storage: total: 11.14 TiB used: 7.77 GiB (0.1%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 1TB size: 931.51 GiB
ID-2: /dev/sda vendor: Western Digital model: WD5001FZWX-00ZHUA0 size: 4.55 TiB
ID-3: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
ID-4: /dev/sdc vendor: Seagate model: ST6000DM004-2EH11C size: 5.46 TiB
Partition: ID-1: / size: 95.34 GiB used: 7.77 GiB (8.2%) fs: ext4 dev: /dev/sda3
Sensors: System Temperatures: cpu: 26.0 C mobo: N/A gpu: nvidia temp: 37 C
Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0%
Info: Processes: 213 Uptime: 10m Memory: 15.60 GiB used: 1.70 GiB (10.9%) Init: systemd Compilers: gcc: 8.2.1 Shell: bash
v: 4.4.23 inxi: 3.0.28


Analysing your observations, it is obvious there is no system (HW-SW) problem, since everything works as expected, except some late “start” on system-components connections (just thinking out loud…).

It should be easily found what causes this with systemd-analyze blame, though I suspect it’s the disk fsck (check for errors).
I wouldn’t worry, but it doesn’t hurt to look it up…

systemd-analyze blame


thanks for the reply, this is what I got after that command. All this loading times look pretty fast to me. What do you think?

      3.008s lvm2-monitor.service
      2.304s systemd-journal-flush.service
      2.225s dev-sda3.device
      1.836s man-db.service
      1.687s ModemManager.service
      1.577s systemd-modules-load.service
      1.294s tlp.service
      1.025s NetworkManager.service
       834ms polkit.service
       736ms systemd-logind.service
       641ms systemd-udevd.service
       614ms avahi-daemon.service
       585ms grub-boot-indeterminate.service
       353ms udisks2.service
       293ms upower.service
       258ms systemd-timesyncd.service
       249ms logrotate.service
       220ms systemd-tmpfiles-setup-dev.service
       181ms sys-kernel-debug.mount
       179ms dev-hugepages.mount
       177ms org.cups.cupsd.service
       169ms systemd-binfmt.service
       162ms systemd-sysctl.service
       155ms tmp.mount
       155ms systemd-remount-fs.service
       154ms dev-mqueue.mount
       130ms wpa_supplicant.service
       112ms systemd-tmpfiles-setup.service
       112ms proc-sys-fs-binfmt_misc.mount
       109ms systemd-random-seed.service
       100ms kmod-static-nodes.service
        77ms systemd-fsck@dev-disk-by\x2duuid-D616\x2d95A3.service
        67ms bluetooth.service
        51ms systemd-udev-trigger.service
        50ms rtkit-daemon.service
        47ms systemd-journald.service
        47ms boot-efi.mount


I agree, of course. Does this happen all times/boots?
So, do you have to wait at SDDM screen until keyboard and mouse are alive?
You may check the logs for errors and if no serious output, review full logs

journalctl -b -p3 
cat /var/log/Xorg.0.log | grep -E "(EE)|(WW)"

Please use proper formatting for outputs.

closed #5

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