Parallel Port Problems

For discussing Linux compatible (or not) devices

Moderators: ChrisThornett, LXF moderators

Parallel Port Problems

Postby TonyBradley » Fri Sep 13, 2013 9:43 am

I can't use my parallel printer

The (I think) relevant output of lspci -vvv is...

00:08.0 Parallel controller: NetMos Technology PCI 9865 Multi-I/O Controller (prog-if 03 [IEEE1284])
Subsystem: Device a000:2000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at efa0 [size=8]
Region 1: I/O ports at ef88 [size=8]
Region 2: Memory at febf7000 (32-bit, non-prefetchable) [size=4K]
Region 4: Memory at febf6000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>

In response to Netz, when I say "can't use", I mean the printer simply doesn't respond in any way. It and the cables are working, as I've used them with an old non-Linux box.

A little further info that may shed further light is the following result of grepping dmesg for parport...

[ 6.317307] parport_pc 00:08: reported by Plug and Play ACPI
[ 6.317356] parport0: PC-style at 0x378, irq 5 [PCSPP]
[ 31.039493] lp0: using parport0 (interrupt-driven).

It looks like the printer is assigned to parport0, which I assume to be the motherboard parallel port.. How can I assign it either parport_pc or parport0?

Any ideas/suggestions please?
Last edited by TonyBradley on Sat Sep 14, 2013 12:15 pm, edited 3 times in total.
TonyBradley
 
Posts: 22
Joined: Thu Jul 13, 2006 1:40 pm
Location: Plymouth

Postby nelz » Fri Sep 13, 2013 10:27 am

What does "can't use" mean? Can you set it up or not? Once set up, what happens when you try to use it? Any error messages /var/log/cups? What distro are you using? Which printer is it? you haven't given us much (well, anything) to go on.

See the READ THIS FIRST sticky thread.
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)
User avatar
nelz
Site admin
 
Posts: 8497
Joined: Mon Apr 04, 2005 11:52 am
Location: Warrington, UK

Postby wyliecoyoteuk » Fri Sep 13, 2013 3:41 pm

Most common cause of failure is BIOS settings.
Parallel port can be EPP, EPC, or standard. (From what I can recall, I haven't seen a parallel port printer for years).
If you have the wrong one selected, it won't work.
try each in turn.
The sig between the asterisks is so cool that only REALLY COOL people can even see it!

*************** ************
User avatar
wyliecoyoteuk
LXF regular
 
Posts: 3454
Joined: Sun Apr 10, 2005 10:41 pm
Location: Birmingham, UK

Postby ferrari » Mon Sep 16, 2013 12:34 am

What is reported by
Code: Select all
lsmod |grep par

For reference, I get
Code: Select all
parport_pc             37266  1
parport                46311  3 lp,ppdev,parport_pc


Assuming the necessary modules are loaded, with your printer connected, try running the CUPs parallel backend manually like this
Code: Select all
/usr/lib/cups/backend/parallel

Is the printer detected?
ferrari
LXF regular
 
Posts: 142
Joined: Tue May 03, 2005 11:09 am


Return to Hardware

Who is online

Users browsing this forum: No registered users and 0 guests