Hello ...anyone?
I am having a similar problem with my parallel port/printer : CUPS will not recognize my parallel port.
I am installing a HP LaserJet 5MP on RedHat 9
Here is some output...
[root@localhost share]# lpinfo -v
network socket
network http
network ipp
network lpd
direct scsi
serial serial:/dev/ttyS0?baud=115200
serial serial:/dev/ttyS1?baud=115200
serial serial:/dev/ttyS2?baud=115200
serial serial:/dev/ttyS3?baud=115200
serial serial:/dev/ttyS4?baud=115200
serial serial:/dev/ttyS5?baud=115200
serial serial:/dev/ttyS6?baud=115200
serial serial:/dev/ttyS7?baud=115200
serial serial:/dev/ttyS8?baud=115200
serial serial:/dev/ttyS9?baud=115200
serial serial:/dev/ttyS10?baud=115200
serial serial:/dev/ttyS11?baud=115200
serial serial:/dev/ttyS12?baud=115200
serial serial:/dev/ttyS13?baud=115200
serial serial:/dev/ttyS14?baud=115200
serial serial:/dev/ttyS15?baud=115200
serial serial:/dev/ttyS16?baud=115200
serial serial:/dev/ttyS17?baud=115200
serial serial:/dev/ttyS18?baud=115200
serial serial:/dev/ttyS19?baud=115200
serial serial:/dev/ttyS20?baud=115200
serial serial:/dev/ttyS21?baud=115200
serial serial:/dev/ttyS22?baud=115200
serial serial:/dev/ttyS23?baud=115200
serial serial:/dev/ttyS24?baud=115200
serial serial:/dev/ttyS25?baud=115200
serial serial:/dev/ttyS26?baud=115200
serial serial:/dev/ttyS27?baud=115200
serial serial:/dev/ttyS28?baud=115200
serial serial:/dev/ttyS29?baud=115200
serial serial:/dev/ttyS30?baud=115200
serial serial:/dev/ttyS31?baud=115200
direct usb:/dev/usb/lp0
direct usb:/dev/usb/lp1
direct usb:/dev/usb/lp2
direct usb:/dev/usb/lp3
direct usb:/dev/usb/lp4
direct usb:/dev/usb/lp5
direct usb:/dev/usb/lp6
direct usb:/dev/usb/lp7
direct usb:/dev/usb/lp8
direct usb:/dev/usb/lp9
direct usb:/dev/usb/lp10
direct usb:/dev/usb/lp11
direct usb:/dev/usb/lp12
direct usb:/dev/usb/lp13
direct usb:/dev/usb/lp14
direct usb:/dev/usb/lp15
network smb
When entering 'modprobe parport_pc", I get the following:
[root@localhost share]# modprobe parport_pc
/lib/modules/2.4.20-8/kernel/drivers/parport/parport_pc.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-8/kernel/drivers/parport/parport_pc.o: insmod /lib/modules/2.4.20-8/kernel/drivers/parport/parport_pc.o failed
/lib/modules/2.4.20-8/kernel/drivers/parport/parport_pc.o: insmod parport_pc failed
[root@localhost share]#
When I modprobe 'lp' and 'parport' , I get no response, even though 'lsmod' includes them in its list.
At this stage...the newbie says...."Help??"
![Confused](https://www.linuxquestions.org/questions/images/smilies/confused.gif)