Hi, On Mon, Feb 24, 2003 at 07:04:10PM -0500, Richard M. Teitel wrote: > All I can tell you at the moment are that they are files that seem to > indicate what the OS has found on the machine. I haven't figured out how > they are used. The sysconfig/hwconf file shows all the devices connected > to the machine, including the scanner.
Ignore that file for now. I guess it's some magic hardware detection tool. Once manual detection works, you can try to get it working automatically. > Red Hat 8.0 uses kernel 2.4.18-14. I'm a little surprised at your > comment. I would have thought that finding the scanner in the hwconf > file and not detecting it with sane-find-scanner would say that the > kernel detected it but SANE did not. That would be true if sane-find-scanner finds the scanner but scanimage -L doesn't. sane-find-scanner just asks the kernel for scanners. It lists all scanners, even if they are not supported by SANE. If it doesn't list all (USB+SCSI) scanners, it's a bug in sane-find-scanner. > First, when I tried to run rmmod scanner the system said "command not > found," even when I tried it from the /sbin directory. I tried to run > modprobe and got the same response. As root? If this doesn't work, your system is broken. These are just the basic module loading/unloading commands. If for some reason /sbin is not in root's path, you can run the commands with the full pathname (e.g. /sbin/rmmod scanner). > However, again, with the scanner > vendor and product id's correctly entered in the hwconf file, doesn't > the kernel already know it's there? The scanner was detected as a USB device most probably, but the kernel doesn't know that it's a scanner. There is no class or other identification that tells the scanner which USB device is a scanner so the ids of each scanner must be added to the source code of the kernel or entered manually. The latter method is done with the above mentioned modprobe command. With this command you telle the kernel to load the scanner driver and that the USB device is a scanner. > Second, I looked at the plustek.conf file and found that it already has > the /dev/usb/scanner0 line. That's ok but that won't help until sane-find-scanner finds your scanner. > But my problem really seems to be getting > SANE to run the Plustek script for the UMAX scanner. How do I establish > that relationship? That works automatically. The SANE frontend (e.g. xsane or scanimage) asks the SANE backends to check for known scanners. Each backend now checks if any of the scanners it knows is present. Ideally, you don't need to fiddle with any SANE config file at all. > >You can also look at what's connected to your system by running "cat > >/proc/bus/usb/devices". There you should find the ids of your scanner, > >in case I gave you the wrong ones. If this file doesn't exist, run > >"mount -t usbdevfs /proc/bus/usb /proc/bus/usb". > > > > > I looked at that file and found that the scanner is included in the > list, with the vendor and product id's you mentioned earlier. Check the line that starts with "I:" (after the lines with the ids of your scanner). I bet that it has a "driver=(none)" entry there. You need a "driver=usbscanner". You can achieve this with the modprobe command mentioned above. > The scanner.txt document is not included in the Red Hat installation. It most probably is, it's part of the kernel source. So I guess you just haven't installed the necessary package (kernel source probably) :-) Bye, Henning ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
