From: Barbara Post <b.post@laposte.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ohci_hcd, usb scanner and kernel 2.6.8.1 or 2.6.10 troubles
Date: Sat, 05 Mar 2005 12:01:24 +0100 [thread overview]
Message-ID: <42299184.2040205@laposte.net> (raw)
In-Reply-To: <420D455D.7050505@kernelpanic.ru>
Hello,
I finally succeeded in making my USB scanner work with 2.6.8.1 and above kernels. I remind you I was
able to see connection/disconnection messages, but not to use it via xsane.
I found the solution on a Debian mailing-list, that worked for me :
cd to /dev
type :
/sbin/MAKEDEV usb
This command created the required character devices. Since USB support has been rewritten between
2.6.7 and 2.6.8.1 kernels, this was likely to happen when one manually installs a new kernel...
Barbara
Boris B. Zhmurov wrote:
>
> 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.
>
>
prev parent reply other threads:[~2005-03-05 10:59 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
2005-03-05 11:01 ` Barbara Post [this message]
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=42299184.2040205@laposte.net \
--to=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