From: Neil Kalo <neilkalo@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Steve Holland <sdh4@iastate.edu>,
Oliver Neukum <oliver@neukum.org>
Subject: Re: usbmc seems broken
Date: Thu, 4 Feb 2010 08:32:21 +0000 [thread overview]
Message-ID: <5c343a41002040032w54bb9953nd6bfe60a06553625@mail.gmail.com> (raw)
In-Reply-To: <20100127015947.GA11685@kroah.com>
Upgraded to: 2.6.32.7-37.fc12.i686.PAE
Still no joy. Plugging in the meter gives:
Feb 4 08:27:04 localhost kernel: usb 4-1: new full speed USB device
using ohci_hcd and address 2
Feb 4 08:27:04 localhost kernel: usb 4-1: New USB device found,
idVendor=05e6, idProduct=2100
Feb 4 08:27:04 localhost kernel: usb 4-1: New USB device strings:
Mfr=2, Product=3, SerialNumber=1
Feb 4 08:27:04 localhost kernel: usb 4-1: Product: 2100 Multimeter
Feb 4 08:27:04 localhost kernel: usb 4-1: Manufacturer: KEITHLEY INSTRUMENTS
Feb 4 08:27:04 localhost kernel: usb 4-1: SerialNumber: 1160791
Feb 4 08:27:04 localhost kernel: usb 4-1: configuration #1 chosen from 1 choice
Feb 4 08:27:04 localhost kernel: usbcore: registered new interface
driver usbtmc
But "cat /dev/usbtmc0" gives:
cat: /dev/usbtmc0: Connection timed out
And in the logs:
Feb 4 08:27:35 localhost kernel: usbtmc 4-1:1.0: Unable to read data,
error -110
The very old driver still works:
Feb 4 08:31:02 localhost kernel: USBTMC: MKDEV
Feb 4 08:31:02 localhost kernel: USBTMC: CDEV_ADD f900000 1
Feb 4 08:31:02 localhost kernel: usbcore: registered new interface
driver USBTMC
[root@mc22 usbtmc-module]# cat /dev/usbtmc0
Minor Number Manufacturer Product Serial Number
001 KEITHLEY INSTRUMENTS 2100 Multimeter 1160791
On Wed, Jan 27, 2010 at 1:59 AM, Greg KH <greg@kroah.com> wrote:
> On Tue, Jan 26, 2010 at 05:01:25PM -0800, Andrew Morton wrote:
>> (cc's added)
>>
>> On Fri, 22 Jan 2010 16:40:06 +0000
>> Neil Kalo <neilkalo@gmail.com> wrote:
>>
>> > I cannot get usbtmc to work with my device. I am using fedora 12:
>> > 2.6.31.12-174.2.3.fc12.i686.PAE
>> >
>> > Jan 22 15:40:26 localhost kernel: usb 4-1: new full speed USB device
>> > using ohci_hcd and address 4
>> > Jan 22 15:40:26 localhost kernel: usb 4-1: New USB device found,
>> > idVendor=05e6, idProduct=2100
>> > Jan 22 15:40:26 localhost kernel: usb 4-1: New USB device strings:
>> > Mfr=2, Product=3, SerialNumber=1
>> > Jan 22 15:40:26 localhost kernel: usb 4-1: Product: 2100 Multimeter
>> > Jan 22 15:40:26 localhost kernel: usb 4-1: Manufacturer: KEITHLEY INSTRUMENTS
>> > Jan 22 15:40:26 localhost kernel: usb 4-1: SerialNumber: 1160791
>> > Jan 22 15:40:26 localhost kernel: usb 4-1: configuration #1 chosen from 1 choice
>> > Jan 22 15:40:26 localhost kernel: usbtmc 4-1:1.0: can't read capabilities
>
> This was a bug in this version of the driver.
>
> Please upgrade to 2.6.32, the problem is fixed.
>
> If you are curious, commit id d0a38365d9585bf3fb71f7c57fd532441a14f3e8
> solved the problem.
>
> Hope this helps,
>
> greg k-h
>
next prev parent reply other threads:[~2010-02-04 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 16:40 Neil Kalo
2010-01-27 1:01 ` Andrew Morton
2010-01-27 1:59 ` Greg KH
2010-02-04 8:32 ` Neil Kalo [this message]
2010-02-24 2:18 ` 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=5c343a41002040032w54bb9953nd6bfe60a06553625@mail.gmail.com \
--to=neilkalo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=sdh4@iastate.edu \
/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
all inboxes | Powered by JetHome®