Hi, On Mon, May 06, 2002 at 06:18:20PM +0200, Edvard Rognlid wrote: > The newst rpm for redhat 7.2 I could find vas for version 1.0.5-4.
I don't know if you can just use the RPMs of other distributions (e.g. Mandrake) from http://www.mostang.com/sane/source.html . Maybe someone with knowledge about RedHat can comment on this. > And > since I'm a newbee to Linux I don't know how to install for other type of > files than RPM's. Thats the reason I use 1.0.5-4. Can you give me som > instructions on how to intall 1.0.7? There should be some information about compiling and installing software that's not in .tar.gz format in the documentation of your distribution. Basicly, unpack sane-backends-1.0.7.tar.gz e.g. in /tmp, and read the README file. > >Nothing like the above mentioned lines about "saned"? Then saned isn't > >running (or segfaults right after the start). > When trying xsane for win98 when xinetd is runing I get this in > var/messages: > May 6 17:54:29 barcelona saned[4168]: access by edvard@radich accepted > May 6 17:54:30 barcelona saned[4168]: exiting Looks ok in principle. However, I wonder why the modprobe message from below doesn't occur here. > When trying xsane using saned -d5 I get this in var/messages: > May 6 18:02:01 barcelona saned[4194]: access by edvard@radich accepted > May 6 18:02:01 barcelona modprobe: modprobe: Can't locate module > char-major-81 char-major-81 is video for linux, that's ok. You can disable v4l in /etc/sane.d/dll.conf if you like to stop this message. > May 6 18:02:01 barcelona last message repeated 3 times > May 6 18:02:14 barcelona saned[4194]: exiting > > >Try running > > > >SANE_DEBUG_NET=255 scanimage -L > > > >This should print some info about what the net backend is doing. > > Just: > [root@barcelona log]# SANE_DEBUG_NET=255 scanimage -L > device `microtek:/dev/sge' is a Microtek ScanMaker E3 flatbed scanner > device `microtek:/dev/sg4' is a Microtek ScanMaker E3 flatbed scanner > [root@barcelona log]# Something is badly wrong here. Maybe RedHat has disabled debug messages? You should get something like this: [sanei_debug] Setting debug level of net to 255. [net] sane_init: SANE net backend version 1.0.3 from sane-backends-1.0.5 [net] add_device: adding backend localhost [net] add_device: backend localhost added [net] sane_get_devices: local_only = 0 [net] sane_get_devices: finished Does "SANE_DEBUG_DLL=255 scanimage -L" print something useful? If it doesn't, RedHat has modified the SANE package. In this case, I can't help you with this package, you should ask RedHat instead. > At http://www.penguin-breeder.org/Penguin-Breedersane.htm I found the > folowing: > "Sometimes, saned starts only when debugging is enabled. To be able to use > saned with debugging enabled from inetd or xinetd, you have to use a little > wrapper. That's a dirty trick to avoid one of the bugs mentioned by me. Even if you are hit by this bug, this work-around may not work. It just changes the timing. > This is also handy, if you need debug output from the backend and > you don't want to start saned by hand all the time... rename saned to > something like saned.bin and create a shell script like this > #!/bin/sh > SANE_DEBUG_MUSTEK=128 > export SANE_DEBUG_MUSTEK You should use MICROTEK instead of MUSTEK here. > cd /tmp > exec $0.bin 2> saned.$$.stderr | tee saned.$$.stdout If I remember correctly, this didn't work for me. I simply used something like /usr/sbin/saned.bin 2>/tmp/saned.err > This will make two files with stdout and stderr from the last session in > /tmp. The debug information will be in saned.*.stderr. " > > This might my problem, or? If thats the case maby a new version will help. I'm pretty sure that a new version will fix your problem. Bye, Henning
