Hi, I've an Epson gt-5500 sscsi scanner connected to Adaptec 2940 (aic7xxx).
After recent upgrades something got changed and the scanner is nomore detected, sometimes I've a kernel panic message too.

bash-4.4# date; scan ; date
Tue May 23 20:54:30 CEST 2017
Host adapter 0 (ahci) found.
Host adapter 1 (ahci) found.
Host adapter 2 (ahci) found.
Host adapter 3 (ahci) found.
Host adapter 4 (ahci) found.
Host adapter 5 (ahci) found.
Host adapter 6 (pata_amd) found.
Host adapter 7 (pata_amd) found.
Host adapter 8 (aic7xxx) found.
Scanning SCSI subsystem for new devices
Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: WDC WD20EZRX-00D Rev: 0A80
Type: Direct-Access ANSI SCSI revision: 05
Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3500418AS Rev: CC34
Type: Direct-Access ANSI SCSI revision: 05
Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: WDC WD10EZRX-00A Rev: 1A01
Type: Direct-Access ANSI SCSI revision: 05
Scanning host 3 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 3 0 0 0 ...
OLD: Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: TSSTcorp Model: CDDVDW SH-224BB Rev: SB00
Type: CD-ROM ANSI SCSI revision: 05
Scanning host 4 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 5 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 6 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 7 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 8 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 8 0 5 0 ...
OLD: Host: scsi8 Channel: 00 Id: 05 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: -1
0 new device(s) found.
0 device(s) removed.
Tue May 23 13:59:22 CEST 2017

as you can see it detects something but reports nothing, moreover using lsscsi it says the found device is a "disk". Any ideas? I attach the complete scanning output, the lsscsi and the dmess outputs.

Thanks,
Nicola

Attached Files

	dmesg-new1.txt (122.5 KB, 10 views)
	lsscsi-new1.txt (378 Bytes, 8 views)
	sg_error_dmesgs.txt (1.7 KB, 8 views)
	sg_error2.txt (2.0 KB, 12 views)
	sg_error-bah1.txt (2.8 KB, 7 views)

look here, perhaps:

http://www.sane-project.org/man/sane-epson2.5.html

hi, well .. the sane-find-scanner finds "somethings" but instead of the scanner it says it's a disk:
Scanning host 8 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 8 0 5 0 ...
OLD: Host: scsi8 Channel: 00 Id: 05 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: -1
0 new device(s) found.
0 device(s) removed.


and the lsscsi output is:
[0:0:0:0] disk ATA WDC WD20EZRX-00D 0A80 /dev/sda
[1:0:0:0] disk ATA ST3500418AS CC34 /dev/sdb
[2:0:0:0] disk ATA WDC WD10EZRX-00A 1A01 /dev/sdc
[3:0:0:0] cd/dvd TSSTcorp CDDVDW SH-224BB SB00 /dev/sr0
[8:0:5:0] disk /dev/sdd <--- I've no disk connected, the scanner uses that ID: 05


I've done current upgrades and none of the configuration files changed (I've a copy of the personalized ones)
... looking at /var/log/messages up to the past week it worked and was correctly detected:
May 18 21:03:15 casa kernel: [46350.816048] scsi host9: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
May 18 21:03:15 casa kernel: [46350.816048] <Adaptec 2940 Ultra SCSI adapter>
May 18 21:03:15 casa kernel: [46350.816048] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
May 18 21:03:15 casa kernel: [46350.816048]
May 18 21:03:17 casa kernel: [46352.139643] scsi 9:0:5:0: Processor EPSON SCANNER GT-5500 1.01 PQ: 0 ANSI: 2
May 18 21:03:17 casa kernel: [46352.139655] scsi target9:0:5: Beginning Domain Validation
May 18 21:03:17 casa kernel: [46352.150974] scsi target9:0:5: Ending Domain Validation
May 18 21:03:17 casa kernel: [46352.151216] scsi 9:0:5:0: Attached scsi generic sg5 type 3


