-
Notifications
You must be signed in to change notification settings - Fork 6
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
Won't connect to device on Fedora #158
Comments
That's very odd... I have a bug on NixOS where I have to wait ~30s or so before I can connect my device, but this sounds like something different. await navigator.serial.requestPort({ filters: [{ usbProductId: 0x8253, usbVendorId: 0x303a }]}); This (you forgot the array) pops up my CC2 as expected. Have you gone through the permission steps that are required on Linux? I really need to add these back, I forgot about those during a recent redesign |
Agreed, @Craig-StJean have you checked out and made sure to follow https://docs.charachorder.com/Device%20Manager.html#linux-serial-port-access ? |
Whoops, yes, I made it an array when I was testing it, just missed that typing it out here.
Yes, I found that before and went through it. My device is ttyACM0 and the group is dialout and everything seems to be in order with permissions. I have an old laptop running Mint I'll take out of storage later today and try it with. Maybe it'll work better on that... |
1 similar comment
Whoops, yes, I made it an array when I was testing it, just missed that typing it out here.
Yes, I found that before and went through it. My device is ttyACM0 and the group is dialout and everything seems to be in order with permissions. I have an old laptop running Mint I'll take out of storage later today and try it with. Maybe it'll work better on that... |
I don't know why, but it seems to be connecting now 😅 |
I assume the issue is that I'm on Fedora as I've tried different browsers but I can't connect to my cc2.
This won't give me a device:
If I call it without a filter and select my device manually then call
.getInfo()
on the SerialPort object it just gives me an empty object.In my terminal when I use
lsusb
I get the following as one of the entries, so it is connected to my device correctly:The text was updated successfully, but these errors were encountered: