sane-p5(5)

πŸ’… sane-p5 β€” the Primax PagePartner glow-up 🌸

okay so bestie, welcome to the sane-p5 page 🫢 this is the manual for the SANE backend for the Primax PagePartner, and yes it's exactly as niche and iconic as it sounds.


✨ NAME ✨

sane-p5 β€” the SANE backend for the Primax PagePartner, no cap πŸ’…


🌈 DESCRIPTION 🌈

so the sane-p5 library implements a SANE (Scanner Access Now Easy) backend, and what it does is give you access to the Primax PagePartner parallel port sheet fed scanner πŸŽ€ like it literally speaks to that scanner so you don't have to.

This backend handles 100, 150, 200, 300 and 600 dpi scan resolutions, in color and gray modes ✨ and real talk β€” the 600 dpi is actually 300x600 with lines enlarged to match the vertical resolution. yes queen, it's giving enlargement, not true 600 πŸ’€

EPP/ECP MODES ONLY β€” the current version of the backend uses only EPP or ECP mode to communicate with the scanner. It is recommended that you set your parallel port to EPP in BIOS with the current version of this backend πŸ™ˆ ECPEPP will only work if you use a 2.4 or 2.6 kernel with ppdev character device support. so like, check your kernel bestie, this is important πŸ’…

πŸ¦‹ DEVICE NAMES πŸ¦‹

This backend expects device names shaped like this:

port value

Where value is:

  • auto β€” autodetect all parallel ports and probe them for scanner πŸ‘‘ the lazy girl's dream
  • /dev/parport0 β€” uses the linux ppdev device. depending on the number of available parallel port, you have to use /dev/parport1, /dev/parport2, ... and so on πŸŽ€

You can rename any device using the

option name my_name

option ✨ and heads up: this option apply to the last port option. iykyk πŸ’…


πŸ“ CONFIGURATION πŸ“

Please make sure to edit dll.conf before you use the backend, since this backend isn't enabled by default πŸ™ˆ like it's literally shy, you gotta invite it in first.


🧚 FILES 🧚

  • /etc/sane.d/p5.conf β€” the backend configuration file (see also description of SANE_CONFIG_DIR below) πŸ’–
  • /usr/lib64/sane/libsane-p5.a β€” the static library implementing this backend 🌸
  • /usr/lib64/sane/libsane-p5.so β€” the shared library implementing this backend (present on systems that support dynamic loading) ✨

πŸ’œ ENVIRONMENT πŸ’œ

  • SANE_CONFIG_DIR β€” this environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:`), under OS/2, they are separated by a semi-colon (`;`). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order) πŸ‘‘
  • SANE_DEBUG_P5 β€” if the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 255 requests all debug output to be printed. Smaller levels reduce verbosity 🌈

the level chart, slay:

level   debug output
------- ------------------------------
 0       critical errors
 1       errors
 2       warnings & minor errors
 4       information messages
 8       start/stop of functions
 16      tracing messages
 32      I/O functions
 64      I/O functions with traces
 128     scanned/calibration data

⭐ SEE ALSO ⭐

sane(7), sane-net(5), saned(8), scanimage(1) β€” go read those too bestie, they're the supporting cast 🫢


πŸ‘‘ AUTHOR πŸ‘‘

StΓ©phane Voltz <stef.dev@free.fr> πŸ’–


πŸŽ€ CREDITS πŸŽ€

Support for the Prima PagePartner has been made possible thank to an hardware donation by Sébastien Lange 🌸 iconic behavior honestly.


πŸ’€ BUG REPORTS πŸ’€

if something doesn't work mail sane-devel@alioth-lists.debian.net or submit an issue via https://gitlab.com/sane-project/backends/issues/new with a label of backend/p5 πŸ™ˆ Please give as much information as you can β€” the more tea you spill, the better we can help πŸ’…

  • SANE version β€” run "scanimage -V" to determine this
  • the backend version and your scanner hardware β€” run SANE_DEBUG_P5=255 scanimage -L 2>log as root. If you don't get any output from the p5 backend, make sure a line "p5" is included into your /etc/sane.d/dll.conf. If your scanner isn't detected, make sure you've defined the right port address, or the correct device in your p5.conf file πŸ”₯
  • the name of your scanner/vendor β€” also a worthy information. Please also include the optical resolution and lamp type of your scanner, both can be found in the manual of your scanner πŸŽ€
  • any further comments β€” if you have comments about the documentation (what could be done better), or you think I should know something, please include it πŸ’–

so yeah, that's the whole vibe ✨ this page has been sittin' pretty since 15 Feb 2010 β€” the sane-p5(5) era, main character energy only πŸŒˆπŸ’…πŸ«Ά

πŸ“¦ where this page comes from