Perixx 1800 Keyboard Driver for Linux
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Christoph Haas 774803dfa7
Add udev rule description (tested on Arch with Kernel 4.18)
5 years ago
.gitignore Update .gitignore 5 years ago
.gitlab-ci.yml Add .gitlab-ci.yml for syncing to github 5 years ago
LICENSE Initial commit 7 years ago
Makefile Added fix for archlinux 7 years ago Add udev rule description (tested on Arch with Kernel 4.18) 5 years ago
dkms.conf Initial commit 7 years ago Added fix for archlinux 7 years ago Created QT Creator project 6 years ago
perixxkbd.c Updated to support kernel 4.15.x, tested on Arch Linux with Kernel 4.15.7 and 4.15.8 (dkms) 5 years ago

Linux Microdia Keyboard (Perixx PX-1800) Chipset Driver

For Chipset 0x0c45:0x7603 The kernel reports the chipset as Microdia

Written for the Perixx PX-1800 USB Keyboard: Perixx PX-1800 Keyboard

Original base:,

NOTE: Makefile and instructions are only tested on Ubuntu 16.04 and Archlinux 2016.10 (Kernel 4.8.4)

Building in Qt Creator

In the Qt Creator go to the "Projects" and unset the "Shadow build" In the "Build Steps" remove all items and add "make" item. In the make item in the first field set make, in the second field set command (default) for your Makefile. Also you can set your build script.



# debian-based:
sudo apt-get install git build-essential linux-headers-generic dkms

# fedora:
sudo dnf install git kernel-devel kernel-headers
sudo dnf groupinstall "Development Tools" "Development Libraries"

# arch:
sudo pacman -S git base-devel linux-headers dkms

# on all platforms:
git clone
cd perixx1800keyboard
sudo ./ dkms

Manual Install

# Dependencies:
git build-essential linux-headers dkms
git clone
cd perixx1800keyboard
sudo ./


NOTE: attempts to blacklist the driver for you. You shouldn't need to do anything manually. These instructions are to explain the process, in the event something goes wrong.

You need to blacklist the device from the generic USB hid driver in order for the perixxkbd driver to control it.

Kernel Module

If the USB hid driver is compiled as a kernel module you will need to create a quirks file and blacklist it there.

You can determine if the driver is a module by running the following:

lsmod | grep usbhid

If grep finds something, it means that the driver is a module.

Create a file called /etc/modprobe.d/usbhid.conf and add the following to it:

options usbhid quirks=0x0c45:0x7603:0x0004

If you find that the generic USB driver is still taking the device, try changing the 0x0004 to a 0x0007.

Compiled into Kernel

If the generic USB hid driver is compiled into the kernel, then the driver is not loaded as a module and setting the option via modprobe will not work. In this case you must pass the option to the driver via the grub boot loader.

Create a new file in /etc/default/grub.d/. For example, you might call it perixx1800keyboard.conf. (If your grub package doesn't have this directory, just modify the generic /etc/default/grub configuration file):


Then run sudo update-grub and reboot.

Again, if you find that 0x4 doesn't work, try 0x7.

Add to initramfs

On Archlinux the module has to be added to /etc/mkinitcpio.conf. Otherwise usbhid will fetch the keyboard before perixxkbd is loaded.

Therefor add "perixxkbd" to the MODULES section and rebuild the initramfs with sudo mkinitcpio -p linux

Add a UDEV rule

If none of the above works and usbhid takes control over the keyboard, add a custom udev rule to manually rebind the driver.

Create a new file /etc/udev/rules.d/10-perixxkbd.rules:

ATTRS{idVendor}=="0c45", ATTRS{idProduct}=="7603", MODE="0666", PROGRAM="/bin/sh -c 'echo -n $id:1.1 >/sys/bus/usb/drivers/usbhid/unbind;echo -n $id:1.1 >/sys/bus/usb/drivers/perixxkbd/bind'"