Re: [chirp_users] CHMOD ...

2020-06-08 Thread W Paul Mills
Unless it is not in group dialout, it should work. Only other thing I can think is check dialout in with both "sudo vigr" and "sudo vigr -s" and make sure both dialout listings show your username. "vigr" stands for "vi" and "group", "vi" the editor

Re: [chirp_users] CHMOD ...

2020-06-08 Thread Angus Ainslie
You could create a udev rule that will set the permissions and/or group each time the device is plugged in. https://askubuntu.com/questions/15570/configure-udev-to-change-permissions-on-usb-hid-device On 2020-06-08 08:44, Pat Anderson wrote: > You are right that the device recreates itself every

Re: [chirp_users] CHMOD ...

2020-06-08 Thread Pat Anderson
You are right that the device recreates itself every time it is plugged in and the chmod is not persistent. However, I am a member of the dialout group, and that does not give me the required permission to access the /dev/ttyUSB0 device. I don't know why. So far, only the chmod "trick" if you will

Re: [chirp_users] CHMOD ...

2020-06-08 Thread W Paul Mills
While this will work, it is not really the right way to do it. It is also temporary. These devices recreate themselves every boot, or every time you reinsert a device. The right way is "sudo adduser user dialout" Substitue your user name for "user." On some systems the group may be different.

Re: [chirp_users] CHMOD ...

2020-06-07 Thread Pat Anderson
I did and you are welcome! Pat Anderson KD7OAC On Sun, Jun 7, 2020 at 5:15 PM Peter via chirp_users < chirp_users@intrepid.danplanet.com> wrote: > Hi all: > > I am not sure who came up with the brilliant tip of chmod 777 > /dev/ttyUSB0 as I have deleted the email suggesting that. > > So THANK YO

[chirp_users] CHMOD ...

2020-06-07 Thread Peter via chirp_users
Hi all: I am not sure who came up with the brilliant tip of chmod 777 /dev/ttyUSB0 as I have deleted the email suggesting that. So THANK YOU for that suggestion. I was getting frustrated trying to get Chirp on Linux Mint 19.2 to up/download from my new (to me) Icom 2100H. All I got was error m