Bug 905633

Summary:	YaST2 - Printer - Add Printer: Does not detect directly connected printer on parallel port
Product:	[openSUSE] openSUSE Distribution	Reporter:	Paul Tannington <paul.pgp-7>
Component:	YaST2	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	jsmeix
Version:	13.2
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 13.2
Whiteboard:
Found By:	Community User	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Paul Tannington 2014-11-15 12:20:14 UTC

YaST2 > Printer > Add
Does not detect directly connected printer on the parallel port.


To reproduce:

Connect a printer to the parallel (LPTn) port.
Switch the printer on.
Start YaST2
Select 'Printer'
Select 'Add'

Result:
Printer is not detected.


This appears(?) to be due to module "lp" not being loaded.

If prior to attempting to add the printer a "modprobe lp" is executed, then YaST2 detects the printer and it is possible to complete the installation.

Comment 1 Johannes Meixner 2014-11-17 10:56:49 UTC

As far as I know installing the parallel-printer-support package
should make the "lp" module be loaded automatically.

For details see bug#673845

*** This bug has been marked as a duplicate of bug 673845 ***

Comment 2 Johannes Meixner 2014-11-17 11:04:42 UTC

FYI:
See also "Parallel port printers do no longer work out of the box" at
https://en.opensuse.org/Archive:Printing_News

Comment 3 Paul Tannington 2014-11-17 11:40:33 UTC

Thanks for the information.

FYI package "parallel-printer-support" was installed.

There is a brief discussion of this problem on the openSUSE user forum:
https://forums.opensuse.org/showthread.php/502578-quot-Lost-quot-parallel-port-%28LPT%29-after-install-of-13-2

I now have the printer installed and working, so I guess unless anyone else reports this it can remain as closed/resolved.

Comment 4 Johannes Meixner 2014-11-18 11:44:19 UTC

For the log:

On my openSUSE 13.2 system (virtual KVM machine)
automated loading of the "lp" kernel module seems to work:
----------------------------------------------------------------------------
[after reboot]

# ls -l /dev/lp*
crw-rw---- 1 root lp 6, 0 Nov 18 08:54 /dev/lp0
crw-rw---- 1 root lp 6, 1 Nov 18 08:54 /dev/lp1
crw-rw---- 1 root lp 6, 2 Nov 18 08:54 /dev/lp2
crw-rw---- 1 root lp 6, 3 Nov 18 08:54 /dev/lp3

# file /dev/lp0
/dev/lp0: character special (6/0)

# lsmod | egrep 'parport|lp'
parport_pc             41414  0 
parport                46395  2 ppdev,parport_pc

# echo -en "" >/dev/lp0
-bash: /dev/lp0: No such device or address

# lsmod | egrep 'parport|lp'
lp                     17759  0 
parport_pc             41414  0 
parport                46395  3 lp,ppdev,parport_pc

f74:~ # dmesg | grep lp
... lp: driver loaded but no devices found

----------------------------------------------------------------------------

An error like "/dev/lp0: No such device or address" is expected
because I have nothing connected at /dev/lp0.

But it shows that accessing the /dev/lp0 device node
results automated loading of the "lp" kernel module.