Usb Vid-0fe6 Amp-pid-9900 ((full)) -
USB device: VID 0FE6 / PID 9900 — descriptive overview and actionable guidance
Summary
- VID 0FE6 (hex) identifies the vendor; PID 9900 (hex) identifies the product. Together they uniquely identify a USB device type to the host OS.
- Devices with this VID/PID are typically small USB peripherals (common examples: USB-to-serial adapters, microcontroller-based dev boards, or vendor-specific accessories). Exact function depends on device firmware; VID alone doesn’t guarantee a single product.
How to identify the device on your system
- Windows:
- Open Device Manager (Win+X → Device Manager).
- Find the unknown device or the relevant category (Ports, Universal Serial Bus controllers, etc.).
- Right-click → Properties → Details → Property: “Hardware Ids” to confirm “VID_0FE6&PID_9900”.
- macOS:
- Apple menu → About This Mac → System Report → USB.
- Look for an entry listing Vendor ID: 0x0FE6 and Product ID: 0x9900.
- Linux:
- Plug device in and run: lsusb
- Look for a line like: Bus 001 Device 004: ID 0fe6:9900
- For more detail: sudo dmesg | tail or journalctl -k --since "1 min ago" after plugging in.
Common actionable tasks
- Find a driver:
- If OS installs it automatically, check Device Manager/System Report to confirm the driver name.
- If not, search for drivers using the exact VID/PID string (e.g., “VID_0FE6 PID_9900 driver”) or visit the device vendor’s site if known.
- On Windows, you can update the driver via Device Manager → Update driver → Browse my computer or Search automatically.
- On Linux, many devices use built-in kernel drivers (usbserial, cdc-acm, ftdi_sio, cp210x). Check dmesg for which driver attached; if none, try binding to an appropriate driver or load a kernel module: sudo modprobe usbserial vendor=0x0fe6 product=0x9900 (only for compatible generic usbserial).
- Identify device class (what it does):
- Check lsusb -v (Linux) or the USB Details in macOS/System Report to view bDeviceClass, bDeviceSubClass, and interface descriptors. These fields indicate whether the device is a CDC (serial), HID (input), Mass Storage, Audio, etc.
- Serial/Console access:
- If the device enumerates as a serial/CDC device, note the assigned port:
- Windows: check Ports (COMx) in Device Manager.
- macOS: /dev/tty.usbmodem* or /dev/tty.usbserial*.
- Linux: /dev/ttyUSB* or /dev/ttyACM*.
- Use a terminal program (PuTTY, screen, minicom) with appropriate baud settings (common defaults: 115200 8N1) to communicate.
- If the device enumerates as a serial/CDC device, note the assigned port:
- Firmware updates:
- Only use official firmware or vendor-provided tools. Search for firmware utilities tied to the VID/PID or the product name.
- On microcontroller devices, DFU or vendor-specific bootloader modes may be used—check device descriptors or vendor docs.
- Reverse lookup / vendor info:
- Use the VID to infer vendor: lookup tables (online) map 0x0FE6 to a vendor name. If vendor is unknown or multiple vendors use custom VIDs for developer boards, infer from packaging, markings on PCB, or documentation.
- Security and safety:
- Don’t install unsigned drivers from untrusted sources.
- If the device behavior is unexpected (enumerates as multiple interfaces, creates network adapters, or requests firmware), unplug and investigate vendor documentation.
- Creating udev rule (Linux) to set permissions or create symlink:
- Create file /etc/udev/rules.d/99-mydevice.rules with a line like: SUBSYSTEM=="usb", ATTRidVendor=="0fe6", ATTRidProduct=="9900", MODE="0666", SYMLINK+="my_usb_device"
- Then reload rules: sudo udevadm control --reload && sudo udevadm trigger
Troubleshooting checklist
- Confirm VID/PID with lsusb / Device Manager / System Report.
- Check kernel logs (dmesg/journalctl) for driver messages or errors.
- Try different USB cable/port (power-only cables won’t pass data).
- Test on another OS or machine to see if behavior is platform-specific.
- Search for firmware or vendor name using the VID (0x0FE6) and PID (0x9900).
- If device is unsupported, consider community drivers (GitHub) but vet code carefully.
If you want
- I can look up the vendor name and known product matches for VID 0FE6 PID 9900 (I will search the web for current matches).
The hardware identifier USB VID-0FE6 & PID-9900 refers to the Corechip SR9900 USB 2.0 to Fast Ethernet Adapter. This specialized chip is commonly found in budget-friendly USB-to-Ethernet dongles used to add wired network connectivity to laptops, tablets, and desktop computers that lack a built-in RJ45 port. Technical Overview
The Corechip SR9900 is an ultra-low power, single-chip solution that integrates a USB 2.0 bus controller, a 10/100M Fast Ethernet MAC, and physical layer (PHY). Interface: USB 2.0 (High-Speed), compatible with USB 1.1. Speed: Supports 10/100 Mbps Fast Ethernet.
Power Management: Includes an embedded linear regulator (LDO) to reduce build costs and supports advanced power-saving states like ACPI and APM.
Features: Supports "Wake-on-LAN" (Microsoft Wake-Up Frame) and IPv6 protocols while in low-power states. Common Use Cases
You will typically encounter this device ID when using a "Plug and Play" Ethernet adapter on devices like the ASUSTeK VivoBook S15 or Lenovo IdeaPad Flex 5. It is a popular choice for manufacturers because it provides a reliable, cost-effective way to offer stable wired internet for video conferencing, gaming, or large file transfers where Wi-Fi might be unstable. Driver Installation & Troubleshooting
Most modern operating systems, including Windows 10/11, often include generic drivers that allow this device to work immediately upon plugging it in. However, if the device appears as "Unknown Device" in your Device Manager, you may need to install specific drivers.
Automatic Update: Right-click the device in Device Manager and select "Update Driver". usb vid-0fe6 amp-pid-9900
Manual Download: Official drivers are available from various hardware databases such as DriverIdentifier or DriverMax .
Cross-Platform Support: While primarily used on Windows (XP through 11), the SR9900 chip is also compatible with Linux and Mac OS systems, though manual configuration like usb_modeswitch may be required on some Linux distributions.
If you are experiencing slow speeds, ensure the adapter is connected directly to a high-speed USB port rather than an unpowered hub, as this chip relies on the 480 Mbps bandwidth of the USB 2.0 standard.
The USB Hardware ID VID 0FE6 & PID 9900 identifies a Corechip SR9900 USB 2.0 to Fast Ethernet Adapter
. This device is a low-cost network adapter typically used to add a 10/100M LAN port to laptops or embedded systems. Arch Linux Forums Device Specifications Vendor (VID): 0FE6 (Commonly associated with ICS Advent Product (PID): 9900 (Specific to the Device Type: USB 2.0 Fast Ethernet Adapter (10/100 Mbps). Corechip SR9900. Arch Linux Forums Driver Information
For the device to function correctly on Windows, you typically need the sr9900.inf driver file.
USB VID 0FE6 PID 9900 refers to a generic 10/100M Ethernet Adapter often manufactured by or associated with ICS Advent
. These devices are commonly found in budget-tier USB-to-Ethernet dongles or multi-port hubs. Raspberry Pi Forums 1. Hardware Identification Vendor ID (VID): (Commonly assigned to ICS Advent or CoreChips). Product ID (PID): (Identifies the specific Ethernet controller). Manufacturer String: Often appears as "CoreChips" "ICS Advent" in system logs like Device Class: Typically identifies as a Vendor Specific Class
(255) rather than a standard Communications Device Class (CDC), which often causes compatibility issues on non-Windows systems. Arch Linux Forums 2. Technical Specifications
Detailed descriptors for this device usually reveal the following configuration: USB Version: 2.10 (High-Speed). Maximum Power: 100mA (Bus Powered). Network Speed: 10/100 Mbps (Fast Ethernet). Endpoints: Bulk transfer for receiving data. Bulk transfer for sending data. Interrupt transfer for status/control. Arch Linux Forums 3. Driver & Compatibility Issues
This specific hardware is known for "mode-switching" behavior or requiring specific proprietary drivers to function correctly. Manjaro Linux Forum Linux Support: USB device: VID 0FE6 / PID 9900 —
The device often fails to initialize "out of the box" because the kernel may expect a different PID (like ) for the standard drivers. Users often have to use tools like USB_ModeSwitch to force the device into the correct state. Performance:
Some users report stability issues, such as the adapter disconnecting during high-bandwidth downloads (>1 MB) or failing to be recognized entirely on low-power devices like the Raspberry Pi Windows Drivers: Drivers are typically provided by the manufacturer (e.g., Driverscape ) under the name RD9700 USB2.0 To Fast Ethernet Adapter Raspberry Pi Forums 4. Usage Considerations
Due to the prevalence of "shonky" or low-quality implementations of this chipset, it is frequently criticized in technical communities for poor throughput and unreliable driver support compared to more standard based adapters. Raspberry Pi Forums specific commands
needed to manually bind this device to a Linux kernel driver?
USB to Internet Adapter not recognized - Raspberry Pi Forums
3. Downloading the correct driver
Do not use random "driver updater" websites. Get drivers from trusted sources:
| OS | Driver source | Notes |
|----|--------------|-------|
| Windows | DriverGuide (direct DM9601) or OEM driver | Also works: Plugable’s DM9601 driver archive |
| Linux | Built-in | Load module: sudo modprobe dm9601 |
| macOS | HoRNDIS (old) or generic USB Ethernet kext | Not recommended for macOS 10.15+ |
✅ Safest Windows driver source:
Search for "DM9601 Windows 10 driver" and use files from Plugable or StarTech support pages — they provide signed drivers for this chipset.
Linux (Ubuntu, Debian, Fedora, Arch)
Good news: Linux often has native support for VID_0FE6&PID_9900 via the dm9601 or rdm kernel module.
- Check if detected: Run
lsusb. Look for a line containing0fe6:9900. - Load the module:
sudo modprobe dm9601(orsudo modprobe rdm). - Persist across reboots: Add
dm9601to/etc/modules. - Troubleshooting: If the adapter is detected but not working, check
dmesg | grep dm9601for errors. You may need to blacklist conflicting modules likecdc_ether.
Symptom C: Blue Screen of Death (BSOD) on Plug-In
In rare cases on older Windows versions (7/8), plugging in the device triggers a DRIVER_IRQL_NOT_LESS_OR_EQUAL or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED crash.
Cause: A corrupted or incorrect driver is attempting to interface with the hardware. VID 0FE6 (hex) identifies the vendor; PID 9900
Replace it if:
- You are using Windows 10/11 and want "plug and play."
- You need Gigabit speed (look for VID 0BDA (Realtek) or VID 10EC).
- You want to use this on a modern Mac.
Decoding the USB Identifier: A Complete Guide to USB VID-0FE6 & PID-9900
In the vast ecosystem of Universal Serial Bus (USB) devices, every piece of hardware—from your mouse to your external hard drive—possesses a unique fingerprint. These fingerprints are known as the Vendor ID (VID) and Product ID (PID). For the average user, these alphanumeric codes remain invisible background noise. However, when a device malfunctions, a driver fails to install, or a mysterious entry appears in Device Manager, strings like USB\VID-0FE6&PID-9900 suddenly become critical.
If you have landed on this article, you are likely staring at this exact code in your system logs or error reports. You may be asking: What device is this? Why is it not working? How do I fix it?
This article provides a deep dive into USB VID-0FE6 and PID-9900. We will cover what this specific identifier represents, the common hardware associated with it, step-by-step driver solutions, and advanced troubleshooting for Windows, Linux, and macOS.
2. Device Description
This USB device is typically a low-cost USB 1.1 to Ethernet adapter based on the DM9601 chipset from Davicom Semiconductor, but branded under ICS Advent’s VID. The chipset is widely used in legacy or budget-friendly USB-to-RJ45 dongles for adding network connectivity to systems without an Ethernet port.
While the DM9601 is the original reference design, some generic adapters reuse this VID/PID without proper licensing, making it a common identifier for generic or clone adapters.
Part 4: How to Fix Driver Issues for VID_0FE6&PID_9900
Here is the definitive, step-by-step guide to getting your device working. Follow these in order.
3. Software to Use
Once the driver is installed, the device usually appears as a webcam source named "AV TO USB" or "SMI Grabber."
Recommended Software:
-
OBS Studio (Free & Powerful):
- This is the best option for recording and streaming.
- Under "Sources," click the + icon.
- Select Video Capture Device.
- Select your USB device from the dropdown menu.
- Set the Resolution/FPS Type to "Custom" and set Resolution to
640x480or720x480(these devices are standard definition).
-
VLC Media Player (For Testing):
- Open VLC.
- Media -> Open Capture Device.
- Video device name: Select the USB grabber.
- Click Play.
-
VirtualDub (Legacy Windows):
- If you are on Windows 7 or XP, VirtualDub is the classic tool for capturing from these devices.