Usb Device Id Vid 058f Pid 1234 Full [CERTIFIED | 2025]

If your operating system fails to recognize the device despite seeing the VID/PID, one or more of these issues is present:

If you have a device with VID 058F PID 1234, here are its typical hardware parameters:

| Parameter | Value | |-----------|-------| | Vendor | Alcor Micro Corp. | | Product | USB 2.0 Hub (or Multi-Card Reader) | | USB Version | 2.0 (480 Mbps max) | | Power Draw | 100 mA (Bus-powered) | | Supported Protocols | Mass Storage Class (if reader), Hub Class | | Typical Ports (if hub) | 4 downstream ports | | Card Support (if reader) | SD, SDHC, MMC, MS, xD (varies) | usb device id vid 058f pid 1234 full

On Linux, running lsusb -v -d 058f:1234 will show something like:

Bus 001 Device 003: ID 058f:1234 Alcor Micro Corp. USB 2.0 Hub
Device Descriptor:
  bLength            18
  bDescriptorType     1
  bcdUSB            2.00
  bDeviceClass        9 (Hub)
  bDeviceSubClass     0
  bDeviceProtocol     1 (Single TT)
  bMaxPacketSize0    64
  idVendor           0x058f Alcor Micro Corp.
  idProduct          0x1234 USB 2.0 Hub
  bcdDevice            1.00

Apple’s macOS includes native support for USB hubs and mass storage devices bearing 058F:1234. If your operating system fails to recognize the

Linux handles this device very well. The kernel module hub or usb_storage usually claims it automatically.

If after all driver reinstalls, OS switches, and configuration tweaks the device still shows errors with 058F:1234, consider hardware failure: Apple’s macOS includes native support for USB hubs

| Field | Value | |-------|-------| | Vendor ID (VID) | 0x058F | | Product ID (PID) | 0x1234 | | Vendor Name | Alcor Micro Corp. | | Device Type | Mass Storage Controller (USB Flash Drive) | | Typical Chip Model | Alcor Micro AU698X / AU699X series (or similar older generation) |

No proprietary driver is required.

This specific combination most commonly appears in the following hardware scenarios: