I had several problems with my HP LaserJet 1018 and Gentoo (using driver foo2zjs from author's site). The problem is, I can't get it working unless I RESTART COLDPLUG. I have it tested!! If no coldplug restart is done, printer refuses to work, (saying in dmesg things like this: drivers/usb/class/usblp.c: usblp0: failed reading printer status. If I restart coldplug, it suddenly detects the printer and upload the firmware: (This is shown the place you do a /etc/init.d/coldplug restart): StormByte ginta # /etc/init.d/coldplug restart * Service coldplug stopping * WARNING: you are stopping a boot service. * Service coldplug stopped * Service coldplug starting /etc/hotplug/usb/hplj1018: loading HP LaserJet 1018 firmware /usr/share/foo2zjs/firmware/sihp1018.dl to /dev/usb/lp0 ... /etc/hotplug/usb/hplj1018: ... download successful. * Service coldplug started I would like to have it working WITHOUT restarting (Why do I need to be root (to restart this service) to print pages? Thanks. If you need more info or attachments, please request it.
no idea. I know that the upstream version is issues there and thus have replaced this part in the Gentoo ebuild. When you are using the upstream version deliberately you are on your own, sorry
mmm.. this means that if I prove to have same problem with the portage version of foo2zjs, I could reopen this thread?
you probably will not manage to uninstall the upstream version since you did not install it with portage. Only portage keeps track of all installed files. but yes, you can reopen it. Be specifically sure to remove the /etc/hotplug/usb/hplj1018 when you want to use the portage version
Ok, last thing before I manage to try again. Maybe downloading source again and doing a make uninstall could remove driver? Thanks
yeah could work. Actually good idea - do it that way
I reopen this bug, because time after closing this thread (and marked it as upstream), I formatted and reinstalled system, this time, using foo2zjs ebuild. The behaviour and the bad functioning is present as well with "udev" USE enabled. In case of the ebuild: My printer *only* works when I plug in and turn power on *before* booting machine. In boot process it recognizes it and charges the firmware correctly. But, if I plug in printer in any other time with system fully booted, it charges firmware (or attempts to do so, because I can hear same sounds coming from printer), but printer refuses to print anything. I can't even do "cat /lib/firmware/sihp1018.dl >/dev/usb/lp0 (it simply hangs a little in 'konsole' and does not do anything despite /dev/usb/lp0 exists and printer has been recognized according to dmesg). The workarround I have is to emerge it without udev flag, and manually cat firmware to printer node. I have read in the internet that udev (or hotplug/coldplug) scrips needs a sleep before attempting to load firmware to allow the printer recognition process finish, and after load firmware, but I have no tested with this ebuild version of foo2zjs.
ping?
can you please give me a patch? I do not want to sleep just for fun and I do not know how to detect how long to sleep. Best thing would be to do it in a for-loop and wait for something to show up in dmesg or a devce node to come up.
Unmerge hotplug and coldplug, upgrade to latest stable udev-103 if you haven't do so yet, and try again.
I had version 087-r1 of udev, I synced the tree and I still get this version as last stable one (for amd64), I add the ~amd64 keyword to this and I test. (I'll post another comment for results)
Ok, despite I had to delete and recreate printer to have it working, that version of udev fix this bad behaviour, but, it isn't stable in amd64 yet. Take this bug into account when to its status to stable as soon as possible. Thanks!
Sorry, late modifications problems: Take this bug into account when to its status to stable as soon as possible. WOULD MEAN: Take this bug into account to change its status to stable as soon as possible.
I reopen this bug because of udev is not now in IUSE (is as RDEPEND inside of ebuild) and I plug printer, but I don't have firmware loading (I have to load it manually).
*** This bug has been marked as a duplicate of 147006 ***
