Issue with Airview-EXT9 and -EXT2 under Fedora Core 11

[jks19714]

I have a pair of AirView external spectrum analyzers plugged into a Fedora Core 11 network management workstation. Linux discovers the two devices OK and creates two tty devices in /dev:

ls -l ttyACM*
crw-rw----. 1 root dialout 166, 0 2009-11-29 13:51 ttyACM0
crw-rw----. 1 root dialout 166, 1 2009-11-29 13:51 ttyACM1

Then, I start airview.sh while su'd to root and the application opens. It then sits and "spins its' wheels", but never finds either AirView device.

Any words of wisdom? I noticed that the .sh script identifies ttyACM0 through ttyACM8, so the USB discovery process looks OK.

I even tried creating a special shell script (two_airviews.sh) as follows:

#!/bin/sh
# Start two AirView modules JKS

java -Djava.library.path=. -Dapp.logging.file.path=./log/runtime.log -Dgnu.io.SerialPorts=/dev/ttyACM0 -jar airview-o.jar >> /dev/null 2>&1

java -Djava.library.path=. -Dapp.logging.file.path=./log/runtime.log -Dgnu.io.SerialPorts=/dev/ttyACM1 -jar airview-o.jar >> /dev/null 2>&1

They serquentlially sit and spin their wheels, even when I have the application more than a hint where to find them.

I guess that I could surrender and run it under Windows, but I would REALLY get the application running properly, as the Linux box has a dedicated flat panel for my four-eyed viewing pleasure. :-)

Thanks,
john

[UBNT-Ramin]

The app has been tested and works flawlessly under Centos 5.3/5.4, Fedora 9, Ubuntu 9.0.x/9.10, and OpenSuse 11. I have a hard time believing things changed so much under Fedora 11 that it broke it to that extent, but with the bleeding edge Fedora distros, you never know.

Please locate your runtime.log file under /home/your-username/ubiquiti-networks/, delete the log file, then restart the app from the official script (airview.sh, not the ones you wrote), let it fail, shut the app down, and then please paste the contents of runtime.log here so I can check for any clues.

Thanks,