Description of problem:While sending data to parallel port "Invalid argument”
Version-Release number of selected component (if applicable):RHEL 6.0 server 64 bit
Steps to Reproduce:
1. I tried “echo hello > /dev/parport0 ” to send data to parallel port ,I get the following error message “echo : write error :Invalid argument”. Sending data to “/dev/lp0” gives following error message “/dev/lp0:No such device or address”.
2. It works on RHEL-5.5 using /dev/lp0 device
Am I missing anything here or do I need to do any configuration for RHEL 6.0 to send data to parallel port.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
This request was erroneously denied for the current release of Red Hat
Enterprise Linux. The error has been fixed and this request has been
re-proposed for the current release.
Is there any update for this problem? The latest RHEL6 updates do not resolve it.
elrepo.org has the missing driver packaged as a kmod (kmod-lp) for rhel6:
as documented in Michael's thread here:
Patch(es) available on kernel-2.6.32-156.el6
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
This update introduces parallel port printer support for Red Hat Enterprise Linux 6.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
Removing external tracker bug with the id 'DOC-56684' as it is not valid for this tracker