> On Fri, 10 Jan 2003, Bill Davidsen wrote:
>
> | The 2.5.5x kernels can't find my printer. 2.4 kernels work fine. dmesg
> | attached, I'll send config if anyone cares.
> |
> | Known problem, new problem, or just some config error? The modules load
> | but don't find anything.
> |
> | lsmod:
> | Module Size Used by
> | apm 15140
> | parport_pc 33320
> | parport 34496
>
> I'm having trouble seeing the trouble.
The lpr/lpq programs tell me /dev/lp0 "no such device", and catting a file
to the device fails. It looks as if the driver isn't listening to the lp0
major,minor or something.
As noted, all works fine in 2.4.{18,20} when booted.
> >From your dmesg:
>
> | pnp: the driver 'parport_pc' has been registered
> | pnp: pnp: match found with the PnP device '00:12' and the driver 'parport_pc'
> | pnp: the device '00:12' has been activated
> | parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
> | parport0: irq 7 detected
> | parport0: cpp_mux: aa55f00f52ad51(80)
> | parport0: cpp_daisy: aa5500ff(80)
> | parport0: assign_addrs: aa5500ff(80)
> | Module parport cannot be unloaded due to unsafe usage in include/linux/module.h:347
> | Module parport_pc cannot be unloaded due to unsafe usage in include/linux/module.h:347
> | parport0: cpp_mux: aa55f00f52ad51(80)
> | parport0: cpp_daisy: aa5500ff(80)
> | parport0: assign_addrs: aa5500ff(80)
>
> I'm not using PnP. With 2.5.54, I see:
> parport0: PC-style at 0x378 [PCSPP(,...)]
> lp0: using parport0 (polling).
>
> Are you expecting to see the "lp0" line also?
I'd settle for a usable device, that isn't happening. I'd believe I need
to change config, but I'm at a loss for what.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/