On Sat, Nov 06, 2004 at 05:02:31PM +0000, Dries Hoet wrote: > I can't get my scanner working. scanimage -L says there are no scanners > available. The scanner produces some noise however and the head moves a bit.
Hi, I've seen similar problems reported a few times now, but I can't seem to work out what the common link is. I have a feeling it may be something that's changed in parport_pc between 2.4 and 2.6. In particular, people who have their ports reporting as ECP-S rather than ECP don't seem to have much luck. It's particularly weird because it seems to work for a little while and then the data stops flowing. Could you try enabling the force_nibble mode in canon_pp.conf? and if that fails and you're feeling brave, try playing with your parport_pc module options (ie, specify dma and irq manually). Beyond that I'm not sure what's causing the problem. I now have a couple of machines around with 2.6 on them, so I'll try to do some testing soon. Cheers, - Matthew Duggan > This is the output of sane-troubleshoot: > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > sane-troubleshoot version 2004-09-02 started Sat Nov 6 16:59:32 2004 ... > [canon_pp] detect_mode: Port supports ECP-S. > [canon_pp] detect_mode: Using ECP-S Mode ... > [canon_pp] Had to reset scanner, waiting for the head to get back. > [canon_pp] initialise: >> scanner_init > [canon_pp] NEW Send Command (length 10): > [canon_pp] NEW Send Command (length 10): > [canon_pp] << write[canon_pp] * Check Status: > [canon_pp] NEW read_data (2 bytes): > [canon_pp] -> ieee_transfer(2) * > [canon_pp] IEEE transfer (2 bytes) > [canon_pp] <- (2) > [canon_pp] Ready - 0x0606 > [canon_pp] NEW Send Command (length 10): > [canon_pp] << write[canon_pp] * Check Status: > [canon_pp] NEW read_data (2 bytes): > [canon_pp] Timeout: Read Data 1 (0x00 in 0x01) - Status = 0x07 ...