Have you tried to run the command with sudo?
If you have verified with lsusb -v that you can see the USB device connected to the machine then you should be able to get it going on linux with no issues, I had a machine set up running multiple brands of USB ASICs to both bgminer & cgminer running with different configs so that part should work ok. The thing that I had to do was use sudo to allow the miner software permission to access the USB devices. One I did that it worked like a dream.
Good luck..
I have been running it under root (after issuing the sudo -s command) and it seems to be doing that. I started running it with the sudo command before the minerd command and I am still getting lots of yellow text and no green text. thus the hashrate on the pool site is showing nothing. I am at a loss here. I am see the device in lspci and the minerd command is recognizing the device and is able to use it. the command is also successfully connected to the pool and showing some activity. the only problem I am having is that the program isn't doing anything under Linux. It works great in windows and I get the green and blue text through mining. I am not understanding why it's not working under Linux. To be clear, the program was compiled as I described in the first post, the program is working and is connecting to the pool and recognizing the device and is able to use it. It just won't work, I can see it's not working because the terminal isn't showing green text and is instead showing lots of yellow. Obviously something is wrong and I don't know what it is. It works fine in this same program under windows I just don't know why it's not working here. Is there a driver or something that I need to install in order for it to work better under Linux? Also, what am I looking for in the lsusb command, There is too much stuff being displayed and I am wanting to know what I should greg since it's a lot of stuff to go through. What Linux distribution would you recommend, I am using MINT and I am starting to think that this might be the problem. If it doesn't seem so that I am really at a loss here. I'm patching it for now and I'll post back with the results.
UPDATE!!!
Just updates the machine (apt-get upgrade) in hoping that a newer version of the Linux kernel would better support the device. I also ran the lsusb -v command and this came up
Bus 002 Device 006: ID 0483:5740 STMicroelectronics STM32F407
idProduct 0x5740 STM32F407
iProduct 2 STM32 Virtual COM Port
Still no sign of any green text so whatever is wrong it's still wrong. And to further clarify, the yellow text that keeps showing up is basically telling me that it can't stop dispatching new work. Windows finds work within 30 seconds but this doesn't seem to be doing the same.
ANOTHER UPDATE!!!
So I ran cpuminer with the syslog option and this is what came up. This could be useful in finding my solution to the problem
Jul 11 12:56:46 baron modem-manager[792]: <info> (ttyACM0) closing serial port...
Jul 11 12:56:46 baron modem-manager[792]: <info> (ttyACM0) serial port closed
Jul 11 12:56:46 baron modem-manager[792]: <info> (ttyACM0) opening serial port...
Jul 11 12:56:52 baron modem-manager[792]: <info> (ttyACM0) closing serial port...
Jul 11 12:56:52 baron modem-manager[792]: <info> (ttyACM0) serial port closed
Jul 11 12:56:52 baron modem-manager[792]: <info> (ttyACM0) opening serial port...
Jul 11 12:57:04 baron modem-manager[792]: <info> (ttyACM0) closing serial port...
Jul 11 12:57:04 baron modem-manager[792]: <info> (ttyACM0) serial port closed
Jul 11 12:57:04 baron modem-manager[792]: <info> (ttyACM0) opening serial port...
Jul 11 12:57:10 baron modem-manager[792]: <info> (ttyACM0) closing serial port...
Jul 11 12:57:10 baron modem-manager[792]: <info> (ttyACM0) serial port closed
It seems that the modem manager keeps continuously opening and closing the port, I also checked the modem manager and it doesn't seem to be detecting the device. I wonder if I need some drivers for this thing. This is just something to consider.