while now ...
May 27 10:53:02 casa kernel: [ 74.720058] scsi host8: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
May 27 10:53:02 casa kernel: [ 74.720058] <Adaptec 2940 Ultra SCSI adapter>
May 27 10:53:02 casa kernel: [ 74.720058] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
May 27 10:53:02 casa kernel: [ 74.720058]
May 27 10:53:09 casa kernel: [ 81.539095] ata5: hard resetting link
May 27 10:53:09 casa kernel: [ 81.845244] ata5: SATA link down (SStatus 0 SControl 300)
May 27 10:53:09 casa kernel: [ 81.845262] ata5: EH complete
May 27 10:53:09 casa kernel: [ 81.942566] ata5: hard resetting link
May 27 10:53:09 casa kernel: [ 82.253312] ata5: SATA link down (SStatus 0 SControl 300)
May 27 10:53:09 casa kernel: [ 82.253324] ata5: EH complete
May 27 10:53:10 casa kernel: [ 82.877670] ata6: hard resetting link
May 27 10:53:10 casa kernel: [ 83.181335] ata6: SATA link down (SStatus 0 SControl 300)
May 27 10:53:10 casa kernel: [ 83.181346] ata6: EH complete
May 27 10:53:10 casa kernel: [ 83.278023] ata6: hard resetting link
May 27 10:53:11 casa kernel: [ 83.589353] ata6: SATA link down (SStatus 0 SControl 300)
May 27 10:53:11 casa kernel: [ 83.589368] ata6: EH complete
May 27 10:53:11 casa kernel: [ 84.201651] ata7: soft resetting link
May 27 10:53:11 casa kernel: [ 84.371611] ata7: EH complete
May 27 10:53:12 casa kernel: [ 84.469145] ata7: soft resetting link
May 27 10:53:12 casa kernel: [ 84.635087] ata7: EH complete
May 27 10:53:12 casa kernel: [ 84.704644] ata7: soft resetting link
May 27 10:53:12 casa kernel: [ 84.867152] ata7: EH complete
May 27 10:53:12 casa kernel: [ 84.922668] ata7: soft resetting link
May 27 10:53:12 casa kernel: [ 85.091242] ata7: EH complete
May 27 10:53:13 casa kernel: [ 85.648624] ata8: EH complete
May 27 10:53:13 casa kernel: [ 85.692736] ata8: EH complete
May 27 10:53:13 casa kernel: [ 85.725264] ata8: EH complete
May 27 10:53:13 casa kernel: [ 85.769236] ata8: EH complete
May 27 10:53:17 casa kernel: [ 89.970954] scsi host8: scsi scan: INQUIRY result too short (5), using 36
May 27 10:53:17 casa kernel: [ 89.970960] scsi 8:0:5:0: Direct-Access PQ: 0 ANSI: 0
May 27 10:53:17 casa kernel: [ 89.970972] scsi target8:0:5: Beginning Domain Validation
May 27 10:53:28 casa kernel: [ 100.843031] scsi 8:0:5:0: tag#0 Attempting to queue an ABORT message
May 27 10:53:33 casa kernel: [ 105.952061] scsi 8:0:5:0: tag#0 Attempting to queue a TARGET RESET message
May 27 10:53:54 casa kernel: [ 126.432033] scsi 8:0:5:0: tag#0 Attempting to queue an ABORT message
May 27 10:53:59 casa kernel: [ 131.552035] scsi 8:0:5:0: tag#0 Attempting to queue a TARGET RESET message
May 27 10:54:09 casa kernel: [ 141.792031] scsi 8:0:5:0: Device offlined - not ready after error recovery
May 27 10:54:09 casa kernel: [ 141.792070] scsi target8:0:5: Ending Domain Validation
May 27 10:54:09 casa kernel: [ 141.793337] sd 8:0:5:0: Attached scsi generic sg4 type 0
May 27 10:54:40 casa kernel: [ 173.035042] sd 8:0:5:0: tag#0 Attempting to queue an ABORT message
May 27 10:54:46 casa kernel: [ 178.144058] sd 8:0:5:0: tag#0 Attempting to queue a TARGET RESET message
May 27 10:55:06 casa kernel: [ 198.624023] sd 8:0:5:0: tag#0 Attempting to queue an ABORT message
May 27 10:55:11 casa kernel: [ 203.744029] sd 8:0:5:0: tag#0 Attempting to queue a TARGET RESET message
May 27 10:55:21 casa kernel: [ 213.984039] sd 8:0:5:0: Device offlined - not ready after error recovery
May 27 10:55:21 casa kernel: [ 213.984120] sd 8:0:5:0: [sdd] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00
May 27 10:55:21 casa kernel: [ 213.984124] sd 8:0:5:0: [sdd] Sense not available.
May 27 10:55:21 casa kernel: [ 213.984132] sd 8:0:5:0: [sdd] 0 512-byte logical blocks: (0 B/0 B)
May 27 10:55:21 casa kernel: [ 213.984136] sd 8:0:5:0: [sdd] 0-byte physical blocks
May 27 10:55:21 casa kernel: [ 213.984148] sd 8:0:5:0: [sdd] Write Protect is off
May 27 10:55:21 casa kernel: [ 213.984516] sd 8:0:5:0: [sdd] Attached SCSI disk
May 27 10:55:42 casa kernel: [ 234.987036] scsi 8:0:5:1: tag#0 Attempting to queue an ABORT message
May 27 10:55:48 casa kernel: [ 240.096065] scsi 8:0:5:1: tag#0 Attempting to queue a TARGET RESET message
May 27 10:55:58 casa kernel: [ 250.337024] scsi 8:0:5:1: tag#0 Attempting to queue an ABORT message
May 27 10:55:58 casa kernel: [ 250.338009] scsi 8:0:5:1: tag#0 Command already completed
May 27 10:55:58 casa kernel: [ 250.598778] scsi 8:0:5:1: Device offlined - not ready after error recovery
May 27 10:56:19 casa kernel: [ 271.851030] scsi 8:0:6:0: tag#0 Attempting to queue an ABORT message
May 27 10:56:40 casa kernel: [ 292.843033] scsi 8:0:6:0: tag#0 Attempting to queue an ABORT message
May 27 11:33:40 casa kernel: [ 2512.902933] ata5: hard resetting link
May 27 11:33:40 casa kernel: [ 2513.213348] ata5: SATA link down (SStatus 0 SControl 300)
May 27 11:33:40 casa kernel: [ 2513.213360] ata5: EH complete
May 27 11:33:40 casa kernel: [ 2513.329858] ata5: hard resetting link
May 27 11:33:41 casa kernel: [ 2513.637349] ata5: SATA link down (SStatus 0 SControl 300)
May 27 11:33:41 casa kernel: [ 2513.637365] ata5: EH complete
May 27 11:33:41 casa kernel: [ 2514.318790] ata6: hard resetting link
May 27 11:33:42 casa kernel: [ 2514.629356] ata6: SATA link down (SStatus 0 SControl 300)
May 27 11:33:42 casa kernel: [ 2514.629368] ata6: EH complete
May 27 11:33:42 casa kernel: [ 2514.751788] ata6: hard resetting link
May 27 11:33:42 casa kernel: [ 2515.061364] ata6: SATA link down (SStatus 0 SControl 300)
May 27 11:33:42 casa kernel: [ 2515.061375] ata6: EH complete
May 27 11:33:43 casa kernel: [ 2515.758572] ata7: soft resetting link
May 27 11:33:43 casa kernel: [ 2515.923128] ata7: EH complete
May 27 11:33:43 casa kernel: [ 2516.035977] ata7: soft resetting link
May 27 11:33:43 casa kernel: [ 2516.203426] ata7: EH complete
May 27 11:33:43 casa kernel: [ 2516.279712] ata7: soft resetting link
May 27 11:33:44 casa kernel: [ 2516.443114] ata7: EH complete
May 27 11:33:44 casa kernel: [ 2516.557802] ata7: soft resetting link
May 27 11:33:44 casa kernel: [ 2516.723279] ata7: EH complete
May 27 11:33:44 casa kernel: [ 2517.308273] ata8: EH complete
May 27 11:33:44 casa kernel: [ 2517.360175] ata8: EH complete
May 27 11:33:45 casa kernel: [ 2517.395395] ata8: EH complete
May 27 11:33:45 casa kernel: [ 2517.449875] ata8: EH complete
May 27 11:34:06 casa kernel: [ 2538.987041] scsi 8:0:0:0: tag#0 Attempting to queue an ABORT message
May 27 11:34:27 casa kernel: [ 2559.979037] scsi 8:0:0:0: tag#0 Attempting to queue an ABORT message
May 27 11:34:48 casa kernel: [ 2580.971045] scsi 8:0:1:0: tag#0 Attempting to queue an ABORT message
May 27 11:35:09 casa kernel: [ 2601.963031] scsi 8:0:1:0: tag#0 Attempting to queue an ABORT message
May 27 11:35:30 casa kernel: [ 2622.955042] scsi 8:0:2:0: tag#0 Attempting to queue an ABORT message
May 27 11:35:51 casa kernel: [ 2643.947041] scsi 8:0:2:0: tag#0 Attempting to queue an ABORT message
May 27 11:36:12 casa kernel: [ 2664.940040] scsi 8:0:3:0: tag#0 Attempting to queue an ABORT message
May 27 11:36:33 casa kernel: [ 2685.931048] scsi 8:0:3:0: tag#0 Attempting to queue an ABORT message
May 27 11:36:54 casa kernel: [ 2706.923044] scsi 8:0:4:0: tag#0 Attempting to queue an ABORT message
May 27 11:37:15 casa kernel: [ 2727.915048] scsi 8:0:4:0: tag#0 Attempting to queue an ABORT message
May 27 11:37:36 casa kernel: [ 2748.907065] scsi 8:0:6:0: tag#0 Attempting to queue an ABORT message
May 27 11:37:57 casa kernel: [ 2769.899044] scsi 8:0:6:0: tag#0 Attempting to queue an ABORT message
May 27 11:38:52 casa kernel: [ 2825.362204] ata5: hard resetting link
May 27 11:38:53 casa kernel: [ 2825.669347] ata5: SATA link down (SStatus 0 SControl 300)
May 27 11:38:53 casa kernel: [ 2825.669358] ata5: EH complete
May 27 11:38:53 casa kernel: [ 2825.785260] ata5: hard resetting link
May 27 11:38:53 casa kernel: [ 2826.093400] ata5: SATA link down (SStatus 0 SControl 300)
May 27 11:38:53 casa kernel: [ 2826.093415] ata5: EH complete
May 27 11:38:54 casa kernel: [ 2826.786650] ata6: hard resetting link
May 27 11:38:54 casa kernel: [ 2827.093242] ata6: SATA link down (SStatus 0 SControl 300)
May 27 11:38:54 casa kernel: [ 2827.093249] ata6: EH complete
May 27 11:38:54 casa kernel: [ 2827.200182] ata6: hard resetting link
May 27 11:38:55 casa kernel: [ 2827.509327] ata6: SATA link down (SStatus 0 SControl 300)
May 27 11:38:55 casa kernel: [ 2827.509337] ata6: EH complete
May 27 11:38:55 casa kernel: [ 2828.223760] ata7: soft resetting link
May 27 11:38:56 casa kernel: [ 2828.387135] ata7: EH complete
May 27 11:38:56 casa kernel: [ 2828.463025] ata7: soft resetting link
May 27 11:38:56 casa kernel: [ 2828.627139] ata7: EH complete
May 27 11:38:56 casa kernel: [ 2828.721511] ata7: soft resetting link
May 27 11:38:56 casa kernel: [ 2828.891091] ata7: EH complete
May 27 11:38:56 casa kernel: [ 2829.003568] ata7: soft resetting link
May 27 11:38:56 casa kernel: [ 2829.171126] ata7: EH complete
May 27 11:38:57 casa kernel: [ 2829.756167] ata8: EH complete
May 27 11:38:57 casa kernel: [ 2829.807327] ata8: EH complete
May 27 11:38:57 casa kernel: [ 2829.841414] ata8: EH complete
May 27 11:38:57 casa kernel: [ 2829.894565] ata8: EH complete
May 27 11:39:19 casa kernel: [ 2851.819046] scsi 8:0:0:0: tag#0 Attempting to queue an ABORT message
May 27 11:39:40 casa kernel: [ 2872.811040] scsi 8:0:0:0: tag#0 Attempting to queue an ABORT message
May 27 11:40:01 casa kernel: [ 2893.803049] scsi 8:0:1:0: tag#0 Attempting to queue an ABORT message
May 27 11:40:22 casa kernel: [ 2914.795025] scsi 8:0:1:0: tag#0 Attempting to queue an ABORT message
May 27 11:40:43 casa kernel: [ 2935.787034] scsi 8:0:2:0: tag#0 Attempting to queue an ABORT message
May 27 11:40:46 casa kernel: [ 2938.401779] ata5: hard resetting link
May 27 11:40:46 casa kernel: [ 2938.709374] ata5: SATA link down (SStatus 0 SControl 300)
May 27 11:40:46 casa kernel: [ 2938.709384] ata5: EH complete
May 27 11:40:46 casa kernel: [ 2938.779537] ata5: hard resetting link
May 27 11:40:46 casa kernel: [ 2939.085361] ata5: SATA link down (SStatus 0 SControl 300)
May 27 11:40:46 casa kernel: [ 2939.085377] ata5: EH complete
May 27 11:40:47 casa kernel: [ 2939.734543] ata6: hard resetting link
May 27 11:40:47 casa kernel: [ 2940.045347] ata6: SATA link down (SStatus 0 SControl 300)
May 27 11:40:47 casa kernel: [ 2940.045360] ata6: EH complete
May 27 11:40:47 casa kernel: [ 2940.158560] ata6: hard resetting link
May 27 11:40:48 casa kernel: [ 2940.469338] ata6: SATA link down (SStatus 0 SControl 300)
May 27 11:40:48 casa kernel: [ 2940.469349] ata6: EH complete
May 27 11:40:48 casa kernel: [ 2941.153595] ata7: soft resetting link
May 27 11:40:48 casa kernel: [ 2941.323422] ata7: EH complete
May 27 11:40:49 casa kernel: [ 2941.429622] ata7: soft resetting link
May 27 11:40:49 casa kernel: [ 2941.595392] ata7: EH complete
May 27 11:40:49 casa kernel: [ 2941.672068] ata7: soft resetting link
May 27 11:40:49 casa kernel: [ 2941.835125] ata7: EH complete
May 27 11:40:49 casa kernel: [ 2941.942633] ata7: soft resetting link
May 27 11:40:49 casa kernel: [ 2942.107090] ata7: EH complete
May 27 11:40:50 casa kernel: [ 2942.716619] ata8: EH complete
May 27 11:40:50 casa kernel: [ 2942.769076] ata8: EH complete
May 27 11:40:50 casa kernel: [ 2942.806039] ata8: EH complete
May 27 11:40:50 casa kernel: [ 2942.860808] ata8: EH complete
May 27 11:41:12 casa kernel: [ 2964.971041] scsi 8:0:0:0: tag#0 Attempting to queue an ABORT message
May 27 11:41:33 casa kernel: [ 2985.963038] scsi 8:0:0:0: tag#0 Attempting to queue an ABORT message
May 27 11:41:54 casa kernel: [ 3006.955038] scsi 8:0:1:0: tag#0 Attempting to queue an ABORT message
May 27 11:42:15 casa kernel: [ 3027.947031] scsi 8:0:1:0: tag#0 Attempting to queue an ABORT message
May 27 11:42:36 casa kernel: [ 3048.939030] scsi 8:0:2:0: tag#0 Attempting to queue an ABORT message
May 27 11:42:57 casa kernel: [ 3069.931032] scsi 8:0:2:0: tag#0 Attempting to queue an ABORT message
May 27 11:43:18 casa kernel: [ 3090.923048] scsi 8:0:3:0: tag#0 Attempting to queue an ABORT message
May 27 11:43:39 casa kernel: [ 3111.915052] scsi 8:0:3:0: tag#0 Attempting to queue an ABORT message
May 27 11:44:00 casa kernel: [ 3132.907050] scsi 8:0:4:0: tag#0 Attempting to queue an ABORT message
May 27 11:44:21 casa kernel: [ 3153.899037] scsi 8:0:4:0: tag#0 Attempting to queue an ABORT message
May 27 11:44:42 casa kernel: [ 3174.891045] scsi 8:0:6:0: tag#0 Attempting to queue an ABORT message
May 27 11:45:03 casa kernel: [ 3195.883051] scsi 8:0:6:0: tag#0 Attempting to queue an ABORT message

