[sane-devel] Success!

At long last, I have SANE working with my scanner. I have a UMAX Astra 1200S and after many unsuccessful hours/days with NetBSD/ppc, I hooked everything together with a FreeBSD machine and it works like a champ. Kudos to the SANE team! -- Paul Beard 8040 27th Ave NE Seattle WA 98115 206 529

[sane-devel] Epson Perfection 1650 Photo & Suse 7.2

me. > > I have little doubt that I have done the wrong thing and this will be because I do not understand what I am doing. This sums up what drove me away from linux . . . . . you need to install libgimp or perhaps all of the gimp package to resolve this dependency. rpmfind.net should he

[sane-devel] Scanjet 5P on FreeBSD

inux versions ># >= 2.4.8. > This is very similar to what I saw with my PMac 9500 and NetBSD/macppc. The scanner was "seen" by the scsicontrol utilities/dmesg but all SANE could find was a scanner of unknown type. -- Paul Beard 8040 27th Ave NE Seattle WA 98115 206 529 8400 Some programming languages manage to absorb change but withstand progress.

[sane-devel] xsane issues on Mac OS X

ing to pass the resultant compiled code on to the 'fink' > project which takes linux code and ports it to Mac? in any way I can: fink has been a great help to me. -- Paul Beard 8040 27th Ave NE Seattle WA 98115 206 529 8400 God is the tangential point between zero and infinity. -- Alfred Jarry

[sane-devel] xsane issues on Mac OS X

ist xsane-back-gtk.c:801: bad macro argument list xsane-back-gtk.c:801: bad macro argument list cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode make[1]: *** [xsane-back-gtk.o] Error 1 make: *** [all-recursive] Error 1 -- Paul Beard 8040 27th Ave NE Seattle W

[sane-devel] sane/xsane on Mac OS X?

have a scsi drive installed help at all? -- Paul Beard 8040 27th Ave NE Seattle WA 98115 206 529 8400 Don't take life too seriously -- you'll never get out of it alive.

[sane-devel] sane/xsane on Mac OS X?

Henning Meier-Geinitz wrote: > Hi, > > On Sun, Apr 07, 2002 at 10:28:18PM -0700, paul beard wrote: > >>An update: I did get sane-backends built and installed simply by >>commenting out the canon backend. > > > Cool! Can you please shoiw us the error messag

[sane-devel] sane/xsane on Mac OS X?

n/ppc/2.95.2/specs Apple Computer, Inc. version gcc-932.1, based on gcc version 2.95.2 19991024 (release) -- Paul Beard 8040 27th Ave NE Seattle WA 98115 206 529 8400 Murphy's Law is recursive. Washing your car to make it rain doesn't work.

[sane-devel] sane/xsane on Mac OS X?

I tried building this a week or two back and it failed for reasons I never bothered to investigate. But now I'm thinking of pursuing it more aggressively: what kind of information would help with porting/patching to make it work on this platform? -- Paul Beard 8040 27th Ave NE Seatt

[sane-devel] A front-end for Mac OS X

l 11 make[1]: *** [canon.lo] Error 1 make: *** [all-recursive] Error 1 I'll try frontends as well: I hadn't seen any mention of OS X so far, so stop me if this is already resolved. -- Paul Beard 8040 27th Ave NE Seattle WA 98115 206 529 8400 Only presidents, editors, and people with tapeworms have the right to use the editorial "we."

[sane-devel] How to find out if USB is available for compilation

I guess I don't understand this part of it: the presence of a library or header doesn't mean there is an accessible device, does it? I realize looking at dmesg output is less than optimal, but I'm not sure how else to discover and access devices. Oliver Rauch wrote: > Hello Paul, > > this is

[sane-devel] How to find out if USB is available for compilation

I don't know if this is what you want to do, but dmesg would have that info (I'm no aware of the moral equivalent of /proc). here's some examples from NetBSD and FreeBSD. [/home/paul]# uname -a NetBSD purple.paulbeard.org 1.5.2 NetBSD 1.5.2 (PURPLE) #0: Fri Feb 15 22:35:22 PST 2002 r...@purple

[Fwd: Re: [sane-devel] sane weirdness + UMAX Astra 1220 S]

Original Message Subject: Re: [sane-devel] sane weirdness + UMAX Astra 1220 S Date: Thu, 28 Feb 2002 14:48:30 -0800 From: paul To: Hubert Figuiere CC: sane-de...@mostang.com References: <1014935689.691.21.camel@dirkpitt> sounds familiar . . . if Abel is reading this, perhaps

[sane-devel] sane weirdness + UMAX Astra 1220 S

Hubert Figuiere wrote: > On Thu, 2002-02-28 at 23:48, paul wrote: > >>sounds familiar . . . if Abel is reading this, perhaps he can >>supply you with some diagnostic patches in hopes of working out >>how this wacky Apple hardware works. >> > > The weird stuff is that cdrecord works nicely :-

