From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Kieran Kunhya <kierank@obe.tv>
Cc: linux-input@vger.kernel.org
Subject: Re: usbhid: PicoLCD 256x64 USB error -71
Date: Sun, 18 May 2014 20:37:18 +0200 [thread overview]
Message-ID: <20140518203718.5422588f@neptune.home> (raw)
In-Reply-To: <032001cf7156$31a75610$94f60230$@obe.tv>
Hi Kieran,
On Fri, 16 May 2014 "Kieran Kunhya" <kierank@obe.tv> wrote:
> As requested I forward my bug report to the list:
>
> From time to time on an ASRock IMB-181D motherboard this device fails to be
> added.
> It seems to work reliably when using Windows 7.
> The errors in dmesg vary but usually take the form:
> [ 5.328040] usb 3-7: string descriptor 0 read error: -71
> (snip)
> [ 10.333605] usbhid 3-7:1.0: can't add hid device: -71
> [ 10.333639] usbhid: probe of 3-7:1.0 failed with error -71
> I can provide a PicoLCD unit if necessary and possibly also fund a
> fix/workaround.
>
> More information is available here:
> https://bugzilla.kernel.org/show_bug.cgi?id=76341
Hm, picoLCD works for me, but I get -71 error code if I swap both
data pins (but with read failure "device descriptor read/64, error -71").
Here it works with:
J4, pin 1 = red
J4, pin 2 = white
J4, pin 3 = green
J4, pin 4 = black
J4, pin 5 = n/a
I successfully tried on:
- Gigabyte mainboard (GA-A75M-UD2H) (USB2 & USB3 ports) [3.15-rc5, 64bit]
- Acer Travelmate 66x [3.15-rc2, 32bit]
- Commell LE-365 [3.14, 32bit]
- IEI KINO-690S1 [3.14, 64bit]
Did some previous kernel release work?
Could you provide verbose lsusb output and firmware version for your PicoLCD?
Thanks,
Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-18 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 22:28 usbhid: PicoLCD 256x64 USB error -71 Kieran Kunhya
2014-05-18 18:37 ` Bruno Prémont [this message]
2014-05-18 19:44 ` Kieran Kunhya
2014-05-21 13:08 ` Kieran Kunhya
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=20140518203718.5422588f@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=kierank@obe.tv \
--cc=linux-input@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).