[sane-devel] Linux 2.5.62
Hi, On Tue, Feb 25, 2003 at 04:36:12PM +0100, Stian Jordet wrote: > Tadaa, the dynamic minors were the problem. Disabling that, and > everything works. Sorry for the noise, and thanks for your patience. I can confirm your observation. Dynamic minors without devfs doesn't work. Neither with libusb nor kernel scanner driver. However, I don't get the message that the scanner is detected at scanner1, for me it's still scanner0. All other combinations seem to work (devfs with dynamic minors, devfs without dynamic minors, no devfs + no dynamic minors). I'll ask linux-usb-devel if this is a know issue. Bye, Henning
[sane-devel] Linux 2.5.62
tir, 2003-02-25 kl. 12:24 skrev Henning Meier-Geinitz: > 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. Tadaa, the dynamic minors were the problem. Disabling that, and everything works. Sorry for the noise, and thanks for your patience. Best regards, Stian Jordet
[sane-devel] Linux 2.5.62
Hi, On Tue, Feb 25, 2003 at 03:44:24PM +0100, Thomas Soumarmon wrote: > Couldn't it be the old problem of permissioning of /dev/usb/scanner1 ? No, libusb doesn't even touch this file. Theoretically, it may be a permission problem of /proc/bus/usb/002/003, but why should it work with 2.4 and not with 2.5? And why do both the kernel scanner driver and libusb not work? It doesn't harm to try as root anyway. I'll do some more tests with 2.5 now. Bye, Henning
[sane-devel] Linux 2.5.62
tir, 2003-02-25 kl. 15:44 skrev Thomas Soumarmon: > Couldn't it be the old problem of permissioning of /dev/usb/scanner1 ? > Does the user has read and write access to the device file ? No.. that was the first thing I checked. And to be sure, I even chmod'ed them 777, just to be sure. Regards, Stian
[sane-devel] Linux 2.5.62
Couldn't it be the old problem of permissioning of /dev/usb/scanner1 ? Does the user has read and write access to the device file ? Le Mardi 25 F=E9vrier 2003 14:55, Stian Jordet a =E9crit : > tir, 2003-02-25 kl. 14:26 skrev Henning Meier-Geinitz: > > Hi, > > Well, then I guess it's something else (not related to the kernel > > scanner driver). Please enable SANE_DEBUG_SANEI_USB=3D255 also. > > Ahh, this made more sense, I think (altough still no idea what the > problem might be. "Operasjonen er ikke tillatt" is norwegian for > something like "Operation not permitted". > > [plustek] Checking for 0x04b8-0x011d > [sanei_usb] sanei_usb_find_devices: vendor=3D0x04b8, product=3D0x011d, > attach=3D0x405cd184 > [plustek] Found device at >libusb:002:003< > [sanei_usb] sanei_usb_open: trying to open device `libusb:002:003' > USB error: could not set config 1: Operasjonen er ikke tillatt > [sanei_usb] sanei_usb_open: libusb complained: could not set config 1: > Operasjonen er ikke tillatt > [sanei_usb] Make sure you run as root or set appropriate permissions > [plustek] open failed: -1 > [plustek] sane_get_devices (0xbfffe848, 0) > [plustek] sane_exit > > > > chevrolet:~# sane-find-scanner > > > > > > # No SCSI scanners found. If you expected something different, ma= ke > > > sure that > > > # you have loaded a SCSI driver for your SCSI adapter. > > > > > > found USB scanner (vendor=3D0x0731, product=3D0x0528) at libusb:001= :002 > > > found USB scanner (vendor=3D0x04b8 [EPSON], product=3D0x011d [EPSON > > > Scanner]) at libusb:002:003 > > > > What kind of device is the first one? > > The first device is a usb-cradle for my Sony Ericsson P800 phone... > > Thanks for your patience :) > > Best regards, > Stian > > ___ > Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Linux 2.5.62
tir, 2003-02-25 kl. 14:26 skrev Henning Meier-Geinitz: > Hi, > Well, then I guess it's something else (not related to the kernel > scanner driver). Please enable SANE_DEBUG_SANEI_USB=255 also. Ahh, this made more sense, I think (altough still no idea what the problem might be. "Operasjonen er ikke tillatt" is norwegian for something like "Operation not permitted". [plustek] Checking for 0x04b8-0x011d [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011d, attach=0x405cd184 [plustek] Found device at >libusb:002:003< [sanei_usb] sanei_usb_open: trying to open device `libusb:002:003' USB error: could not set config 1: Operasjonen er ikke tillatt [sanei_usb] sanei_usb_open: libusb complained: could not set config 1: Operasjonen er ikke tillatt [sanei_usb] Make sure you run as root or set appropriate permissions [plustek] open failed: -1 [plustek] sane_get_devices (0xbfffe848, 0) [plustek] sane_exit > > chevrolet:~# sane-find-scanner > > > > # No SCSI scanners found. If you expected something different, make > > sure that > > # you have loaded a SCSI driver for your SCSI adapter. > > > > found USB scanner (vendor=0x0731, product=0x0528) at libusb:001:002 > > found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON > > Scanner]) at libusb:002:003 > > What kind of device is the first one? The first device is a usb-cradle for my Sony Ericsson P800 phone... Thanks for your patience :) Best regards, Stian
[sane-devel] Linux 2.5.62
Hi, On Tue, Feb 25, 2003 at 01:57:08PM +0100, Stian Jordet wrote: > > > I'm using 2.4.21-pre3, which is working very good. > > > But I can try pre4. > > > > If it works, no need to upgrade. > > You said that the 2.5.62 and 2.4.21-pre4 driver were mostly the same, so > I thought I could narrow it down. Oh well. There is not much change between pre3 and pre4. The only change that might influence the detection of your scanner is the "endpoint detection cleanup". See http://www.meier-geinitz.de/kernel/ for which patch went in which version. But I would be surprised if this is a problem. I keep 2.4-latest and 2.5-latest as similar as possible. The differences are related to API changes and new features in 2.5. > I get the same issues with libusb: > > [plustek] Checking for 0x04b8-0x010f > [plustek] Checking for 0x04b8-0x011d > [plustek] Found device at >libusb:002:003< > [plustek] open failed: -1 > [plustek] sane_get_devices (0xbfffe868, 0) > [plustek] sane_exit Well, then I guess it's something else (not related to the kernel scanner driver). Please enable SANE_DEBUG_SANEI_USB=255 also. > chevrolet:~# sane-find-scanner > > # No SCSI scanners found. If you expected something different, make > sure that > # you have loaded a SCSI driver for your SCSI adapter. > > found USB scanner (vendor=0x0731, product=0x0528) at libusb:001:002 > found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON > Scanner]) at libusb:002:003 What kind of device is the first one? > Hmm. Weird, since everything works perfect in 2.4.x. But quite a lot of > other thing works better with 2.5.63 now, so I prefer to use that... If my xserver ran on 2.5, I would use it also for the development machine. Bye, Henning
[sane-devel] Linux 2.5.62
tir, 2003-02-25 kl. 12:24 skrev Henning Meier-Geinitz: > 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? Nope, exact same error :( > > 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. I do not use devfs, but I do use Dynamic minors. I'll try to compile without it. > 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 will... > > I'm using 2.4.21-pre3, which is working very good. > > But I can try pre4. > > If it works, no need to upgrade. You said that the 2.5.62 and 2.4.21-pre4 driver were mostly the same, so I thought I could narrow it down. Oh well. > > 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. I get the same issues with libusb: [plustek] Checking for 0x04b8-0x010f [plustek] Checking for 0x04b8-0x011d [plustek] Found device at >libusb:002:003< [plustek] open failed: -1 [plustek] sane_get_devices (0xbfffe868, 0) [plustek] sane_exit chevrolet:~# sane-find-scanner # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. found USB scanner (vendor=0x0731, product=0x0528) at libusb:001:002 found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON Scanner]) at libusb:002:003 Hmm. Weird, since everything works perfect in 2.4.x. But quite a lot of other thing works better with 2.5.63 now, so I prefer to use that... best regards, Stian Jordet
[sane-devel] Linux 2.5.62
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
[sane-devel] Linux 2.5.62
man, 2003-02-24 kl. 20:50 skrev Henning Meier-Geinitz: > Hi, > > On Mon, Feb 24, 2003 at 08:05:16PM +0100, Stian Jordet wrote: > > I have lately been using kernel 2.5.x on my computer. Because of several > > reasons I like that better. But, I cannot seem to get the scanner to > > work. It works fine with 2.4.x. It's a Epson Perfection 1260, and I have > > tried both the Epson Kowa backend and the plustek backend (which both > > works fine in 2.4.x). When using SANE_DEBUG_EPSON=255 I get that it > > can't open the device. But when loading the scanner module, it seems to > > find my scanner. And, as I said, the exact same setup works with 2.4.x, > > and my usb-printer works with 2.5.x. So my question is, are there any > > known issues with scanning with 2.5.x kernels? > > The kernel scanner driver in 2.5.* is usually more bleeding edge. > Currently 2.5.62 has (almost) the same driver as 2.4.21-pre4. Both > work for me, but 2.5.* gets little testing (from me). But I haven't > gotten any bug reports either. > > > [epson] sane_init, >usb /dev/usb/scanner0< > > [epson] attach(usb /dev/usb/scanner0) > > [epson] SANE Epson Backend v1.4.0ek - 2002-7-22 > > [epson] attach(usb /dev/usb/scanner0) > > [epson] attach: opening usb /dev/usb/scanner0 > > [epson] sane_start: /dev/usb/scanner0 open (USB) failed: No such device > > [epson] sane_get_devices() > > you are trying to open /dev/usb/scanner0. > > > [plustek] usbDev_open(/dev/usb/scanner0,) > > Same here. > > > >From my dmesg: > > drivers/usb/image/scanner.c: USB scanner device (0x04b8/0x011d) now > > attached to scanner1 > > But it seems to be connecte to /dev/usb/scanner1. > > Fix the config files (plustek.conf/epson.conf). > I have tried both. You have any idea why it want scanner1 in 2.5.x and scanner0 in 2.4.x? I'm using 2.4.21-pre3, which is working very good. But I can try pre4. Hmm. Thanks anyway. Since there is no known issues, it's just my setup, I guess. Regards, Stian
[sane-devel] Linux 2.5.62
Hi, On Mon, Feb 24, 2003 at 08:05:16PM +0100, Stian Jordet wrote: > I have lately been using kernel 2.5.x on my computer. Because of several > reasons I like that better. But, I cannot seem to get the scanner to > work. It works fine with 2.4.x. It's a Epson Perfection 1260, and I have > tried both the Epson Kowa backend and the plustek backend (which both > works fine in 2.4.x). When using SANE_DEBUG_EPSON=255 I get that it > can't open the device. But when loading the scanner module, it seems to > find my scanner. And, as I said, the exact same setup works with 2.4.x, > and my usb-printer works with 2.5.x. So my question is, are there any > known issues with scanning with 2.5.x kernels? The kernel scanner driver in 2.5.* is usually more bleeding edge. Currently 2.5.62 has (almost) the same driver as 2.4.21-pre4. Both work for me, but 2.5.* gets little testing (from me). But I haven't gotten any bug reports either. > [epson] sane_init, >usb /dev/usb/scanner0< > [epson] attach(usb /dev/usb/scanner0) > [epson] SANE Epson Backend v1.4.0ek - 2002-7-22 > [epson] attach(usb /dev/usb/scanner0) > [epson] attach: opening usb /dev/usb/scanner0 > [epson] sane_start: /dev/usb/scanner0 open (USB) failed: No such device > [epson] sane_get_devices() you are trying to open /dev/usb/scanner0. > [plustek] usbDev_open(/dev/usb/scanner0,) Same here. > >From my dmesg: > drivers/usb/image/scanner.c: USB scanner device (0x04b8/0x011d) now > attached to scanner1 But it seems to be connecte to /dev/usb/scanner1. Fix the config files (plustek.conf/epson.conf). Bye, Henning
[sane-devel] Linux 2.5.62
Hello, I have lately been using kernel 2.5.x on my computer. Because of several reasons I like that better. But, I cannot seem to get the scanner to work. It works fine with 2.4.x. It's a Epson Perfection 1260, and I have tried both the Epson Kowa backend and the plustek backend (which both works fine in 2.4.x). When using SANE_DEBUG_EPSON=255 I get that it can't open the device. But when loading the scanner module, it seems to find my scanner. And, as I said, the exact same setup works with 2.4.x, and my usb-printer works with 2.5.x. So my question is, are there any known issues with scanning with 2.5.x kernels? Best regards, Stian Jordet [epson] sane_init, >usb /dev/usb/scanner0< [epson] attach(usb /dev/usb/scanner0) [epson] SANE Epson Backend v1.4.0ek - 2002-7-22 [epson] attach(usb /dev/usb/scanner0) [epson] attach: opening usb /dev/usb/scanner0 [epson] sane_start: /dev/usb/scanner0 open (USB) failed: No such device [epson] sane_get_devices() [plustek] gray Gamma : 1.00 [plustek] - [plustek] drvopen() [plustek] usbDev_open(/dev/usb/scanner0,) [plustek] open failed: -1 [plustek] sane_get_devices (0xbfffe868, 0) [plustek] sane_exit >From my dmesg: drivers/usb/image/scanner.c: USB scanner device (0x04b8/0x011d) now attached to scanner1