[sane-devel] SCSI issues persist: open to suggestions

Hubert Figuiere wrote: > > Mine is even weirder: a PowerCenter Pro 240 (from PowerComputing). Think > of a 7300 with a little hacks. And I have 2 SCSI controller: the > built-in NCR based and the AHA 2930-B that works well. My scanner in on > the internal SCSI while the boot disk is on the Adapt

[sane-devel] SCSI issues persist: open to suggestions

Hubert Figuiere wrote: > > It appear that I have some similar problems: sane-find-scanner find my > UMAX Astra 1220S but xcanimage is unable to get even a preview. > > On my side I have a little clue about what is happening: I have a 2.2.x > PowerPC kernel and use the Debian sid version of Sane

[sane-devel] SCSI issues persist: open to suggestions

> Theodore Kilgore wrote: > >> Paul, >> >> If you are interested in installing a Linux distro, it is probably >> possible (if you have disk space) to download the distro onto your hard >> drive and install from there. Naturally, for this you need adequate space >> on the hard drive. I have very

[sane-devel] SCSI issues persist: open to suggestions

well, I am able to reproduce the problems I am seeing with my scanner: I can get it to respond once, ie, use scanimage or one the X frontends to access it. Then it's time to reboot or power-cycle the scanner. I have yet to acquire an image. Since I assume the hardware is OK (unless as Abel sugg

[sane-devel] issues with libm and SANE??

Henning Meier-Geinitz wrote: > Hi, > > I don't know. I have never seen similar things on any platform > (including NetBSD). As this isn't the only problem you observed with > SANE: Are you really sure that there aren't some major problems with > you installation of NetBSD? well, pretty sur

[sane-devel] help with scsi questions??

[sane-devel list cc:ed] I'm working with the SANE folks to figure out why the scsi scanner on my 9500's external bus is so flaky. We have worked through some compiler issues (too much optimization was causing values to get munged) and some patches to how SANE probes the scanner itself. The scanne

[sane-devel] issues with libm and SANE??

I am really close to getting my scanner to work with NetBSD/macppc but now I seem to be tripping over some math functions. I had errors on "pow" being undefined, so we swapped them out for "log" functions. And I get the same result. /usr/pkg/lib/sane/libsane-umax.so.1: Undefined PLT symbol "l

[sane-devel] sane 1.07 sane-find-scanner does not work

what shell are you using? Art Fore wrote: > It is not in the path. I done a ./sane-find-scanner and it works. Will have > to find out the file for this from Suse I guess. > > Art

[sane-devel] Sane is definately not Scanner Access Now Easy

This is a multi-part message in MIME format. --020104010809040506090607 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit you can create your own .bashrc and .profile to accomodate things like paths, etc. find a sample attached: see www.dotfile

[sane-devel] UMAX and netbsd/macppc woes persist

Abel Deuring and I have made some progress on this problem (he's doing the lion's share of the work): there seems to be some communication problem between the kernel's scsi interface and SANE. The kernel and some scsi probing tools see the scanner while SANE 1.0.7 cannot. Abel sent me some debu

[sane-devel] libm issues on macppc

This is a multi-part message in MIME format. --020308070805080500030403 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I evidently looked in the wrong place or some other way incorrectly and missed libm. I created a symlink or two to resolve

[sane-devel] hardcoded paths or missing environment variables??

ktruss /usr/pkg/bin/scanimage -d umax:/dev/uk0 | grep ENOENT I can make some of these errors go away if I am in /usr/pkg/etc/sane.d: is there a convention for that somewhere? 12288 scanimage open("/etc/ld.so.conf", 0, 0x418535c8) Err#2 ENOENT 12288 scanimage __stat13("/usr/pkg/lib/libm.so.0"

[sane-devel] More questions: missing some odds and ends

It appears I am missing some stuff SANE expects me to have: [/usr/pkg/etc/sane.d]# ktruss /usr/pkg/bin/scanimage -d umax:/dev/uk0 | grep ENOENT 1428 scanimage open("/etc/ld.so.conf", 0, 0x418535c8) Err#2 ENOENT 1428 scanimage __stat13("/usr/pkg/lib/libm.so.0", 0x7fffe758) Err#2 ENOENT 1

[sane-devel] UMAX and netbsd/macppc woes persist

abel deuring wrote: > paul beard wrote: > > Did you check the > permission settings? Can you run > > export SANE_DEBUG_SANEI_SCSI=255 > scanimage umax:/dev/uk0 > > and send me the debug output? > This looks like a problem: [sanei_scsi] sanei_scsi

[sane-devel] UMAX and netbsd/macppc woes persist

abel deuring wrote: > paul beard wrote: >> >> "scanimage: open of device umax:/dev/uk0 failed: Invalid >> argument\n" >> > > After all, this is a new error message isn't it ;) I've seen it before, I think . . . > Did you

