From 6fd49fc3b7d4d153e024049414efa4b49ebea9ae Mon Sep 17 00:00:00 2001 From: Quentin Date: Thu, 22 Aug 2024 12:30:03 +0200 Subject: [PATCH 1/5] add via troubleshooting --- help/troubleshooting.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/help/troubleshooting.md b/help/troubleshooting.md index d9ba031..3e9d512 100644 --- a/help/troubleshooting.md +++ b/help/troubleshooting.md @@ -52,6 +52,30 @@ Since the LEDs are arranged in a chain, focus your efforts on the last LED that Please refer to the [diagnosing a broken trace](./diagnose_broken_trace.html#inspect-the-schematics) guide to learn how to inspect the schematics for your particular board. +# Flashing/Using Troubleshooting + +## Keyboard not recognized by VIA + +If your keyboard is not recognized by VIA, might be getting the following error: + +``` +Received invalid protocol version from device +``` + +Outlined below are some steps, in order of complexity: +- make sure you use a chromium-based browser like edge, google chrome +- flash the [latest firmware version](https://github.com/Bastardkb/bastardkb-qmk/releases/latest) + +### Custom udev rules + +If your keyboard is still not recognized and you are running a **Linux-based distribution**, you need to setup some custom udev rules to allow access to `hidraw` devices. + +To allow all users to access all `hidraw` devices, run the following command in your console: + +``` +export USER_GID=`id -g`; sudo --preserve-env=USER_GID sh -c 'echo "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", MODE=\"0660\", GROUP=\"$USER_GID\", TAG+=\"uaccess\", TAG+=\"udev-acl\"" > /etc/udev/rules.d/92-viia.rules && udevadm control --reload && udevadm trigger' +``` + # Glossary This section explains some of the terms used while troubleshooting in brief. From e3343be09d71c95163fde58a504d168c05afd91c Mon Sep 17 00:00:00 2001 From: Quentin Date: Thu, 22 Aug 2024 12:40:21 +0200 Subject: [PATCH 2/5] Update troubleshooting.md --- help/troubleshooting.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/help/troubleshooting.md b/help/troubleshooting.md index 3e9d512..467a69f 100644 --- a/help/troubleshooting.md +++ b/help/troubleshooting.md @@ -70,10 +70,16 @@ Outlined below are some steps, in order of complexity: If your keyboard is still not recognized and you are running a **Linux-based distribution**, you need to setup some custom udev rules to allow access to `hidraw` devices. -To allow all users to access all `hidraw` devices, run the following command in your console: +First, write this text to `/etc/udev/rules.d/92-viia.rules`: ``` -export USER_GID=`id -g`; sudo --preserve-env=USER_GID sh -c 'echo "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", MODE=\"0660\", GROUP=\"$USER_GID\", TAG+=\"uaccess\", TAG+=\"udev-acl\"" > /etc/udev/rules.d/92-viia.rules && udevadm control --reload && udevadm trigger' +KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0660", GROUP="users", TAG+="uaccess", TAG+="udev-acl" +``` + +Then, reload `udev` by running this command as `root`: + +``` +udevadm control --reload-rules && udevadm trigger ``` # Glossary From 3097b390a46b1f3f9fe8fc70d43d7ccb881d081e Mon Sep 17 00:00:00 2001 From: Quentin Date: Thu, 22 Aug 2024 12:45:32 +0200 Subject: [PATCH 3/5] Update troubleshooting.md --- help/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/help/troubleshooting.md b/help/troubleshooting.md index 467a69f..bf0750b 100644 --- a/help/troubleshooting.md +++ b/help/troubleshooting.md @@ -70,7 +70,7 @@ Outlined below are some steps, in order of complexity: If your keyboard is still not recognized and you are running a **Linux-based distribution**, you need to setup some custom udev rules to allow access to `hidraw` devices. -First, write this text to `/etc/udev/rules.d/92-viia.rules`: +First, write this text to `/etc/udev/rules.d/92-via.rules`: ``` KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0660", GROUP="users", TAG+="uaccess", TAG+="udev-acl" From b2975344f0d9cc23774f3d24cac08bb770abd501 Mon Sep 17 00:00:00 2001 From: Quentin Date: Thu, 22 Aug 2024 12:45:55 +0200 Subject: [PATCH 4/5] Update troubleshooting.md --- help/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/help/troubleshooting.md b/help/troubleshooting.md index bf0750b..6bfc75e 100644 --- a/help/troubleshooting.md +++ b/help/troubleshooting.md @@ -68,7 +68,7 @@ Outlined below are some steps, in order of complexity: ### Custom udev rules -If your keyboard is still not recognized and you are running a **Linux-based distribution**, you need to setup some custom udev rules to allow access to `hidraw` devices. +If your keyboard is still not recognized and you are running a **Linux-based distribution**, you need to setup some custom udev rules to allow access to `hidraw` devices for regular users: First, write this text to `/etc/udev/rules.d/92-via.rules`: From 42831e8a2ba0ff88dc319ed3b2cecc1cf36e5140 Mon Sep 17 00:00:00 2001 From: Quentin Date: Thu, 22 Aug 2024 13:09:37 +0200 Subject: [PATCH 5/5] Update .wordlist.txt --- .wordlist.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.wordlist.txt b/.wordlist.txt index 4e01460..3a3d006 100644 --- a/.wordlist.txt +++ b/.wordlist.txt @@ -130,4 +130,8 @@ noeeprom eeprom drgscrl dragscroll -reflash \ No newline at end of file +reflash + +hidraw +uaccess +udevadm \ No newline at end of file