LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 10-28-2005, 03:23 PM   #1
loninappleton
Member
 
Registered: Oct 2004
Distribution: red hat fedora core 2
Posts: 61

Rep: Reputation: 15
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
 
Old 10-28-2005, 09:49 PM   #2
Sargek
Member
 
Registered: Jan 2003
Location: San Antonio, Texas
Distribution: Debian testing
Posts: 416

Rep: Reputation: 32
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...
 
Old 10-28-2005, 11:28 PM   #3
loninappleton
Member
 
Registered: Oct 2004
Distribution: red hat fedora core 2
Posts: 61

Original Poster
Rep: Reputation: 15
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.
 
Old 10-28-2005, 11:44 PM   #4
Sargek
Member
 
Registered: Jan 2003
Location: San Antonio, Texas
Distribution: Debian testing
Posts: 416

Rep: Reputation: 32
Driver

Quote:
Originally posted by loninappleton
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.
You are still going to need a driver - hardware cannot be communicated with without a driver. Your only hope may be to run the winblows driver with some type of wrapper, but I am not sure if these exist but for a few types of devices.

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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
USB drive not working properly, read only device? (USB key storage device) Arodef Linux - Hardware 14 01-01-2010 07:32 AM
I would like to test an unknown midi device dunbar Linux - Hardware 20 10-03-2006 07:51 PM
USB Device Representation in Linux BobCap Programming 1 10-12-2005 08:51 PM
Installing Linux on an USB Device LkNsngth Linux - Hardware 3 02-12-2005 11:56 PM
Linux does not detect usb device. josedsilva Linux - Hardware 3 07-21-2004 08:29 PM


All times are GMT -5. The time now is 01:50 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration