old-www/HOWTO/PLIP-4.html

42 lines
1.5 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>LINUX PLIP MINI-HOWTO: Kernel messages about the PLIP interface. </TITLE>
<LINK HREF="PLIP-5.html" REL=next>
<LINK HREF="PLIP-3.html" REL=previous>
<LINK HREF="PLIP.html#toc4" REL=contents>
</HEAD>
<BODY>
<A HREF="PLIP-5.html">Next</A>
<A HREF="PLIP-3.html">Previous</A>
<A HREF="PLIP.html#toc4">Contents</A>
<HR>
<H2><A NAME="s4">4. Kernel messages about the PLIP interface. </A></H2>
<P>After you've reconfigured and compiled the kernel with PLIP support enabled,
when you boot the system, if the kernel supports PLIP directly, or when you
load (later, see below) the PLIP module if you compiled PLIP as modules, you
should get something like this (numbers may differ):
<P>
<BLOCKQUOTE><CODE>
<PRE>
NET3 PLIP version 2.2 gniibe@mri.co.jp
plip1: Parallel port at 0x378, using assigned IRQ 7.
</PRE>
</CODE></BLOCKQUOTE>
<P>Depending upon your klogd and syslogd configuration the plip message could
have been stored in your system log files: don't panic if you don't see the
above message.
If you compiled PLIP as a module and lsmod shows that the plip module is
loaded, then it's enough.
<P>Please take notice of the interface name. Usually is plip1, but may be
plip0 or even plip2, plip3, and so on. It depends on the IO Address.
<P>
<HR>
<A HREF="PLIP-5.html">Next</A>
<A HREF="PLIP-3.html">Previous</A>
<A HREF="PLIP.html#toc4">Contents</A>
</BODY>
</HTML>