[sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
To permanently disable the kernel scanner driver, you probably have to modify the hotplug configuration so that the module is no longer automatically loaded. One crude way of doing this is to rename the scanner.o file. Karl Heinz On Jan 9, 2004, at 7:31 PM, Olaf Meeuwissen wrote: > Lincoln Peters writes: > >> On Thu, 2004-01-08 at 22:09, Olaf Meeuwissen wrote: # scanimage -L device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner I know that my scanner is NOT an Epson GT-9300! >>> >>> You may know that, but your scanner doesn't ;-) >>> The problem is that EPSON decided to market the same scanner under a >>> different name abroad (here is Japan it's a GT-9300), but didn't >>> bother to change the name returned by the scanner. The epson (and >>> epkowa) backend(s) use the name returned by the scanner, not what is >>> printed on the label (for rather obvious reasons). >> >> That is reassuring. However, having made one (low-res) scan, >> "scanimage" now fails to detect the scanner. I don't know what I >> might >> have done to cause it to stop working. > > Neither do I, but you might try replugging the scanner and making sure > that the kernel hasn't loaded the scanner module (which forces the use > of libusb). > > Check with '/sbin/lsmod | grep scanner'. You can use 'rmmod scanner' > to remove the module. > > Hope this helps, > -- > 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 mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] HP Scanjet 3670...
Hi, On Fri, Jan 09, 2004 at 01:38:57PM +0100, Christian Josefsson wrote: > I'm a Computer Science student, which has come to the point of writing > my Master Thesis. Since I'm interested in systems programming and Linux > and in the posession of a unsupported scanner, namely hp scanjet 3670, > I've concidered writing a driver for that scanner as part of my Thesis > (the thesis would also contain other investigations ...). > But since there appears to be some activity going on in writing a driver > for the scanjet 3670 I would like to hear, how far you have come, and > if it would be feasible for one more person trying to write the driver... I haven't heard from mancio_...@libero.it after his initial posting (http://lists.alioth.debian.org/pipermail/sane-devel/2003-November/009360.html). If he doesn't answer on this list, try to contact him directly. > However in case the driver is already close to finished and/or there already > are enough developers aiming at the same driver, I'd stop pursuing this > idea and instead find myself another subject for my Thesis. At least I don't remember anyone posted a link to code or a website for that scanner. If that doesn't happen some weeks after the first announcement, this usually menas that the project is dead. But I like to be surprised otherwise :-) Anyway, even if someone worked on this project, you could still try to write a backend for any of the other unsupported scanners. The list is so long, you shouldn't have trouble to find one :-) Bye, Henning
[sane-devel] CanoScan LiDE 30 mystery solved
Hi, On Fri, Jan 09, 2004 at 09:48:40AM +0100, Jaeger, Gerhard wrote: > > I guess that should be added to sane-plustek.man. Also there is no > > mention of "SANE_DEBUG_PLUSTEK". > > This in fact is not true, have a look at "CONTACT AND BUG-REPORTS"... Ah, ok. I just looked at the environment section. :-) Bye, Henning
[sane-devel] Problems with mustek_pp and releasing the parallel port
Jim George wrote: > without inetd running but with gdb. > > scanimage hung and when I crtl-c'd out I get the following > "scanimage: received signal 2 > scanimage: trying to stop scanner" > > saned didn't quit. When I pressed ctrl-c in gdb I got > > [...] > > Program received signal SIGINT, Interrupt. > 0x4027786d in sanei_debug_sanei_pa4s2_call () >from /usr/lib/sane/libsane-mustek_pp.so.1 " > > I then did 'bt' and got > "#0 0x4027786d in sanei_debug_sanei_pa4s2_call () >from /usr/lib/sane/libsane-mustek_pp.so.1 > #1 0x4079090 in sanei_pa4s2_readbyte () >from /usr/lib/sane/libsane-mustek_pp.so.1 > #2 0x4026ff0e in Mustek_PP_1015_wait_bit () >from /usr/lib/sane/libsane-mustek_pp.so.1 > #3 0x4027219c in cis_motor_control () >from /usr/lib/sane/libsane-mustek_pp.so.1 > #4 0x402721fb in cis_return_home () from /usr/lib/sane/libsane-mustek_pp.so.1 > #5 0x40272d0c in cis_drv_close () from /usr/lib/sane/libsane-mustek_pp.so.1 > #6 0x4026ef62 in sane_mustek_pp_close () from > /usr/lib/sane/libsane-mustek_pp.so.1 > #7 0x4003bd31 in sane_dll_close () from /usr/lib/libsane.so.1 > #8 0x08049d1d in close_handle () > #9 0x0804b6d0 in process_request () > #10 0x0804bc92 in main () > #11 0x401594c2 in __libc_start_main () from /lib/i686/libc.so.6" > > I hope this helps. Hi Jim, now we are getting somewhere. It looks like the driver is waiting for the scanner motor to stabilize, but it waits forever, either because it doesn't stabilize, or because the communication with the scanner is somehow messed up. Do you have libieee1284 installed? If so, what version is it? It would be useful to also see the debug output of sanei_pa4s2. I know you are short of disk space, so I won't ask you to collect all output. Just let it scroll off the screen. I'm only interested in the last few tens of lines or so (as long as the last few lines of mustek_pp output are included): - stop inetd - as root: SANE_DEBUG_MUSTEK_PP=128 SANE_DEBUG_SANEI_PA4S2=255 saned -d128 - in another window: scanimage -d net:localhost:mustek_pp:Mustek-1200CP > /dev/null Best regards, Eddy --- Tiscali ADSL: 12 maanden aan 29,50 /maand! Snel Internet, en voor iedereen. http://reg.tiscali.be/default.asp?lg=nl
[sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
Lincoln Peters writes: > I had heard that my EPSON Perfection 2400 scanner was supported by > SANE. Rest assured, it is. > # scanimage -L > device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner > > I know that my scanner is NOT an Epson GT-9300! You may know that, but your scanner doesn't ;-) The problem is that EPSON decided to market the same scanner under a different name abroad (here is Japan it's a GT-9300), but didn't bother to change the name returned by the scanner. The epson (and epkowa) backend(s) use the name returned by the scanner, not what is printed on the label (for rather obvious reasons). > [snip] Hope this helps, -- 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] HP Scanjet 3670...
Hi! I'm a Computer Science student, which has come to the point of writing my Master Thesis. Since I'm interested in systems programming and Linux and in the posession of a unsupported scanner, namely hp scanjet 3670, I've concidered writing a driver for that scanner as part of my Thesis (the thesis would also contain other investigations ...). But since there appears to be some activity going on in writing a driver for the scanjet 3670 I would like to hear, how far you have come, and if it would be feasible for one more person trying to write the driver... However in case the driver is already close to finished and/or there already are enough developers aiming at the same driver, I'd stop pursuing this idea and instead find myself another subject for my Thesis. Kind regards // Christian --- Christian Josefsson mail=md0josch@[mdstud,medic,cs,math,md,etek].chalmers.se God made machine language; all the rest is the work of man. ---
[sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
Hi, I already got this report and check it here on my box... Ciao, Gerhard On Freitag, 9. Januar 2004 09:31, Mattias Ellert wrote: > Noah Daniels wrote: > > Hi, > > > > I'm still having the same problem with the plustek backend that several > > people have reported, even using this latest build of the various SANE > > packages. > > > > Basically, sane-find-scanner finds the scanner, but scanimage -L does > > not. However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner > > DOES start working, and scans a partial low-res image before hanging. I > > know this behavior has been reported before, by Henrik Rintala. > > > > I can provide a debug log if anyone's interested... I'd love to be able > > to get this working (printing to a Canoscan 650). > > > > thanks! > > > > -- > > Noah Daniels > > Using the latest version of libusb from CVS (or the binary packages from > 2004-01-05) has been reported to fix the problem that scanimage -L does > not see the scanner unless the DEBUG environment is used. > > The following gdb log of the state of scanimage at the time it freezes > after a scan was provided by a user having a Canon N670U scanner that > uses the Plustek backend on MacOS X. > > To me it looks like the reader process has finished and is waiting to be > killed, but the main process is still trying to read from it. > > Note that the patch in the bug report > https://alioth.debian.org/tracker/index.php?func=detail&aid=300434&group_id >=1308&atid=410366 > > has been applied here, in order to avoid calling pthread_cancel which is > broken on MacOS X. > > Mattias
[sane-devel] CanoScan LiDE 30 mystery solved
On Donnerstag, 8. Januar 2004 18:51, Henning Meier-Geinitz wrote:
[SNIPSNAP]
> True. Most man pages contain something like this:
Okay, okay, I got it ;-)))
The next version will contain this part.
>
> ENVIRONMENT
>SANE_CONFIG_DIR
> This environment variable specifies the list of
> directories that may contain the configuration file.
> Under UNIX, the directories are separated by a colon
> (:'), under OS/2, they are separated by a semi-colon
> (;'). If this variable is not set, the configuration
> file is searched in two default directories: first, the
> current working directory (".") and then in
> /usr/local/etc/sane.d. If the value of the environment
> variable ends with the directory separator character,
> then the default directories are searched after the
> explicitly specified directories. For example, setting
> SANE_CONFIG_DIR to "/tmp/config:" would result in
> directories "tmp/config", ".", and
> "/usr/local/etc/sane.d" being searched (in this order).
>
> I guess that should be added to sane-plustek.man. Also there is no
> mention of "SANE_DEBUG_PLUSTEK".
This in fact is not true, have a look at "CONTACT AND BUG-REPORTS"...
Ciao,
Gerhard
[sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
Hi, On Donnerstag, 8. Januar 2004 20:17, Noah Daniels wrote: [SNIPSNAP] > Basically, sane-find-scanner finds the scanner, but scanimage -L does not. > However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner DOES > start working, and scans a partial low-res image before hanging. I know > this behavior has been reported before, by Henrik Rintala. > > I can provide a debug log if anyone's interested... I'd love to be able to > get this working (printing to a Canoscan 650). you can send me these logs, but I'm pretty sure, that the backend itself is not the problem. Probably we can find some workaround, when doing some delays on the correct positions - but in the end, as you already noted, the scanner will hang during the scan... The best solution will be to contact the libusb guys and fix the problems, where they come from... Ciao, Gerhard
[sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
This is a multi-part message in MIME format. --050409050009020202060209 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Noah Daniels wrote: > Hi, > > I'm still having the same problem with the plustek backend that several > people have reported, even using this latest build of the various SANE > packages. > > Basically, sane-find-scanner finds the scanner, but scanimage -L does not. > However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner DOES start > working, and scans a partial low-res image before hanging. I know this > behavior has been reported before, by Henrik Rintala. > > I can provide a debug log if anyone's interested... I'd love to be able to > get this working (printing to a Canoscan 650). > > thanks! > > -- > Noah Daniels Using the latest version of libusb from CVS (or the binary packages from 2004-01-05) has been reported to fix the problem that scanimage -L does not see the scanner unless the DEBUG environment is used. The following gdb log of the state of scanimage at the time it freezes after a scan was provided by a user having a Canon N670U scanner that uses the Plustek backend on MacOS X. To me it looks like the reader process has finished and is waiting to be killed, but the main process is still trying to read from it. Note that the patch in the bug report https://alioth.debian.org/tracker/index.php?func=detail&aid=300434&group_id=1308&atid=410366 has been applied here, in order to avoid calling pthread_cancel which is broken on MacOS X. Mattias -- mattias.ell...@tsl.uu.se tel: +46 18 471 32 58 http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13 --050409050009020202060209 Content-Type: text/plain; name="plustek.txt" Content-Disposition: inline; filename="plustek.txt" Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp3.cern.ch id i098YBJm006043 (gdb) info threads 2 process 799 thread 0x1c43 0x90017048 in semaphore_wait_signal_trap () * 1 process 799 thread 0x307 0x9000ebc4 in read () (gdb) thread 1 [Switching to thread 1 (process 799 thread 0x307)] #0 0x9000ebc4 in read () (gdb) backtrace #0 0x9000ebc4 in read () #1 0x0021ab44 in sane_plustek_read (handle=3D0xdd000, data=3D0xbfff7820 "= xN,~K$fO*qT)f=3D$SR\"gV,", '?' , "?=CB=AB\215uM\\E,jF4\= 237~e", '?' ..., max_length=3D32768, length=3D0xb8= 60) at plustek.c:2071 #2 0x4600 in scan_it () at scanimage.c:1142 #3 0x6078 in main (argc=3D45792, argv=3D0xa000104c) at scanimage.c:19= 75 (gdb) thread 2 [Switching to thread 2 (process 799 thread 0x1c43)] #0 0x90017048 in semaphore_wait_signal_trap () (gdb) backtrace #0 0x90017048 in semaphore_wait_signal_trap () #1 0x9000e890 in _pthread_cond_wait () #2 0x0021d91c in local_thread (arg=3D0x25bd1c) at sanei_thread.c:221 #3 0x900247e8 in _pthread_body () (gdb) --050409050009020202060209--
[sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
The scanner is fully supported with Sane. It is also correctly identified: The GT-9300 is the internal name of the device. The name "Perfection 2400" is not stored anywhere in the firmware, it's just printed on the outside. The Sane backend only sees the internal name, and this is what it reports. If you change the scanning mode on the commmand line, you will be able to scan both grayscale and color in addition to the black&white (or lineart mode). Is it possible that RH9 unloads the driver if you are not scanning for a while and has a problem reloading it? This is very likely not a Sane problem, but a problem with your USB subsystem. I'm not familiar with RH9, so I'm not in a position to comment on that. Sorry. Karl Heinz > I had heard that my EPSON Perfection 2400 scanner was supported by > SANE. I plugged it into the USB port on a computer running Red Hat > Linux 9.0, installed SANE from source, and then ran the > "sane-find-scanner" program. I got the following output: > > # 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. > # Also you need support for SCSI Generic (sg) in your operating system. > # If using Linux, try "modprobe sg". > > found USB scanner (vendor=0x04b8, product=0x011b) at /dev/usb/scanner0 > found USB scanner (vendor=0x04b8 [EPSON], product=0x011b [EPSON Scanner]) > at libusb:001:002 > # Your USB scanner was (probably) detected. It may or may not be > supported by > # SANE. Try scanimage -L and read the backend's manpage. > > # Scanners connected to the parallel port or other proprietary ports > can't be > # detected by this program. > > As the "sane-find-scanner" program suggested, I ran "scanimage -L", and > got the following: > > # 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). > > As the HOWTO suggested, I tried it again: > > # scanimage -L > device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner > > I know that my scanner is NOT an Epson GT-9300! I seem to be able to > scan pictures even when the scanner is incorrectly identified, but they > come out as line art (perhaps this is because I haven't yet looked up > the EPSON-specific command line options). > > I have commented out every driver listed in /etc/sane.d/dll.conf > *except* the "epson" driver, to minimize the chance of SANE using the > wrong driver. Furthermore, the /etc/sane.d/epson.conf file has every > line commented out except for: > > usb /dev/usb/scanner0 > > I also double-checked that libusb is installed. I don't have any other > USB devices connected to the computer, but I am reasonably sure that the > USB interface itself is properly configured (I wouldn't expect a > misconfigured USB interface to be able to report that I have an EPSON > scanner). I am also sure that the problem does not lie in the > permissions (I'm using it while logged in as root). > > > I have also found that, for some reason, if I leave it and come back a > few minutes later, SANE will fail to find my scanner. The > "sane-find-scanner" command works as before, but "scanimage -L" fails to > detect a scanner no matter how many times I try it. If I try to scan > the image using the command: > > # scanimage -d epson:/dev/usb/scanner0 --format tiff > new.tiff > > I get the following error: > > scanimage: open of device /dev/usb/scanner0 failed: Invalid argument > > > According to both the website and the mailing list archives, the EPSON > Perfection 2400 PHOTO scanner works with SANE, but I cannot figure out > how. What am I doing wrong? > > -- > Lincoln Peters > > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-requ...@lists.alioth.debian.org >
[sane-devel] 2.6.1-rc3 lost scanner, gnomeradio's gui segfaults
Greets everyone; I'm setup to use libusb here, rahter than drivers/usb/scanner in the kernel config. Up to 2.6.1-rc1-mm1 and possibly a little later, my scanner worked just fine. But now on 2.6.1-rc3 its disappeared. I also have everything in the i2c category except i2c-dev (builtin) as modules trying to find some combination that will let sensors run. I had all that compiled in the last time it worked. Also, gnomeradio just segfaulted on startup and left the radio on when it did. That also worked previously. Ideas? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
