Skip to content
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

using usbipd with my own device BSOD #700

Closed
skunx99 opened this issue Sep 14, 2023 · 6 comments
Closed

using usbipd with my own device BSOD #700

skunx99 opened this issue Sep 14, 2023 · 6 comments

Comments

@skunx99
Copy link

skunx99 commented Sep 14, 2023

Hi all, never used usbipd before today, so sorry for anything newb like...

I make my own usb adapters and want to work with it over WSL, after getting everything installed and trying to attach, the system make a buzzing notice and I see something about "maybe incompatible" flash up then the computer BSOD's

This is a HID gamepad device, no drives but the defaults ones with windows and linux are used. It does work on linux and on windows on its own.

Guessing there are logs somewhere I can look at? Just not sure how to troubleshoot this one, the BSOD is a bit damaging at times. So it makes it hard to play with things.

Let me know what info I can get that would be of more help.

@dorssel
Copy link
Owner

dorssel commented Sep 14, 2023

What version of usbipd-win are you using?

What is the BSOD stop code, and which module/driver does it list as the source of the crash?

The warning is probably about USB filter drivers. You'll get the same for usbipd list, without the crash, so you can read it.

@skunx99
Copy link
Author

skunx99 commented Sep 14, 2023

yes the list does show it, the one it is complaining about is software not a driver. Is there a way to tell it to be blind to it permently?

"
usbipd: warning: Unknown USB filter 'USBlyzer' may be incompatible with this software; 'bind --force' may be required.
"

that device I wat to use is not being used by USBlyzer atm.

@dorssel
Copy link
Owner

dorssel commented Sep 14, 2023

Is there a way to tell it to be blind to it permently?

Well, yes, that is what it is telling you to do. Try usbipd bind --help for further help.

@skunx99
Copy link
Author

skunx99 commented Sep 14, 2023

ah, that explained it better, thx!
Maybe unrelated so let me know if I need to go elsewhere.

The Device shows up in lsusb, but not in /dev/input -- well, /dev/input does not exist?

Never saw that before so I guess the kernel can figure out what it is?

[ 14.812396] usb 1-1: New USB device found, idVendor=16d0, idProduct=0d04, bcdDevice= 2.00
[ 14.812400] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[ 14.812401] usb 1-1: Product: Gamer-Pro Advanced.2
[ 14.812403] usb 1-1: Manufacturer: Bliss-Box
[ 14.812404] usb 1-1: SerialNumber: 000+
[ 14.825714] input: Bliss-Box Gamer-Pro Advanced.2 as /devices/platform/vhci_hcd.0/usb1/1-1/1-1:1.0/0003:16D0:0D04.0001/input/input0
[ 14.825718] hid-generic 0003:16D0:0D04.0001: input: USB HID v1.11 Gamepad [Bliss-Box Gamer-Pro Advanced.2] on usb-vhci_hcd.0-1/input0

edit
think I found the talk on it
microsoft/WSL#7747

@dorssel
Copy link
Owner

dorssel commented Sep 14, 2023

Yes, you'll need to add the required drivers to the kernel. That's a WSL issue.
Is your problem resolved now?

@skunx99
Copy link
Author

skunx99 commented Sep 14, 2023

yes thx.

@dorssel dorssel closed this as completed Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants