From 61d66ab233a636bdbb6de8c795902d4d24f9d80f Mon Sep 17 00:00:00 2001 From: Justin Widen Date: Wed, 5 Nov 2025 23:09:04 -0600 Subject: [PATCH] Add dialout fix instructions for WSL2 Added a small section with instructions for fixing USB device access in WSL2, due to the user not having access to dialout. Signed-off-by: Justin Widen --- .../Windows-WSL2-Installation-Instructions.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/doc/md/Installation_Instructions/Windows-WSL2-Installation-Instructions.md b/doc/md/Installation_Instructions/Windows-WSL2-Installation-Instructions.md index ab25bbcde..74cf54de8 100644 --- a/doc/md/Installation_Instructions/Windows-WSL2-Installation-Instructions.md +++ b/doc/md/Installation_Instructions/Windows-WSL2-Installation-Instructions.md @@ -393,6 +393,26 @@ sudo service udev restart sudo udevadm trigger --action=change ``` +#### USB device access in WSL2 (tty permissions) + +When you attach the Proxmark3 to WSL2 via `usbipd`, the Linux device node (for example `/dev/ttyACM0`) is created inside the WSL distro. That device is usually owned by `root:dialout` and is only readable/writable by `root` and members of the `dialout` group. + +If you are seeing `Could not find Proxmark3 on /dev/ttyACM0`, it usually means your user doesn't have permission to open the serial device. + +Fix: +```bash +# add your user to the dialout group (this is persistent) +sudo usermod -aG dialout $USER + +# apply the new group membership in the current shell (no restart) +newgrp dialout + +# verify the changes: +id # should show 'dialout' in the groups list +ls -l /dev/ttyACM* # device should be group 'dialout' and group-writable +``` + + ## Verify Device Exists ^[Top](#top)