USB<->Serial converter based on Moschip 7840 does not work in Hardy

[Andreas]

I've just upgraded my server from Gutsy to Hardy.
Most of my applications is still working (eventhough some fixes where needed). However there is one final thing that doesn't work; my USB <-> Serial converter.

The converter is identified by the system that the mos7840 module is loaded. But when the module should identify the converter I get the message "probe of 8-1:1.0 failed with error -5". When running Gutsy everything worked fine.

See below for log extracts from dmesg from my server running Gutsy and Hardy. I've also included an verbose listing of lsusb on the converter.

Output from dmesg in Hardy:
[ 38.565449] /build/buildd/linux-2.6.24/drivers/usb/serial/mos7840.c: Moschip 7840/7820 USB Serial Driver 1.3.1
[ 38.565472] mos7840: probe of 8-1:1.0 failed with error -5
[ 38.565480] usbcore: registered new interface driver mos7840

Output from dmesg in Gutsy:
[ 34.265121] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/mos7840.c: Moschip 7840/7820 USB Serial Driver 1.3.1
[ 34.265140] mos7840 8-1:1.0: Moschip 7840/7820 USB Serial Driver converter detected
[ 34.271350] usbcore: registered new interface driver mos7840

lsusb -v
Code:

Bus 008 Device 003: ID 9710:7840 MosChip Semiconductor
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 255 Vendor Specific Class
  bDeviceSubClass 0
  bDeviceProtocol 255
  bMaxPacketSize0 64
  idVendor 0x9710 MosChip Semiconductor
  idProduct 0x7840
  bcdDevice 0.01
  iManufacturer 0
  iProduct 0
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 81
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 9
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 255
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x04 EP 4 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x85 EP 5 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x06 EP 6 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x87 EP 7 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x08 EP 8 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 255
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x89 EP 9 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 5
Device Qualifier (for other device speed):
  bLength 10
  bDescriptorType 6
  bcdUSB 2.00
  bDeviceClass 255 Vendor Specific Class
  bDeviceSubClass 0
  bDeviceProtocol 255
  bMaxPacketSize0 64
  bNumConfigurations 1
Device Status: 0x0000
  (Bus Powered)

I've run out on ideas on how to handle the error. Any ideas?

/Andreas

[Martin Kossick (hacktick)]

Hi,
thank you for reporting this bug.
Could you test your usb-converter with another PC and a live hardy,
intrepid or jaunty?

greetings

Martin

[Andreas (andreas-dahlen)]

Hi!
I tested with another computer and had the same problem.

With Intrepid the mos7840 seams to install correctly;
[ 10.524931] usbserial: USB Serial support registered for Moschip 7840/7820 USB Serial Driver
[ 10.524933] mos7840: Moschip 7840/7820 USB Serial Driver 1.3.1
[ 10.524958] mos7840 8-1:1.0: Moschip 7840/7820 USB Serial Driver converter detected
[ 10.526552] usb 8-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB2
[ 10.526594] usb 8-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB3
[ 10.526635] usb 8-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB4
[ 10.526675] usb 8-1: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB5
[ 10.526685] usbcore: registered new interface driver mos7840

However I havn't manage to use my serial interface yet. Right now I'm not sure if its due to a problem with the driver or my clientapplication, since it has been upgraded since my last try.

/Andreas

[jcarroll (justcarroll)]

I have had the same issues. It seems install but is unusable. I believe I have the same device reported above.

Moschip does provide the code for a driver but I have been unable to get it to compile. Still working on it.

The README file reports that it has been tested on Fadora and others.

Release 8.10 (intrepid)

Justin

[xteejx (xteejx-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it, and if it is still an issue, we would appreciate if you could upload updated logs and any other logs that are relevant for this particular issue.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]