Description of problem: This is ID Vendor 0x85a (Xircom) ID Product 0x3 (Portstation Paraller Port) connected thru usb. There are also ps/2 ports and usb ports working OK, however parallel port is not listed in any printing dialog. Automatic scannig for printer finds nothing, however modules parport, parport_pc, ppdev and lp are loaded correctly.
Do you have a printer connected?
The printers are connected and powered up. Tried with two different printers Kyocera FS-1600 and HP DeskJet 3820. HP DeskJet has also and USB port - connecting it thru USB works OK, but the parallel port is invisible to printing system. lpinfo -l -v shows nothing interesting in this case: Device: uri = scsi class = direct info = SCSI Printer make-and-model = Unknown device-id = location = Device: uri = http class = network info = Internet Printing Protocol (http) make-and-model = Unknown device-id = location = Device: uri = socket class = network info = AppSocket/HP JetDirect make-and-model = Unknown device-id = location = Device: uri = lpd class = network info = LPD/LPR Host or Printer make-and-model = Unknown device-id = location = Device: uri = ipp class = network info = Internet Printing Protocol (ipp) make-and-model = Unknown device-id = location = Device: uri = serial:/dev/ttyS0?baud=115200 class = serial info = Serial Port #1 make-and-model = Unknown device-id = location = Device: uri = https class = network info = Internet Printing Protocol (https) make-and-model = Unknown device-id = location = Device: uri = smb class = network info = Windows Printer via SAMBA make-and-model = Unknown device-id = location = Device: uri = hp class = direct info = HP Printer (HPLIP) make-and-model = Unknown device-id = location = Device: uri = hpfax class = direct info = HP Fax (HPLIP) make-and-model = Unknown device-id = location =
Does 'dmesg' say anything about it?
Before modprobe of parport and other modules, there is nothing about parport, after those modules are inserted only ppdev: user-space parallel port driver appears in dmesg.
Is this device supported by the kernel in any way? Sounds like it might not be. Changing component.
Honestly I do not know. My impression was, if the parport driver is inserted it is on purpose, therefore I was blaiming the CUPS. The hwdata usb.ids from linux-usb.org lists this device, but that's all I can say. I was expecting this was another USB to something converter. It is however not explicitely listed in: http://www.kernel.org/doc/Documentation/usb/usb-serial.txt In general USB-parallel converters should work for years: http://forums.whirlpool.net.au/forum-replies-archive.cfm/565307.html http://www.linuxforums.org/forum/redhat-fedora-linux-help/49553-printer-problem-using-usb-parallel-cable.html
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.