-
Notifications
You must be signed in to change notification settings - Fork 22
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
"Unable to find device" on Linux, AMD #63
Comments
Update: works on a different machine, same OS, same cable, etc, only this time it's an 8th gen Intel i5. Connecting the Pinecil gives additional udev logs, notably:
My problem is now solved, however, happy to leave this open if the devs want to nail the root cause. |
Interesting! Thank you very much, this is very helpful. |
I also have this issue with a AMD Ryzen 7040 laptop, also using arch and tested with fedora and windows in a vm both not working. Also it flashed fine using my old intel based laptop. |
It could totally be coincidence but I'm definitely curious to learn if a USB device could end up handled differently depending on whether the CPU is AMD/Intel. When I have time I'll see if I can get a trace |
blisp throws a "device not found" error while trying to flash a Pinecil V2. On the Pinecil docs, it's stated that the device will appear as a
/dev/ttyACM*
device, but this does not occur on my machine (AMD Ryzen 3600X, Arch Linux with current kernel).The device is recognised, just not mapped to anything directly under
/dev/
. Here's part of the logs forudevadm monitor -p
Trying blisp with
-p /dev/bus/usb/003/046
gives"Couldn't open device, err: -1"
dmesg
log:Pinecil version output:
The text was updated successfully, but these errors were encountered: