--oNLI4EWr1RPQuPCf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, May 27, 2002 at 02:13:10PM -0500, Joel Uckelman wrote:
> Thanks! That did the trick. What does reinstalling the sane-backends=20
> package do that fixes th
Thus spake Tim Waugh:
>
> On Sun, May 26, 2002 at 09:09:45PM -0500, Joel Uckelman wrote:
>
> > I upgraded to RedHat 7.3 yesterday, which apparently has caused my
> > Epson 610 to stop working.
>
> This is a known issue that will be addressed shortly. In the mean
> time, you should be able to wor
--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Your /proc/bus/usb/devices output is incomplete: You've left out
a few lines that show which driver did recognize your scanner. You
need the first "I:" line after t
--b1ERR0FXR0PvNIRE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sun, May 26, 2002 at 09:09:45PM -0500, Joel Uckelman wrote:
> I upgraded to RedHat 7.3 yesterday, which apparently has caused my
> Epson 610 to stop working.
This is a known issue that will be addressed
> crw-r--r--1 root root 180, 48 Apr 11
> 09:25 /dev/usb/scanner0
Shouldn't you have write access to the device ?
___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
Thus spake Sylvain Petreolle:
>
> > crw-r--r--1 root root 180, 48 Apr 11
> > 09:25 /dev/usb/scanner0
>
> Shouldn't you have write access to the device ?
Yes, but since I was screwing with it as root, I did have write access. I'd
twiddled the permissions a bit in the process---it wa
I upgraded to RedHat 7.3 yesterday, which apparently has caused my Epson
610 to stop working. Now, sane-find-scanner detects it:
sane-find-scanner: found USB scanner (vendor = 0x04b8, product = 0x0103) at
device /dev/usb/scanner0
And it shows up in /proc/bus/usb/devices:
C:* #Ifs= 1 Cfg#= 1 At
