# Device or resource busy

**URL:** <https://community.keyboard.io/t/device-or-resource-busy/451>\
**Category:** Help and Getting Started\
**Created:** [October 19, 2017, 11:53am UTC](https://community.keyboard.io/t/device-or-resource-busy/451 "2017-10-19T11:53:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Jennigma](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/jennigma/32/353_2.png) [@Jennigma](https://community.keyboard.io/u/Jennigma)\
**Post date:** [October 19, 2017, 4:43pm UTC](https://community.keyboard.io/t/device-or-resource-busy/451/3 "2017-10-19T16:43:44Z")

</div>

You are using Ubuntu? We discussed this a couple days ago when I was starting to work through a Linux install for writing up docs. Discussion here:

> [@Feedback requested: simplified software installation](https://community.keyboard.io/t/feedback-requested-simplified-software-installation/348/23):
>
> I was using Debian. If you are on Ubuntu, check if you have ModemManager installed, it has a tendency of jumping on each and every serial port, which can easily result in them getting busy. The Kaleidoscope repo has some [udev rules](https://github.com/keyboardio/Kaleidoscope/blob/master/etc/99-kaleidoscope.rules) you can install, which will prevent ModemManager stealing the keyboard’s serial port. Stick that file in /etc/udev/rules.d, and then sudo udevadm control -R should reload the rules. Plugging the keyboard in afterwards should then work.

Stopping ModemManager may be a bit more extreme than needed; you can follow algernon’s advice to get ModemManager to just ignore the keyboard. 🙂

---

_[View the full topic](https://community.keyboard.io/t/device-or-resource-busy/451)._