Linuxmint USB - insufficient permissions No available USB device found with matching PID/VID

jimmy 2016-12-09 17:20:17 UTC #1

Axoloti core just arrived. Already have patcher installed, set up USB but am having trouble getting the patcher to recognize. Not sure if the cable I'm using is data enabled, but when I plug it in the green light illuminates on the core and the patcher seems to recognize the core. At start up Patcher console reads:

Axoloti version : 1.0.11-0-gc534986 build time : 28/08/2016 23:02:12 UTC
Link to firmware CRC 50A29AA2
Status: factory (1.0.11,anon) : OK ( 1.0.11,clean )
Status : home : OK
Status: community (1.0.11,anon) : OK ( 1.0.11,clean )
USB device found
insufficient permissions
USB device found
insufficient permissions
No available USB device found with matching PID/VID
search path : /home/linuxmint18xfce/axoloti/axoloti-factory/objects
search path : /home/linuxmint18xfce/axoloti/objects
search path : /home/linuxmint18xfce/axoloti/axoloti-contrib/objects
finished loading objects

Thanks in advance for any help on this!

johannes 2016-12-09 17:35:34 UTC #2

You should see events in dmesg when plugging in/out Axoloti Core, that would comfirm your cable has data wires.
To fix access permissions, please execute add_udev_rules.sh in axoloti/platform_linux

jimmy 2016-12-09 17:46:22 UTC #3

Thanks for quick response.

Ran add_udev_rules.sh /// patcher still not recognizing core.
Here's terminal read out:
set -e

cd $(dirname $0)

install udev rules

if [ ! -f /etc/udev/rules.d/49-axoloti.rules ];
then
echo "##### copying 49-axoloti.rules rules to /etc/udev/rules.d/ #####"
sudo cp 49-axoloti.rules /etc/udev/rules.d/

reload udev rules

echo "##### reloading udev rules #####"
sudo udevadm control --reload-rules
else
echo "##### udev rules already present, skipping #####"
fi

echo "DONE"

johannes 2016-12-09 18:06:54 UTC #4

Perhaps you need to unplug/replug Axoloti Core to activate that rule?
Or maybe Linuxmint does not use "udev" or uses a different location for the rules?

jimmy 2016-12-09 18:13:26 UTC #5

Unplugging/replugging doesn't seem to have any effect. New to linux in general, so really not sure about where rules are located.

thetechnobear 2016-12-09 18:14:56 UTC #6

check the rules is in /etc/udev/rules.d

run sudo udevadm control --reload-rules, and see if any error message is displayed.

then monitor console logs with dmesg whilst you plug the axo board in.
you can check it matches the rules file.

also you can try to give the user permission temporarily using chmod +w on the usb file... at least to check the udev rule is the issue.

why do we think its the udev rules? if you run axoloti from the command line, does it say you dont have permission to access device?

jimmy 2016-12-09 18:18:03 UTC #7

I don't know why udev rules would be an issue. Just following the suggestion of @johannes

Patcher console gives me this message:
USB device found
insufficient permissions
USB device found
insufficient permissions
No available USB device found with matching PID/VID

johannes 2016-12-09 18:19:49 UTC #8

Perhaps try a reboot to activate the udev permission rule? A reboot should be avoidable, but will certainly reload the udev rules.

jimmy 2016-12-09 18:30:08 UTC #9

reboot has no effect on issue

jimmy 2016-12-09 18:55:16 UTC #10

Forgive my struggling to keep up. Not understanding the sudo udevadm control.

When i run that line. there's no error - but theres really no output at all:
linuxmint18xfce@linuxmint18xfce-Presario-C700-Notebook-PC ~ $ sudo udevadm control --reload-rules
[sudo] password for linuxmint18xfce:
linuxmint18xfce@linuxmint18xfce-Presario-C700-Notebook-PC ~ $

running dmesg gives an output, but not a live one that reacts to plugging in/unplugging the board. it does however give these lines referring to the core:

[ 69.884071] usb 2-2: new full-speed USB device number 3 using uhci_hcd
[ 70.071316] usb 2-2: New USB device found, idVendor=16c0, idProduct=0442
[ 70.071324] usb 2-2: New USB device strings: Mfr=1, Product=5, SerialNumber=3
[ 70.071329] usb 2-2: Product: Axoloti Core
[ 70.071332] usb 2-2: Manufacturer: Axoloti
[ 70.071336] usb 2-2: SerialNumber: 002300243435511733353932
[ 70.268239] usbcore: registered new interface driver snd-usb-audio
[ 279.075552] perf interrupt took too long (2538 > 2500), lowering kernel.perf_event_max_sample_rate to 50000

thetechnobear 2016-12-09 23:44:16 UTC #11

ok, so device is recognised...

i dont know for linuxmint, but usually you can find the usb device in /proc/bus/usb...
you can then check the permissions, that udev rules are giving it. (also do chmod +w to test it)

iirc , lsusb will help you track down which device it is.

Minus2 2018-06-19 17:08:41 UTC #12

What was the fix to this I’m having same issue and am noob to Linux but have followed every step including those of other threads.

thetechnobear 2018-06-21 08:34:15 UTC #13

on Linux permissions to access devices (usb) are handled by udev, so you need to create a udev rule to allow this.

we do this in the deb package, but I assume you cannot use due to linux mint, but you can look at the scripts/rules we use here

github.com

axoloti/axoloti/blob/master/platform_linux/add_udev_rules.sh

#!/bin/sh

set -e

cd $(dirname $0)

# install udev rules

if [ ! -f /etc/udev/rules.d/49-axoloti.rules ]; 
then
   echo "##### copying 49-axoloti.rules rules to /etc/udev/rules.d/ #####"
   sudo cp 49-axoloti.rules /etc/udev/rules.d/
# reload udev rules
   echo "##### reloading udev rules #####"
   sudo udevadm control --reload-rules
else
   echo "##### udev rules already present, skipping #####"
fi

echo "DONE"

This file has been truncated. show original

github.com

axoloti/axoloti/blob/master/platform_linux/49-axoloti.rules

# 16C0:0442 - Axoloti Core
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0442", MODE:="0666"
# 0483:df11 - Axoloti Core (STM32 microcontroller) in DFU mode
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", MODE:="0666"

this will grant permission to all users to read/write to the usb axoloti device.

you can find more info about udev by a quick bit of googlefu
e.g.

edit: if your referring to the last issue jimmy had, ive no idea, since he didn't come back to me with any information … so I assume he repeated the steps and it worked

Minus2 2018-06-26 12:35:35 UTC #14

Awesome I will try this. I just reinstalled windows and got things going that route. It’s a slow machine now for sure but it got me patching. I’ll report results when I get home on other Linux machine. I also checked out a book on learning Linux ( teach a man to fish)