HP Scanner:: zilch

[Gary Kline]

On Thu, Dec 22, 2005 at 04:46:56PM -0700, Warren Block wrote:
> On Thu, 22 Dec 2005, Gary Kline wrote:
> 
> >	Before I write off the HP Scanjet 4100c, I thought it's
> >	best to check with the list first.
> >
> >	I have "device usb" in the kernel; I did a kernel load of
> >	uscanner.ko and a kldstat shows that the module is there.
> >	My two USB ports seem to be alive.  Is there a command to
> >	double-check??
> 
> Device detection should auto-load the uscanner module for you.
> 
> >	I have yet to reboot to reinitialize my 5.3 system.  Otherwise,
> >	can anybody suggest ideas of things to try next?  xsane execs
> >	but cannot find anything.
> >
> >	thanks for some clues.
> >
> >	gary
> >
> >	PS: In /usr/local/etc/sane.d, the hp.conf file lists the
> >	    4100c with two heex addrs.  ....
> 
> My Epson requires this line in epson.conf:
> 
> usb /dev/uscanner0
> 
> The hp.conf file kind of implies something similar, but I can't tell 
> whether it would want the line above or this:
> 
> /dev/uscanner0
>   option connect-device

	Hm, this is strange. I have two hp files in sane.d, both sseem
	oriented toward Linux.  There is an entry for the 4100c in
	"hp.conf", but it wants to create /dev/scanner.  

root at tao:/usr/local/etc/sane.d# ll hp*
-r--r--r--  1 root  wheel  497 Dec 22 16:40 hp.conf
-r--r--r--  1 root  wheel  238 Oct  9 23:09 hp5400.conf

>From "hp.conf"::

root at tao:/usr/local/etc/sane.d# more hp.conf 
scsi HP
# Uncomment the following if you have "Error during device I/O" on SCSI
#   option dumb-read
#
# The usual place for a SCSI-scanner on Linux
/dev/scanner
#
# USB-scanners supported by the hp-backend
# HP ScanJet 4100C
usb 0x03f0 0x0101
	.
	.
	.

Would it make sense to create an "hp4100.conf" with your epson line
"usb /dev/uscanner0" as a first line?



> 
	I am missing /dev/uscanner0.  How is this /dev created?  


q2 16:27 <tao> [5015] kldstat
Id Refs Address    Size     Name
 1   11 0xc0400000 5e7530   kernel
 2   14 0xc09e8000 537f0    acpi.ko
 3    1 0xc1aaf000 2000     blank_saver.ko
 4    1 0xc1ad1000 17000    linux.ko
 5    1 0xc2352000 3000     uscanner.ko

	Does this output look right?  This may be right the scanner 
	wasn't seen.  I figured that by kldloading uscanner.ko, 
	/dev/uscanner0 would be auto-created.  I need some other 
	magic.




-- 
   Gary Kline     kline at thought.org   www.thought.org     Public service Unix