# Can't see OpenMV on Ubuntu despite doing adduser dialout

**URL:** <https://forums.openmv.io/t/cant-see-openmv-on-ubuntu-despite-doing-adduser-dialout/274>\
**Category:** OpenMV Boards\
**Created:** [May 30, 2017, 1:38am UTC](https://forums.openmv.io/t/cant-see-openmv-on-ubuntu-despite-doing-adduser-dialout/274 "2017-05-30T01:38:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zlite](https://avatars.discourse-cdn.com/v4/letter/z/c6cbf5/32.png) [@zlite](https://forums.openmv.io/u/zlite)\
**Post date:** [May 30, 2017, 1:38am UTC](https://forums.openmv.io/t/cant-see-openmv-on-ubuntu-despite-doing-adduser-dialout/274/1 "2017-05-30T01:38:23Z")

</div>

I’ve done all the things listed in the Linux installation instructions, including sudo adduser dialout" but the OpenMV IDE still says “Error: Permission Denied” when I try to connect

The computer is a Chromebook Pixel running Ubuntu xenial (16)

When I do a dmesg it shows that the OpenMV has been assigned to ttyACM0 (see below). Is that what the IDE is looking for? If not, how do I tell it to do so?

[87804.052239] usb 1-1: new full-speed USB device number 48 using xhci\_hcd  
[87804.217727] usb 1-1: New USB device found, idVendor=1209, idProduct=abd1  
[87804.217747] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3  
[87804.217762] usb 1-1: Product: OpenMV Virtual Comm Port in FS Mode  
[87804.217776] usb 1-1: Manufacturer: OpenMV  
[87804.217785] usb 1-1: SerialNumber: 000000000011  
[87804.219490] cdc\_acm 1-1:1.0: This device cannot do calls on its own. It is not a modem.  
[87804.219555] cdc\_acm 1-1:1.0: ttyACM0: USB ACM device  
[87804.220702] usb-storage 1-1:1.2: USB Mass Storage device detected

---

<div class="post-metadata">

**Author:** ![kwagyeman](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/kwagyeman/32/4_2.png) [@kwagyeman](https://forums.openmv.io/u/kwagyeman)\
**Post date:** [May 30, 2017, 1:54am UTC](https://forums.openmv.io/t/cant-see-openmv-on-ubuntu-despite-doing-adduser-dialout/274/2 "2017-05-30T01:54:48Z")

</div>

Log out first. Log back in.

" sudo adduser dialout"

Requires re-longing in.

---

<div class="post-metadata">

**Author:** ![iabdalkader](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.openmv.io/iabdalkader/32/1169_2.png) [@iabdalkader](https://forums.openmv.io/u/iabdalkader)\
**Post date:** [May 30, 2017, 2:00am UTC](https://forums.openmv.io/t/cant-see-openmv-on-ubuntu-despite-doing-adduser-dialout/274/3 "2017-05-30T02:00:35Z")

</div>

If there’s more than one serial port, the IDE will ask you to choose. Did you log out after adding the user to group dialout ? if so, you could try this [udev file](https://raw.githubusercontent.com/openmv/openmv/master/udev/50-openmv.rules), just copy it to **/etc/udev/rules.d/** and make it executable

```python
sudo chmod +x /etc/udev/rules.d/50-openmv.rules

```

then reboot or reload udev rules

```python
sudo udevadm control --reload

```

---

<div class="post-metadata">

**Author:** ![zlite](https://avatars.discourse-cdn.com/v4/letter/z/c6cbf5/32.png) [@zlite](https://forums.openmv.io/u/zlite)\
**Post date:** [May 30, 2017, 8:08am UTC](https://forums.openmv.io/t/cant-see-openmv-on-ubuntu-despite-doing-adduser-dialout/274/4 "2017-05-30T08:08:05Z")

</div>

Thanks guys. I did all that, but no joy – still Permission Denied. So I dug around a bit, and it turns out that the command should actually be “sudo adduser serial” (not “dialout”). Now it works

I think something has changed in Debian/Ubuntu, or perhaps that particular port is part of the serial group, not the dialout group. At any rate, might be something worth noting in the docs…

---

<div class="post-metadata">

**Author:** ![dhylands](https://avatars.discourse-cdn.com/v4/letter/d/ea5d25/32.png) [@dhylands](https://forums.openmv.io/u/dhylands)\
**Post date:** [May 30, 2017, 4:56pm UTC](https://forums.openmv.io/t/cant-see-openmv-on-ubuntu-despite-doing-adduser-dialout/274/5 "2017-05-30T16:56:55Z")

</div>

Different distros setup the group stuff differently, so the real answer is to look at the /dev/ttyACM0 file and see which group it belongs to and whether there are even group write permissions.
