[gutsy] keyspan serial adapter not detected

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Like I said, it worked on my Feisty desktop machine:
martin@martin-desktop:~$ uname -a
Linux martin-desktop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

Here is the Gutsy macbook pro where it doesn't work:
martin@martin-laptop:~$ uname -a
Linux martin-laptop 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux

The adapter was plugged into both systems when I captured this information. The device gets power over USB and does not light on the Gutsy system. On the Feisty system, it hesitates for a second, the hard drive spins and then the power light lights.

cheers.
martin.

I'm sorry, the output of lsusb with the device connected would also be helpful. Thanks again.

Well, it does appear to see it - it just doesn't power it...

martin@martin-laptop:~$ lsusb
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 003: ID 05ac:021a Apple Computer, Inc.
Bus 005 Device 001: ID 0000:0000
Bus 005 Device 002: ID 05ac:8242 Apple Computer, Inc.
Bus 007 Device 002: ID 05ac:8502 Apple Computer, Inc.
Bus 007 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 06cd:011a Keyspan
Bus 001 Device 004: ID 05ac:8205 Apple Computer, Inc.
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000

here is the section about the hub from the lsusb -v command - let me know if you want the rest of the output:

Bus 001 Device 005: ID 06cd:011a Keyspan
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 255 Vendor Specific Class
  bDeviceSubClass 255 Vendor Specific Subclass
  bDeviceProtocol 255 Vendor Specific Protocol
  bMaxPacketSize0 64
  idVendor 0x06cd Keyspan
  idProduct 0x011a
  bcdDevice c0.01
  iManufacturer 0
  iProduct 0
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 218
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 0
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 1
      bNumEndpoints 13
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 10
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval ...

Additionally, I tried the adapter with gutsy running in VMWare on OS X. Same outcome.

I have the same problem.
It seems that the source was recently taken out of the kernel due to a poor license from Keyspan.
We have been using these devices extensively on many machines since they always had good linux support.
Their site recommends using a linux which supports their product. I would rather not have to change linux distributions.
Is there any work around to still use the Keyspan usb-serial adapters with Gutsy?

I didn't realize that. I checked out the current kernel tree in Gutsy - there seemed to be Keyspan modules in there. I was going to try to check out the Feisty sources to diff/check them as well but never got around to them.

inux-source-2.6.22 (2.6.22-4.10) gutsy; urgency=low

  [Ben Collins]

  * Bump ABI
  * build/config: Disable obsolete tsdev driver.
  * build: Add tsdev to list of modules intentionally removed.
  * build/headers: Include *.lds files (fixes ia64 headers).
  * build/headers: Add arch/powerpc/include/asm symlink to get all headers.
  * build/module-check: Fix logic for printed messages.
  * build/maintainer: Use linux instead of upstream-linux for local diffs
  * build/config: Enable SLUB slab allocator (vs. SLAB).
  * build/config: Disable orinoco_nortel, use prefered hostap_plx
  * build/config: Disable ir-usb in favor of irda-usb
  * build/config: Disable sis5513(ide) in favor of pata_sis(libata)
  * build/config: Disable piix(ide) in favour of pata_oldpiix, ata_piix and
    pata_mpiix (libata)
  * build/config: Disable zaurus driver in favour of the cdc_ether driver
  * build/abi: Note a few modules intentionally removed.
  * build/config: Disable mxb and dpc7146 driver in favour of hexium_orion
  * build/config: Disable usbtest driver (for development only)
  * build/config: Disable keyspan driver in favour of keyspan_pda
  * build/abi: Add mxb and usbtest to list of removed modules.

The keyspan_pda does not seem to allow serial communication with a keyspan USA-19HS

  Ya,

  I have the exact same problem. Works perfect with 2.6.20, does not work with 2.6.22. Same version of Ubuntu (Gutsy). Except I am trying to connect to a 19HS

  Ok, roll your own. I just downloaded the source for the kernel from Ubuntu, followed these steps: https://help.ubuntu.com/community/Kernel/Compile then rebooted.. had an issue with my network card no longer working to which I found a simple solution and voila. It all works.

   When you get the source for the kernel, do a make xconfig and then search for keyspan. Enable your driver and build.

I was having the same issue. I have now built a .deb package that contains the missing keyspan module, details at http://www.denis.lemire.name/2007/10/19/ubuntu-keyspan/

Same problem here. 19HS also. Thanks for deb Denis, works for me.

This is a HUGE problem for me as my Keyspan USA-19HS isn't detected (my laptop does not have serial ports built in).

I'm wary of compiling my own kernel... or installing .deb kernel mods (i like to try to stay stock, BUT Denis' method works beautifully if they want to try it)... could this driver component be enabled in a future kernel update to Gutsy???

On 26/10/2007, DeployPenguins <email address hidden> wrote:
>
> This is a HUGE problem for me as my Keyspan USA-19HS isn't detected (my
> laptop does not have serial ports built in).
>
> I'm wary of compiling my own kernel... or installing .deb kernel mods (i
> like to try to stay stock, BUT Denis' method works beautifully if they
> want to try it)... could this driver component be enabled in a future
> kernel update to Gutsy???

  I can't speak for Denis's kernel but you really have nothing to lose by
