Re: 2.1.???-124 - PLIP Problem.

John Campbell (jcampbel@lynn.ci-n.com)
Mon, 5 Oct 1998 17:42:41 -0400 (EDT)

>
> I have not been able to get plip to properly recognize a parallel
> port
> device since (I think) around the time of the change in the parralel
> port driver.
>
[snip]
>
> Config info:
> [tested in 4 different machines]
> ..[snip]..
> CONFIG_PARPORT=y
> CONFIG_PARPORT_PC=y
> ..[snip]..
> CONFIG_PLIP=m
> ..[snip]..
> CONFIG_PRINTER=m
> ..[snip]..
>
I've had PLIP working with this exact configuration as recently as
2.1.122. I'm using two parallel ports, one for PLIP and one for a printer. I
had some difficulty with IRQs and suchlike that I rectified by adding this
to my rc.local:

# Turn on IP forwarding between the parport and the ARCnet
echo 1 > /proc/sys/net/ipv4/ip_forward

# Set the parallel port IRQs
# parport0 is on 0x378 IRQ 7, parport1 is on 0x278 IRQ 3
echo 7 > /proc/parport/0/irq
echo 3 > /proc/parport/1/irq

# Activate the PLIP and line printer modules
/sbin/insmod lp parport=0
/sbin/insmod plip parport=1

I have three machines using PLIP, a 2.1.12x box and a 2.0.35 box,
both running with a printer and a PLIP connection, and a 1.2.13 laptop that
necessitated the whole PLIP thing to begin with, as a result of its serial
port being broken and its lack of PCMCIA.

I actually had _less_ luck getting PLIP to work in 2.0.35... it took
a lot of fooling around with module options and load order to get both PLIP
and the printer to work properly. I'm still not certain I can get it to boot
clean and come up with everything working without manual intervention, but
hopefully, the next time I reboot the 2.0 machine, it'll be into 2.2.0, and
I won't have that problem any more.

1.2.13 was simple and straightforward, but that's primarily because
it only has the one parallel port, so I don't have to worry about making
sure the printer works, too.

---
John Campbell
jcampbel@lynn.ci-n.com


QotD:
 Customer: "I'm running Windows '95."
 Tech: "Yes."
 Customer: "My computer isn't working now."
 Tech: "Yes, you said that."


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/