search

PiSupply / PaPiRus

Resources for PaPiRus ePaper eInk displays
https://www.pi-supply.com/product/papirus-epaper-eink-screen-hat-for-raspberry-pi/
Other
346 stars 88 forks source link

IO error When "cold" start #14

Closed ced510xe closed 7 years ago

ced510xe commented 8 years ago

Hello

I have this error when I start my programm : Traceback (most recent call last): File "/home/pi/Desktop/Test/Test.py", line 137, in main(sys.argv[1:]) File "/home/pi/Desktop/Test/Test.py", line 58, in main epd = EPD() File "/usr/local/lib/python2.7/dist-packages/papirus/epd.py", line 66, in init with open(os.path.join(self._epd_path, 'version')) as f: IOError: [Errno 2] No such file or directory: '/dev/epd/version'

With a "sudo papirus-setup" it work after but where are the base problèm??

YoungAtHome commented 8 years ago

No dev EPD means device service is not running. Check the logic in the papirus-config as the start /stop code logic may be backwards, so you start it if it's running and stop it if not!

All the papirus Python code works by writing and reading through the device files so /dev/EPD is crucial.

Let us know what you get working. On 11 Mar 2016 11:26 pm, "ced510xe" notifications@github.com wrote:

Hello

I have this error when I start my programm : Traceback (most recent call last): File "/home/pi/Desktop/Test/Test.py", line 137, in main(sys.argv[1:]) File "/home/pi/Desktop/Test/Test.py", line 58, in main epd = EPD() File "/usr/local/lib/python2.7/dist-packages/papirus/epd.py", line 66, in init with open(os.path.join(self._epd_path, 'version')) as f: IOError: [Errno 2] No such file or directory: '/dev/epd/version'

With a "sudo papirus-setup" it work after but where are the base problèm??

— Reply to this email directly or view it on GitHub https://github.com/PiSupply/PaPiRus/issues/14.

tjmgregory commented 8 years ago

Was having an identical problem to ced510xe above. We found that the solution for us was to add the following to the .bashrc: sudo service epd-fuse start Feel like this is a temporary fix, but saves running all of papirus-setup each time. Hope this helps :)

jflowers1974 commented 8 years ago

@theooos Thanks. I was pulling my hair out - I seemingly could only get my screen to work after re-installing the driver each time. At least now it works after a reboot.

johnhorner commented 7 years ago

I'm trying sudo service epd-fuse start and all I get is

Job for epd-fuse.service failed. See 'systemctl status epd-fuse.service' and 'journalctl -xn' for details.

When I do systemctl status epd-fuse.service I get this:

● epd-fuse.service - LSB: Start epd_fuse to control E-Ink panel
   Loaded: loaded (/etc/init.d/epd-fuse)
   Active: failed (Result: exit-code) since Sun 2016-12-11 16:30:44 AEDT; 34s ago
  Process: 2080 ExecStart=/etc/init.d/epd-fuse start (code=exited, status=1/FAILURE)

and when I do journalctl -xn all I get is No journal files were found.

EDIT: Fixed this by running papirus-config again and enabling EPD: Image

And doing that plus adding the sudo service epd-fuse start to .bashrc seems to fix the issue even after restart.

shawaj commented 7 years ago

What Pi version is this on? And latest firmware?

It shouldn't need anything changing to get it to auto appear on boot.

With a clean install I did today it survives every restart on stock noobs on a Pi 3.

On 11 Dec 2016 5:55 am, "johnhorner" notifications@github.com wrote:

I'm trying sudo service epd-fuse start and all I get is

Job for epd-fuse.service failed. See 'systemctl status epd-fuse.service' and 'journalctl -xn' for details.

When I do systemctl status epd-fuse.service I get this:

● epd-fuse.service - LSB: Start epd_fuse to control E-Ink panel Loaded: loaded (/etc/init.d/epd-fuse) Active: failed (Result: exit-code) since Sun 2016-12-11 16:30:44 AEDT; 34s ago Process: 2080 ExecStart=/etc/init.d/epd-fuse start (code=exited, status=1/FAILURE)

and when I do journalctl -xn all I get is No journal files were found.

EDIT: Fixed this by running papirus-config again and enabling EPD: Image http://imgur.com/d5su11I

And doing that plus adding the sudo service epd-fuse start to .bashrc seems to fix the issue even after restart.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/PiSupply/PaPiRus/issues/14#issuecomment-266265072, or mute the thread https://github.com/notifications/unsubscribe-auth/ADNCuqwyEEpLepmrO8dlo1LJdN5ehi6uks5rG5A6gaJpZM4HvIpU .

francesco-vannini commented 7 years ago

I am going to close this issue as it is over a year old and no replies have been provided. I will assume the issue is resolved, please feel free to open again if not.

MZandtheRaspberryPi commented 4 years ago

FYI I was getting this error too, with a cronjob to start the papyrus e-ink display on reboot. Setting a sleep before starting the program for 20 seconds fixed it (you could probably do a shorter sleep).

This helped me figure out to let it sleep: https://www.raspberrypi.org/forums/viewtopic.php?t=216375