# Cannot install node-red-contrib-oled after upgrade to buster and v1.03

**URL:** <https://discourse.nodered.org/t/cannot-install-node-red-contrib-oled-after-upgrade-to-buster-and-v1-03/19238>\
**Category:** General\
**Created:** [16 December 2019 20:59 UTC](https://discourse.nodered.org/t/cannot-install-node-red-contrib-oled-after-upgrade-to-buster-and-v1-03/19238 "2019-12-16T20:59:31Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [17 December 2019 12:31 UTC](https://discourse.nodered.org/t/cannot-install-node-red-contrib-oled-after-upgrade-to-buster-and-v1-03/19238/2 "2019-12-17T12:31:13Z")

</div>

Looks like it might be running into the i2c issues that being discussed over here

> [@Node-red-contrib-i2c fails to install](https://discourse.nodered.org/t/node-red-contrib-i2c-fails-to-install/18774):
>
> I can't install the following npm install node-red-contrib-i2c npm install node-red-contrib-i2c npm ERR! code EISDIR npm ERR! syscall read npm ERR! errno -21 npm ERR! EISDIR: illegal operation on a directory, read npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/\_logs/2019-12-04T05\_05\_30\_126Z-debug.log npm -v 6.13.1 node -v v13.2.0 18 verbose stack Error: EISDIR: illegal operation on a directory, read 19 verbose cwd /home/pi 20 verbose Linux 4.19.75-v7l+ …

Might be best rasing an issue on the nodes github page and see if the author can sort it out

You can try playing around manually installing the i2c-bus npm package but it would just be luck if it works

---

_[View the full topic](https://discourse.nodered.org/t/cannot-install-node-red-contrib-oled-after-upgrade-to-buster-and-v1-03/19238)._