Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permission Denied for AnyTone AT-D878UV Radio #46

Open
JeffHochberg opened this issue Jan 22, 2020 · 1 comment
Open

Permission Denied for AnyTone AT-D878UV Radio #46

JeffHochberg opened this issue Jan 22, 2020 · 1 comment

Comments

@JeffHochberg
Copy link

Hello,

I followed the instructions on adding /etc/udev/rules.d/99-dmr.rules and added the recommended values:

# TYT MD-UV380
SUBSYSTEM=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", MODE="666"

# Baofeng RD-5R, TD-5R, DM-1801
SUBSYSTEM=="usb", ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="0073", MODE="666"

# Anytone AT-D868UV: ignore this device in Modem Manager
ATTRS{idVendor}=="28e9" ATTRS{idProduct}=="018a", ENV{ID_MM_DEVICE_IGNORE}="1"

I ran sudo udevadm control --reload-rules and disconnected/reconnected my AnyTone AT-D878UV to my computer.

user@ubuntu:~/Desktop/dmrconfig-test$ dmrconfig -r
Serial port: /dev/ttyACM0
/dev/ttyACM0: Permission denied
No radio detected.
Check your USB cable!

I compared line 8 in 99-dmr.rules to lines 2 and 5 - it looked like there was a comma missing between ATTRS{idVendor}=="28e9" and ATTRS{idProduct}=="018a" so I tried adding a comma. I also tried adding SUBSYSTEM=="usb", before ATTRS{idVendor}=="28e9".

Neither of those modifications helped.

The following work as expected:

sudo dmrconfig -r
sudo dmrconfig -r -t

It looks like the idVendor and idProduct values for the 878 are identical to the 868.

I ran dmesg and see the following when I connect my 878:

[ 883.017593] usb 3-2: USB disconnect, device number 6
[ 889.614753] usb 3-2: new full-speed USB device number 7 using xhci_hcd
[ 890.017197] usb 3-2: New USB device found, idVendor=28e9, idProduct=018a, bcdDevice= 1.00
[ 890.017199] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 890.017201] usb 3-2: Product: GD32 Virtual ComPort in FS Mode
[ 890.017202] usb 3-2: Manufacturer: GD32Microelectronics
[ 890.017203] usb 3-2: SerialNumber: 000000010000
[ 890.020957] cdc_acm 3-2:1.0: ttyACM0: USB ACM device

Any thoughts as to why I am still running into permissions issues?

Thanks!

-JeffH

Jeff Hochberg
W4JEW
Atlanta, GA

@neotericpiguy
Copy link

I don't know if you've solved this or found a work around, but I have a BTECH DMR 6x2.
What is the output of your lsusb

vizio> lsusb
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 13d3:5178 IMC Networks
Bus 001 Device 005: ID 04ca:3006 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 1532:0109 Razer USA, Ltd Lycosa Keyboard
Bus 002 Device 004: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 024: ID 28e9:018a GD32Microelectronics GD32 Virtual ComPort in FS Mode
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The GD32Microelectronics GD32 Virtual ComPort in FS Mode line with the 28e9:018a is how you know what values to set in the 99-dmr.rules so I use the line

SUBSYSTEM=="usb", ATTRS{idVendor}=="28e9", ATTRS{idProduct}=="018a", MODE="666"

To set my rules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants