I copied the firmware file to "/opt/gt68xx/sbfw.usb" and edited the file "gt68xx.conf"
---------------- # Mustek ScanExpress 1200 UB Plus: override "mustek-scanexpress-1200-ub-plus" firmware "/opt/gt68xx/SBfw.usb" ---------------- and copied it to "cp gt68xx.conf /etc/sane.d/" and then ran "/usr/bin/sane-find-scanner -v" but my scanner was not found. I have my scanner connected directly to the usb0 port on my motherboard. Questions: 1) What dev port does the system look at to find my scanner, and, do I have to mount it? 2) From some other reading I did, does a module need to be loaded, such as, (or something similar)? insmod /lib/modules/2.4.20-31.9/kernel/drivers/usb/scanner.o vendor=0x055f product=0x0006 Thanks again for your patience with me and help. -Martin ----------------------------- Date: Sun, 14 Aug 2005 10:15:15 +0200 From: Henning Meier-Geinitz <henn...@meier-geinitz.de> Subject: Re: [sane-devel] Getting Mustek 1200 UB Plus scanner working To: sane-devel@lists.alioth.debian.org Message-ID: <20050814081515.gb9...@meier-geinitz.de> Content-Type: text/plain; charset=us-ascii Hi, On Sat, Aug 13, 2005 at 11:38:44PM -0400, Martin wrote: >> I am trying to get my Mustek 1200 UB Plus scanner working on the USB >> port, but after reading a whole bunch of articles on Google.com, I am >> still not sure howto configure the modules and sane-backend and >> sane-frontend components, mustek_usb.conf, etc., and get it working so I >> can actually use my scanner. > > That scanner is supported by the gt68xx backend, not mustek_usb. Here is more documentation: http://www.meier-geinitz.de/sane/gt68xx-backend/ The main point is that you get the firmware from the above mentioned page and copy it to the location listed in man sane-gt68xx. After that you should be able to scan at least as root (scanimage -L; scanimage --help; scanimage >image.pnm). If scanning as normal user doesn't work, look into the documentation for your distribution, it should be explained there. Bye, Henning -------- Original Message -------- Subject: Getting Mustek 1200 UB Plus scanner working Date: Sun, 14 Aug 2005 06:55:58 -0400 From: Martin <mart...@ix.netcom.com> To: sane-devel@lists.alioth.debian.org I'm running RedHat 9 on a AMD K6-2 system. I am trying to get my Mustek 1200 UB Plus scanner working on the USB port, but after reading a whole bunch of articles on Google.com, I am still not sure howto configure the modules and sane-backend and sane-frontend components, mustek_usb.conf, etc., and get it all working so I can actually use my scanner. My systems is, CPU: AMD K6-2 333MHz Mem: 324Mb O/S: RedHat 9 Linux I have the USB cable plugged into the usb0 port of my motherboard. Your would be greatly appreciated. Thanks, -Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050814/10f5706a/attachment.htm From j...@jblache.org Sun Aug 14 21:03:30 2005 From: j...@jblache.org (Julien BLACHE) Date: Sun Aug 14 21:03:45 2005 Subject: [sane-devel] Canon LiDE 20 vertical lines In-Reply-To: <20050814173025.gc10...@xiph.org> (Monty's message of "Sun, 14 Aug 2005 13:30:25 -0400") References: <20050731234220.gc7...@obelix.kosmos.all> <20050805081004.ga23...@obelix.kosmos.all> <20050805151229.ga23...@xiph.org> <200508071705.57883.gerh...@gjaeger.de> <20050814173025.gc10...@xiph.org> Message-ID: <87ll348c4d....@frigate.technologeek.org> Monty <xiphm...@xiph.org> wrote: > I'm sorry, I should be fair here: It's not clear that this isn't a > packaging or versioning problem in Debian. However, both the .14 and > .15 releases are broken here (in different ways). You know, we have a fair number of users. When a scanner, especially a recent one like the LiDE 20 breaks, we get a bug report in under a week. > Yes, but--- I'll bet real money that Debian's .14 is not a clean .14. 1.0.14 didn't contain a lot of patches. Most of the patches were not affecting backends. 1.0.15 had a couple of patches for different backends, mainly because 1.0.16 took so long to release. There indeed was a patch for the plustek backend in 1.0.15; I pulled the backend from CVS after Gerhard made some fixes for the Epson Perfection 1260. See for yourself: <http://svn.technologeek.org/cgi-bin/viewcvs.cgi/SANE/sane-backends/tags/?root=debian> Look in debian/patches for each tagged release. I don't like the accusations you're making. This is not $RANDOM_DISTRO here with $RANDOM_MAINTAINER applying $RANDOM_PATCHES. I've been maintaining SANE in Debian together with Aur?lien Jarno for more than 2 years now. We are reading sane-devel on a daily basis at least, and hang out on #sane permanently. Whenever something happens, we're here to help. Whenever an important patch or new functionality pops up in the CVS, I mark the commit mail and wait a few days to see how things go. If things go well, I pull the backend from CVS. (I tend to be the one pulling new functionalities into the package) When this happens, this backend is on my radar and I track each and every CVS commit affecting it. When we have fixes or get a bug report, we react immediately and propagate it to either this mailing-list or the CVS ASAP. I spent some time assembling the sane-backends-extras source package to collect as many (mostly) stable external backends as possible. It's intended for use outside of Debian too, and I know it's being used. The result of that is that the hp4200 backend is back from the dead and just made it to the CVS. Our goal is to provide to our users the best scanning experience they could possibly have. And judging by the feedback we receive, we're doing a great job. Today, scanning on Debian with any recent scanner works *out of the box* for all USB scanners (of course not the ones requiring a firmware, but that's trivial); PP scanners tend to work great too, SCSI scanners are, well, SCSI scanners with all the associated troubles. Want more ? Aur?lien took over the maintenance of libusb in Debian, only because it is used by SANE and we wanted to have as much control as possible over our dependencies, especially the critical ones. And it proved to be a good idea. So now, next time you'll have a problem with our packages, you'll learn to either mail us or use reportbug in due time. Until then, shut up. And I mean it. If you had quality problems with 1.0.14 or 1.0.15 Debian packages, you should have reported that back then. Go look at the state of SANE in other distros. Two years ago, I took a look at the SANE packages of every single distro out of there, looking for useful patches to integrate. The result ? Nothing. All I saw was a dirty, unmaintained pile of hacks, badly written RPM specfiles, buggy scripts, dangerous patches. Sadly, this situation hasn't evolved much. JB. -- Julien BLACHE <http://www.jblache.org> <j...@jblache.org> GPG KeyID 0xF5D65169
