Description of problem: It seems that udev names parallel ports /dev/parport? now, but cups expects /dev/lp? . I was able to work around this by making a hard link, but either cups or udev should change so that they expect the same names. Version-Release number of selected component (if applicable): udev-166-1.fc15.i686 cups-1.4.6-9.fc15.i686 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
/dev/parport* is not the correct device node. It is for low-level manipulation of the pins. The correct device node name is /dev/lp*. Hard-linking to /dev/parport* is not correct.
if you really need /dev/lp*, then: # MAKEDEV /dev/lp # cp -avr /dev/lp[0-9] /lib/udev/devices/
Or use USB :-)
My printer only has a parallel port connection; using USB won't work. There is still a bug here somewhere. Shouldn't udev be making a device for this automatically? If not, do we really expect normal users to be making their own device nodes?
I will note that after doing the above, the device creation is persistent across reboots.
The issue is unrelated to /dev/parport*. Udev does not provide any "dead" device nodes anymore by default, also not for /dev/lp*. In the past, these nodes have been used to trigger autoloading of the lp module on device node access. There are two options, either force-load lp on every bootup by adding a config file to: /etc/modules-load.d/ or do create a static device node in /lib/udev/devices/. The lp module does not support auto-loading/probing out-of-the-box, and udev dropped support/workarounds for _all_ the non-hotplug-aware subsystems. If such hardware is used on recent systems, it requires manual configuration step as described above.
That explains it, thanks Kay. I think this just needs mentioning in the release notes.
The release notes should be good enough. It would be nicer to catch this on upgrades or installs, but there are probably few people using parallel ports these days.
*** Bug 699052 has been marked as a duplicate of this bug. ***
Harald, if we want to package device nodes for /dev/lp as part of cups, what's the best way to do that?
I've added some lp device nodes to cups-1.4.6-17.fc16, FWIW.
> I've added some lp device nodes to cups That seems to solve the problem, doesn't it? At least it works for me now with an updated cups. Can't this be closed? (Maybe changing the component to "cups" first?)
This problem is experienced in the latest Fedora 16. Interestingly enough, the install worked perfectly, but the system lost connection to the printer with a printer applet warning popup that says "Printer 'printer name' may not be connected". It shows this every minute or so. How can it see the printer during install, but not after? Sounds like a clear continuing bug in the programming to me. Should one still have to do the manual config bit?
KitchM: the problem you are seeing seems to be different: whereas you were able to configure the printer but later saw a communication problem, the original bug reported here was that the communication channel just didn't even exist in the first place. Could you please report a separate bug so that we can diagnose what's going on? Thanks.
Tim Waugh: Good idea. Thanks. I did that.