Hi Julien,
the syslog contains
Mar 30 23:20:22 silverboxy kernel: ppdev0: registered pardevice
Mar 30 23:20:24 silverboxy kernel: ppdev0: registered pardevice
Mar 30 23:20:25 silverboxy kernel: ppdev0: released pardevice because
user-space
forgot
Mar 30 23:20:25 silverboxy kernel: ppdev0: unregistered pardevice
Mar 30 23:20:25 silverboxy kernel: parport0: ppdev0 forgot to release port
Mar 30 23:20:25 silverboxy kernel: ppdev0: unregistered pardevice
Mar 30 23:20:28 silverboxy kernel: ppdev0: registered pardevice
Mar 30 23:20:29 silverboxy kernel: ppdev0: registered pardevice
Mar 30 23:21:38 silverboxy kernel: ppdev0: released pardevice because
user-space
forgot
Mar 30 23:21:38 silverboxy kernel: ppdev0: unregistered pardevice
Mar 30 23:21:38 silverboxy kernel: parport0: ppdev0 forgot to release port
Mar 30 23:21:38 silverboxy kernel: ppdev0: unregistered pardevice
Mar 30 23:22:06 silverboxy kernel: ppdev0: registered pardevice
Mar 30 23:22:06 silverboxy kernel: ppdev0: registered pardevice
Mar 30 23:22:56 silverboxy kernel: ppdev0: released pardevice because
user-space
forgot
Mar 30 23:22:56 silverboxy kernel: ppdev0: unregistered pardevice
Mar 30 23:22:56 silverboxy kernel: parport0: ppdev0 forgot to release port
Mar 30 23:22:56 silverboxy kernel: ppdev0: unregistered pardevice
I attach logs from mustek and hpsj5s (which is very short).
Thanks,
Rainer
Am Mittwoch, 30. März 2005 23:02 schrieb Julien BLACHE:
> Rainer Dorsch <[EMAIL PROTECTED]> wrote:
>
> Hi Rainer,
>
> > open("/dev/scanner", O_RDWR|O_NONBLOCK|O_EXCL) = -1 ENOENT (No such file
> > or directory)
> > open("/etc/ieee1284.conf", O_RDONLY) = -1 ENOENT (No such file or
> > directory)
> > open("/dev/parport0", O_RDONLY|O_NOCTTY) = 5
> > ioctl(5, PPCLAIM, 0x4004c7bc <unfinished ...>
> > silverboxy:~#
>
> OK, exact same thing.
>
> I'm going to ask you for one (really, two) debug logs from the mustek
> and hpsj5s backends, and I should have enough information to pinpoint
> the problem. (btw, I guess you still see the same parport related
> messages in /var/log/messages ?).
>
> Could you run:
> # SANE_DEBUG_MUSTEK=255 scanimage -L 2> mustek.log
> # SANE_DEBUG_HPSJ5S=255 scanimage -L 2> hpsj5s.log
>
> And send me both files ?
>
> (I still think both backends are misusing libieee1284 and not
> releasing the parport; otherwise, the parport is claimed by another
> process, and there's nothing I can do I think)
>
> Thanks,
>
> JB.
--
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367
[sanei_debug] Setting debug level of mustek to 255.
[mustek] SANE mustek backend version 1.0 build 137 from sane-backends 1.0.15
[mustek] sane_init: authorize != null
[mustek] sane_init: using sanei_scsi_open_extended
[mustek] sane_init: reading config file `mustek.conf'
[mustek] sane_init: config file line 1: ignoring comment line
[mustek] sane_init: config file line 2: ignoring empty line
[mustek] sane_init: config file line 3: ignoring comment line
[mustek] sane_init: config file line 4: ignoring comment line
[mustek] sane_init: config file line 5: ignoring comment line
[mustek] sane_init: config file line 6: ignoring comment line
[mustek] sane_init: config file line 7: ignoring comment line
[mustek] sane_init: config file line 8: ignoring comment line
[mustek] sane_init: config file line 9: ignoring empty line
[mustek] sane_init: config file line 10: ignoring comment line
[mustek] sane_init: config file line 11: trying to attach `scsi MUSTEK * Scanner'
[mustek] sane_init: config file line 12: ignoring comment line
[mustek] sane_init: config file line 13: ignoring comment line
[mustek] sane_init: config file line 14: ignoring comment line
[mustek] sane_init: config file line 15: ignoring comment line
[mustek] sane_init: config file line 16: ignoring comment line
[mustek] sane_init: config file line 17: ignoring empty line
[mustek] sane_init: config file line 18: trying to attach `scsi SCANNER'
[mustek] sane_init: config file line 19: ignoring comment line
[mustek] sane_init: config file line 20: ignoring comment line
[mustek] sane_init: config file line 21: ignoring comment line
[mustek] sane_init: config file line 22: ignoring comment line
[mustek] sane_init: config file line 23: ignoring comment line
[mustek] sane_init: config file line 24: ignoring empty line
[mustek] sane_init: config file line 25: trying to attach `/dev/scanner'
[mustek] attach: trying device /dev/scanner
[mustek] dev_open /dev/scanner
[mustek] dev_open: Invalid argument: can't open /dev/scanner as a SCSI device
[mustek] dev_open: Invalid argument: can't open /dev/scanner as an AB306N device
[sanei_debug] Setting debug level of hpsj5s to 255.
[hpsj5s] >>sane_init[hpsj5s] sane_init: version_code != 0, authorize != 0
[hpsj5s] sane_init: SANE hpsj5s backend version 1.0.3
[hpsj5s] <<sane_init
