Bug 132793 - Parallel port is not connected
Summary: Parallel port is not connected
Status: RESOLVED INVALID
: 132792 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: 64bit SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-08 20:11 UTC by Michael Lanczak
Modified: 2005-11-09 13:17 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Lanczak 2005-11-08 20:11:40 UTC
The connection of the parallel port is not standard after installation of LINUX.
First you must open the data /etc/modprobe.conf and remove the commentary sign '#' in line 'options parport_pc io=0x378 irq=none,none'for driving printers on the parallel port.
You must mind, that I am a professional computer user and programer and have no problems to find such a data like "/etc/modprobe.conf" with the register with correct lines. But a normal computer user, a layman must get many problems here!
Comment 1 Martin Lasarsch 2005-11-09 13:16:42 UTC
hm, works for me:

d159:~ # procinfo | grep parp
irq  7:         0 parport0 

d159:~ # grep parp /proc/ioports
0378-037a : parport0

d159:~ # grep parp /etc/modprobe.conf
# Load lp after parport
install parport /sbin/modprobe -i parport && /sbin/modprobe lp
alias parport_lowlevel    parport_pc
# options parport_pc io=0x378 irq=none,none
# options parport_pc io=0x378,0x278  irq=none,none

i also talked with our printer maintainer, this could happen, it depends on the hardware. I searched the bugzilla for more problems like this, you are the first one. So you need only to uncomment the line if you have problems with the parport, means autoprobing is not working.
Comment 2 Martin Lasarsch 2005-11-09 13:17:05 UTC
*** Bug 132792 has been marked as a duplicate of this bug. ***