Ckb-next: I have to unplug and plug in my Keyboard for it to work.

[derbrachialist]

Every time I boot, I have to unplug and plug in my K95 Keyboard for it to work.
It does not register keystrokes and the LEDs are set to the default rainbow thing at boot.

[Sur3]

Did you follow the usb quirks guide? https://github.com/ckb-next/ckb-next/wiki/Troubleshooting

[derbrachialist]

I need some help with that.
I typed in the command and go the following quirks: usbhid.quirks=0x1b1c:0x1b2d:0x20000408,0x1b1c:0x1b2e:0x20000408,0x1b1c:0x1b3b:0x20000408
Do I just add this to my grub boot sequence? Just at the end?

[derbrachialist]

I edited it to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet usbhid.quirks=0x1b1c:0x1b2d:0x20000408,0x1b1c:0x1b2e:0x20000408,0x1b1c:0x1b3b:0x20000408 rd.driver.pre=vfio-pci kvm.ignore_msrs=1 cryptdevice=UUID=a7bba2cf-...:luks-a7bba2cf... root=/dev/mapper/luks-a7bba2c... resume=/dev/mapper/luks-a7bba2cf..."

Will reopen if it does not fix the problem or I did it wrong.

[derbrachialist]

still got the problem at like every 5th boot

[STiAT]

At boot or after login?

asking because it could possibly be related to https://github.com/ckb-next/ckb-next/issues/584

If it's at boot time it probably isn't related, but if it's after/at login it may be related, since that with the usb mouse occurs at ~20 % of the times as well, and seems to be related to usb detection (did a bit of debugging with KitsuWhoaa today, but didn't get to a conclusion, we'll continue this though).

I don't know the code well enough to judge, but the symptoms are pretty... similar.

[derbrachialist]

After login.

I removed the GRUB_CMDLINE because it broke my drm protection and I could no longer watch Netflix.

[Mageas]

I had the same problem. In my case, all I had to do was stop the daemon service and then turn it on.
I made a script that starts automatically when my computer starts.

#!/bin/bash

# Fichier de logs et format de date
LOG_FILE="`dirname $(readlink -f $0)`/logs/${0##*/}.log"
DATE () {
    echo $(date +"%d/%m/%y %H:%M:%S")
}

# List of corsair devices
MY_DEVICES=(
    "CORSAIR SCIMITAR RGB ELITE Gaming Mouse"
);

printf '\n[%s]: Start of ckb-next debug' "$(DATE)" >> $LOG_FILE

# Name of all devices
get_devices_name () {
    printf '\n[%s]: List of devices' "$(DATE)" >> $LOG_FILE
    for device in $(ls /sys/bus/usb/devices/*/product); do 
        echo $(cat $device);
    done 
}

# Force the replug of the USB
force_usb_replug () {
    for device in $(ls /sys/bus/usb/devices/*/product); do 
        local device_name=$(cat $device);
        for my_device in "${MY_DEVICES[@]}"; do 
            if [[ "$device_name" == "$my_device" ]]; then
                IFS='/' read -r -a device_ids <<< "$device"
                local device_id="${device_ids[5]}"

                echo "Replugging: $device_name"
                printf '\n[%s]: Replugging: %s' "$(DATE)" "$device_name" >> $LOG_FILE
                echo "${device_id}" | sudo tee /sys/bus/usb/drivers/usb/unbind
                echo "${device_id}" | sudo tee /sys/bus/usb/drivers/usb/bind
                sleep 1s
            fi
        done 
    done
}

# Restart daemon services
restart_daemon_service () {
    # Waiting for app to launch
    while [ -z $(pidof ckb-next) ] || [ -z $(pidof ckb-next-daemon) ]; do
        printf '\n[%s]: Waiting for ckb-next and ckb-next-daemon' "$(DATE)" >> $LOG_FILE
        sleep 3s
    done

    sleep 1s

    # Restart daemon
    sudo systemctl stop ckb-next-daemon.service
    sleep 1s
    sudo systemctl start ckb-next-daemon.service

    printf '\n[%s]: Daemon restarted' "$(DATE)" >> $LOG_FILE

}

if [[ "$1" == "--name" ]]; then
    get_devices_name
elif [[ "$1" == "--force" ]]; then
    force_usb_replug
    restart_daemon_service
else
    restart_daemon_service
fi

How the script works:
--name: List of all devices.
--force: Force the USB to disconnect then restart the daemon (You have to change the content of MY_DEVICES table with the name of your devices)
Without flag: Restart the daemon

I run the script without any flags (You need to run as root. use systemctl for startup).
Hoping this might help you!

EDIT: The last version of this script was edited by a friend!

[tatokis]

EDIT: Completely wrong issue. Apologies

[CerulanLumina]

What's the status on this issue? It's still very prevalent for me, occurring on perhaps 80-90% of boots. Oddly enough, sometimes if I start typing in my password to sddm quickly enough I'll get a few characters in before it ceases to work. Even weirder if it stops working in the middle of a key press the key gets spammed repeatedly until unplugging the keyboard.

[Ravenslofty]

Tasos made some commits to master to attempt to fix the situations he got
the keyboard to stop working when resuming from sleep. You could join us in
IRC and we can try to debug the issue there, but first make sure you are
using the latest Git code.

On Sat, 3 Oct 2020, 12:58 Cerulan Lumina, [e-mail] wrote:

What's the status on this issue? It's still very prevalent for me,
occurring on perhaps 80-90% of boots. Oddly enough, sometimes if I start
typing in my password to sddm quickly enough I'll get a few characters in
before it ceases to work. Even weirder if it stops working in the middle of
a key press the key gets spammed repeatedly until unplugging the keyboard.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ckb-next/ckb-next/issues/580#issuecomment-703092176,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALPDW5O6V3LTNWCYRQUOBTSI4GX7ANCNFSM4M5HC4WA
.