Closed 3DJupp closed 7 years ago
its not an issue with the kernel right now, the latest: https://github.com/Hexxeh/rpi-firmware/commit/41561448388d90f19f2e40ac62ce1c21c2e064ec The latest firmware that worked before the epd fix does not work, too: https://github.com/Hexxeh/rpi-firmware/commit/52241088c1da59a359110d39c1875cda56496764
From Raspbian?
Just tried it from a fresh Raspbian/NOOBS and it worked fine.
Tested with both a standard and the Zero W with both kernels and all is fine. Aren't you maybe trying to run the installation over an existing one?
@francesco-vannini @shawaj Of course, it's not a fresh installation, but which directories do i need to clean in order to get it running?
Run sudo systemctl status epd-fuse.service
And post the output here please
Hey :)
This error appears:
Mar 25 15:25:53 ePaper epd_fuse[632]: fuse: unknown option `--panel='
Can you post the full output?
Also can you not just start from a fresh version of Raspbian/NOOBS?
But that's not a solution for me, there should be something, that I could revert in order to get it working (the empty panelId for instance)
It's like rebooting a device as an act of troubleshooting. It might help for now, but no one really knows what causes the problem.
Which directories are used by papirus and gratis?
I had something like that error in the early days that was caused by the panel value being unset in the file /etc/default/epd-fuse which caused the setup (systemd) to fail (and occasionally when messing around trying things)
i am doing this from memory as i don't currently have a pi with a papirus available at the moment but if you check in that file and/or run papirus-config or papirus-set I think that should fix it
Great, that's it. papirus-config and disable the driver, papirus-set and check the screen size (2.0 for PaPiRus Zero) And then back again to papirus-config and enable the driver again
Great, glad you sorted it!
@francesco-vannini shall we add this fix to an FAQ somewhere? Not sure what causes it though
On 26 Mar 2017 12:01 pm, "Dominic Spatz" notifications@github.com wrote:
Closed #100 https://github.com/PiSupply/PaPiRus/issues/100.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/PiSupply/PaPiRus/issues/100#event-1015637799, or mute the thread https://github.com/notifications/unsubscribe-auth/ADNCuiGsefgO3MwHKMBRq0gBh5j7WLo3ks5rpkWmgaJpZM4MpFXn .
@ukscone has suggested this could be due to timing papirus-set without any options after it and/or installing over an existing install
*running, but timing