Quote:
Originally Posted by NeilW
Hmm....as per my comments in the "Linuxization" thread under this topic, I've spent several fruitless hours trying to get my HEQ5 to talk to Indi via just such an adapter
|
Hi Neil,
You might want to have a look at this additional follow-up post I made
the other day -
http://www.iceinspace.com.au/forum/s...9&postcount=30
Your first step should be to identify exactly what type of USB Serial
Adapter you have. Different makes and models use different chipsets
and each class of chipset requires a specific driver that may not be included
in your kernel by default.
If you have a no-name generic adapter, its identity will be betrayed
when the system first boots or you plug it in.
For example, if you plug it in and type -
# dmesg | grep usb
at the bottom of the transcript you should see some message lines,
the first of which starts with "New USB device found".
Within that transcript you will find information about the device,
including its "idVendor" and "idProduct" numbers. Every make/model of
USB device in the world that has been registered with the USB-IF
consortium is assigned these identifiers.
Within the transcript you may also see a line to the effect -
device v1234 p5678 is not supported.
The kernel being able to operate with a particular USB Adapter is
a two step process.
Firstly, when the device is initially detected on the USB bus, for example
when it is inserted, the device is probed by the USB subsystem software.
The primary task of the probing step is to ascertain the vendor ID
and the product ID of the USB peripheral just inserted.
In the second phase, if the device is recognized, the USB subsystem
passes off handling of it to a specific kernel device driver that knows
how to handle that specific device. In the case of a USB Serial Adapter
that driver, once it loads, will also automagically instantiate the
/dev/ttyUSB0 device.
So just because a device is initially successfully probed by the USB
subsystem does not necessarily mean that the device driver
for that peripheral will be loaded if the kernel does not know about
it.
If the driver is not compiled into the kernel or has not been included
as a kernel module, then it will need to be compiled.
Best regards
Gary