LBP310x support #13
Comments
|
Hi vasishath, Please could you report the printer state reply? Regards, |
|
Hi Laura, Thanks for your reply.. Thanks |
|
Yes. See, for example, https://ask.wireshark.org/questions/11054/analysing-usb-traffic
…On Saturday, January 14, 2017 11:59:19 PM EST Vasishath Kaushal wrote:
Hi Laura,
Thanks for your reply..
How am i supposed to get that ? Will usbmon on wireshark do this ?
Thanks
|
|
All you need is enable the CUPS error log. You may do this with the http CUPS interface at localhost:631 and inpsect the error log from here. Or may do this by hand: search for 'LogLevel' section in /etc/cups/cupsd.conf and change it to "debug" (default is "info"). Then restart cups service and you'll find all captdirver communications in '/var/log/cups/error_log' file. |
|
here is cups error log when I try to print using LBP3108 D [31/May/2021:12:30:50 +0800] [Job 85] Applying default options... |
|
Something is wrong with your Ghostscript, not with captdriver. Is the PPD file readable? |
yes, it's readable |
|
Actually, I think our driver is at fault here, at time of writing. I noticed this in the log posted by @cyanogenic : We have an unknown printer error. Captdriver does not yet recognise the LBP3100/3108/3150 printer family. We have printed to the LBP 3010, a different but similar printer, with commits d6c5861 and earlier. @cyanogenic: try adding this line at the end of This will attempt to reuse LBP3010 code to support your LBP3108. I don't have an LBP3100, but I am making a wild guess based on comparisons between the specifications for the 3010 and the 3100. The printers seem to have identical specifications except for the printing speed. Please be aware that the lbp3010 ops have been largely untested since d6c5861. If the above hack doesn't work, try checking out d6c5861, adding the |
It did work! thanks a lot |
|
Yes, it treats every page as a single job (now). The reason is, multi-page printing is buggy and the printer tends to hang. You can try to edit the code to re-enable multi-page printing. YMMV. |
|
Which PPD file did you use @cyanogenic, As for the slow printing, I think it is also due the pipeline from document to device: When you print from a vector or mixed vector and raster document (this includes PDFs, word processor documents and web pages), GhostScript is used by CUPS to render a raw raster from your document. This raw raster is then taken by captdriver and converted to the Hi-SCoA format accepted by the printer. This goes the same way for apps that output rasters directly, except that GhostScript is in such cases not required. There are two bottlenecks here: GhostScript (which can be really slow at times) and Just take a look inside I am thinking of a workaround in which we pre-compress every page at the start of the print job, or at least a few at a time. This will certainly significantly increase the time needed to set up a print job and the amount of memory used. However, the delay between pages can be greatly reduced. Those who need to print multiple copies of complex pages, while running the printer in cold weather*, will benefit most.
|
|
In early version of the driver I had issues with multi-page printing. The printer froze after first page and required hard reset (power off). As a workaround I added full reset after each page ("end job - start job"). It was terribly slow but at least it worked. |
I use ppd for lbp3000. |
|
@cyanogenic (or anyone reading this): if you still have access to your LBP3100, would you be ok with posting the If you have been printing with captdriver with debug logging on, just run If nothing appears, try the older logs using Thanks in advance! |
I tried this driver with my LBP3108 (common with LBP 3100 and 3150) and its reporting the printer status correctly i.e idle, paused or turned off etc. But when i try to print a test page, it stops at "rendering complete". I tried restarting the printer but it didn't help. I am a developer and own this printer and am ready to help you with any debug/traces of the CAPT commands exchanged between the PC and printer.
I tried this on Arch Linux.
Thanks a lot.
The text was updated successfully, but these errors were encountered: