boot for security key [SoloKey]
USB ID 1209:50b0 · Generic
| Vendor | Generic |
|---|---|
| Vendor ID | 1209 |
| Device ID | 50b0 |
| Windows hardware ID | USB\VID_1209&PID_50B0 |
| Linux modalias | usb:v1209p50B0 |
| Linux driver | no driver with exact ID |
Frequently asked questions
Which device has USB ID 1209:50b0?
USB ID 1209:50b0 is “boot for security key [SoloKey]” made by Generic (vendor ID 1209, device ID 50b0).
Which Linux driver supports boot for security key [SoloKey]?
Linux kernel 6.12 lists no driver for this exact ID. Most USB devices (keyboards, mice, storage, webcams, audio) still work through generic class drivers such as usbhid, usb-storage, uvcvideo or snd-usb-audio. Overview of device classes and their drivers
How do I check whether boot for security key [SoloKey] is in my computer?
On Linux, lsusb -d 1209:50b0 shows the device if it is present. On Windows, open Device Manager, then Properties → Details → Hardware Ids; it appears as USB\VID_1209&PID_50B0.
How do I see which driver is currently in use?
lsusb -t prints the device tree with the bound driver (Driver=…) for each interface.
Nearby entries
- 4c61 – MightyPork GEX wireless dongle
- 4d53 – mindsensors.com NXTCam5
- 5038 – frotz.net mdebug rswd protocol
- 5039 – frotz.net lpcboot protocol
- 5050 – trebb ISO50
- 5070 – SoloHacker security key [SoloKey]
- 5222 – telavivmakers attami
- 53c0 – SatoshiLabs TREZOR Bootloader
- 53c1 – SatoshiLabs TREZOR
- 5432 – Open Programmer
- 5457 – Openlab.Taipei Taiwanduino
- 571c – StreetoArcade PancadariaStick