[sane-devel] Problem in setting up Xsane (problem half solved)
Hi Henning, Henning Meier-Geinitz wrote: > - snip - > Does sane-find-scanner find your scanner? Does it find it if you run > as user? If it only works as root, you must set up permissions for the > SCSI devices. See man sane-scsi and search for "permission". I hesitate to proceed as "root" because a warning popup. I did all configuration as user with 'su' command. Sorry what 'permission' you are referring to? I could not find it on man sane-scsi as user # sane-find-scanner # Note that sane-find-scanner will find any scanner that is connected # to a SCSI bus and some scanners that are connected to the Universal # Serial Bus (USB) depending on your OS. It will even find scanners # that are not supported at all by SANE. It won't find a scanner that # is connected to a parallel or proprietary port. sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/sg1 sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/sg > When it's found by sane-find-scanner, try scanimage -L. # scanimage -L 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). (remark: the scanner has been turned on when starting the computer) > If it's not found, show us the output of > > SANE_DEBUG_SNAPSCAN=255 scanimage -L # sane_debug_snapscan=255 scanimage -L 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) . # sane_debug_snapscan=310 scanimage -L 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). B.Regards Stephen
[sane-devel] First try dutch translation
This is a multi-part message in MIME format.
--060901030903000702050404
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Hi martin & Bertrik
Before eventually making a new translation, I tried to see what
translations were done and how they translated terms. I made the
script attached to this mail to make a comparaison.
Since you are comparing two translations, it may be of use to you.
ljm
--
(c) ljm @ xs4all . nl. No part of this copyright message may be
reproduced, read or seen, dead or alive or by any means, including
but not limited to telepathy without the benevolence of the author.
--060901030903000702050404
Content-Type: text/plain;
name="mkhtml.sh"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="mkhtml.sh"
#!/bin/bash
# accumulate all in a single file
for f in `ls sane-backends.*.po` ; do
lan=`echo $f | awk -F. '{print $2}'`
cat $f |
awk -F\" '
/^\#: .*/ {
state=1
}
/^$/ {
printf("\n")
state=0
}
/^msgid.*/ {
if (state != 0 ) {
print "ERROR PARSING FILE"
state=0
}
if ($2 != ""){
printf("%s", $2)
}
state=2
}
/^msgstr.*/ {
if (state==2){
printf("|%s|",lan)
if ($2 != ""){
printf("%s", $2)
}
}
state=3
}
/^".*/{
if (state==2) printf("%s",$2)
if (state==3) printf("%s",$2)
}' lan=$lan >> /tmp/a$$
done
sort /tmp/a$$ | egrep -v '^$'| awk -F\| '
BEGIN{
print ""
print ""
print ""
}
{
if ($1 !=lst){
lst=$1
print ""
printf("%s\n",$1)
}
printf("%s%s\n",$2,$3)
}
END { print "" }
' | grep -v ''
--060901030903000702050404--
[sane-devel] backend naming conventions/constraints
I tried getting things to work with a hyphenated backend name, but to no avail. The dll backend uses the literal name in dll.conf to check for functions in the backend :-( Here's part of the output of running iscan with SANE_DEBUG_DLL=128: [dll] load: dlopen()ing `/usr/lib/sane/libsane-epson-kowa.so.1' [dll] load: unable to find _sane_epson-kowa_init [dll] load: unable to find _sane_epson-kowa_exit [dll] load: unable to find _sane_epson-kowa_get_devices [dll] load: unable to find _sane_epson-kowa_open [dll] load: unable to find _sane_epson-kowa_close [dll] load: unable to find _sane_epson-kowa_get_option_descriptor [dll] load: unable to find _sane_epson-kowa_control_option [dll] load: unable to find _sane_epson-kowa_get_parameters [dll] load: unable to find _sane_epson-kowa_start [dll] load: unable to find _sane_epson-kowa_read [dll] load: unable to find _sane_epson-kowa_cancel [dll] load: unable to find _sane_epson-kowa_set_io_mode [dll] load: unable to find _sane_epson-kowa_get_select_fd Some minor mods in the dll backend could easily fix that (I'd think), but since I have to rely on existing sane-backends packages out there that is not an option for me right now. I'll go with epkowa for the backend. Olaf Meeuwissen writes: > Henning Meier-Geinitz writes: > > On Thu, Feb 27, 2003 at 09:16:35AM +0900, Olaf Meeuwissen wrote: > > > Yup, backends/Makefile.in uses > > > > > > %-s.lo: %-s.c > > > @$(LIBTOOL) $(MCOMP) $(COMPILE) -DSTUBS -DBACKEND_NAME=$* $< > > > > > > %.lo: %.c > > > @$(LIBTOOL) $(MCOMP) $(COMPILE) -DBACKEND_NAME=$* \ > > > -DLIBDIR=$(libsanedir) $< > > > > > > So using epson-kowa.c screws things up. However, I only have one > > > backend to build with "Image Scan!" so I could hack around this. > > > Either in Makefile.in or in my source file. I hacked around this with -DBACKEND_NAME=$(subst -,_,$*) to keep my sources compilable. -- Olaf MeeuwissenEPSON KOWA Corporation, ECS GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] Problem in setting up Xsane (problem half solved)
Hi folks Lot of thanks for your advice. Thanks to Holger for the link which is the same as on my 1st posting. My problem is now half solved. The trick is I have to disable the Plug and Play driver on the ISA SCSI card by following the steps described on the aforesaid link su password # /sbin/insmod sg Using /lib/modules/2.4.18-3/kernel/drivers/scsi/sg.o # /sbin/insmod aha152x aha152x=0x140,9,7,0 Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: AGFA Model: SNAPSCAN 310 Rev: 1.90 Type: Scanner ANSI SCSI revision: 02 Starting 'Xsane' still could not detect the scanner (licence accepted). I don't know its setup. Can any folk on the list shed me some light Another strange thing is when I restart the PC I have to do 'insmod' again otherwise the scanner could not be detected. # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e Type: CD-ROM ANSI SCSI revision: 02 The scanner disappeared. Any solution? Thanks in advance. B.Regards Stephen Holger Drefs wrote: > Dear Stephen, > > Friday, February 28, 2003, 9:37:36 AM, you wrote: > SL> # /sbin/modprobe aha152x aha152x=0x140,10 (enter) > SL> no response > > SL> # cat /proc/scsi/scsi > SL> Attached devices: > SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00 > SL>Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e > SL>Type: CD-ROM ANSI SCSI revision: 02 > SL> Host: scsi1 Channel: 00 Id: 00 Lun: 00 > SL>Vendor: Model: Rev: > SL>Type: ANSI SCSI revision: > > SL> Started 'Xsane'. After accepting the Licence, a warning popup saying > SL> device not found. > > It can´t find anything because there is anything. > > BUT, i found a step-by-step advisory for you, try this: > http://duvet.eee.nottingham.ac.uk/scanner/snapscan_310_linux.html > > I could read that there is some more parameters and prerequisites > necessary for your card. > > Best regards, > Holger > > -- > > PS Being yealous on Henning because his mails go much faster into the > list, app. 1 hour less. > >
[sane-devel] Problem in setting up Xsane (problem half solved)
Hi, On Fri, Feb 28, 2003 at 09:02:00AM -0700, Dr. Jones wrote: > Herr Meier-Geinitz: Sorry for starting a rant just at the beginning, it's not directed to you only: 1) This is a mailing list. I'm not the only one who answers. Please do not direct mails to me. If I can, I will answer. But most of the time there are other developers or users who are qualified better. 2) Start a new thread when you don't respond to an existing message. If you want to ask about a different topic, do not reply to an existing message but write a new one. I nearly missed your message because it was inside this thread. Now for your questions: > I am having trouble getting sane and xsane set up on my system. I > have an HP ScanJet 4c with the symbios SCSI card. It worked fine > under windows and I notice in the sane docs that it should work with > linux. > My problems may lie in the initial set up of sane, xsane and > sane-frontends in my debian linux system. For most scanners, it's not necessary to set up any part of SANE at all. > I read that I could run 'sane-find-scanner' and yet even after > reinstalling sane and xsane, I could not run that command. You mean that that file is not found? So you didn't install it. Which version of SANE do you use? In very old versions sane-find-scanner was not installed. > If I run 'locate sane' I get a host of directories where various sane > files and folders exist. I am wishing I could purge everything > related to sane from my system and then start afresh with a clean new > setup of sane. If you use RPMs, just uninstall all the sane packages from your system by using your package management tool or rpm directly. As for your scanner: First load the SCSI driver for your symbios scsi card and make sure it is detected (cat /proc/scsi/scsi). Bye, Henning
[sane-devel] Problem in setting up Xsane (problem half solved)
Hi, On Fri, Feb 28, 2003 at 11:55:06PM +0800, Stephen Liu wrote: > Henning Meier-Geinitz wrote: > >- snip - > >Does sane-find-scanner find your scanner? Does it find it if you run > >as user? If it only works as root, you must set up permissions for the > >SCSI devices. See man sane-scsi and search for "permission". > > I hesitate to proceed as "root" because a warning popup. If you do what I write there is no warning popup. I didn't say you should do your usual scanning as root. Just the detection to find out what's going on. > Sorry what 'permission' you are referring to? I could not find it on > man sane-scsi The permissions of the scsi devices (e.g. /dev/sg0). They must be set up so the user can access them. Is this really not in your man page? Aynway, it doesn't matter as the permissions semm to be set up correctly: > as user > # sane-find-scanner > sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device > /dev/sg1 Fine, there it is. So there is no need to run as root. > >If it's not found, show us the output of > > > >SANE_DEBUG_SNAPSCAN=255 scanimage -L > > # sane_debug_snapscan=255 scanimage -L No, please do exactly what I wrote. Hint: capital letters. Use copy&paste to make sure that you don't make any mistakes. If this doesn't produce any debug output, check that "snapscan" (in this exact spelling) is in /etc/sane.d/dll.conf. Bye, Henning
[sane-devel] Problem in setting up Xsane
Hi Martijn, Thanks for your response. su password # /sbin/modprobe aha152x aha152x=0x140,10 (enter) no response # /sbin/modprobe aha152x aha152x=0x140,9 (enter) it hanged there for long time compelling me to restart the Koncole Window Restarted Konsole Window # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: Model: Rev: Type: ANSI SCSI revision: Started 'Xsane'. After accepting the Licence, a warning popup saying device not found. su password # /sbin/rmmod aha152x aha152x: Device or resource busy I have to re-start the computer. Also tried /sbin/modprobe aha152x io=0x140,9 with the same result. B.Regards Stephen Liu Martijn van Oosterhout wrote: > On Fri, Feb 28, 2003 at 10:19:18AM +0800, Stephen Liu wrote: > >># /sbin/insmod aha152x=0x140,10 >>Using /lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10 >>insmod: >>/lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10: >>Not a directory > > > Wrong command. The arguments are not part of the filename. Besides, you > should be using modprobe as it will take care of any possible dependancies. > > # /sbin/modprobe aha152x aha152x=0x140,10 > > Though it might be: > > # /sbin/modprobe aha152x io=0x140,10 > > Which would be more in line with other drivers. > > NOTE: I don't own any scsi devices. I just use a CD burner at work.
[sane-devel] Problem installing new HP5400 backend
Hello, I have been trying to install the new HP5400 backend for my HP5470c on Redhat8.0. (but with no luck) I downloaded and installed sane-backends-1.0.11 and sane-find-scanner recognizes the scanner, however scanimage -L reports "No scanners were identified" I downloaded the HP5400 backend and modified the paths in the Makefile before doing a make install. I made no changes to the hp5400.conf file sane-find-scanner returns:- "found USB scanner (vendor=0x03f0, product=0x1105) at /dev/usb/scanner0 # Your USB scanner was detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage." cat on /proc/bus/usb/devices returns:- P: Vendor=03f0 ProdID=1105 Rev= 0.00 S: Manufacturer=Hewlett-Packard S: Product=HP Scanjet 5400C Series I added the following line to /etc/rc.d/rc.local modprobe scanner vendor=0x03f0 product=0x1105 /usr/local/etc/sane.d/hp.conf has only 2 lines:- /dev/usb/scanner0 option connect-device Any suggestion on what to do now would be greatly appreciated as I have no idea where to start. Regards Rob Male
[sane-devel] root vs. user?
Thanks to everyone for their replies. I have now got it working as root.=20 However, when I log in as a user it can't find the scanner. I have checke= d=20 file access preferences on all the configuration files that I can think o= f,=20 but to no avail.=20 Has anyone else had this problem? Regards, Brad
[sane-devel] Problem in setting up Xsane (problem half solved)
As a matter of update and additional information, here's what I find when I checked on my SCSI adapter. cat /proc/scsi/scsi produced the following output: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONYModel: CDU5211 Rev: yys2 Type: cd-rom revision: 02ANSI SCSI Please bear in mind that my system's CD Rom drive is indeed a Sony model, 52x, but it is connect to the motherboard with a simple ribbon cabble to a connector right next to the RAM slots. I called my system manufacturer and was assured that my system has a CD ROM with IDE interface. For reasons unknown to me, and perhaps very clear to some of you, my cd rom is somehow being associated with the SCSI card I have installed in my system for my scanner. Here's information from the card itself: SBC -2AA 94v-0 fcc id cmc 2502 27-95 rev b c2502-66500 3529 532 4HEGCPF 1) This is a mailing list. I'm not the only one who answers. Please do not direct mails to me. If I can, I will answer. But most of the time there are other developers or users who are qualified better. 2) Start a new thread when you don't respond to an existing message. If you want to ask about a different topic, do not reply to an existing message but write a new one. I nearly missed your message because it was inside this thread. Fair enough, Henning. I wouldn't want to answer everyone's questions directly either. > I am having trouble getting sane and xsane set up on my system. I > have an HP ScanJet 4c with the symbios SCSI card. It worked fine > under windows and I notice in the sane docs that it should work with > linux. > My problems may lie in the initial set up of sane, xsane and > sane-frontends in my debian linux system. >> For most scanners, it's not necessary to set up any part of SANE at all. I am running debian and have run apt-get install xsane as well as apt-get install sane. Yeah, likely redundant, but damn...I am just trying to get this scanner working. > I read that I could run 'sane-find-scanner' and yet even after > reinstalling sane and xsane, I could not run that command. >> You mean that that file is not found? So you didn't install it. Which version of SANE do you use? In very old versions sane-find-scanner was not installed. Yes, I mean if I run 'locate sane-find-scanner' nothing is returned except the prompt. How do I get that installed? > If I run 'locate sane' I get a host of directories where various sane > files and folders exist. I am wishing I could purge everything > related to sane from my system and then start afresh with a clean new > setup of sane. >>As for your scanner: First load the SCSI driver for your symbios scsi card and make sure it is detected (cat /proc/scsi/scsi). In loading my driver..where are suggesting I would find the driver files? Scott
[sane-devel] HP 4470C driver status
Hi, On Mon, Feb 24, 2003 at 06:52:26PM +0100, Witek Kr?cicki wrote: > Is there anything going on with driver to the HP SJ 4470C flatbed? Have you looked at http://home.foni.net/~johanneshub/? The latest change is from February 05, 2003. If you want to contribute or ask questions, try to contact Johannes Hub. Bye, Henning
[sane-devel] Problem in setting up Xsane
--LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 28, 2003 at 10:19:18AM +0800, Stephen Liu wrote: > # /sbin/insmod aha152x=3D0x140,10 > Using /lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=3D0x14= 0,10 > insmod:=20 > /lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=3D0x140,10:= =20 > Not a directory Wrong command. The arguments are not part of the filename. Besides, you should be using modprobe as it will take care of any possible dependancies. # /sbin/modprobe aha152x aha152x=3D0x140,10 Though it might be: # /sbin/modprobe aha152x io=3D0x140,10 Which would be more in line with other drivers. NOTE: I don't own any scsi devices. I just use a CD burner at work. --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Support bacteria! They're the only culture some people have. --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+XtZeY5Twig3Ge+YRAuyEAJ9dBgbxzak/QHREpUK3WSot6x1vSwCfRkYZ vxIDstRUpIDmuqaRaM2NJMo= =r9wV -END PGP SIGNATURE- --LpQ9ahxlCli8rRTG--
[sane-devel] Problem in setting up Xsane (problem half solved)
Hi, On Fri, Feb 28, 2003 at 08:45:54PM +0800, Stephen Liu wrote: > # cat /proc/scsi/scsi > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e > Type: CD-ROM ANSI SCSI revision: 02 > Host: scsi1 Channel: 00 Id: 02 Lun: 00 > Vendor: AGFA Model: SNAPSCAN 310 Rev: 1.90 > Type: Scanner ANSI SCSI revision: 02 Good. Does sane-find-scanner find your scanner? Does it find it if you run as user? If it only works as root, you must set up permissions for the SCSI devices. See man sane-scsi and search for "permission". When it's found by sane-find-scanner, try scanimage -L. If it's not found, show us the output of SANE_DEBUG_SNAPSCAN=255 scanimage -L Bye, Henning
[sane-devel] backend naming conventions/constraints
Hi, On Fri, Feb 28, 2003 at 08:50:44PM +0900, Olaf Meeuwissen wrote: > I tried getting things to work with a hyphenated backend name, but to > no avail. The dll backend uses the literal name in dll.conf to check > for functions in the backend :-( What would be the alternative? How should it get the internal backend name? > Some minor mods in the dll backend could easily fix that (I'd think), > but since I have to rely on existing sane-backends packages out there > that is not an option for me right now. I'll go with epkowa for the > backend. Sounds fine for me. Keep in mind that attaching to a sane backend is quite flexible. That's the reason for some of the tricks used in the Makefile. 1) static linking a) link to one backend statically (e.g. net). The symbold must be sane_init () (without backend name) for this to work. b) link to libsane-dll.a which includes (preloads) all backends statically. The api symbols must use e.g. sane_mustek_init () to avoid duplicated symbols. 2) shared libraries a) link to any sane backend as shared library. The symbol names must be sane_init(). The so name of the library must be libsane.so (not libsane-mustek.so), otherwise you can't change the backend after linking. That's the reason for the change in libtool. b) link to libsane-dll.so as a shared libryry which preloads all other backends (see above). 3) dynamic loading link to libsane-dll.so which loads all other backends dynamically. I'm open for changes but it's not as easy as it looks on first sight. Bye, Henning
[sane-devel] [Fwd: Broken link on SANE site]
Hi, On Thu, Feb 27, 2003 at 02:44:40PM +0100, Laurent-jan wrote: > I got this mail about broken links. Because the links are in > other pages than the FAQ, I forward it to the mailinglist. Thanks. Fixed on mostang.com. Bye, Henning
[sane-devel] command line gamma value for coolscan2?
> Using xsane, I normally set the Gamma value using the coolscan2 > backend to "3" for all three colors. Looking at "scanimage", I > cannot find any single setting that seems to handle the same > option. Am I missing something or is there some doc available > which describes building the -gamma-table values from a single- > value setting on the command line? The gamma value is interpreted by the frontend, which then calculates a LUT table and passes it on to the scanner. Apparently there is a tool in sane-backends for generating gamma tables from the command line for use with scanimage, but I haven't tried it yet. Andras === Major Andras e-mail: and...@users.sourceforge.net www:http://andras.webhop.org/ ===
[sane-devel] root vs. user?
Hi, On Fri, Feb 28, 2003 at 03:16:06PM +1000, Brad wrote: > Thanks to everyone for their replies. I have now got it working as root. > However, when I log in as a user it can't find the scanner. I have checked > file access preferences on all the configuration files that I can think of, > but to no avail. The problem is not SANE or any of it files but the device files of your SCSI scanner. Have a look at man sane-scsi, search for "permission". Bye, Henning
[sane-devel] Problem in setting up Xsane
Stephen Liu wrote: > > Hi Martijn, > > Thanks for your response. > > su > password > > # /sbin/modprobe aha152x aha152x=0x140,10 (enter) > no response > > # /sbin/modprobe aha152x aha152x=0x140,9 (enter) > it hanged there for long time compelling me to restart the Koncole Window > > Restarted Konsole Window > > # cat /proc/scsi/scsi > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 >Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e >Type: CD-ROM ANSI SCSI revision: 02 > Host: scsi1 Channel: 00 Id: 00 Lun: 00 >Vendor: Model: Rev: >Type: ANSI SCSI revision: > That "smells" like a cabling problem or some other hardware issue. The adapter driver seems to find some sort of deice, but probably can't read the result of the usual SCSI INQUIRY command. At least the field "type" should be "scanner" or perhaps "processor". Please check /var/log/messages, if there is any entry from the aha152x driver, when you insmod thatz module. Abel
[sane-devel] Re: Problem in setting up Xsane
Hi, To make it work on my machine (debian stable) : /etc/modutils/actions : -- post-install aha152x modprobe sg -- /etc/modutils/aliases : -- alias scsi_host aha152x options aha152x aha152x=0x140,10 alias /dev/sg1 scsi_host -- If you don't own a debian, put these 4 lines into your modules.conf. Else, don't forget the update-modules command on debian !! Regards. Pierre Souchay
[sane-devel] Problem in setting up Xsane
Hi Oliver, Please see my reply to Henning. B.Regards Stephen Oliver Schwartz wrote: >>I tried several combinations but it said 'aha152x' already exists >>there > > > You need to run "rmmod aha152x" before running insmod again. > > The syntax (according to the source code of aha152x) is > > insmod aha152x io=0x140 irq=9 > > -Oliver > ___ > Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel >
[sane-devel] Problem in setting up Xsane
Hi Holger, Please see my reply to Henning B.Regards Stephen Holger Drefs wrote: > Hello Stephen, > > What does lsmod show now? > What does cat /proc/scsi/scsi show now? > > Thursday, February 27, 2003, 5:57:22 PM, you wrote: > SL> I tried several combinations but it said 'aha152x' already exists there > SL> [root@server /]# /sbin/insmod aha152x aha152x=0x140,10 > ... > SL> Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o > SL> insmod: a module named aha152x already exists > > Ok, so it´s already loaded on system boot, you should find out which > parameters are used, because they are may be wrong. > > Best regards, > Holger > >
[sane-devel] Problem in setting up Xsane
Hi Henning There is something strange. This morrning ater starting the machine, su password # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e Type: CD-ROM ANSI SCSI revision: 02 # /sbin/rmmod aha152x rmmod: module aha152x is not loaded # /sbin/insmod aha152x=0x140,10 Using /lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10 insmod: /lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10: Not a directory B.Regards Stephen Henning Meier-Geinitz wrote: > Hi, > > On Fri, Feb 28, 2003 at 12:57:22AM +0800, Stephen Liu wrote: > >>I tried several combinations but it said 'aha152x' already exists there >> >>[root@server /]# /sbin/insmod aha152x aha152x=0x140,10 >>Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o >>insmod: a module named aha152x already exists > > > Well, yes, it already exists in the kernel :-) Tha means you have > loaded it successfully before. If you want to try again with some > other parameters, remove the module before loading it again: rmmod > aha152x. Have a look at the manpages for understanding what you are > doing (e.g. man insmod). > > If the modules loaded without errors, you may be done. Check > /proc/scsi/scsi if your scanner is listed. [root@server satimis]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e Type: CD-ROM ANSI SCSI revision: 02 > > Bye, > Henning > ___ > Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel >
Re[2]: [sane-devel] Problem in setting up Xsane
Dear Stephen, Friday, February 28, 2003, 9:37:36 AM, you wrote: SL> # /sbin/modprobe aha152x aha152x=3D0x140,10 (enter) SL> no response SL> # cat /proc/scsi/scsi SL> Attached devices: SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00 SL>Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e SL>Type: CD-ROM ANSI SCSI revision: 02 SL> Host: scsi1 Channel: 00 Id: 00 Lun: 00 SL>Vendor: Model: Rev: SL>Type: ANSI SCSI revision: SL> Started 'Xsane'. After accepting the Licence, a warning popup saying=20 SL> device not found. It can=B4t find anything because there is anything. BUT, i found a step-by-step advisory for you, try this: http://duvet.eee.nottingham.ac.uk/scanner/snapscan_310_linux.html I could read that there is some more parameters and prerequisites necessary for your card. Best regards, Holger -- PS Being yealous on Henning because his mails go much faster into the list, app. 1 hour less.
[sane-devel] Problem in setting up Xsane (problem half solved)
This is a multi-part message in MIME format. --=_NextPart_000_0038_01C2DF08.0DB20C60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Herr Meier-Geinitz: I am having trouble getting sane and xsane set up on my system. I have = an HP ScanJet 4c with the symbios SCSI card. It worked fine under = windows and I notice in the sane docs that it should work with linux.=20 My problems may lie in the initial set up of sane, xsane and = sane-frontends in my debian linux system. I read that I could run = 'sane-find-scanner' and yet even after reinstalling sane and xsane, I = could not run that command.=20 If I run 'locate sane' I get a host of directories where various sane = files and folders exist. I am wishing I could purge everything related = to sane from my system and then start afresh with a clean new setup of = sane. Any suggestions on how to accomplish this?=20 Scott --=_NextPart_000_0038_01C2DF08.0DB20C60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Herr Meier-Geinitz: I am having trouble getting sane and = xsane set up=20 on my system. I have an HP ScanJet 4c with the symbios SCSI card. It = worked fine=20 under windows and I notice in the sane docs that it should work with = linux.=20 My problems may lie in the initial set = up of sane,=20 xsane and sane-frontends in my debian linux system. I read that I could = run=20 'sane-find-scanner' and yet even after reinstalling sane and xsane, I = could not=20 run that command. If I run 'locate sane' I get a host of = directories=20 where various sane files and folders exist. I am wishing I could purge=20 everything related to sane from my system and then start afresh with a = clean new=20 setup of sane. Any suggestions on how to accomplish = this?=20 Scott --=_NextPart_000_0038_01C2DF08.0DB20C60--
[sane-devel] backend naming conventions/constraints
Hi, Henning Meier-Geinitz writes: > On Thu, Feb 27, 2003 at 09:16:35AM +0900, Olaf Meeuwissen wrote: > > Yup, backends/Makefile.in uses > > > > %-s.lo: %-s.c > > @$(LIBTOOL) $(MCOMP) $(COMPILE) -DSTUBS -DBACKEND_NAME=$* $< > > > > %.lo: %.c > > @$(LIBTOOL) $(MCOMP) $(COMPILE) -DBACKEND_NAME=$* \ > > -DLIBDIR=$(libsanedir) $< > > > > So using epson-kowa.c screws things up. However, I only have one > > backend to build with "Image Scan!" so I could hack around this. > > Either in Makefile.in or in my source file. > > Yes, but isn't you backend used together with other frontends? I don't know, probably yes, but how does that interact with the way I build the epson-kowa backend? Does libsane-dll choke on hyphenated backends? FYI, "Image Scan!" depends on sane-backends to load its backend (to the best of my knowledge, I inherited the code and haven't wrapped my brain around it quite yet) and "borrows" the sane-backends code to get its custom backend build. > > BTW, is there any reason the build system is not updated to reflect > > the improved capabilities of libtool? It pretty much seems to be > > based on libtool-1.0 or so, while the current version is 1.4. > > Libtool in SANE is 1.4.3. Can you explain the "improved capabilities" > in more detail? We usually only update libtool if absolutely necessary > because it requires manual inclusion of our local changes. And I > hesitate to change anything in backend/Makefile.in if I don't fully > understand the implications :-) Understood. I was referring to the Makefile.in rules, which to me seemed a bit, eh, well, manual. But then again, when was the last time I wrote a Makefile.in? Since I switched to automake, I guess. If SANE uses libtool 1.4.3, I'd say you're up-to-date. > > > Why don't you use "libsane-epson_kowa" or "libsane-epsonkowa"? > > > > Apart from esthetics and readability? Guess not, so it boils down to > > whether I think it's worth the trouble. > > The other backends that use more than one "word" use "_" (e.g. > mustek_usb). Time permitting, I'll see what happens with epson-kowa and if that does not work or otherwise breaks things (including some of the other frontends) I think I'll use "epkowa" after our domain name. Thanks, -- Olaf MeeuwissenEPSON KOWA Corporation, ECS GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] Problem installing new HP5400 backend
Hi Robe, Maybe you did not indicate in dll.conf that it should load hp5400 backend= ? edit /usr/local/etc/sane.d/dll.conf or /etc/sane.d/dll.conf=20 and on a new line add : hp5400=20 Note that direct load of backend (e.g. with -d hp5400) has not been teste= d=20 yet. Let us know if it works. Le Vendredi 28 F=E9vrier 2003 07:15, Rob Male a =E9crit : > Hello, > I have been trying to install the new HP5400 backend for my HP5470c on > Redhat8.0. (but with no luck) > > I downloaded and installed sane-backends-1.0.11 and sane-find-scanner > recognizes the scanner, however scanimage -L reports "No scanners were > identified" > > I downloaded the HP5400 backend and modified the paths in the Makefile > before doing a make install. > I made no changes to the hp5400.conf file > > sane-find-scanner returns:- > "found USB scanner (vendor=3D0x03f0, product=3D0x1105) at /dev/usb/scan= ner0 > # Your USB scanner was detected. It may or may not be supported by > # SANE. Try scanimage -L and read the backend's manpage." > > cat on /proc/bus/usb/devices returns:- > P: Vendor=3D03f0 ProdID=3D1105 Rev=3D 0.00 > S: Manufacturer=3DHewlett-Packard > S: Product=3DHP Scanjet 5400C Series > > I added the following line to /etc/rc.d/rc.local > modprobe scanner vendor=3D0x03f0 product=3D0x1105 > > /usr/local/etc/sane.d/hp.conf has only 2 lines:- > /dev/usb/scanner0 > option connect-device > > Any suggestion on what to do now would be greatly appreciated as I have > no idea where to start. > > Regards Rob Male > > > ___ > Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] HP5400 status update
--qM81t570OJUP5TU/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Lots of features have been added including calibration, gamma correction, more options on XSane (offsets etc), more bug fixes. You name it, it's all there. I even fixed the soname (like it matters). What we really need is people to TEST it. After all, how can you know if something works if it's only been tested on two scanners in the world. http://sourceforge.net/projects/hp5400backend Have a nice day, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Support bacteria! They're the only culture some people have. --qM81t570OJUP5TU/ Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+Xh1eY5Twig3Ge+YRAhrLAJ9qBespa/QiP8JqQAl7yadLsaa/FACgk0ou FnFiXmAH08hT991GEB0oEFc= =SWw0 -END PGP SIGNATURE- --qM81t570OJUP5TU/--
[sane-devel] Problem in setting up Xsane
Hi Henning, Henning Meier-Geinitz wrote: > - snip - > Please read the webpage again. There is no "140h". It's "0x140". And > there is no space after the comma. Now try: > insmod aha152x aha152x=0x140,9 I tried several combinations but it said 'aha152x' already exists there [root@server /]# /sbin/insmod aha152x aha152x=0x140,10 Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o insmod: a module named aha152x already exists [root@server /]# /sbin/insmod aha152x aha152x=0x140,9 Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o insmod: a module named aha152x already exists [root@server /]# /sbin/insmod aha152x aha152x=0x140,11 Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o insmod: a module named aha152x already exists [root@server /]# /sbin/insmod aha152x aha152x=0x140,8 Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o insmod: a module named aha152x already exists [root@server /]# /sbin/insmod aha152x aha152x=0x140,09 Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o insmod: a module named aha152x already exists B.Regards Stephen
[sane-devel] Color not consistent or correct
Hi, please send answers to the list, not to me personally. I'm cc'ing the list. On Fri, Feb 28, 2003 at 04:41:26AM +0530, ionm...@indiainfo.com wrote: > Scanner - Epson Perfection 1250. Do you use the plustek or Epson Kowa backend? > When I scan printed photos the results are excellent and consistent. What happens if you don't use XSane's automatic film setting but set up the colors manually? I.e. use the invert button and change the gamma/brightness for the colors so the image looks correctly? I'm trying to find out if it's a xsane or backend problem. > When I try to use xscanimage it reports...xscanimage: error while > loading shared libraries: libsane.so.1: cannot open shared object > file: No such file or directory. What's the difference between you xsane and xscanimage installations? Did you install one of them from source and the other from RPM? Check the "/usr/local/lib" is in /etc/ld.so.conf. > A "find" produces... > /usr/local/lib/sane/libsane.so.1 > /usr/local/lib/libsane.so.1 For testing, you could try "LD_LIBRARY_PATH=/usr/local/lib xscanimage". There are other frontends you can test, e.g. quiteinsane, kooka. For more, check the SANE homepage. > Would a screen shot of the scan results be of any help? Put it on a web page and send a link to sane-devel. Bye, Henning
