On 08/03/2010 02:47 PM, Mario Daniel Carugno wrote: > Yes, that's all i do to configure the printer. > Now I want to automatize the removal of the module after i turn on the printer. > If there's a rule that loads the module when the printer is turned on, > I guess there must be a way to catch that rule to disable the module > loading. > > 2010/8/3 vlad <vla@xxxxxxxxxxx>: >> Hello, >> On Tue, Aug 03, 2010 at 09:52:05AM -0300, Mario Daniel Carugno wrote: >>> Thanks for the help >>> I don't use backlist because in the wiki says so. >>> >>> In http://wiki.archlinux.org/index.php/CUPS_printer-specific_problems#LaserJet_1020 >>> i can read: >>> >>> "Ensure that the usblp module is not blacklisted in the MODULES array >>> of /etc/rc.conf" >>> >>> Just in case, I'll try it anyway. >>> Thanks >>> >> There's clearly described what you have to do. >> " >> ... >> Ensure that the CUPS daemon is running and added to the /etc/rc.conf >> file: >> # /etc/rc.d/cups start >> File: /etc/rc.conf >> DAEMONS=(... cups crond ...) >> >> Now plug in the USB printer and turn it on. The printer will whirl, >> pause, then whirl once more as the firmware is uploaded. Now remove the >> usblp module: >> # rmmod usblp >> Note: The usblp module must be removed after the firmware is loaded to >> the printer, and before any printing job is submitted. >> " >> As I understand it there is no way to automatize this. >> -- >> > Ok I see your problem, you could try to do what someone suggests in the thread referenced in the wiki: "You would have to guarantee the sequence load usblp/call hplj1000 script/unload usblp. IMHO to avoid race conditions, it would be better to incorporate load/unload usblp into the hplj1000 script itself: load usblp before the script looks for an lp* device, and unload usblp after the firmware has been successfully copied." If that proves to work then let the packager know about the workaround and maybe submit a patch. One last thing, try not to top post, it makes reading the thread harder. -- Mauro Santos
