Well first off if you read the github change that make it clear it is possible for breakage to happen if you use it as development continues. " Second did you install python-pip and python-setuptools or did you install python2-pip and python2-setuptools I just got done compiling around 30 something python and python2 packages on Arch and have not had a single issues relating to a broken python or python2 install. My guess is you need the python2 related packages. If it is a broken python install I would try reinstalling python and python2 test again. If still borked try creating a new image test again, if borked again report a bunch to archlinuxarm . My guess is there is nothing wrong with the python* packages.
which arch kernel are you running? You should be on the legacy one for the beagle if you’re working with capes also you should make sure you’re using dtc-overlay as opposed to dtc. This post has some information in regards to the device tree and arch linux arm.
Thank you! I used the latest 3.12 kernel and installed the legacy version. Now my program works fine!
By the way, why doesn’t the newest kernel support the capes?
lauantai, 23. marraskuuta 2013 20.28.13 UTC+2 don kirjoitti:
3.12 is just barely ( a month or so ) out of RC status. Just need someone to port the code and device tree files over from 3.8. Which probably is harder than I made it sound. Not really sure I have not looked at the code on either kernel version.