Re: Maxi-scan A4 scanner (AGAIN!!!) under Mandrake 8.0 (2.4.3)

From: Ben Stanley (bds02@uow.edu.au)
Date: Tue May 22 2001 - 15:13:22 PDT

  • Next message: Ben Stanley: "Re: Problems with Prisa 620S [snapscan] + BUG in xsane 0.76"

    Ceri Hankey wrote:

    > Hi,
    >
    > I am STILL fighting to get my scanner working under Linux - NEITHER
    > the USB one (Agfa 1212u) NOR the SCSI one (MaxiScan A4 attached to an
    > Acard SCSI controller (atp870u driver)) will work.
    >
    > Here is a list of results on trying to access the SCSI Scanner...
    >
    > >> SANE_DEBUG_SNAPSCAN=255 SANE_DEBUG_SCSI=255 scanimage -L >rdebug.log
    > [sanei_debug] Setting debug level of snapscan to 255.
    > [snapscan] sane_snapscan_init
    > [snapscan] add_device(/dev/scanner)
    > [snapscan] add_device: error opening device /dev/scanner: Invalid
    > argument
    > [snapscan] add_device(/dev/sg4)
    > [snapscan] add_device: error opening device /dev/sg4: Invalid argument
    > [snapscan] sane_snapscan_get_devices (0xbffff320, 0)
    > [snapscan] sane_snapscan_exit
    >
    >
    > Extract from messages:...
    >
    > May 22 21:02:49 ceri2 modprobe: modprobe: Can't locate module
    > char-major-81
    > May 22 21:02:49 ceri2 last message repeated 4 times
    > May 22 21:02:49 ceri2 kernel: scanner.c: open_scanner(0): Unable to
    > access minor data
    > May 22 21:02:49 ceri2 last message repeated 26 times
    >
    > ## What does the above mean?
    >
    I haven't been following this thread.. perhaps you've been here before.
    If so, please forgive me.

    Do you have a modular kernel? Almost everyone does :-).

    This looks like your kernel does not know how to talk to the SCSI card
    you have installed. After probing for the SCSI device, if correctly
    configured, your system logs should show the results of loading the SCSI
    module. I get:

    May 22 14:35:37 dragon modprobe: modprobe: Can't locate module char-major-81
    May 22 14:35:37 dragon last message repeated 3 times
    May 22 14:35:37 dragon kernel: SCSI subsystem driver Revision: 1.00
    May 22 14:35:38 dragon kernel: aha152x: BIOS test: passed, detected 1
    controller(s)
    May 22 14:35:38 dragon kernel: aha152x: resetting bus...
    May 22 14:35:38 dragon kernel: aha152x0: vital data: rev=1, io=0x140
    (0x140/0x140), irq=10, scsiid=7, reconnect=enabled, parity=enabled,
    synchronous=disabled, delay=1000, extended translation=disabled
    May 22 14:35:38 dragon kernel: aha152x0: trying software interrupt, ok.
    May 22 14:35:38 dragon kernel: scsi0 : Adaptec 152x SCSI driver;
    $Revision: 2.4 $
    May 22 14:35:39 dragon kernel: Vendor: Color Model:
    FlatbedScanner_9 Rev: 0117
    May 22 14:35:39 dragon kernel: Type: Scanner
        ANSI SCSI revision: 02
    May 22 14:35:39 dragon kernel: Vendor: IOMEGA Model: ZIP 100
        Rev: D.13
    May 22 14:35:39 dragon kernel: Type: Direct-Access
        ANSI SCSI revision: 02
    May 22 14:35:40 dragon kernel: Detected scsi generic sg0 at scsi0,
    channel 0, id 2, lun 0, type 6
    May 22 14:50:01 dragon kernel: scsi : 0 hosts left.

    This will only be triggered if you have correctly set up
    /etc/modules.conf so that it knows about your SCSI card. There should be
    a line mentioning the module for your scsi card, something like

    alias aha152x scsi_hostadapter

    See the SCSI-HOWTO and Modules-HOWTO for more info.

    Note that on my RH system, the module gets automatically unloaded 15
    minutes later (because nothing is using it) - hence the scsi: 0 hosts
    left message.

    This info is also available after the module is loaded by doing cat
    /proc/scsi/scsi.

    I can't help you with the USB stuff - sorry.

    Ben.

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
    



    This archive was generated by hypermail 2b29 : Tue May 22 2001 - 15:15:31 PDT