Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
I’d be glad to help you troubleshoot your udev rule! To provide the most accurate guidance, could you let me know which OS and version you are using? You can use the tdx-info command to get this information - more details are available at https://developer.toradex.com/software/development-resources/tdx-info/.
Common Troubleshooting Steps
While waiting for your platform details, here are some general troubleshooting approaches based on the available documentation:
1. Verify Device Detection
First, confirm your USB HID device is being detected. Use these commands to check:
udevadm info -a -p $(udevadm info -q path -n /dev/input/eventX)
Replace eventX with your actual device node.
2. Test Rule Syntax
Your current rule looks correct for basic USB device matching. However, you might want to try different matching approaches:
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{name}=="Your_Device_Name", ATTRS{idVendor}=="2934", ATTRS{idProduct}=="4142", TAG+="uaccess"
3. Reload and Test Rules
After creating or modifying your rule, reload the udev rules:
udevadm control --reload-rules
udevadm trigger
4. Check Rule Priority
Since you mentioned the rule must have priority before 73-seat-late.rules, ensure your filename 70-ceta-hid.rules has the correct numeric prefix. Rules are processed in alphanumeric order, so 70 should indeed run before 73.
5. Alternative Approaches
If the TAG+=“uaccess” approach isn’t working, you could try setting specific permissions:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2934", ATTRS{idProduct}=="4142", MODE="0666"
Once you provide your OS and version information, I can give you more specific guidance tailored to your platform.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.