Re: usbcore / Linux 2.6.+ / USB IO Board 04d8:000a

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Alan, Oliver,

Am 08.09.2012 18:04, schrieb Alan Stern:
If you're certain that the problem is associated with the kernel version, you could try using git bisect to pinpoint exactly what change to the kernel caused the problem to start.
Never used git bisect before, but will give it a try. There might be a lot of changes to relevant modules between 2.6 and 3.2 - don't you think? what modules could be relevant in your opinion?
Has anybody an idea how to get this running?
Does the device work when plugged into a regular desktop system?  Have
you tested it recently under a 2.4 kernel to make sure that combination
still works?

Alan Stern

yes, the device is working perfectly under Windows (7) and in Ubuntu
10.04 with kernel 2.6.+.
The cdc_acm driver is loaded and a device /dev/ttyACM0 is created.
But starting with kernel 3.2.+ - as in Ubuntu 12.04 or Debian Wheezy -
the descriptors cannot be read.
Do you mean that the descriptors cannot be read when running Ubuntu
12.04 on a desktop system?
Yes. Connected the Board to a Ubuntu 12.04 x64 Desktop system:

# uname -a
Linux desktop01 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

# dmesg
[20012.271332] usb 1-1.2: new full-speed USB device number 3 using ehci_hcd
[20017.357551] usb 1-1.2: unable to read config index 0 descriptor/start: -32
[20017.357557] usb 1-1.2: chopping to 0 config(s)
[20017.359046] usb 1-1.2: string descriptor 0 read error: -32
[20017.359207] usb 1-1.2: no configuration chosen from 0 choices


@greg k-h: Thanks a lot, but it's not a power problem.

Is there any further log or information that I can contribute?
Can you provide a comparable usbmon trace from a kernel where the
device works?
Will deliver tomorrow!

Also, to make sure that nothing important has been omitted, please
resend the earlier trace without any "grep" filtering.  And do the same
with the new trace.
Ok, will try that. On the RPI there was a lot of traffic going on in that trace as there's an internal USB hub and a USB GPIO onboard. That's why I used grep.

Best regards,
 Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux