@NorPhi wrote:
Hello,
For the lazy ones | tl;dr:
UNICORN HAT NOT WORKING ON ARCH LINUX ARM SCROLL DOWN TO SEE IMPORT ERROR MESSAGE!I wanted to use my Unicorn Hat (UH) shield with Arch Linux ARM (ALARM) on my Raspberry Pi 2 (RP2).
I've cloned the GIT repo yesterday morning (15.3.) and installed everything in the ../python folder via PIP into a virtualenv. the unicornd daemon was installed via sudo make install arch-linux (although I'm really not happy using make install for anything as it tends to just make everything a mess) and then enabled at boot via systemctl. ALARM is also up to date. Bleeding edge, the way Linux is supposed to be!If I now start any of the provided example scripts e. g. sudo ./demo.py nothing happens and it's not ctrl-C stopable. I read that some people hat similar problems running the UH "package" on ALARM but fixed it by downgrading gcc or editing some Makefile's - however, according to the pull request history of GitHub all the suggested/successful solutions to these problems were already merged. Except for one issue (#35) stating that rpi-ws281x is broken in the newest ALARM, which was untouched since January. Someone commented that the daemon occassionally throws DMA errors but I haven't noticed any (or I'm looking at the wrong place, also possible).
When I open a python console (remember, virtual env!) and try '''import unicornhat as uh''' I get this:
import unicornhat as uh Failed to open /dev/vcio, trying old method. Failed to create mailbox device /dev/mailbox-598: Permission denied Failed to open /dev/vcio, trying old method. Failed to create mailbox device /dev/mailbox-598: Permission denied Failed to open /dev/vcio, trying old method. Failed to create mailbox device /dev/mailbox-598: Permission denied Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/norphi/Projects/unicorn-hat/python/UnicornHat/unicornhat.py", line 14, in <module> ws2812.begin() File "/home/norphi/Projects/bioreactor_building/.env/lib/python3.5/site-packages/neopixel.py", line 107, in begin raise RuntimeError('ws2811_init failed with code {0}'.format(resp)) RuntimeError: ws2811_init failed with code -1
Permission denied could be a hint but I don't even get why /dev/mail... So this isn't really helping me. Anyone an Idea? Is it really the same issue as #35? Something else?
As you can see from my path ../bioreactor_building/.. I'm up to no good again. Help a mad scientist, win an ego boost!
Also someone explain me how to highlight inline code in markdown, please, as everything I tried wasn't working.
The funny part: Actually I just need Python 3.5.1 on my RP2 but installing anything that isn't obsolete by months on a Debian based system seems to be just not possible at all. I ended up rendering my Rasbian unbootable. Still no idea how that did happen...
Greetings,
NorPhi
Posts: 4
Participants: 2