I am trying to get a Digital PC 5510, running SuSE 6.2 (kernel 2.2.10),
connected to a Canon Bjc-4200 through the built-in parallell port
According to the "Linux printing support database" this printer is
listed as "Works perfectly", and as using the bjc600 GhostScript
driver:
http://www.picante.com/~gtaylor/pht/show_printer.cgi?recnum=60512
So what I did was to connect the parallell port cable to the only
place I found that fit on the back of the PC, install a printer with
the bjc600 driver, connected to /dev/lp0, using YaST, as mentioned
here
http://www.picante.com/~gtaylor/pht/current/pht-8.html#ss8.3
I then tried printing ascii files to this printer, like eg.
lpr .kderc
What happens then if I immediately tries
lpq
is that I get messages like
lp is ready and printing
Rank Owner Job Files Total Size
active root 5 .kderc 264 bytes
If I try this again a little bit later, the message is gone, without
anything appearing on the printer or even any lamps on the printer
blinking.
I have found no logs under /var/spool/lpd/ or /var/log/ of what's
happening.
I have tried different printing queues like "ascii", "lp1", and "lp2"
with the same result.
I have tried cat'ing text files to the lp devices like this:
doohan:~ # cat .kderc >/dev/lp0
doohan:~ # cat .kderc >/dev/lp1
bash: /dev/lp1: Device not configured
doohan:~ # cat .kderc >/dev/lp2
bash: /dev/lp2: Device not configured
Nothing happened and no lamps blinked.
I have tried running the tunelp command:
doohan:~ # tunelp -s /dev/lp0
/dev/lp0 status is 255, out of paper, on-line
doohan:~ # tunelp -s /dev/lp1
/dev/lp1: Device not configured
doohan:~ # tunelp -s /dev/lp2
/dev/lp2: Device not configured
But I get the same response from /dev/lp0, whether the printer is
turned on or off, so it's not a message I trust much.
/var/log/messages have the following messages about the parport, which
is the only messages I have about the parport, and came into the log
at the same point as I first tried to define the printer in YaST:
Jun 18 13:12:11 doohan kernel: 0x378: CTR: wrote 0x0c, read 0xff
Jun 18 13:12:11 doohan kernel: 0x378: DATA: wrote 0xaa, read 0xff
Jun 18 13:12:11 doohan kernel: parport0: PC-style at 0x378 [SPP,PS2]
Jun 18 13:12:11 doohan kernel: parport0: no IEEE-1284 device present.
Jun 18 13:12:11 doohan kernel: lp0: using parport0 (polling).
There seems to be at least one module loaded that has something to do
with the parallell port:
doohan:~ # lsmod
Module Size Used by
parport_probe 2980 0 (autoclean)
parport_pc 5600 1 (autoclean)
lp 5184 0 (autoclean)
parport 6788 1 (autoclean) [parport_probe parport_pc lp]
ppp_deflate 38032 0 (autoclean)
bsd_comp 3432 0 (autoclean)
ppp 19960 0 (autoclean) [ppp_deflate bsd_comp]
slhc 4160 0 (autoclean) [ppp]
ip_masq_ftp 2320 0
sd_mod 15408 0 (autoclean) (unused)
3c59x 18440 1 (autoclean)
tulip 30080 1 (autoclean)
serial 41940 0 (autoclean)
memstat 1412 0 (unused)
nls_iso8859-1 2024 1 (autoclean)
But, as I said, nothing happens when I try to print a file. My
problem is that I don't know if this is caused by problems in the
printer spooler? Problems in the parport driver? Physical problems
with the parport? Problems with the cable? Problems with the
printer? Wrong /dev/lpx? (/dev/lp0 seems to be the only one working,
so maybe not) Wrong connection for the parallell port? (Unlikely,
since this is the only parallell port connector I found on the box.
But you never know with this built-in stuff)
Any hints as how to narrow down the search will be highly appreciated!
Thanx!
- Steinar
-- 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 Jun 18 2000 - 13:12:13 EDT