> The kernel panics are troubling....
>
> Another user who was asking me for advice discovered that his problems
> went away when he commented out the "dll.conf" entries for all but the
> correct backends (i.e. microtek, in his case).
>
> I suspect that another backend (maybe microtek2?) was not being careful
> enough in its device identification, and harassing his scanner and/or
> scsi bus into a panic.
>
> Oliver: you say "scanimage -L" only works when you are non-root. If it
> only lists the pnm devices, then probably the /dev permissions
> kept it from poking at the SCSI bus.
>
No, it listed nothing.It simply hung.
permissions: crw-rw-rw- 1 root disk 21, 0 Mar 5 00:52
/dev/sg0
> -matt m.
>
> ps: with regards to the AVA-1502: evil crap. my quality-of-life while
> doing scans has improved considerably since buying a US$80 Tekram
> PCI scsi card (390U, with a NCR53c875 controller in it).
> However, the original AVA-1502 *did* work while I used it.
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
Oliver
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com