serial port could not open no such file or directory

[Justin Nesselrotte]

Basically, I'm currently running bumblebee with just a small amount of changes (my github fork).  Nothing that would cause this. When starting bumblebee, it shows the main screen, but under status, it shows "error could not open port /dev/ttyACM0: (Errno 2) No such file or directory: '/dev/ttyACM0'

I would normally say that the obvious answer is that /dev/ttyACM0 doesn't exist. But it does. Running a 'ls /dev/tty*' shows it is there. And I've checked to make sure the spelling is correct.

So I'm not entirely sure what's up. I have dialout user permissions. It was working before, but now, not even the unmodified master branch will work. Why can't it see the serial port?

[Hyon Lim]

Did you check permission of tty device?

Normally (in case of ubuntu), your account should have dialout group.

Change the permission by 

$ sudo chmos 777 <device>

to solve easily.

-Hyon

This mail was written in mobile phone.

--
 
 

[Zach 'Hoeken' Smith]

Yeah, ubuntu was giving me some similar trouble a while back.  It's basically a permissions issue like hyon said.

----

Zach Hoeken Smith

Work: www.haxlr8r.com

Blog: www.hoektronics.com

Twitter: @hoeken  Skype: chilldude22

QQ: 1489598623  China: +86-186-8209-7069

--
 
 

[Justin Nesselrotte]

So after more research, I finally figured out exactly what the problem is. It's not exactly permissions. It seems to be a bug with bumblebee. (Currently working on it)

The best way I can demonstrate it is to tell you to set up a printer with the printcore driver, with a serial port like /dev/ttyFun or something. When booting, bumblebee will report it doesn't exist. If you go edit the config.json file, to change it to a dummy driver, and remove the port and baud lines, it'll still complain when you run the software that the port isn't found. Note, that you may have to run it once with the dummy driver with the port and baud lines still there for this to take effect.

Basically, from what I can tell, it's retaining the port information when it shouldn't be. It seems to be reading the config file each time, so I don't know if it caches it or what. Either way, if you run the test above, and it works correctly again, the other problem should be fixed too.