[sane-devel] HP 4600 vs. Mustek_usb2
On Mon, 2008-12-08 at 22:50 -0500, Triften Chmil wrote: The output of sane-find-scanner -v -v on http://www.sane-project.org/unsupported/hp-scanjet-4600.html says that it may contain an SQ113 chip, which is the same as in the Mustek_usb2 supported scanners, so I've started comparing the logs and playback I've got to the commands used by Mustek_usb2. Things are lining up well so far (at least the basic functions like openchip, closechip and the register reading). Has anyone gone and tested scanning using the mustek2 backend as is? If not, how can I go about forcing the use of a backend on an unsupported scanner? It seems like other backends have config files to change the vendor and product IDs of support scanners, but the man page mustek_usb2 doesn't mention this. Thanks, Triften Hello, Triften! A little while ago I encountered the same problem with mustek_usb2 backend. My scanner is Mustek BearPaw 2448CU Pro, but backend currently only supports 2448TA Pro. I can't say for sure, but probably this backend was written in a bit of a hurry, and it's unfinished, since it only works with one scanner and doesn't support adding new scanners via config files. Just as Allan pointed out, the only way to add your scanner backend is inside sources. About a month ago Jack McGill from this mailing list offered me help with doing so. Here I quote his letter: Hello Igor, Take a look at these pages: http://www.sane-project.org/unsupported/mustek-bearpaw-2448-cu-pro.html and http://www.meier-geinitz.de/sane/mustek_usb2-backend/ It looks like this page could possibly be added to the mustek_usb2 backend. This backend supports the BearPaw 2448 TA Pro, which is reported to be similar to the 2448 CU Pro. Browsing through the backend source code, it looks like in the file mustek_usb2_asic.c at about line 3521, there are entries for the product ID and Vendor ID's. and in the file mustek_usb2.c, line 124 there are some settings for the scanner. So, you might want to try changing line 146 of mustek_usb2.c from SANE_FALSE to SANE_TRUE (is this a CIS scanner?) and change line 3521 of mustek_usb2_asic.c from 0x0409 to 0x0408 and ./configure, make, make install at the command line. I have to warn you that I am not a programmer and I am new to SANE, so don't blame me if it doesn't work ;-). -- Jack McGill jmcgill85258 at yahoo.com Of course, you have to put your scanner's vendor and product id there, not mine. Remember, you need to remove your current sane and especially its backends from system, then recompile and reinstall from sources. Beware though, that when you finally get your scanner detected, it doesn't yet guarantee that it will work as expected. Surely, try it, but keep your hand on scanner plug just in case you hear something unusual. You may try looking up our old discussion Can't seem to find config files in archives, it's not very long. Maybe you'll find something useful there too. Myself? Well, my scanner is now identified, but when I try to scan anything, output is pretty insane, also scanner sometimes starts bashing it's head against the wall ;) So more work will be necessary to get it up and running. When I'm done with my stuff right now, probably I'll get to it, I really hope there'll be some time. For now I'm just reading mailing list with hope of some news on my scanner. So, good luck with your HP ScanJet 4600! If you'll ever have any questions, feel free to ask. -- Igor G Novikov septagramm at gmail.com
[sane-devel] no devices available
George Herzog gaherzog at gmail.com writes: I recently did a urpmi.update and now I cannot use my epson perfection 1640su scanner. I have only one of each: libsane1, sane backends, and xsane installed. The scanner was always detected and worked well before the update. any assistance will be very much appreciated. Does sane-find-scanner list the device? If so, what does scanimage -L say? Does trying this as a regular user or as root make a difference? SCSI or USB? If USB, does lsusb list it? If SCSI, was it powered on when you booted? Does it show in the dmesg output? Distribution? Version? Architecture? Hope that helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
[sane-devel] Perl Bindings
2008/12/10 m. allan noah kitno455 at gmail.com: No, they are not floats, they are fixed. It is possible to manipulate them without UNFIXing them. The fujitsu backend has produced these type of warnings for years, even on simple things like --resolution=100, and I never could figure out why, until now... Of course, you are right that they are fixed - I should have expressed myself more precisely - and whilst it may be possible to manipulate them without unfixing them, I don't see why the -1 is necessary: val = pos + window_val[index] - 1 If your patch fixed the issue, I wonder if it was just a fluke, that your *info was 0 on that run? It seems unlikely - but... Regards Jeff
[sane-devel] genius scanner
?Hi I have a genius colorpage vivid 4xe scanner which used to work well with suse 10, since installing suse 11.0 I have not been able to install the scanner using yast , the scanner is recognised but will not work, if I try to edit it just hangs. Some messages below. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? scanimage: open of device gt68xx:libusb:004:055 failed: Invalid argument sane-find-scanner ? # No SCSI scanners found. If you expected something different, make sure that ? # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x0458, product=0x201a [600DPI USB Scanner], chip=GT-6816) at libusb:004:055 ? # Your USB scanner was (probably) detected. It may or may not be supported by ? # SANE. Try scanimage -L and read the backend's manpage. scanimage -L device `gt68xx:libusb:004:117' is a Genius Colorpage Vivid4xe flatbed scanner Tell me what to do next!! ? Thanks Peter.
[sane-devel] epjitsu (Fujitsu fi-60f) on fedora 8
Hello, I'm trying to connect a Fujitsu fi-60f to a system running fedora 8. I got to the point (I think..) where all of the pieces are in the right place but I can't get it to work. Any help would be appreciated. Here are the vitals: $ /sbin/lsusb Bus 001 Device 003: ID 04c5:10c7 Fujitsu, Ltd --- $ scanimage -V scanimage (sane-backends) 1.0.19; backend version 1.0.19 --- $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04c5, product=0x10c7) at libusb:001:003 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. --- $ SANE_DEBUG_EPJITSU=15 scanimage -L 2f60.log No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). $ cat f60.log [sanei_debug] Setting debug level of epjitsu to 15. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.10, from sane-backends 1.0.19 [epjitsu] sane_init: reading config file epjitsu.conf [epjitsu] sane_init: firmware '/usr/local/share/sane/epjitsu/60f_0A06.nal' [epjitsu] sane_init: looking for 'usb 0x04c5 0x10c7' [epjitsu] attach_one: start 'libusb:001:003' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: could not open device: 11 [epjitsu] connect_fd: finish [epjitsu] sane_close: start [epjitsu] teardown_buffers: start [epjitsu] teardown_buffers: finish [epjitsu] sane_close: finish [epjitsu] sane_init: firmware '/usr/local/share/sane/epjitsu/300_0A00.nal' [epjitsu] sane_init: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_init: found 0 scanner(s) [epjitsu] sane_init: finish [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: finish [epjitsu] sane_exit: start [epjitsu] sane_exit: finish --- Now I gathered that status 11 is SANE_STATUS_ACCESS_DENIED so I tried the same command using sudo but got the same response and the log file was completely empty...:confused: $ SANE_DEBUG_EPJITSU=15 sudo scanimage -L 2f60.log No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). $ cat f60.log $ Again, any help would be greatly appreciated. Ronen -- View this message in context: http://www.nabble.com/epjitsu-%28Fujitsu-fi-60f%29-on-fedora-8-tp20940308p20940308.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] epjitsu (Fujitsu fi-60f) on fedora 8
any chance you have your old copy of sane still installed? I bet that is getting used instead of your /usr/local copy when you are logged in as root allan On Wed, Dec 10, 2008 at 12:44 PM, ronenk rkahana at ztarmobile.com wrote: Hello, I'm trying to connect a Fujitsu fi-60f to a system running fedora 8. I got to the point (I think..) where all of the pieces are in the right place but I can't get it to work. Any help would be appreciated. Here are the vitals: $ /sbin/lsusb Bus 001 Device 003: ID 04c5:10c7 Fujitsu, Ltd --- $ scanimage -V scanimage (sane-backends) 1.0.19; backend version 1.0.19 --- $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04c5, product=0x10c7) at libusb:001:003 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. --- $ SANE_DEBUG_EPJITSU=15 scanimage -L 2f60.log No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). $ cat f60.log [sanei_debug] Setting debug level of epjitsu to 15. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.10, from sane-backends 1.0.19 [epjitsu] sane_init: reading config file epjitsu.conf [epjitsu] sane_init: firmware '/usr/local/share/sane/epjitsu/60f_0A06.nal' [epjitsu] sane_init: looking for 'usb 0x04c5 0x10c7' [epjitsu] attach_one: start 'libusb:001:003' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: could not open device: 11 [epjitsu] connect_fd: finish [epjitsu] sane_close: start [epjitsu] teardown_buffers: start [epjitsu] teardown_buffers: finish [epjitsu] sane_close: finish [epjitsu] sane_init: firmware '/usr/local/share/sane/epjitsu/300_0A00.nal' [epjitsu] sane_init: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_init: found 0 scanner(s) [epjitsu] sane_init: finish [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: finish [epjitsu] sane_exit: start [epjitsu] sane_exit: finish --- Now I gathered that status 11 is SANE_STATUS_ACCESS_DENIED so I tried the same command using sudo but got the same response and the log file was completely empty...:confused: $ SANE_DEBUG_EPJITSU=15 sudo scanimage -L 2f60.log No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). $ cat f60.log $ Again, any help would be greatly appreciated. Ronen -- View this message in context: http://www.nabble.com/epjitsu-%28Fujitsu-fi-60f%29-on-fedora-8-tp20940308p20940308.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] epjitsu (Fujitsu fi-60f) on fedora 8
try adding SANE_DEBUG_DLL=5 to your logging, and see if the dll backend is failing to look in /usr/local/lib for the backends. allan On Wed, Dec 10, 2008 at 1:34 PM, ronenk rkahana at ztarmobile.com wrote: Allan, Thanks for the quick response. I removed the SANE version that came with the distro (1.0.18) before building 1.0.19. YUM does not show anything installed and find shows only files in the /usr/local dir $ sudo yum list *sane* Available Packages libsane-hpaio.i386 2.8.2-1.fc8 updates-newkey python-imaging-sane.i386 1.1.6-4.fc8fedora sane-backends.i386 1.0.18-17.fc8 fedora sane-backends-devel.i386 1.0.18-17.fc8 fedora sane-backends-libs.i386 1.0.18-17.fc8 fedora sane-frontends.i386 1.0.14-3.fc7 fedora xsane.i386 0.994-4.fc8fedora xsane-gimp.i386 0.994-4.fc8fedora $ sudo find / -name *sane* /usr/local/sbin/saned /usr/local/lib/libsane.so.1.0.19 /usr/local/lib/sane /usr/local/lib/sane/libsane-umax1220u.la /usr/local/lib/sane/libsane-dll.la /usr/local/lib/sane/libsane-s9036.so.1 /usr/local/lib/sane/libsane-dell1600n_net.so.1.0.19 /usr/local/lib/sane/libsane-stv680.so /usr/local/lib/sane/libsane-matsushita.so /usr/local/lib/sane/libsane-dll.so.1 /usr/local/lib/sane/libsane-sm3840.so.1.0.19 /usr/local/lib/sane/libsane-teco2.so /usr/local/lib/sane/libsane-lexmark.la /usr/local/lib/sane/libsane-test.so.1.0.19 /usr/local/lib/sane/libsane-hp3900.so.1.0.19 /usr/local/lib/sane/libsane-sceptre.la /usr/local/lib/sane/libsane-avision.so /usr/local/lib/sane/libsane-hp5400.so /usr/local/lib/sane/libsane-test.so.1 /usr/local/lib/sane/libsane-plustek_pp.so.1.0.19 /usr/local/lib/sane/libsane-as6e.la /usr/local/lib/sane/libsane-epson2.so.1.0.19 /usr/local/lib/sane/libsane-test.so /usr/local/lib/sane/libsane-umax1220u.so /usr/local/lib/sane/libsane-microtek.la /usr/local/lib/sane/libsane-avision.so.1 /usr/local/lib/sane/libsane-hp4200.la /usr/local/lib/sane/libsane-hp5590.la /usr/local/lib/sane/libsane-hs2p.so.1.0.19 /usr/local/lib/sane/libsane-coolscan2.so.1.0.19 /usr/local/lib/sane/libsane-dc240.la /usr/local/lib/sane/libsane-snapscan.la /usr/local/lib/sane/libsane-microtek.so.1 /usr/local/lib/sane/libsane-bh.so /usr/local/lib/sane/libsane-leo.so /usr/local/lib/sane/libsane-net.so.1 /usr/local/lib/sane/libsane-hp4200.so.1.0.19 /usr/local/lib/sane/libsane-apple.so.1.0.19 /usr/local/lib/sane/libsane-hp3900.so.1 /usr/local/lib/sane/libsane-microtek2.so /usr/local/lib/sane/libsane-dc240.so.1.0.19 /usr/local/lib/sane/libsane-tamarack.so /usr/local/lib/sane/libsane-cardscan.la /usr/local/lib/sane/libsane-microtek2.so.1 /usr/local/lib/sane/libsane-stv680.so.1 /usr/local/lib/sane/libsane-gt68xx.so.1 /usr/local/lib/sane/libsane-teco1.so.1.0.19 /usr/local/lib/sane/libsane-teco1.la /usr/local/lib/sane/libsane-ricoh.so /usr/local/lib/sane/libsane-umax_pp.so /usr/local/lib/sane/libsane-ricoh.so.1.0.19 /usr/local/lib/sane/libsane-plustek.la /usr/local/lib/sane/libsane-leo.so.1 /usr/local/lib/sane/libsane-abaton.la /usr/local/lib/sane/libsane-ma1509.so.1.0.19 /usr/local/lib/sane/libsane-pixma.la /usr/local/lib/sane/libsane-epson.so /usr/local/lib/sane/libsane-niash.so /usr/local/lib/sane/libsane-sceptre.so /usr/local/lib/sane/libsane-plustek.so /usr/local/lib/sane/libsane-sp15c.so.1.0.19 /usr/local/lib/sane/libsane-umax.so.1 /usr/local/lib/sane/libsane-nec.so /usr/local/lib/sane/libsane-dell1600n_net.so /usr/local/lib/sane/libsane-hp5400.la /usr/local/lib/sane/libsane-abaton.so.1 /usr/local/lib/sane/libsane-coolscan2.so /usr/local/lib/sane/libsane-genesys.la /usr/local/lib/sane/libsane-ma1509.la /usr/local/lib/sane/libsane-epson2.so.1 /usr/local/lib/sane/libsane-dll.so /usr/local/lib/sane/libsane-dc210.so.1.0.19 /usr/local/lib/sane/libsane-dmc.so /usr/local/lib/sane/libsane-umax.la /usr/local/lib/sane/libsane-coolscan.so.1 /usr/local/lib/sane/libsane-artec_eplus48u.so /usr/local/lib/sane/libsane-hpljm1005.so /usr/local/lib/sane/libsane-stv680.la /usr/local/lib/sane/libsane-mustek_usb.la /usr/local/lib/sane/libsane-leo.la /usr/local/lib/sane/libsane-artec.so.1.0.19 /usr/local/lib/sane/libsane-net.so.1.0.19 /usr/local/lib/sane/libsane-hp5590.so /usr/local/lib/sane/libsane-stv680.so.1.0.19 /usr/local/lib/sane/libsane-ma1509.so.1 /usr/local/lib/sane/libsane-apple.la /usr/local/lib/sane/libsane-dll.so.1.0.19 /usr/local/lib/sane/libsane-qcam.so /usr/local/lib/sane/libsane-epjitsu.la /usr/local/lib/sane/libsane-dc240.so.1 /usr/local/lib/sane/libsane-canon.so.1 /usr/local/lib/sane/libsane-u12.so.1.0.19 /usr/local/lib/sane/libsane-abaton.so /usr/local/lib/sane/libsane-sceptre.so.1.0.19 /usr/local/lib/sane/libsane-fujitsu.so.1.0.19 /usr/local/lib/sane/libsane-st400.so.1.0.19
[sane-devel] epjitsu (Fujitsu fi-60f) on fedora 8
On Wed, Dec 10, 2008 at 2:44 PM, ronenk rkahana at ztarmobile.com wrote: Mea culpa - the fireware file was not placed in the correct directory. Once the file was placed in /usr/local/share/sane/epjitsu I was able to scan using sudo. Sorry for the hassle. How do I get non root users to be able to access the scanner? on your OS, you probably need to make a udev rule somewhere in /etc/udev/rules.d. I think the file provided by fedora was 60-libsane.rules. you might need to extract that file from the original rpm, and add this machine's vid and pid allan Thanks, Ronen -- View this message in context: http://www.nabble.com/epjitsu-%28Fujitsu-fi-60f%29-on-fedora-8-tp20940308p20942714.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] epjitsu (Fujitsu fi-60f) on fedora 8
Can't thank you enough Allan. I took the libsane.rules from the source tar (.../sane-backends-1.0.19/tools/udev) and renamed it to /etc/udev/rules.d/60-libsane.rules $ run+=/etc/udev/rules.d/60-libsane.rules created a user group called 'scanner' and added my user to the group. it works!:clap: m. allan noah-3 wrote: On Wed, Dec 10, 2008 at 2:44 PM, ronenk rkahana at ztarmobile.com wrote: Mea culpa - the fireware file was not placed in the correct directory. Once the file was placed in /usr/local/share/sane/epjitsu I was able to scan using sudo. Sorry for the hassle. How do I get non root users to be able to access the scanner? on your OS, you probably need to make a udev rule somewhere in /etc/udev/rules.d. I think the file provided by fedora was 60-libsane.rules. you might need to extract that file from the original rpm, and add this machine's vid and pid allan Thanks, Ronen -- View this message in context: http://www.nabble.com/epjitsu-%28Fujitsu-fi-60f%29-on-fedora-8-tp20940308p20942714.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- View this message in context: http://www.nabble.com/epjitsu-%28Fujitsu-fi-60f%29-on-fedora-8-tp20940308p20943434.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] Canon Pixma MP970 scanner: Connection refused]
hello Brian, could you please do the following: set SANE_DEBUG_PIXMA to 13 in bash that is export SANE_DEBUG_PIXMA=13 or in tcsh setenv SANE_DEBUG_PIXMA=13 and then a scanimage and mail me the logfile? I want to have a look at the logfileas as this really looks funny. It would be good if you could also mail me a tcp packet dump (wireshark, set port 8612 as option when you start logging). It surprises me that the correct address is detected: [pixma] Found scanner at ip address: 192.168.1.252 but then we start sending to 127.0.0.1. This suggest an error in the reverse mapping of the scanners address. What does nslookup 192.168.1.252 return? Does that return localhost? Does /etc/hosts have the scanners address as localhost? best regards, Louis On Sat, 2008-12-06 at 14:37 +0100, Brian Rosenberger wrote: Hi Nicolas, I am using a Canon Pixma MP970 scanner with your latest additions to sane-backends. It is working with USB like a charm, but using network it seems that it always defaults to 127.0.0.1 (localhost) instead of using the scanners ip (which is 192.168.1.252). I tried to set ip in pixma.conf without success. Do you have any ideas? Thanks Brian LOG: brian at bru02:~$ scanimage -L [sanei_debug] Setting debug level of pixma to 255. [pixma] pixma version 0.15.0 [pixma] pixma_collect_devices() found Canon Pixma MP970 at libusb:002:002 [pixma] sanei_bjnp_find_devices: [pixma] Select returned, time left 0.996000 [pixma] Discover response: [pixma] :42 4a 4e 50 82 01 00 00 00 00 00 00 00 00 00 10 [pixma] 0010:00 01 08 00 06 04 00 00 85 cb a6 8d c0 a8 01 fc [pixma] Found scanner at ip address: 192.168.1.252 [pixma] Get scanner identity [pixma] :42 4a 4e 50 02 30 00 00 00 00 00 00 00 00 00 00 [pixma] Sending UDP command to 127.0.0.1:8612 [pixma] udp_command: no data received (recv): Connection refused[pixma] udp_command: no data received (recv): Connection refused[pixma] udp_command: no data received (recv): Connection refused[pixma] Cannot read scanner make model: bjnp://localhost:8612 [pixma] pixma_find_scanners() found 1 devices device `pixma:04A91726_20CCB5' is a CANON Canon Pixma MP970 multi-function peripheral
No subject
-=
---
# Disable all ENV{DEVTYPE} lines because we (Suse/Novell) do not need the=
m.
-=
---
Kind Regards
Johannes Meixner
--=20
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex
--8323584-400571133-1231494495=:8042--
No subject
-no-undefined declare that a library does not refer to external symbols I fail to see how that has anything to do with the library version. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
No subject
, then you don't need to compile anything from source just install the correct packages and it should work. If you really run Fedora 9, I suggest to remove all the stuff compiled from source first. If you did that already you should not find any sane related thing anywhere under /usr/local. Then installing the following packages should give you a running sane: sane-backends-1.0.19-10.fc9.i386.rpm sane-backends-devel-1.0.19-10.fc9.i386.rpm sane-backends-libs-1.0.19-10.fc9.i386.rpm If rpm complains that one or more of the packages are already installed, you can still reinstall the package by doing 'rpm -Uvh --replacefiles --replacepkgs ...' Hope that helps, Simon 1) Entered in sane source and executed make uninstall that removed /usr/local/bin 2nd typed the command ./configure /usr/etc --disable-locking 3rd make 4th typed the command rm -rf /etc/sane.d 5th make install RESULT: if i type the command `./configure --prefix=3D/usr --sysconfdir=3D/etc --disable-locking` bash: checking: command not found if I type ./configure /usr/etc --disable-locking This error comes configure: WARNING: you should use --build, --host, --target configure: WARNING: invalid host type: /usr/etc checking build system type... Invalid configuration `/usr/etc': machine `/usr/etc' not recognized configure: error: /bin/sh ./config.sub /usr/etc failed So please let me know is --disable-locking some argument ? Thanks Date: Thu, 5 Feb 2009 10:16:24 -0500 Subject: Re: [sane-devel] Which HP-AIO Devices are supported by SANE From: kitno455 at gmail.com To: rohitsharma36 at hotmail.com run the first command, without the quotes around it. allan On Thu, Feb 5, 2009 at 10:13 AM, rohit bal rohitsharma36 at hotmail.com wrote: hi Allan, if i type the command `./configure --prefix=3D/usr --sysconfdir=3D/e= tc --disable-locking` bash: checking: command not found if I type ./configure /usr/etc --disable-locking This error comes configure: WARNING: you should use --build, --host, --target configure: WARNING: invalid host type: /usr/etc checking build system type... Invalid configuration `/usr/etc': machine `/usr/etc' not recognized configure: error: /bin/sh ./config.sub /usr/etc failed So please let me know is --disable-locking some argument ? Regards, Roh Date: Thu, 5 Feb 2009 09:59:59 -0500 Subject: Re: [sane-devel] Which HP-AIO Devices are supported by SAN= E From: kitno455 at gmail.com To: rohitsharma36 at hotmail.com WHY CAN YOU NOT RUN THE COMMANDS AS I SENT THEM TO YOU? allan On Thu, Feb 5, 2009 at 9:59 AM, rohit bal rohitsharma36 at hotmail.co= m wrote: step 2 gives error ./configure /usr/etc --disable-locking configure: WARNING: you should use --build, --host, --target configure: WARNING: invalid host type: /usr/etc checking build system type... Invalid configuration `/usr/etc': machine `/usr/etc' not recognized configure: error: /bin/sh ./config.sub /usr/etc failed Date: Thu, 5 Feb 2009 09:55:22 -0500 Subject: Re: [sane-devel] Which HP-AIO Devices are supported by SANE From: kitno455 at gmail.com To: rohitsharma36 at hotmail.com I said all. allan On Thu, Feb 5, 2009 at 9:53 AM, rohit bal rohitsharma36 at hotmail.com wrote: shall I follow all steps 1 to 5 or only 3 to 5 Date: Thu, 5 Feb 2009 09:50:11 -0500 Subject: Re: [sane-devel] Which HP-AIO Devices are supported = by SANE From: kitno455 at gmail.com To: rohitsharma36 at hotmail.com On Thu, Feb 5, 2009 at 9:47 AM, rohit bal rohitsharma36 at hotmail.com wrote: Hi Allan, The steps I followed were 1) Entered in sane source and executed 'make uninstall' tha= t removed /usr/local/bin 2nd typed the command ./configure /usr/etc --disable-lockin= g ^= ^ this above is not what i told you to type. try all steps agai= n. 3rd make 4th typed the command rm -rf /etc/sane.d 5th make install After that I saw there is a copy of sane folder in /usr/local/lib in /usr/local/bin I have only 3 executables(scanimage,gamma4scanimage,sane-find-scanner,san= e-config file). and Which scanimage stills shows old path /usr/local/bin Thanks Date: Thu, 5 Feb 2009 09:29:14 -0500 Subject: Re: [sane-devel] Which HP-AIO Devices are support= ed by SANE From: kitno455 at gmail.com To: rohitsharma36 at hotmail.com CC: sane-devel at lists.alioth.debian.org 1. cd into your source and run 'make uninstall'. that shou= ld remove everything sane related from /usr/local 2. `./configure --prefix=3D/usr --sysconfdir=3D/etc --disable-locking` 3. make 5. make install allan On Thu, Feb 5,
