Test a usb device in linux
I have asked this question various ways in various forums but
no good answers yet. So here goes. I have a device attached to the computer running Mepis 3.3.2test03. The device is recognized at bootup as being from Yamaha but only certain things about the device are recognized. I just checked with a linux usb forum which showed a program called comtest. I was not proficient at getting that going. So the question remains: How to send a signal from Linux OS to a USB device? At the bottom (and though it wastes bandwidth) I'll give my kudzu -p. The goal is to find a tool that can turn the device on in software. Software has been built by yamaha for the Windows 98 OS. The device is a Yamaha RP U100 receiver. The receiver plays streams, cds and system notifications issued from the my soundcard which is a Turtle Beach Santa Cruz. The device connects via USB cable to the receiver and accepts commands to turn the device on and off in Windows plus many other functions. The device is discontinued and nothing new coming from yamaha on it. Assuming that USB modules for doing these activities are standard, how can I test and operate the device with Linux? FYI: Demudi, Linux USB listserv and ALSA listserv have not responded to this. At Linux USB, I got lost in the jargon. What generic Linux USB module can turn a device off and on? The USB specification for the device is USB 1.1 from kudzu -p class: OTHER bus: PCI detached: 0 driver: i2c-viapro desc: "Unknown vendor|Generic i2c-viapro device" vendorId: 1106 deviceId: 3050 subVendorId: 0000 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 7 pcifn: 3 - class: OTHER bus: PCI detached: 0 driver: unknown desc: "Unknown vendor|unknown device 1106:0596" vendorId: 1106 deviceId: 0596 subVendorId: 1106 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 7 pcifn: 0 - class: OTHER bus: PCI detached: 0 driver: unknown desc: "Unknown vendor|unknown device 1106:8598" vendorId: 1106 deviceId: 8598 subVendorId: 0000 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 1 pcifn: 0 - class: OTHER bus: USB detached: 0 driver: unknown desc: "Linux 2.6.12 uhci_hcd UHCI Host Controller" usbclass: 9 usbsubclass: 0 usbprotocol: 0 usbbus: 1 usblevel: 0 usbport: 0 usbdev: 1 vendorId: 0000 deviceId: 0000 usbmfr: Linux 2.6.12 uhci_hcd usbprod: UHCI Host Controller - class: OTHER bus: PCI detached: 0 driver: via-agp desc: "Unknown vendor|Generic via-agp device" vendorId: 1106 deviceId: 0691 subVendorId: 0000 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 0 pcifn: 0 - class: OTHER bus: USB detached: 0 driver: audio desc: "YAMAHA Corporation YAMAHA RP-U100 USB Audio" usbclass: 3 usbsubclass: 0 usbprotocol: 0 usbbus: 1 usblevel: 1 usbport: 0 usbdev: 2 vendorId: 0499 deviceId: 3101 usbmfr: YAMAHA Corporation usbprod: YAMAHA RP-U100 USB Audio - class: OTHER bus: USB detached: 0 driver: unknown desc: "YAMAHA Corporation YAMAHA RP-U100 USB Audio" usbclass: 1 usbsubclass: 1 usbprotocol: 0 usbbus: 1 usblevel: 1 usbport: 0 usbdev: 2 vendorId: 0499 deviceId: 3101 usbmfr: YAMAHA Corporation usbprod: YAMAHA RP-U100 USB Audio - class: NETWORK bus: PCI detached: 0 device: eth0 driver: tulip desc: "Unknown vendor|Generic tulip device" network.hwaddr: 00:12:17:52:76:07 vendorId: 1317 deviceId: 0985 subVendorId: 1317 subDeviceId: 0574 pciType: 1 pcidom: 0 pcibus: 0 pcidev: f pcifn: 0 - class: MOUSE bus: PSAUX detached: 0 device: input/mice driver: generic3ps/2 desc: "ImPS/2 Generic Wheel Mouse" - class: AUDIO bus: PCI detached: 0 driver: snd-cs46xx desc: "Unknown vendor|Generic snd-cs46xx device" vendorId: 1013 deviceId: 6003 subVendorId: 5053 subDeviceId: 3357 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 14 pcifn: 0 - class: AUDIO bus: USB detached: 0 driver: audio desc: "YAMAHA Corporation YAMAHA RP-U100 USB Audio" usbclass: 1 usbsubclass: 2 usbprotocol: 0 usbbus: 1 usblevel: 1 usbport: 0 usbdev: 2 vendorId: 0499 deviceId: 3101 usbmfr: YAMAHA Corporation usbprod: YAMAHA RP-U100 USB Audio - class: AUDIO bus: USB detached: 0 driver: audio desc: "YAMAHA Corporation YAMAHA RP-U100 USB Audio" usbclass: 1 usbsubclass: 2 usbprotocol: 0 usbbus: 1 usblevel: 1 usbport: 0 usbdev: 2 vendorId: 0499 deviceId: 3101 usbmfr: YAMAHA Corporation usbprod: YAMAHA RP-U100 USB Audio - class: AUDIO bus: USB detached: 0 driver: audio desc: "YAMAHA Corporation YAMAHA RP-U100 USB Audio" usbclass: 1 usbsubclass: 2 usbprotocol: 0 usbbus: 1 usblevel: 1 usbport: 0 usbdev: 2 vendorId: 0499 deviceId: 3101 usbmfr: YAMAHA Corporation usbprod: YAMAHA RP-U100 USB Audio - class: AUDIO bus: USB detached: 0 driver: audio desc: "YAMAHA Corporation YAMAHA RP-U100 USB Audio" usbclass: 1 usbsubclass: 2 usbprotocol: 0 usbbus: 1 usblevel: 1 usbport: 0 usbdev: 2 vendorId: 0499 deviceId: 3101 usbmfr: YAMAHA Corporation usbprod: YAMAHA RP-U100 USB Audio - class: VIDEO bus: PCI detached: 0 device: fb0 driver: unknown desc: "Unknown vendor|unknown device 102b:0519" vendorId: 102b deviceId: 0519 subVendorId: 0000 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 12 pcifn: 0 - class: FLOPPY bus: MISC detached: 0 device: fd0 driver: unknown desc: "3.5" 1.44MB floppy drive" - class: HD bus: IDE detached: 0 device: hdb driver: ignore desc: "Maxtor 2R015H1" physical: 16383/16/63 logical: 29065/16/63 - class: KEYBOARD bus: PSAUX detached: 0 driver: ignore desc: "AT Translated Set 2 keyboard" - class: USB bus: PCI detached: 0 driver: uhci-hcd desc: "Unknown vendor|unknown device 1106:3038" vendorId: 1106 deviceId: 3038 subVendorId: 0925 subDeviceId: 1234 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 7 pcifn: 2 - class: IDE bus: PCI detached: 0 driver: unknown desc: "Unknown vendor|unknown device 1106:0571" vendorId: 1106 deviceId: 0571 subVendorId: 0000 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 7 pcifn: 1 |
Correct me if I am wrong , anyone, but communicating with a specific hardware device requires a driver. If you have no driver, you might be able to reverse-engineer the winblows driver and write one. Another approach would be to find the specifications originally used to write the winblows driver for this device and write a driver from that. Good luck. Another option might be to use a wrapper that runs in Linux, but allows you to run winblows drivers. I know these exist, but can't think of the names at the moment...
|
The ways of inspecting the yamaha software are not obvious.
My question and assumption is that the hardware accepts input. it does not know where it is coming from and the Yamaha designers may or may not have made the hardware Windows-responsive only. Yamaha makes many digital devices. I cannot believe this reciever is unique. |
Driver
Quote:
The hardware is not winblows-responsive only, but the only way for a computer to communicate with hardware is through a driver, and apparently yamaha has written a winblows driver, which will not work in Linux. The hardware does not care where it gets input from, but it will only accept input in the way the designers made it to. The only way to know this is to have the design specs, or to reverse engineer the existing winblows driver, which might be difficult at best. Think of a driver as the "middle man" between an OS and hardware. |
All times are GMT -5. The time now is 02:24 AM. |