linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: keyspan USB serial not creating devices
Date: Fri, 07 Nov 2008 19:01:11 +0000	[thread overview]
Message-ID: <20081107190111.GB24511@kroah.com> (raw)
In-Reply-To: <7d4fe611c622c163c76d7c430f09f61d.squirrel@www.datavault.us>

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

  reply	other threads:[~2008-11-07 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 17:02 keyspan USB serial not creating devices Yan Seiner
2008-11-07 19:01 ` Greg KH [this message]
2008-11-08 15:26 ` Yan Seiner
2008-11-08 18:34 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081107190111.GB24511@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).