[sane-devel] sane, 2.6 + hotplug scripts

Oliver Schwartz Oliver.Schwartz@gmx.de
Fri, 23 Apr 2004 18:05:24 +0200

Hash: SHA1


On Friday 23 April 2004 14.38, Jago Pearce wrote:
> - recompiled sane with libusb support
> - added hotplugging support to the kernel
> - copied tools/hotplug/libsane.usermap and libusbscanner to
> /etc/hotplug/usb/
> - verified my scanner (acer640U) is in libsane.usermap
> - ran /etc/init.d/hotplug restart
> With the presence of libsane.usermap in /etc/hotplug/usb/ that
> start up scripts go crazy
> outputting stff to the screen. /proc/bus/usb/ permissions remain as
> root.

the hotplug handling changed significantly from kernel 2.4 to 2.6, if=20
I read the documentation correctly it even changed from 2.5 to 2.6.=20
If you upgrade your kernel to 2.6 you should definitely upgrade the=20
hotplug package as well.

I've seen strange things happen on my machine as well with old hotplug=20
scripts (Suse 8.2, upgraded to Suse kernel 2.6.5,=20
hotplug-2002-08-26). It seems that the hotplug script re-detects the=20
scanner after each scan. This sometimes causes the frontend to hang=20
when starting a new scan. I have a feeling that this also accounts=20
for some of the other problems people have using SANE on 2.6.

> The scripts are exactly as they are in the distribution tarballs.

I'm not sure if the scripts can be used with newer versions of=20
hotplug, but they should be easily adoptable. I haven't tried it=20
here, though.

Another workaround may be to completely disable hotplugging for the=20
time being, but that has a number of other drawbacks.

=2D -Oliver
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)