[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Sane / Scanner problem




I thought the kernel was recognizing the scanner, but after reading the boot
messages more carefully, only the card was being detected. I checked the scanner
in windows and it wasn't detected there either. So I dinked around with the hw
and got things fixed. Scanner and card are now detected and running. Thanks!

When I boot, though, I get the scanner detection message, but I get messages
detecting generic sga at scsi id 0, generic sgb at scsi id 1 ---generic sgf at
scsi id 7. In /etc/lilo.conf, I force detection with append="aha152x=0x140,9,2"
and my scanner has its scsi id set to 2. Any idea what's up with the extra
scanner messages?

Michael Heyes










Kenneth Scharf <scharkalvin@yahoo.com> on 11/16/99 11:21:50 AM

To:   Mike Heyes/LincolnFP/BerisfordPlc@BerisfordPlc
cc:   debian-user@lists.debian.org

Subject:  Sane / Scanner problem





>I have scsi generic support, and aha152x support
>compiled in the kernel
>(potato
>with 2.2.13) and have sane installed. The scsi card
is >Adaptec 1505.
>The kernel
>recognizes the card fine. I didn't have the sg
devices >in my /dev
>directory, so
>I did a MAKEDEV sg to make them. I made the sym. link
>from /dev/scanner
>to
>/dev/sg0 (the only scsi device in my system is the
>card).
>Went to /etc/sane.d and ran find-scanner, but sane
>couldn't find the
>scanner.
>What am I missing?

use dmseg and check that the scanner was actually
detected by the scsi driver.  My scanner (hp sj3c) had
to be turned on before the computer and completly
warmed up before the kernel would detect it (meant
turning on the scanner 3 minutes before booting
linux!).

Also make sure permissions for /dev/sg0 allow user or
group access, or run find-scanner as root.

=====
Amateur Radio, when all else fails!

http://www.qsl.net/wa2mze

Debian Gnu Linux, Live Free or .....


__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com





Reply to: