1 |
On AD 2008 July 30 Wednesday 03:49:23 PM -0700, Grant wrote: |
2 |
> I can't figure out where the device file is. With the scanner |
3 |
> connected and powered on I did an 'updatedb && locate scanner' and it |
4 |
> didn't come up with anything in /dev, I don't have a /dev/usb/ |
5 |
> directory, and the output of 'ls /dev/usb*' is the same with the |
6 |
> scanner on or off. Any idea where that file might be? Those two |
7 |
> commands also don't mention it. |
8 |
|
9 |
Another way to get info is to power on the scanner and plug it in, then |
10 |
`modprobe -r` the appropriate kernel module(s) and then modprobe them |
11 |
while doing `tail -F /var/log/messages`. The kernel (udev) will create the |
12 |
appropriate /dev entries upon successful modprobe. |
13 |
|
14 |
In order for your user to be registered as a member of a group you have |
15 |
to log completely out (including your X session) and back in. You can |
16 |
verify your group memberships with the groups command. Judging from |
17 |
what you've said I bet it was merely an issue of adding your user to the |
18 |
scanner or usb group. My experience with usb scanners is they generally |
19 |
just work whereas when I start up my SCSI scanner I always have to |
20 |
remodprobe the kernel drivers and then `chown :scanner /dev/sg? && |
21 |
chmod 0770 /dev/sg?`, but there's probably a better (right) way to do |
22 |
that. :-) |
23 |
|
24 |
|
25 |
Justin |