How to Install Your Printer/Scanner in Puppy

Problems and successes with specific brands/models of printers
Message
Author
User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

Re: Scan Plugin

#361 Post by rcrsn51 »

MagicZaurus wrote:I have the plugin pet installed. I didn't try without it. But if it is useful for you, I can uninstall the pet tomorrow and try again.
Don't do that. The plugin PET contains some files that are also in the hplip_scan PET. So deleting the former may break the latter.

I built it that way to support a group of HP printer-only units that need those files but don't need hplip_scan.

I need to re-think this situation. In a mainstream Linux like Ubuntu, this is academic because you would automatically install 100% of HPLIP and all its dependencies whether you need them or not.

But you can try this:

Go into the folder /usr/share/hplip and temporarily rename the folders "prnt" and "scan". See what still works.

Thanks for your help with this.

MagicZaurus
Posts: 107
Joined: Mon 05 Jan 2009, 17:35

Test Result

#362 Post by MagicZaurus »

Here the result of my test. It seems both the prnt & scan folders are required.

1) Rename prnt folder to no_prnt & scan to no_scan. Printing and scanning doesn't work anymore. Peasyscan reports "Failed to open device. ... Failure during Device I/O". For printing the job gets stuck and can be seen in the CUPS web interface. I canceled the print job there.

2) Rename no_prnt to prnt. Printing works now, but scanning doesn't work with the same error message.

3) Rename no_scan to scan. Printing and scanning works normal.

In case you want to test anything else, then just let me know.

Your hplip pets are really nice and small. Thanks a lot for the time you spent to create them. Getting this printer working was much easier than I expected and I never expected that scanning will work.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#363 Post by rcrsn51 »

Excellent. I don't understand why Starhawk's colour Postscript Laserjet above does NOT need the plugin while yours does. Maybe because yours is an enterprise model with more features.

BTW, I just discovered that the new hpaio scanner backend can now auto-detect networked scanners! This means that you should not need a PeasyScan config file to find it, and that Xsane should work.

Run: scanimage -L

Is your model detected? Then run PeasyScan, but click Cancel on the initial config file window. This will make PeasyScan search for printers instead of using a config file.

starhawk
Posts: 4906
Joined: Mon 22 Nov 2010, 06:04
Location: Everybody knows this is nowhere...

#364 Post by starhawk »

It's actually starhawk's father's printer ;) I was just asked to test it.

As for why one needs a plugin and one does not... HP is a bunch of bastards, you know :P especially when they go to price ink.

bark_bark_bark
Posts: 1885
Joined: Tue 05 Jun 2012, 12:17
Location: Wisconsin USA

#365 Post by bark_bark_bark »

starhawk wrote:It's actually starhawk's father's printer ;) I was just asked to test it.

As for why one needs a plugin and one does not... HP is a bunch of bastards, you know :P especially when they go to price ink.
For the price of ink, you could get a new printer that has ink in it.
....

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#366 Post by rcrsn51 »

@starhawk and bark_bark_bark:

I was in the middle of a technical discussion with MagicZaurus. If you want to take cheap shots at HP, please start your own thread.

MagicZaurus
Posts: 107
Joined: Mon 05 Jan 2009, 17:35

Autodetect HP Network Scanners

#367 Post by MagicZaurus »

Hi rcrsn51,

