Henning Meier-Geinitz wrote: > Hi, >
<snip> > 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 sure, yes. There may be some hardware issues, from what Abel has been able to determine. The libm issue was a bad symlink from libc, rather than the real math library. No idea how that happened . . . . Right now, I am finding that accessing the scanner is intermittent: for some reason, the bus is getting reset while commands are being sent to the scanner. When I have gotten xsane or xscanimage working, I have not been able to acquire an image, even as a preview, so this is going quite slowly. from an email Abel sent: > So it seems that there are a few issues with the SCSI system of your > machine. > > A more general SCSI question: (I assume that the folks who adapted > NetBSD to the Apple hardware know this, but let us be sure ;) The reason > that Apple installs two SCSI busses in many of their computers is to > have a fast internal bus for the hard disks; this bus needs the usual > careful setup: proper cabling and termination; for the external bus > Apple managed to design the interface in an amazing "error-friendly" > way. I have seen several absolutely wrong setups working flawlessly, > like a 1.5 m cable at the end of the bus without a device and without a > terminator. This can only work for slow transfer speeds, so I wonder if > the NetBSD kernel really ensures that the speed of the external bus is > really 5 MHz. Do you see anything related messages with dmesg or in some > log files? right now the scanner doesn't show up at all: I just added a terminator (it supposedly has active termination internally, but I thought I would see what difference this made).
