1 |
On Wednesday 07 March 2007 13:35:57 David Fellows wrote: |
2 |
> > $ ls /etc/udev/rules.d |
3 |
> > 05-udev-early.rules 60-vmware.rules |
4 |
> > 75-persistent-net-generator.rules 99-libsane.rules |
5 |
> > 50-udev.rules 70-persistent-cd.rules |
6 |
> > 92-scanner.rules 60-persistent-input.rules 70-persistent-net.rules |
7 |
> > 95-net.rules 60-persistent-storage.rules |
8 |
> > 75-cd-aliases-generator.rules |
9 |
> > 99-libgphoto2.rules |
10 |
> > |
11 |
> > Rather more than your system, it seems! |
12 |
> |
13 |
> On my system I have /etc/udev/rules.d/99-libsane.rules which belongs to |
14 |
> media-gfx/sane-backends-1.0.18-r2. |
15 |
> |
16 |
> I emerged xsane, sane-backends and sane-frontends and except for adding |
17 |
> myself to the scanner group it "just worked". I have an Epson 1650 scanner. |
18 |
> I don't use it much. |
19 |
> |
20 |
> Perhaps re-emerging the sane packages would clean things up. |
21 |
> |
22 |
I also have 99-libsane.rules owned by media-gfx/sane-backends-1.0.18-r2. This |
23 |
is the rules file which identifies the USB device as a scanner and sets the |
24 |
correct permissions so that is just works. Please try emerging it again and |
25 |
ensuring it is there. |
26 |
|
27 |
Then run udevstart to apply the rules. |
28 |
|
29 |
Marcus |