Julien, sorry for the late reply.
Am Sonntag, 20. März 2005 23:21 schrieben Sie: > Rainer Dorsch <[EMAIL PROTECTED]> wrote: > >> I guess cups might have claimed the parallel port before. Try without > >> cups running if you want to be sure. There's no good way to avoid > > > > Stopping cups (/etc/init.d/cupsys stop) does not solve the problem. > > If you have the lp module loaded, it might it that claimed the parport > (I'd have to look at the code to be sure, it's been a long time). silverboxy:~# lsmod |grep lp lp 11204 0 parport 41832 3 lp,parport_pc,ppdev silverboxy:~# > > >> that, apart from disabling the backends by default :/ > > > > I would do this only when we understood why libieee1284 is now a problem > > or when more people are complaining. > > As it hasn't been reported so far, I believe there is something > specific to your setup... Could you have a look to /var/log/messages > and see if you can find any message related to the parallel port in > there ? silverboxy:~# grep parport /var/log/messages silverboxy:~# grep parport /var/log/syslog Mar 25 10:17:57 silverboxy kernel: parport0: BUSY timeout (1) in compat_write_block_pio Mar 25 22:30:48 silverboxy kernel: parport0: ppdev0 forgot to release port silverboxy:~# grep 1284 /var/log/syslog silverboxy:~# grep 1284 /var/log/messages silverboxy:~# The second line in syslog is caused by the scanimage -L (?): Mar 25 22:30:45 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:46 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:48 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 25 22:30:48 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:48 silverboxy kernel: parport0: ppdev0 forgot to release port Mar 25 22:30:48 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:56 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:57 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 25 22:30:57 silverboxy kernel: ppdev0: unregistered pardevice Does that tell you anything? Thanks, Rainer > > >> libieee1284 claims the parallel port so that the kernel will load the > >> driver if it isn't loaded already; maybe it could be patched to check > >> that the driver is loaded to avoid this situation... > > > > which driver? it=hpsj5s could be patched? > > libieee1284 itself. > > >> If you agree, I'll close this bug. > > > > Yes, please do so. We understood the problem is specific for my system > > and the solution is documented in BTS. > > I'll wait a little bit more, I'd really like to understand what's > going on, and I have the feeling that it's something terribly simple > that just hasn't popped up to my mind yet ... > > > Many thanks for the great support. > > You're welcome :-) > > JB. -- Rainer Dorsch Alzentalstr. 28 D-71083 Herrenberg 07032-919495 Icq: 32550367
