On Sun, 11 Jul 2010 10:35:48 -0400
Alan Greenberger wrote:
> On 2010-07-10, wrote:
> > My scanner, a very old epson, shows up in dmesg:
> >
> > Processor EPSONGT-9700 1.03 PQ: 0 ANSI: 4
> > scsi 11:0:0:0: Attached scsi generic sg1 type 3
>
> Try running sane-find-scanner (
On Sun, 11 Jul 2010 10:56:26 + (UTC)
Bill Dennen wrote:
> I would suspect that the vendor and device IDs for your device do not
> match those listed in libsave. You can determine your scanner's
> identity through lspci -nn. If it's not 04b8:0112 then there's no
> match for that entry. Pro
On Sun, 11 Jul 2010 10:35:48 -0400
Alan Greenberger wrote:
> On 2010-07-10, wrote:
> > My scanner, a very old epson, shows up in dmesg:
> >
> > Processor EPSONGT-9700 1.03 PQ: 0 ANSI: 4
> > scsi 11:0:0:0: Attached scsi generic sg1 type 3
>
> Try running sane-find-scanner (
On 2010-07-10, wrote:
> My scanner, a very old epson, shows up in dmesg:
>
> Processor EPSONGT-9700 1.03 PQ: 0 ANSI: 4
> scsi 11:0:0:0: Attached scsi generic sg1 type 3
Try running sane-find-scanner (in package sane-utils).
--
To UNSUBSCRIBE, email to debian-user-requ...@
I would suspect that the vendor and device IDs for your device do not
match those listed in libsave. You can determine your scanner's identity
through lspci -nn. If it's not 04b8:0112 then there's no match for that
entry. Probably did match on generic, and that rule may not set the
GROUPID a
My scanner, a very old epson, shows up in dmesg:
Processor EPSONGT-9700 1.03 PQ: 0 ANSI: 4
scsi 11:0:0:0: Attached scsi generic sg1 type 3
I checked /lib/udev/rules and in the libsave rules there is a match:
# Epson Perfection 2450 | Epson GT-9700F | Epson Perfection 2450 P
On Sun, Mar 12, 2006 at 06:49:19PM +0100, Ernst-Magne Vindal wrote:
> First of all, "topposting"..
While we're on the topic of email etiquette, perhaps we could discuss
pruning quotations to the bare minimum.
Top posting, while obnoxious, is not as bad as having to scroll down two
pages bef
t;>Hi All,
>>>
>>>I have a problem that just started with my scanner permissions. I can't
>>>access it by any means unless I am root. I am running a mix of Sarge
>>>and Sid using the 2.6.15-k7 kernel.
>>>
>>>Running sane-find-scanner or sca
I tried that. I set the group to scanner and set permissions to 770.
It didn't change anything.
Ernst-Magne Vindal wrote:
On Sat, March 11, 2006 21:27, Freddy Freeloader said:
Hi All,
I have a problem that just started with my scanner permissions. I can't
access it by
On Sat, March 11, 2006 21:27, Freddy Freeloader said:
> Hi All,
>
> I have a problem that just started with my scanner permissions. I can't
> access it by any means unless I am root. I am running a mix of Sarge
> and Sid using the 2.6.15-k7 kernel.
>
> Running sane-fi
Hi All,
I have a problem that just started with my scanner permissions. I can't
access it by any means unless I am root. I am running a mix of Sarge
and Sid using the 2.6.15-k7 kernel.
Running sane-find-scanner or scanimage -L as root correctly identifies
my scanner, an HP 6200C. Ru
On 2003-06-09 19:30:34, Tom Allison wrote:
> I thought I could do this:
>
> addgroup scanner
> chown root.scanner /dev/scsi/host2.../generic
> adduser {me} scanner
> chmod g+rw /dev/scsi/host2/.../generic
>
> It didn't work.
>
> I had to chmod a+rw to the scsi device for it to work.
The above sh
I finally got my SCSI scanner working.
Now I have to get the permissions set up correctly.
I thought I could do this:
addgroup scanner
chown root.scanner /dev/scsi/host2.../generic
adduser {me} scanner
chmod g+rw /dev/scsi/host2/.../generic
It didn't work.
I had to chmod a+rw to the scsi device f
13 matches
Mail list logo
