I have installed AArch64 (ArchLinuxARM-rpi-3-latest.tar.gz) as described here on a new rpi 3.
Additionally I installed those packages:
I have added this to
/home/alarm/.config/weston.ini with that content:
[alarm@alarm ~]$ weston --log=weston.log --config=.config/weston.ini
takes its time to start the desktop. From there I can launch a terminal and type
chromium. After a while the cursor starts to blink, no output, nothing. While I am still able to move the mouse, the rest of the desktop is frozen until interrupted by
Furthermore, after such an interrupted attempt to start either chromium or firefox, a subsequent
$ weston --log…, results in a black screen with a relatively big mouse pointer and nothing else, after rebooting the system, the normal Desktop appears again.
The content of
weston.log can be found here. Additionally I found this in the output of
Dec 20 09:38:19 alarm kernel: [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA: Dec 20 09:38:19 alarm kernel: [drm] V3D: 34572kb BOs (10) Dec 20 09:38:19 alarm kernel: [drm] V3D shader: 36kb BOs (9) Dec 20 09:38:19 alarm kernel: [drm] dumb: 8132kb BOs (3) Dec 20 09:38:19 alarm kernel: vc4_v3d 3fc00000.v3d: Failed to allocate memory for tile binning: -12. You may need to enable CMA or give it more memory.
Btw. I have also installed Arch within an Virtual Box from the current iso, there the very same setup worked for chromium, so I guess that is ARM related?
What can be the reason why chromium just wont start?
After some more tries I found that even commandline application like
htop stop work, or do not even run at all. In each case, the whole desktop freezes and nothing happens.