Bugzilla – Bug 104874
module "lp" unloaded during startup of YaST printer config
Last modified: 2005-09-02 11:35:14 UTC
I installed beta1 on x86_64 (on caps.suse.de). I connected a HP DeskJet 990C to the parallel port. The "lp" module becomes unloaded during startup of "yast2 printer" so that even manual setup of a parallel port printer doesn't work (in particular printing of testpage cannot work) until I do manually "modprobe lp". Again this is caused by hwinfo (see the old bug 64412, in particular comment number 57): ----------------------------------------------------------------- caps:~ # lsmod | egrep 'parport|lp' lp 30912 0 parport_pc 62192 1 parport 61324 2 lp,parport_pc usblp 31488 0 usbcore 157996 3 usblp,ohci_hcd caps:~ # hwinfo --printer &>/dev/null caps:~ # lsmod | egrep 'parport|lp' parport_pc 62192 0 parport 61324 1 parport_pc usblp 31488 0 usbcore 157996 3 usblp,ohci_hcd ----------------------------------------------------------------- See also bug #102932 which may be the same problem.
*** Bug 102932 has been marked as a duplicate of this bug. ***
Happens als on i686 architecture, see bug #102932. => Assume it happens on any architecture (which has a parallel port).
lp module unloaded when execute SCR::Read (.probe.printer); this is problem of hwinfo (hwinfo --printer makes the same reason)
Sure it unloads lp. AFAIK it's still necessary to reload parport_pc to trigger parport device probing (correct me if I'm wrong). So what should it do? Load lp again? BTW, Johannes, why didn't you drop me a note in bug 64412??? I surely can't fix bugs I don't know about.
As far as I know it is still true that parport device detection happens only when the parport/parport_pc are loaded. But I am no kernel module developer. Therefore we may either rely on what was detected when those modules are loaded during booting or we may like to force re-detection by unloading lp, parport_pc, parport and re-loading parport, parport_pc, lp. Steffen, I remembered bug #52548 which is about 9.1 where it seemed that hwinfo is not responsible to re-load the lp module because it was loaded when there was a device node access. But since 9.1 things are changing so much that I don't know which component is at the moment responsible for what.
Now that we have that dynamic device thing, autoloading no longer works. I'll change hwinfo to load lp, too, then. Let's see what that gives.
done
*** Bug 105920 has been marked as a duplicate of this bug. ***
*** Bug 105379 has been marked as a duplicate of this bug. ***
*** Bug 113558 has been marked as a duplicate of this bug. ***