public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Boris B. Zhmurov" <bb@kernelpanic.ru>
To: linux-kernel@vger.kernel.org
Cc: Barbara Post <b.post@laposte.net>
Subject: Re: ohci_hcd, usb scanner and kernel 2.6.8.1 or 2.6.10 troubles
Date: Sat, 12 Feb 2005 02:53:01 +0300	[thread overview]
Message-ID: <420D455D.7050505@kernelpanic.ru> (raw)
In-Reply-To: <420D3EEF.20406@laposte.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello, Barbara Post.

On 12.02.2005 02:25 you said the following:

| Hi,
| I am unable to use my USB Agfa Snapscan 1212_U scanner, with kernel
| 2.6.8.1 or 2.6.10 (both compiled by myself from www.kernel.org sources)
| and xsane 0.96-1 (Debian).
|
| It worked with kernel 2.6.7.
|
| When I use VMware, I'm able to use it though (in Windows), whatever
| linux kernel I use.
|
| When I start xsane, I get "error opening device
| 'snapscan:libusb:001:004': I/O error on device" or simply "no device
| found" if I restart xsane after the first error message (or sometimes at
| first start).
|
| Sometimes it gets further and when I try to acquire preview, I get "I/O
| error" and the following in /var/log/syslog :
|
| Feb 11 23:19:00 babs1 kernel: ohci_hcd 0000:00:02.2: urb c15e13e0 path
| 1.3 ep1in 82160000 cc 8 --> status -75


I have the same problem with my Epson 1260 on RHEL4 beta2 (linux-2.6.9).
I don't know about 2.6.7, but with 2.4.21 (RHEL3) it works fine.


- --
Boris B. Zhmurov
mailto: bb@kernelpanic.ru
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFCDUVdmEQixi5w37YRApP+AJ9I5M7hf/0HPCATTnemFaNbLhvsbgCfZdTz
+hQ/jvcu7+xDpaXYTiOFZj4=
=6WVB
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-02-11 23:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 23:25 ohci_hcd, usb scanner and kernel 2.6.8.1 or 2.6.10 troubles Barbara Post
2005-02-11 23:53 ` Boris B. Zhmurov [this message]
2005-03-05 11:01   ` Barbara Post

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=420D455D.7050505@kernelpanic.ru \
    --to=bb@kernelpanic.ru \
    --cc=b.post@laposte.net \
    --cc=linux-kernel@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