Since new kernel update ?

I don't know exactly, I'm testing to reverse the updates done. Up to now none worked. I don't remember if I had already done 22May updates - for the kernel I compile it on my own, I have a config file I always use and that never created me problems on 18 May I had 4.11.1.
I have the aic7xxx (m) and the sg (y). If have aic7xxx (y), like it happens for huge, a kernel panic happens.

Solved!! ... moved back to sane-1.0.25 (the one released in slackware 14.2) and the scanner is correctly detected and working. Now I'll check to understand exactly what causes the problem, but for sure that version works perfectly.

Nicola


Upgrade: nope, too optimistic: when rebooted not working again, so still unsolved

1 members found this post helpful.

I'm not sure why that would have fixed it, as that's the version that was present in -current when you made your original post. It's been upgraded since then, though.

I wonder if things would still work if you went ahead and upgraded to the latest sane package now?

Infact that not solved my problem. In the beginning I reinstalled all old packages and nothing worked, I noticed a sane upgrade was available and tried to do the same for it. Immediately it worked, the scanner has been correctly detected and did some scans. To do an extra test I upgraded to the new sane and the sanner was not detected so I returned to the one that worked and I wrote the solved post. I've rebooted the system and the problem was still there. Just in that moment I noticed that the new sane package upgrade date followed my original post date. I've tried to use scsi sg device as module too .. nothing. To do some extra test and exclude hardware problems I tried to used other live distros using the most recent kernel possible and the scanner always worked. I'm a bit out of fresh ideas..

