Thanks for the guidance! It gives the same error as the log:
Oops: Unable to determine board revision from /proc/device-tree/system/linux,revision
or from /proc/cpuinfo
→ No “Hardware” line
→ You’d best google the error to find out why.
Oops! No, I compiled it with ./build from the ClockworkPi github. I removed it and installed it from apt now per your instructions. Now the driver gives me this error:
/usr/local/bin/devterm_thermal_printer.elf: error while loading shared libraries: libwiringPi.so.2: cannot open shared object file: No such file or directory
Getting closer! I’ll keep looking, and I’ll appreciate your help if you have any other tips!
OK, I made a link to libwiringPi.so.2.50 and restarted devterm-printer, then did echo -en “\x12\x54” > /tmp/DEVTERM_PRINTER_IN. It worked! Test print successful.
However, I still can’t print from the shell (from the “Print” command in Firefox, for example.) In the Printers menu, any print jobs become “Held” and it shows an error message that the printer “may not be connected.”
I don’t know where to begin with this one–I guess this is an issue with the cups driver?–so any help would be much appreciated. And thanks so much for your help so far, @guu !
I noticed a comment at bottom of that section in /etc/apparmor.d/usr.sbin.cupsd:
# Site-specific additions and overrides. See local/README for details.
#include <local/usr.sbin.cupsd>
So I think the DevTerm specific fix could go there instead. (Funny enough, the README file they mention doesn’t exist!) I’m not sure how these files get updated, but I’m guessing some kind of package update might wipe out the file you suggested at some point, while this user file might be left alone. Just a guess though. I’m not sure how all this stuff is supposed to work. (The “local” file existed, but was empty on my DevTerm.)