compiling your own. If it doesn't work, simply reboot and choose the next
available Kernel.

   J

--
Justin F. Knotzke
<email address hidden>
http://www.shampoo.ca

Alright... You've encouraged me! I will try compiling a kernel this weekend using your guide as a reference.

Be brave, me... be brave. :)

THANK YOU!

Just a note, the deb package I created isn't a custom kernel, rather it is just adds the missing keyspan module compiled from the same kernel source version as the generic Ubuntu kernel package. Hence, after installing my package you are still using the generic kernel, you just have one additional file added to the modules directory to restore the missing functionality.

Denis,

Thank you for all your hard work in fixing this problem and sharing it with the rest of the community.

That note is helpful to me! You can probably tell, but I'm very, very new to Ubuntu (and Linux in general).

I guess that if a new kernel WERE to be released, your .deb would cease to function???

Thanks again!

No worries, I'm thrilled so many people have found my quick effort useful. You are correct, if an updated kernel packages is released, my module package will most likely not work. It is, however, very easy for me to update it. Given that I use the device regularly, I'll be quick to notice and will need to build a new package for my uses anyway. Hence if the next kernel update doesn't include the update I will update the package and post it to my web site.

I am grateful for Denis' contribution here.

Worked great on my Dell E1405 laptop.

Wow guys !

2 days since i moved to Gusty just to have the new Gimp, and i had the same problem .

Well i'm happy to say that your .deb seems to work perfectly on my laptop ( hp pavillon ). I don't have a very good english so i can't very well express how gratful i'am !
Thanks you very much Denis, i'll pass the information on french site.

Thanks again !

The driver is disabled in Debian and Ubuntu because the firmware it requires to function is not open-source: http://www.keyspan.com/downloads-files/developer/linux/

Obviosuly, this is a poor solution. The working, closed-source module should be copied into the linux-restricted-modules package and installed with it, instead (how to reflect this within the metadata of launchpad, I don't know)

I dusted off my USA-19HS today, because I needed it, but since I've upgraded
to gutsy, I wound up here.

I tried Denis's .deb, but, although it's still 2.6.22-14-generic, some even lower
level version number moved from 46 to 47, and the package doesn't install.

Ok, so I set up to build kernels, then tried to follow the instructions referenced
above, but with limited success. Probably I don't understand where all I have
to edit to re-enable the keyspan driver. I tried debian/config/i386/config.386
since the recommended "oldconfig" invocation seems to build up config from
the config.* files in the arch directory (but I later noticed that it then seems
to delete the config thus generated), but still no keyspan stuff.

(The last time that I configured a kernel I used make menuconfig, which worked
fine. But the kernel build system is already complex without adding the debian
layers around it, and I'm fairly lost)

So, Denis, if you're listening, can you give me a pointer as to which files to edit?
(And did you have to add the execute bit to the stuff in debian/scripts/misc in
order to run the oldconfig script?)

I figured that I'd comment here, rather than asking in a forum (just yet) to add
my voice to the chorus saying that disabling the user's hardware over an
abstract licensing tif, and not providing an obvious and simple way for the user
to make the opposite choice, is a less than fully correct thing to do.

If you look at the comments in the posting on my web site there is a recent comment by a guy named Bob that explains how to tweak my package to install on the current kernel version. This will work as long as you are on 32-bit Intel.

I'm not familiar with the oldconfig script you're referring to. I originally followed this howto: http://www.howtoforge.com/kernel_compilation_ubuntu when I intended to build myself a custom kernel with the Keyspan module. Unfortunately this left me without Intel wireless support, hence my efforts to build the module package instead.

Not sure which file you are trying to edit, if you're trying to edit the kernel config file as opposed to using make menuconfig (as I did) then I'll let you know what the appropriate line is... I don't have my laptop handy at the moment to check my config file...

Maybe if I get some free time this weekend I'll finally get around to building an updated package.

The changelog from Ben Collins doesn't mention a licensing issue.

As far as I know, only Debian has issue with the firmwares, other distros don't, and they are part of the upstream kernel sources. In fact, the simple fact that Ubuntu kernel source actually ships with the firmwares included makes it a totally moot point. Not enabling them doesn't "fix" a possible licence incompatibility since they are shipped :-)

Hopefully, this is just a mistake from Ben thinking the keyspan_pda driver is a _replacement_ for the other one. It's not. The keyspan_pda is a different (and simpler, it's not very reliable at higher speeds) piece of hardware that uses a different driver. The main keyspan serial driver is still needed for most keyspan serial adapters (including mines ! Ben, please fix it !!!).

Looks like CONFIG_USB_SERIAL_KEYSPAN_PDA is not enabled in the current development kernel. Am reassigning to the kernel team. Thanks.

Actually, it's CONFIG_USB_SERIAL_KEYSPAN that is missing, not CONFIG_USB_SERIAL_KEYSPAN_PDA :-)
Also, once it's enabled, you also need to enable all the dependent sub-options for the various firmwares.

This is what I use here:

CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y

doh.

The keyspan module appears to be included again as of the linux 2.6.24-5.8 package.

I confirm : using keyspan on 2.6.24.16 works