You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Parrot Security OS升级后登录时键盘无法输入的技术求助

Fixing Keyboard/Mouse Detection Failure After Parrot Security 3.7 → 3.11 Upgrade

Alright, let's dig into this issue where your keyboard and mouse get disabled at the login screen post-upgrade, even though you can access root via recovery mode. From the Xorg log snippet you shared, the core problem is that the X server is blocking your input devices—this usually boils down to misconfigured drivers, overwritten configs, or compatibility gaps between the new Xorg version (1.19.6 here) and your system's input setup.

First, What Files to Check (From Recovery Mode Root Terminal)

Boot into recovery mode, then head to these key locations to diagnose:

  1. Xorg Input Configuration Files

    • Check /etc/X11/xorg.conf (if it exists) and everything under /etc/X11/xorg.conf.d/ (like 10-evdev.conf or 40-libinput.conf).
    • What to look for: Any lines with Option "Disable" "true" that might be explicitly turning off your devices, or outdated driver references (e.g., using evdev when your system now uses libinput post-upgrade).
  2. Udev Device Rules

    • Navigate to /etc/udev/rules.d/ (custom rules) and /lib/udev/rules.d/ (system defaults).
    • Check for rules that incorrectly mark your keyboard/mouse as unreadable, or set wrong permissions that prevent Xorg from accessing the devices.
  3. Full Xorg Log

    • You only shared the start of /var/log/Xorg.0.log—grab the whole file and search for lines with keyboard, mouse, input, or Disable. Look for messages like:

      [ 78.543] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
      [ 78.543] (II) No input driver specified, ignoring this device.

    • These lines will tell you if Xorg is missing a driver for your devices or actively blocking them.

Step-by-Step Fixes

Let's go through the most likely solutions:

1. Fix Xorg Input Driver Configs

If your config files are messed up, back them up first then adjust:

  • Backup the libinput config (common culprit):
    cp /etc/X11/xorg.conf.d/40-libinput.conf /etc/X11/xorg.conf.d/40-libinput.conf.bak
    
  • Edit the file with nano /etc/X11/xorg.conf.d/40-libinput.conf and make sure it includes these sections for keyboard and mouse:
    Section "InputClass"
            Identifier "keyboard-all"
            MatchIsKeyboard "on"
            Driver "libinput"
            Option "XkbLayout" "us"  # Replace with your actual layout, e.g., "gb" for UK
    EndSection
    
    Section "InputClass"
            Identifier "mouse-all"
            MatchIsMouse "on"
            Driver "libinput"
    EndSection
    
  • If you don't have an xorg.conf file, generate a fresh one:
    Xorg -configure
    cp xorg.conf.new /etc/X11/xorg.conf
    

2. Reset Udev Rules

If udev is misbehaving, reset to default rules:

  • Remove any custom input rules (if you added them):
    rm /etc/udev/rules.d/*-input.rules
    
  • Reload udev and trigger device detection:
    udevadm control --reload-rules && udevadm trigger
    

3. Reinstall Input Drivers

Upgrade glitches can corrupt driver files—reinstall them:

apt update && apt install --reinstall xserver-xorg-input-libinput xserver-xorg-input-evdev libinput10

4. Verify Kernel Modules

Make sure the kernel modules for input devices are loaded:

  • Check loaded modules:
    lsmod | grep -E "usbhid|hid|i8042"
    
  • If any are missing, load them manually:
    modprobe usbhid && modprobe i8042
    
  • Set them to load on boot:
    echo "usbhid" >> /etc/modules
    echo "i8042" >> /etc/modules
    

Test the Fix

After making changes, start the login manager manually to test:

systemctl start lightdm

If your keyboard/mouse work now, reboot into normal mode—everything should be back to normal. If not, double-check the Xorg log for new error messages to narrow it down.

内容的提问来源于stack exchange,提问作者hardeep

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.19 03:22:04