[sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S

2004-10-27 Thread Wolfram Heider 
Am Dienstag, 26. Oktober 2004 22:11 schrieb abel deuring:
 Wolfram Heider wrote:
  Hello list,
 
  when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with
  kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well
  troughout all the kernel-versons of the last years, was gone without the
  slightest trace. scanimage -L, sane-find-scanner and the other little
  helpers remainend silent about it.
  Maybe it's not a really sane-problem but a controller-problem.

 yes, it's most likely a problem in the Linux SCSI system. To look for
 SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents
 of this proc file is managed by the SCSI system of the kernel.

  The controller in use is a Dawicontrol DC-2975-C which connected till now
  over the sym53c8xx/ncr53c8xx-module.
  The strange thing is that with the kernel 2.6.1 of the knoppix
  3.4-distribution everthing works as usual.
  The Suse-Kernel still comes with the sym53c8xx-module, but something
  seems to be wrong with it.

 Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it
 loaded, do you get any error messages in /var/log/messages?

 The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to
 play with some of them. The file
 kernel source dir/drivers/scsi/README.ncr53c8xx describes these
 parameters quite detailed.

 Abel

Hello Abel,

here is the output a modprobe sym53c8xx produces in /var/log/messages:

Oct 26 23:11:16 linux su: (to root) ich on /dev/pts/3
Oct 26 23:11:16 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:11:32 linux kernel: sym0: 875 rev 0x26 at pci :00:11.0 irq 12
Oct 26 23:11:32 linux kernel: sym0: No NVRAM, ID 7, Fast-20, SE, parity 
checking
Oct 26 23:11:32 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:11:32 linux kernel: scsi0 : sym-2.1.18i
Oct 26 23:11:38 linux kernel: sym0:0:0: ABORT operation started.
Oct 26 23:11:43 linux kernel: sym0:0:0: ABORT operation timed-out.
Oct 26 23:11:43 linux kernel: sym0:0:0: DEVICE RESET operation started.
Oct 26 23:11:48 linux kernel: sym0:0:0: DEVICE RESET operation timed-out.
Oct 26 23:11:48 linux kernel: sym0:0:0: BUS RESET operation started.
Oct 26 23:11:53 linux kernel: sym0:0:0: BUS RESET operation timed-out.
Oct 26 23:11:53 linux kernel: sym0:0:0: HOST RESET operation started.
Oct 26 23:11:53 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:11:58 linux kernel: sym0:0:0: HOST RESET operation timed-out.
Oct 26 23:11:58 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 0 lun 0
Oct 26 23:12:03 linux kernel: sym0:1:0: ABORT operation started.
Oct 26 23:12:08 linux kernel: sym0:1:0: ABORT operation timed-out.
Oct 26 23:12:08 linux kernel: sym0:1:0: DEVICE RESET operation started.
Oct 26 23:12:13 linux kernel: sym0:1:0: DEVICE RESET operation timed-out.
Oct 26 23:12:13 linux kernel: sym0:1:0: BUS RESET operation started.
Oct 26 23:12:18 linux kernel: sym0:1:0: BUS RESET operation timed-out.
Oct 26 23:12:18 linux kernel: sym0:1:0: HOST RESET operation started.
Oct 26 23:12:18 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:12:23 linux kernel: sym0:1:0: HOST RESET operation timed-out.
Oct 26 23:12:23 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 1 lun 0
Oct 26 23:12:29 linux kernel: sym0:2:0: ABORT operation started.
Oct 26 23:12:34 linux kernel: sym0:2:0: ABORT operation timed-out.
Oct 26 23:12:34 linux kernel: sym0:2:0: DEVICE RESET operation started.
Oct 26 23:12:38 linux su: (to root) ich on /dev/pts/7
Oct 26 23:12:38 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:12:39 linux kernel: sym0:2:0: DEVICE RESET operation timed-out.
Oct 26 23:12:39 linux kernel: sym0:2:0: BUS RESET operation started.
Oct 26 23:12:42 linux su: pam_unix2: session finished for user root, service 
su 
Oct 26 23:12:42 linux su: (to root) ich on /dev/pts/7
Oct 26 23:12:42 linux su: pam_unix2: session started for user root, service su 
Oct 26 23:12:44 linux kernel: sym0:2:0: BUS RESET operation timed-out.
Oct 26 23:12:44 linux kernel: sym0:2:0: HOST RESET operation started.
Oct 26 23:12:44 linux kernel: sym0: SCSI BUS has been reset.
Oct 26 23:12:49 linux kernel: sym0:2:0: HOST RESET operation timed-out.
Oct 26 23:12:49 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 2 lun 0
Oct 26 23:12:54 linux kernel: sym0:3:0: ABORT operation started.
Oct 26 23:12:59 linux kernel: sym0:3:0: ABORT operation timed-out.
Oct 26 23:12:59 linux kernel: sym0:3:0: DEVICE RESET operation started.
Oct 26 23:13:04 linux kernel: sym0:3:0: DEVICE RESET operation timed-out.
Oct 26 23:13:04 linux kernel: sym0:3:0: BUS RESET operation started.
Oct 26 23:13:09 linux kernel: sym0:3:0: BUS RESET operation timed-out.
Oct 26 23:13:09 linux kernel: sym0:3:0: HOST RESET operation started.
Oct 26 23:13:09 linux kernel: sym0: SCSI BUS has been reset.

Sounds as there is something

[sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S

2004-10-26 Thread Wolfram Heider 
Hello list,

when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with kernel 
2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all 
the kernel-versons of the last years, was gone without the slightest trace.  
scanimage -L, sane-find-scanner and the other little helpers remainend silent 
about it.
Maybe it's not a really sane-problem but a controller-problem.
The controller in use is a Dawicontrol DC-2975-C which connected till now over 
the sym53c8xx/ncr53c8xx-module.
The strange thing is that with the kernel 2.6.1 of the knoppix 
3.4-distribution everthing works as usual.
The Suse-Kernel still comes with the sym53c8xx-module, but something seems to 
be wrong with it.
I wasn't very close to the list in the last few months, so perhaps I missed 
some relevant stuff - sorry if I ask those damn old questions.
Is anybody out there who expierienced a similar kind of behaviour and has got 
a solution for it?

Thanks in advance

Wolfram Heider

[sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S

2004-10-26 Thread abel deuring 
Wolfram Heider wrote:
 Hello list,
 
 when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with kernel 
 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all 
 the kernel-versons of the last years, was gone without the slightest trace.  
 scanimage -L, sane-find-scanner and the other little helpers remainend silent 
 about it.
 Maybe it's not a really sane-problem but a controller-problem.

yes, it's most likely a problem in the Linux SCSI system. To look for 
SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents 
of this proc file is managed by the SCSI system of the kernel.

 The controller in use is a Dawicontrol DC-2975-C which connected till now 
 over 
 the sym53c8xx/ncr53c8xx-module.
 The strange thing is that with the kernel 2.6.1 of the knoppix 
 3.4-distribution everthing works as usual.
 The Suse-Kernel still comes with the sym53c8xx-module, but something seems to 
 be wrong with it.

Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it 
loaded, do you get any error messages in /var/log/messages?

The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to 
play with some of them. The file
kernel source dir/drivers/scsi/README.ncr53c8xx describes these 
parameters quite detailed.

Abel

[sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S

2004-10-26 Thread Wolfram Heider 
Am Dienstag, 26. Oktober 2004 22:11 schrieben Sie:
 Wolfram Heider wrote:
  Hello list,
 
  when I recently updated from Suse 8.2 (2.4er kernel)  to Suse 9.1 with
  kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well
  troughout all the kernel-versons of the last years, was gone without the
  slightest trace. scanimage -L, sane-find-scanner and the other little
  helpers remainend silent about it.
  Maybe it's not a really sane-problem but a controller-problem.

 yes, it's most likely a problem in the Linux SCSI system. To look for
 SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents
 of this proc file is managed by the SCSI system of the kernel.

  The controller in use is a Dawicontrol DC-2975-C which connected till now
  over the sym53c8xx/ncr53c8xx-module.
  The strange thing is that with the kernel 2.6.1 of the knoppix
  3.4-distribution everthing works as usual.
  The Suse-Kernel still comes with the sym53c8xx-module, but something
  seems to be wrong with it.

 Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it
 loaded, do you get any error messages in /var/log/messages?

 The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to
 play with some of them. The file
 kernel source dir/drivers/scsi/README.ncr53c8xx describes these
 parameters quite detailed.

 Abel

Good evening; Abel

thanks for your quick reply.
The sym53c8xx modul isn't loadde at boottime. When loaded by hand via
 modprobe it takes suspiciously long time to come up - and finanally nothing
 has changed - everthing dead as the cemetry of Chicago. Only lspci gives a
 hint that there is something in the slot.
I'll take your advice and play around a little bit with the driver
 parameters. See you later.

Wolfram
( I first choosed the wrong reply address - sorry)