Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Mar 2004 22:15:29 +1030
From:      Malcolm Kay <malcolm.kay@internode.on.net>
To:        Stephen Liu <satimis@icare.com.hk>, Kris Kennaway <kris@obsecurity.org>
Cc:        questions@freebsd.org
Subject:   Re: MAKEDEV question
Message-ID:  <200403082215.29256.malcolm.kay@internode.on.net>
In-Reply-To: <200403082339.33613.satimis@icare.com.hk>
References:  <200403081945.16907.satimis@icare.com.hk> <20040308052442.GA57973@xor.obsecurity.org> <200403082339.33613.satimis@icare.com.hk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Mar 2004 02:09, Stephen Liu wrote:
> - snip -
>
> > > # grep ppc0 /var/run/dmesg.boot
> > > ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0
> > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
> > > ppc0: FIFO with 16/16/7 bytes threshold
> > > ppbus0: <Parallel port bus> on ppc0
> > >
> > > I suppose lpt0 is supported.
> >
> > If your kernel detects it it will be listed in the dmesg:
> >
> > lpt0: <Printer> on ppbus0
> > lpt0: Interrupt-driven port
>
> Hi Kris,
>
> Turned on printer to make following tests
>
> # dmesg
> .....
> ppbus0: <HEWLETT-PACKARD DESKJET 690C> MLC,PCL,PML
> plip0: <PLIP network interface> on ppbus0
> lpt0: <Printer> on ppbus0
> lpt0: Interrupt-driven port
> ppi0: <Parallel I/O> on ppbus0
> ......
>
> ls -l /dev/lpt0
> crw-------  1 root  wheel   16,   0 Mar  8 22:48 /dev/lpt0
>
> It is there.
>
>
> I skipped following steps
>
> 1)
> # ./MAKEDEV port
>
> and
> 2)
> # lptcontrol -i -d /dev/lpt0
> (to set interrupt-driven mode for lpt0)
>
> and
> 3)
> # lptcontrol -p -d /dev/lpt0
> (to set polled-mode for lptN)
>
>
> Jumped to;
> # lptest > /dev/lpt0
> only strange symbols printed and printing continued without stop until =
I
> removed the paper tray.  Communication between printer and port seemed
> working
>

It could be that your printer does not understand plain ascii text. What =
is
the make and model.

The other possibility is that there is something wrong in the communicati=
ons
path -- a dud or incorrectly wired cable.

Malcolm Kay



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403082215.29256.malcolm.kay>