Kete

  • Content Count

    3
  • Joined

  • Last visited

  1. Thanks for your reply. Although I was running my own custom kernel, I had already tested it with the stock kernel as well. The situation did not differ. Anyway, as you said I wrote the stock image to a new microSD and started over. The hang/freeze or the aw, snap error was present. armbianmonitor output: https://drive.google.com/file/d/1UwBDMZ2D8G6q6QdGHGar9pHX50GjTv66/view?usp=sharing Some more log appeared on the serial console at the freeze event: https://dpaste.com/2J847U2EN The end has three lines from dmesg which was the onl
  2. Thank you very much for your swift reply. I immediately got the needed information but somehow armbian forum did not let me post more than once yesterday. Anyway, this is the output: https://drive.google.com/file/d/1MTjonq6bYMsD3ef5iHa7ebHA64Vri6om/view?usp=sharing I have also appended Xorg.0.log to the end of the file. I also tested my own custom compiled kernel for Rock64, and while the experience was a little better, at the end chromium always crashed again with Aw, snap. This is a on 4GB Rock64 SBC. For the fdt I am using rk3328-rock64.dtb.
  3. Thank you very much for your efforts. However, Chromium is totally unstable. It always crashes randomly (aw, snap) after a few minutes of playback in streaming websites. Is there anything that can be done? I have tested other browsers but they are far from perfect. The only option is a HW accelerated one like chromium in full screen mode. At this point is there any hope that vaapi-enabled firefox 80+ can be compiled and used? What about vaapi-enabled gstreamer ones like epiphany? (I tested it but the performance was terrible as it was not HW-accelerated.)