[sane-devel] UMAX and netbsd/macppc woes persist

well, I seem to be stuck. So far, I've been able to verify that the scanner hardware and cabling work in MacOS but not in NetBSD with SANE. I haven't heard anything resembling a success story with SANE and Apple/PowerPC hardware, so if there are any, I'd be interested to see them. Since the ke

[sane-devel] tech-kern: Retiring 'ss*' and PINT in favour of SANE

Thought this might prove interesting: PINT has been officially deprecated in favor of SANE, meaning the uk* driver is the preferred interface, proposed on Jan 12 2000. No other methods are officially supported.

[sane-devel] UMAX and netbsd/macppc woes persist

SO I seem to have PINT installed (configure found and enabled it) enabling PINT backend how do I use it? and I'd like to get this vprintf issue resolved: commenting out the offending line works, as far as compilation goes, but I doubt it's the best solution. [...ckends/work/sane-backends-1.0.

[sane-devel] more on sane-find-scanner not grokking this scanner

I enabled device ss0 in the kernel config, recompiled, installed and rebooted but the scanner still seems to show up on device uk0. uk0 at scsibus0 target 2 lun 0: SCSI2 6/scanner fixed uk0: unknown device So now I have commented out the uk0 device and will recompile, install and reboot to s

[sane-devel] what am I doing wrong on netbsd/macppc with sane 1.0.7??

Henning Meier-Geinitz wrote: > The problem with ss0/uk0 you talked about is on OpenBSD, nor FreeBSD. > On OpenBSD, you can only use the uk0 devices, ss0 won't work. However, > I never had such problems on NetBSD. > OK, I'll recompile with ss0 and see if that makes a difference.

[sane-devel] what am I doing wrong on netbsd/macppc with sane 1.0.7??

Henning Meier-Geinitz wrote: > I have no idea why your scanner can't be seen by SANE (but the cabling > issues someone mentioned). Is there any way to check for SCSI devices > during the runtime on NetBSD? A SCSI test program or something that > prints a list of devices? So you could find out if

[sane-devel] Hmm, why does sane-find-scanner think I have a USB scanner?

it isn't USB: uk0 at scsibus0 target 2 lun 0: SCSI2 6/scanner fixed If I specify the device (/dev/scanner) I get this result. [...-backends/work/sane-backends-1.0.7/tools]# sane-find-scanner /dev/scanner # Note that sane-find-scanner will find any scanner that is connected # to a SCSI bus and

[sane-devel] how does sane-find-scanner work?

I'm trying to do something more constructive than inserting lots of DEBUG printfs in the sane-find-scanner code, though that's not a bad approach if I could figure out what to print(f) out. I can't seem to work out where exactly the device is probed so I can examine what comes back. I have veri

[sane-devel] [Fwd: still looking for this scanner with SANE]

sent this from unsubscribed address . . . . Original Message Subject: still looking for this scanner with SANE Date: Fri, 15 Feb 2002 23:15:04 -0800 From: paul To: sane-de...@mostang.com I have recompiled my kernel to remove the ss0 device, replacing it with uk0, as I recall re

[sane-devel] what am I doing wrong on netbsd/macppc with sane 1.0.7??

Henning Meier-Geinitz wrote: >> > > Looks like your binary xsane is build with libusb-0.1.so.4 and > installed on a system that doesn't have this lib. I don't > know if this works on NetBSD but maybe you can just set a > link to the new library? > > The NetBSD binary packages are not crea

[sane-devel] what am I doing wrong on netbsd/macppc with sane 1.0.7??

well, following this suggestion yielded the same results: commenting out the line completely allowed make to complete. I'm not enough of a hacker to know why this is failing: anyone care to lend me a clue? >>scanimage.c: In function `main': >>scanimage.c:1564: incompatible type for argument 2

[sane-devel] what am I doing wrong on netbsd/macppc with sane 1.0.7??

I finally have gotten this scanner to make itself known to the OS, but now I seem to have other issues. I build from source (using pkgscr?) it fails. gmake[1]: Entering directory `/usr/pkgsrc/graphics/sane-backends/work/sane-backends-1.0.7/frontend' cc -c -DHAVE_CONFIG_H -I. -I. -I../include

[sane-devel] Scanner stopped working

e, > xscanimage and scanimage and each time the program just hangs. No error > messages, nothing. When I run sane-find-scanner I get the following > error message... what platform and OS? I have this scanner on an unsupported platform and I'm curious to see how far out mine is. -- Pa

[sane-devel] sorry for the FAQ but I can't find an answer anywhere

r: checking /dev/ss0... failed to open -- Paul Beard 8040 27th Ave NE Seattle WA 98115 Theory is gray, but the golden tree of life is green. -- Goethe