Hi, On Mon, Feb 24, 2003 at 10:22:25PM +0100, Stian Jordet wrote: [I wrote] > > But it seems to be connecte to /dev/usb/scanner1. > > > > Fix the config files (plustek.conf/epson.conf). > > > I have tried both.
So does it work with /dev/usb/scanner1? > You have any idea why it want scanner1 in 2.5.x and > scanner0 in 2.4.x? No idea. I can't reproduce that behaviour with 2.5.63. Without devfs (device file system), it works just fine. With devfs enabled, the device file is named /dev/usb/scanner48 (because of the minor id). That's a bug but I don't think it's relevant here. Enabling "dynamic minors" works with and without devfs. So do you use devfs and/or dynamic minors? Dynamic minors is in the USB section, part of usbfs. If you want to hunt the bug, can you enable debugging in the scanner driver (drivers/usb/image/scanner.h)? Please show me the output in syslog. Does sane-find-scanner find the scanner at /dev/usb/scanner1? > I'm using 2.4.21-pre3, which is working very good. > But I can try pre4. If it works, no need to upgrade. > Hmm. Thanks anyway. Since there is no known issues, it's just my > setup, I guess. The allocation of minor ids is different in 2.5.*. So there may be a bug. Generally speaking I recommend to use libusb instead of the kernel scanner driver, at least in 2.5.*. The kernel scanner driver in 2.5.* may be removed at any time. Bye, Henning
