keyspan USB serial not creating devices

keyspan USB serial not creating devices

[Yan Seiner]

I have a keyspan USB serial dongle that has quit working.  It used to work
on a machine with an older kernel (2.6.18???), properly creating the
/dev/ttyUSB device.  Unfortunately I no longer have that machine.  The
machine it's on now runs a 2.6.26 kernel, and the device is not being
created.  The dongle is recognized, but no ttyUSB? are created:

[139761.937391] usb 2-10.3: new full speed USB device using ehci_hcd and
address 50
[139762.046702] usb 2-10.3: configuration #1 chosen from 1 choice
[139762.047357] keyspan 2-10.3:1.0: Keyspan - (without firmware)
converter detected
[139762.047364] firmware: requesting keyspan/usa19qi.fw
[139762.089684] usb 2-10.3: New USB device found, idVendor\x06cd,
idProduct\x010b
[139762.089684] usb 2-10.3: New USB device strings: Mfr=0, Product=0,
SerialNumber=0

It used to work with no firmware, but I went ahead and installed the
firmware from the 2.6.27 kernel; no difference. Still no /dev/ttyUSB?
device.

Can anyone shed some light on this?

--Yan


-- 
  o__
  ,>/'_          o__
  (_)\(_)        ,>/'_        o__
Yan Seiner      (_)\(_)       ,>/'_     o__
       Personal Trainer      (_)\(_)    ,>/'_        o__
             Professional Engineer     (_)\(_)       ,>/'_
Who says engineers have to be pencil necked geeks?  (_)\(_)

You are an adult when you realize that everyone's an idiot sometimes. You
are wise when you include yourself.

Re: keyspan USB serial not creating devices

[Greg KH]

On Fri, Nov 07, 2008 at 09:02:43AM -0800, Yan Seiner wrote:
> I have a keyspan USB serial dongle that has quit working.  It used to work
> on a machine with an older kernel (2.6.18???), properly creating the
> /dev/ttyUSB device.  Unfortunately I no longer have that machine.  The
> machine it's on now runs a 2.6.26 kernel, and the device is not being
> created.  The dongle is recognized, but no ttyUSB? are created:
> 
> [139761.937391] usb 2-10.3: new full speed USB device using ehci_hcd and
> address 50
> [139762.046702] usb 2-10.3: configuration #1 chosen from 1 choice
> [139762.047357] keyspan 2-10.3:1.0: Keyspan - (without firmware)
> converter detected
> [139762.047364] firmware: requesting keyspan/usa19qi.fw
> [139762.089684] usb 2-10.3: New USB device found, idVendor\x06cd,
> idProduct\x010b
> [139762.089684] usb 2-10.3: New USB device strings: Mfr=0, Product=0,
> SerialNumber=0
> 
> It used to work with no firmware, but I went ahead and installed the
> firmware from the 2.6.27 kernel; no difference. Still no /dev/ttyUSB?
> device.

These devices never would work without firmware, the older kernel
versions had the firmware built into the drivers.  Are you sure you did
load the firmware for the device properly?  Can you just build the
firmware into the driver and see if that solves your issue?

thanks,

greg k-h

Re: keyspan USB serial not creating devices

[Yan Seiner]

Greg KH wrote:
> On Fri, Nov 07, 2008 at 09:02:43AM -0800, Yan Seiner wrote:
>   
>> I have a keyspan USB serial dongle that has quit working.  It used to work
>> on a machine with an older kernel (2.6.18???), properly creating the
>> /dev/ttyUSB device.  Unfortunately I no longer have that machine.  The
>> machine it's on now runs a 2.6.26 kernel, and the device is not being
>> created.  The dongle is recognized, but no ttyUSB? are created:
>>
>> [139761.937391] usb 2-10.3: new full speed USB device using ehci_hcd and
>> address 50
>> [139762.046702] usb 2-10.3: configuration #1 chosen from 1 choice
>> [139762.047357] keyspan 2-10.3:1.0: Keyspan - (without firmware)
>> converter detected
>> [139762.047364] firmware: requesting keyspan/usa19qi.fw
>> [139762.089684] usb 2-10.3: New USB device found, idVendor\x06cd,
>> idProduct\x010b
>> [139762.089684] usb 2-10.3: New USB device strings: Mfr=0, Product=0,
>> SerialNumber=0
>>
>> It used to work with no firmware, but I went ahead and installed the
>> firmware from the 2.6.27 kernel; no difference. Still no /dev/ttyUSB?
>> device.
>>     
>
> These devices never would work without firmware, the older kernel
> versions had the firmware built into the drivers.  Are you sure you did
> load the firmware for the device properly?  Can you just build the
> firmware into the driver and see if that solves your issue?
>
>   
Interesting... I built a vanilla 2.6.27.4 kernel, and the problem went 
away.  Must be something debian does, or perhaps the 2.6.26 kernel 
handles the firmware differently from the 2.6.27 kernel.

--Yan

Re: keyspan USB serial not creating devices

[Greg KH]

On Sat, Nov 08, 2008 at 07:26:32AM -0800, Yan Seiner wrote:
> Greg KH wrote:
>> On Fri, Nov 07, 2008 at 09:02:43AM -0800, Yan Seiner wrote:
>>   
>>> I have a keyspan USB serial dongle that has quit working.  It used to 
>>> work
>>> on a machine with an older kernel (2.6.18???), properly creating the
>>> /dev/ttyUSB device.  Unfortunately I no longer have that machine.  The
>>> machine it's on now runs a 2.6.26 kernel, and the device is not being
>>> created.  The dongle is recognized, but no ttyUSB? are created:
>>>
>>> [139761.937391] usb 2-10.3: new full speed USB device using ehci_hcd and
>>> address 50
>>> [139762.046702] usb 2-10.3: configuration #1 chosen from 1 choice
>>> [139762.047357] keyspan 2-10.3:1.0: Keyspan - (without firmware)
>>> converter detected
>>> [139762.047364] firmware: requesting keyspan/usa19qi.fw
>>> [139762.089684] usb 2-10.3: New USB device found, idVendor\x06cd,
>>> idProduct\x010b
>>> [139762.089684] usb 2-10.3: New USB device strings: Mfr=0, Product=0,
>>> SerialNumber=0
>>>
>>> It used to work with no firmware, but I went ahead and installed the
>>> firmware from the 2.6.27 kernel; no difference. Still no /dev/ttyUSB?
>>> device.
>>>     
>>
>> These devices never would work without firmware, the older kernel
>> versions had the firmware built into the drivers.  Are you sure you did
>> load the firmware for the device properly?  Can you just build the
>> firmware into the driver and see if that solves your issue?
>>
>>   
> Interesting... I built a vanilla 2.6.27.4 kernel, and the problem went 
> away.  Must be something debian does, or perhaps the 2.6.26 kernel handles 
> the firmware differently from the 2.6.27 kernel.

Ah, yeah, go take it up with the debian people, they exclude firmware
blobs from their kernel trees for various dubious reasons.  This is
their bug, not ours.

good luck,

greg k-h