Please add udevadm control --reload to the install_driver.sh

After installing the udev rule the

sudo udevadm control --reload

command needs to be executed to parse the installed udev rule properly. This would spare a reboot cycle for the users, and it might spare some investigation time. Simply append it to the install_driver.sh file and

  • Guest
  • Jul 11 2018
  • Guest commented
    July 11, 2018 20:25

    Hi Mark,

    I have tried it on KUbuntu 16.04 64 bit.

    I have tried to unplug-replug the device, but it did not helped. I did not wanted to reboot my machine so I have issued this command, and then it worked without reboot. I cannot remember if I did a replug cycle after the rules reload, but I can check it out tomorrow.

  • Mark Garrison commented
    July 11, 2018 20:25

    One quick follow up - the device needs to be removed and reconnected - if the device is left connected after installing the rules file, it won't be applied to them - is that the issue you're seeing here?

  • Mark Garrison commented
    July 11, 2018 20:25

    Thanks for the feedback! However we haven't noticed this before, usually right after installing the rules file and re-launching the Logic software, the devices connect normally. I've mostly tested this on Ubuntu 12, 13, and 14, and I've tested it a handful of times on a few other distros.
    The last problem we saw with the udev rules file was a few years ago, when SYSFS was depreciated, and replaced with ATTRS. after finally making that change, we had a trickling of users on systems that didn't support ATTRS, but I haven't seen any mention of that in years.
    We also saw a few reports on Arch where ENV{DEVTYPE}=="usb_device" needed to be removed to get the rules file to work. However I haven't heard about that in a few years, and we don't test on Arch (I gave up in shame after the installation failed, and there is no official Live disk to test with)
    However this is the first report we've heard where a reboot was required. Could you let me know what distro, distro version, and kernel version you are using? Also feel free to write in to support about this so we can track it on a ticket.