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). >> 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 ? >> 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. -- Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