I attach the most recent messages file, on Jun 5 13:53:24 and 14:08:23 it detected the "scsi 8:0:5:0: Processor EPSON SCANNER GT-5500 1.01 PQ: 0 ANSI: 2"

Attached Files

messages.txt (139.3 KB, 4 views)

Perhaps, bad contact, (scsi cable or on the scssi card)

I've an Adaptec 2940UW. It has an external and an internal SE-HD68F and an internal SE-50M. I tried using different cables on both connectors and nothing changed.
Right now I'm using a live distro, Fedora26 Alpha because it has kernel 4.11.0 (in attached files don't look at the time, I've not changed it to my timezone).
I rebooted the system more than 15 times manipulating the cable, changing from external to internal connnectors, and the scanner has always been perfectly detected and working. When moved back to slackware-current .. usual problems.

Attached Files

	dmesg_fc26.txt (73.7 KB, 9 views)
	journalctl_fc26.txt (80.8 KB, 9 views)

99.99...9% solved the problem: yes you are right there's a problem not with the scsi cable/card but with the mainboard. Doing tests, using also other live distros, lots freezings occurred when doing the rescan-scsi-bus ... it's time for a system upgrade. There's a problem with the pci sots.
I say it because to have much more results I've done some extra "homeworks":
1) installed card and scanner in my sis pc and used Alienbob slackware64-live
2) remounted an old pc, a P4, with a very updated slackware-current and with my same configuration (sorry for the delay but it takes more than 4hours to compile the kernel)
I've rebooted the systems, executed the rescan-scus-bus and the scanner has always been perdectly detected with no delays and no problems using huge kernel, instead for my pc I always have a kernel panic.

Nicola