sane-kodakaio(5)

πŸ“¦
version 1.4.0 Β· 2 versions
  • 1.4.0 Β· alpine 3.24, arch rolling, centos-stream 10, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.0.32 Β· centos-stream 9
, in alpine 3.24, arch rolling, centos-stream 10, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– sane-kodakaio β€” the Kodak aio printer/scanner backend πŸ’–

okay bestie, so this is the manual page for sane-kodakaio (it lives in section 5 of the manual, iykyk) and it's genuinely the whole guide to getting your Kodak all-in-one talking to SANE. let's get into it 🫢


✨ NAME ✨

sane-kodakaio β€” the SANE backend for Kodak aio printer / scanners πŸ’…


🌸 DESCRIPTION 🌸

so the sane-kodakaio library is a SANE (that's Scanner Access Now Easy, iconic name, no notes) backend, and what it does is give you access to Kodak aio printer/scanners β€” think the ESP series and the Hero series, those girlies. πŸ‘‘

this doc right here describes backend version 2.4, which is lowkey a big deal because it's the first candidate for incorporation in sane-backends. main character energy fr fr. ⭐


πŸ¦‹ SUPPORTED HARDWARE πŸ¦‹

this version should support models from the Kodak ESP and Hero series, and possibly some Advent AiO scanners too (we love a maybe πŸ’€). the ESP 5250 and Hero 9.1 are the ones that were actually used to develop the backend, but other models may work.

please go look at the supported devices list at http://www.sane-project.org/sane-backends.html#S-KODAKAIO β€” it's right there, click it bestie.

and if you have a model that's not on that list, or that's reported as 'untested': ngl the best way to figure out your level of support is just to test the scanner directly. vibe check it yourself. πŸ”₯


πŸŽ€ CONFIGURATION FILE πŸŽ€

the config file kodakaio.conf is what you use to tell the backend how to look for scanners, and to hand over the options that control how the backend operates.

heads up bestie: this file gets read every single time the frontend asks the backend for a list of scanners β€” which, generally, is only when the frontend starts. so not constantly, but like, on start. πŸ“

🌈 ENVIRONMENT 🌈

  • SANE_DEBUG_KODAKAIO β€” if the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. and the way that higher debug levels just increase the verbosity of the output?? yeah. more number, more words. πŸ’œ

πŸ’€ KNOWN ISSUES πŸ’€

okay so, not everything is giving. most hardware options are either not supported or not exposed for control by the user, including: multifeed detection, image compression, etc. 😭 so don't come for us about those, they're just not on the menu.


πŸ’– SEE ALSO πŸ’–

  • sane(7) β€” the standard, go read it 🫢

πŸ‘‘ AUTHOR πŸ‘‘

P. Newall β€” thank you for your service, periodt. πŸŽ€


and that's the whole page, bestie!! this was sane-kodakaio(5) from SAN Easy... okay no, it's SANE Scanner Access Now Easy, and the page is dated 17 Jun 2012. slay, go scan something. πŸ’…βœ¨

πŸ“¦ where this page comes from