here the result.
root# scanimage -L
device `hpaio:/net/officejet_6500_e710n-z?ip=xxx.xxx.xxx.xxx&queue=false' is a Hewlett-Packard officejet_6500_e710n-z all-in-one
That OfficeJet is another AOI device in my boss office. The LaserJet seems to not respond. I don't know if that is due to some setting on the printer. The admin interface on the printer has been locked with a password by our IT. But I just printed a document and that is fine, so the connection to the printer is ok.

Peasyscan also only detects the OfficeJet and not the LaserJet.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#368 Post by rcrsn51 »

Interesting.

When you set up the printer, was it auto-detected by CUPS or did you have to manually select the socket protocol?

With my Laserjet Pro MFP m127fn, CUPS does NOT auto-detect, but scanimage -L DOES.

In any case, it's good to know that you can access the scanner through a config file.

Bill

MagicZaurus
Posts: 107
Joined: Mon 05 Jan 2009, 17:35

CUPS vs Scanimage

#369 Post by MagicZaurus »

Here it is the other way around.

CUPS did automatically discover the LaserJet, but scanimage -L doesn't.

Just had the idea to do a port scan on the LaserJet
xxx.xxx.xxx.xxx : 80
xxx.xxx.xxx.xxx : 81
xxx.xxx.xxx.xxx : 82
xxx.xxx.xxx.xxx : 83
xxx.xxx.xxx.xxx : 443
xxx.xxx.xxx.xxx : 515
xxx.xxx.xxx.xxx : 631
Port 631 is CUPS. So maybe that is the reason why CUPS can autodetect the printer over the network. Now would be the question which port scanimage -L is using.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#370 Post by rcrsn51 »

Scanimage -L works by polling all the backends in /etc/sane.d/dll.conf and identifying which ones give a response. The method varies with each backend.

Some backends that are network-enabled (like Epson epkowa) work correctly this way.

Old versions of the hpaio backend did NOT detect networked units. It now has a discovery feature, but it apparently can be blocked by something in the scanner. So your boss's unit is detected but the main unit is not.

I am surprised that this block can be bypassed by supplying the URI via the PeasyScan config file.

I don't know how hpaio searches for remote scanners - possibly through some high-numbered port.

[Edit] I own an HP Envy inkjet with WiFi Direct. It can network scan via a config file, but scanimage -L does NOT detect it. Maybe hpaio discovery only works with certain models.

MagicZaurus
Posts: 107
Joined: Mon 05 Jan 2009, 17:35

Printer Discovery

#371 Post by MagicZaurus »

I have downloaded the HPLIP source. It seems the code for device discovery is in /scan/sane/hpaio.c. There is a function

Code: Select all

static int DevDiscovery(int localOnly)
My knowledge of C programming is not so good that I really understand what the code does, so I can only read the comments in the code. It seems there are 2 ways of network discovery implemented. First looking if CUPS has a print queue for a HP network printer and second using discovery of a "Bonjour" service. That "Bonjour" seems to be some Apple thing. Maybe not all printers support this Apple protocol.

At the same time it seems that for my CUPS the hpaio backend is not able to detect that I already have the printer installed.

Another possibility is that a firewall in our network router or switch blocks this "Bonjour" port, but actual scanning uses some other port which is open.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

Re: Printer Discovery

#372 Post by rcrsn51 »

MagicZaurus wrote:It seems there are 2 ways of network discovery implemented. First looking if CUPS has a print queue for a HP network printer
And yet scanimage -L could detect your boss's printer for which you do NOT have a CUPS print queue.

Who knows?

MagicZaurus
Posts: 107
Joined: Mon 05 Jan 2009, 17:35

#373 Post by MagicZaurus »

The discovery has this sequence.

Code: Select all

/* Look for local all-in-one scan devices (defined by hpmud). */
/* Look for Network Scan devices if localonly flag if FALSE. */
/* Look for all-in-one scan devices for which print queue created */
        cnt = GetCupsPrinters(&cups_printer);
/* Discover NW scanners using Bonjour*/
        bytes_read = mdns_probe_nw_scanners(message, sizeof(message), &cnt);
In my CUPS log file I can see that somebody (scanimage -L) wants to get the installed printers, but it seems CUPS returns an empty list as response, even I have the 475dn installed. (Need to switch on Debug Mode in CUPS web interface.)

If the device can be discovered via the Bonjour service depends on the printer. The 475dn has Bonjour support, but it can be deactivated or password protected in the printer settings.

At least I would conclude that discovery happens on a different port than scanning later on and this is why even the device cannot be discovered it still works to scan from the device by providing the uri.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#374 Post by rcrsn51 »

I would assume that HPLIP is built against the latest mainstream Linux, like Ubuntu, and the latest CUPS. So it shouldn't be a surprise if it doesn't work exactly right in Puppy.

It would be interesting to run an Ubuntu client and see what happens.

bh56
Posts: 55
Joined: Tue 07 Apr 2009, 08:04

Installing a Canon Lide 120

#375 Post by bh56 »

Hope this is the right thread.
The Lide 120 is detected using lsusb but scanimage -l reports no connected scanners.
The sane webpage (http://www.sane-project.org/) lists the lide 120 as unsupported using the genesys 1.0.63 backend.
However, the same scanner is listed as having complete support using the same backend in the git or development branch.
I've tried adding:
# Canon LiDE 120
usb 0x04a9 0x190e
to /etc/sane.d/genesys.conf but still no go.
Any idea on how to get the scanner going?
Thanks
Brendan

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#376 Post by rcrsn51 »

You didn't state which Puppy you are using, but the newest version of the gensys backend is here. Try adding the USB ID code to this one.

If it doesn't work, I can build the development version for you.

Please post your next message in the other thread.

tenochslb

HP 6200s OFFICE JET ALL IN ONE - scanner not working

#377 Post by tenochslb »

sane log:

Code: Select all

root# sane-find-scanner -verbose
This is sane-find-scanner from sane-backends 1.0.26git

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/sg0... failed to open (Invalid argument)
checking /dev/sg1... failed to open (Invalid argument)
 /dev/sg2... failed to open (Invalid argument)
checking /dev/sg3... failed to open (Invalid argument)
checking /dev/found USB scanner (vendor=0x03f0 [HP], product=0x4b11 [Officejet 6200 series]) at libusb:002:005
could not fetch string descriptor: Pipe error
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
done... failed to open (Invalid argument)
checking /dev/sg5... failed to open (Invalid argument)
checking /dev/sg6... failed to open (Invalid argument)
checking /dev/sg7... failed to open (Invalid argument)
checking /dev/sg8... failed to open (Invalid argument)
checking /dev/sg9... failed to open (Invalid argument)
checking /dev/sga... failed to open (Invalid argument)
checking /dev/sgb... failed to open (Invalid argument)
checking /dev/sgc... failed to open (Invalid argument)
checking /dev/sgd... failed to open (Invalid argument)
checking /dev/sge... failed to open (Invalid argument)
checking /dev/sgf... failed to open (Invalid argument)
checking /dev/sgg... failed to open (Invalid argument)
checking /dev/sgh... failed to open (Invalid argument)
checking /dev/sgi... failed to open (Invalid argument)
checking /dev/sgj... failed to open (Invalid argument)
checking /dev/sgk... failed to open (Invalid argument)
checking /dev/sgl... failed to open (Invalid argument)
checking /dev/sgm... failed to open (Invalid argument)
checking /dev/sgn... failed to open (Invalid argument)
checking /dev/sgo... failed to open (Invalid argument)
checking /dev/sgp... failed to open (Invalid argument)
checking /dev/sgq... failed to open (Invalid argument)
checking /dev/sgr... failed to open (Invalid argument)
checking /dev/sgs... failed to open (Invalid argument)
checking /dev/sgt... failed to open (Invalid argument)
checking /dev/sgu... failed to open (Invalid argument)
checking /dev/sgv... failed to open (Invalid argument)
checking /dev/sgw... failed to open (Invalid argument)
checking /dev/sgx... failed to open (Invalid argument)
checking /dev/sgy... failed to open (Invalid argument)
checking /dev/sgz... failed to open (Invalid argument)
  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2... failed to open (Invalid argument)
checking /dev/usb/scanner3... failed to open (Invalid argument)
checking /dev/usb/scanner4... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner7... failed to open (Invalid argument)
checking /dev/usb/scanner8... failed to open (Invalid argument)
checking /dev/usb/scanner9... failed to open (Invalid argument)
checking /dev/usb/scanner10... failed to open (Invalid argument)
checking /dev/usb/scanner11... failed to open (Invalid argument)
checking /dev/usb/scanner12... failed to open (Invalid argument)
checking /dev/usb/scanner13... failed to open (Invalid argument)
checking /dev/usb/scanner14... failed to open (Invalid argument)
checking /dev/usb/scanner15... failed to open (Invalid argument)
checking /dev/usbscanner... failed to open (Invalid argument)
checking /dev/usbscanner0... failed to open (Invalid argument)
checking /dev/usbscanner1... failed to open (Invalid argument)
checking /dev/usbscanner2... failed to open (Invalid argument)
checking /dev/usbscanner3... failed to open (Invalid argument)
checking /dev/usbscanner4... failed to open (Invalid argument)
checking /dev/usbscanner5... failed to open (Invalid argument)
checking /dev/usbscanner6... failed to open (Invalid argument)
checking /dev/usbscanner7... failed to open (Invalid argument)
checking /dev/usbscanner8... failed to open (Invalid argument)
checking /dev/usbscanner9... failed to open (Invalid argument)
checking /dev/usbscanner10... failed to open (Invalid argument)
checking /dev/usbscanner11... failed to open (Invalid argument)
checking /dev/usbscanner12... failed to open (Invalid argument)
checking /dev/usbscanner13... failed to open (Invalid argument)
checking /dev/usbscanner14... failed to open (Invalid argument)
checking /dev/usbscanner15... failed to open (Invalid argument)
found USB scanner (vendor=0x03f0 [HP], product=0x4b11 [Officejet 6200 series]) at libusb:002:005
could not fetch string descriptor: Pipe error
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
done
[/img]
Attachments
image.png
This is the sane version used
(34.35 KiB) Downloaded 595 times

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#378 Post by rcrsn51 »

SANE discovered the USB device. But have you installed a driver for it, like hplip_scan from the main page?

Tahrpup has SANE v1.0.23. It works fine with HPLIP. Installing a new SANE version just complicates matters.

What does the "scanimage -L" command say?

tenochslb

#379 Post by tenochslb »

rcrsn51 wrote: What does the "scanimage -L" command say?

It tells me that no devices were found. Yes I installed the printer and scanner pets from here:

http://www.mediafire.com/download/2uw6a ... 3.16.5.pet

printing works fine and it does use the hplite driver.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#380 Post by rcrsn51 »

tenochslb wrote:printing works fine and it does use the hplite driver.
Just to be clear, do you mean the hplip_print PET from here or the hplite package from another section?

Post Reply