On Sat, Mar 17, 2001 at 01:50:29PM -0500, Tim Waugh wrote:
> On Sat, Mar 17, 2001 at 06:59:17PM +0100, stef wrote:
>
> > parport0: No more nibble data (0 bytes)
> > parport0: faking semi-colon
>
> *sigh*, another manufacturer who gets this wrong..
>
> > parport0 probe: warning, class 'IMAGE' not understood.
>
> It's supposed to be 'SCANNER', but it doesn't much matter.
>
> > parport0 (addr 0): Unknown device, UMAX Astra 1220P
> > parport0 (addr 1): Printer, EPSON Stylus COLOR 440
> > parport0 (addr 2): Printer, EPSON Stylus COLOR 440
> > parport0 (addr 3): Printer, EPSON Stylus COLOR 440
> > parport0: Printer, EPSON Stylus COLOR 440
> > lp0: using parport0 (interrupt-driven).
> >
> > My printer is detected 3 times
>
> Actually four times: at daisy chain addresses 1, 2, and 3, and also as
> a non-chain-aware device.
>
> > It is harmless since the printer and scanner work correctly.
>
> Yes, but annoying, and eventually there may be drivers that actually
> want to look at this information.
>
> I guess this is the scanner's fault, since a ZIP250 with chained Epson
> Stylus colour 760 is reported correctly.
>
> Not that I expect it to make any difference, but if you leave off
> 'reset=1', does that make any difference?
>
No it doesn't make any difference. But on first load after boot the
detection is ok:
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
parport0: Found 1 daisy-chained devices
parport0: No more nibble data (0 bytes)
parport0: faking semi-colon
parport0 probe: warning, class 'IMAGE' not understood.
parport0 (addr 0): Unknown device, UMAX Astra 1220P
parport0: Printer, EPSON Stylus COLOR 440
lp0: using parport0 (interrupt-driven).
Then if the modules are unloaded, then loaded again, I have again 3 ghosts
printers.
Regards,
Stef
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Sun Mar 18 2001 - 08:03:56 EST