[ Date Index ][
Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Rick Timmis wrote:
No I have no idea, but this is something I would like to do. Ideally I would like to provide each office with a networked scanner, plummed back to the main server. Given that they all run thin client this would have to be the way to do it. I would be really interested to work on this with you to find a solution
I think some of the HP Office products will work as network scanners via JetAdmin, so if you have a choice of scanners you might side steps some of the problems. Some of these devices don't have Linux drivers, which I why I was looking at JetAdmin. Haven't played with this option myself mind, just something I saw in the documentation when zipping by. One client has loads of fancy Xerox devices that do everything, and can scan and dump to a samba share, but they cost a small fortune.
I have been trying to set up a network scanning station using a scsi scanner and SANE on a Linux machine so that a single scanner can be used by people on other computers in the vicinity on mostly windows clients - with some success - sort of - things are still very flakey. I still have one major problem. The scanner (epson GT9500) has an old ISAS CSI card. I have not been able to figure out a way of getting the Linuxb ox to load the kernel module for the scsi card (aha152x) automatically so I am reduced to the command line - modprobe aha152x . Tried putting this in boot.local but just succeeded in disabling ethernet when it rebooted!! Don't ask me how that happened, the only connection I can think of is that they are both isa cards.
Try putting the module (and dependencies) in /etc/modules.conf, assuming it is only used for scanning and not disks that need mounting early in the boot.
Module confuse me -- any ideas welcome
My guess is your loading it before the Ethernet card, and shuffling interrupts around, PC hardware does that sort of thing. If the modules.conf does the same thing, try using /etc/init.d/rc.local and run the modprobe after everything else, just as you would manually after the boot, crude, but for as long as it is documented.... Simon -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.