On a slack box dmesg gave me likewise, /dev/rfcomm0 I did a sudo chmod 777 /dev/rfcomm0 and device works fine. I guess with other distros it 's getting the user account the access to the attached device. Kurt KC9LDH -------------------------------------------- On Wed, 11/19/14, Bryan Irwin <[email protected]> wrote:
Subject: Re: [Xastir] Xastir and Mobilinkd Tnc 1 Bluetooth tnc (Kurt) To: "Xastir - APRS client software discussion" <[email protected]> Date: Wednesday, November 19, 2014, 10:52 AM bryan@bryan-Lenovo:~$ ls -la /dev/rfcomm* crw-rw---- 1 root dialout 216, 0 Nov 18 17:33 /dev/rfcomm0 bryan@bryan-Lenovo:~$ groups bryan adm dialout cdrom sudo dip plugdev lpadmin sambashare My problem ended up being that my user account wasn't part of the dialout group. Once I got that reconciled everything worked flawlessly. Now I have to figure out the bug (documented) that shutdown both the bluetooth and wifi in my box so I can have everything working again. _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
