• Content Count

  • Joined

  • Last visited

  1. Ended up installing the fbturbo driver, as per this article (, and it still really didn't improve anything.
  2. I'm wondering the same thing. I was able to install Chromium using the latest Ubuntu Trusty (which is based on Debian Jessie) armhf packages on my Debian Jessie Armbian build running on a Banana Pi M1. I had to install libgcrypt11, chromium-codecs-ffmpeg-extra, and chromium-browser Ubuntu .deb files. The rest of the dependencies were found from the Debian apt sources. But the performance is unbearably slow. I figured with 1GB and a dual-core ARMv7 processor, that web browsing would be at least decent and on par with the experience you get with smartphones. It's not even close. Since Armbia
  3. so is it true that there's currently no way to enable h.264 hardware acceleration on the mainline kernel? I have a great Armbian based mainline kernel build running on my Allwinner A20 based Banana Pi but would really benefit to have h.264 hardware acceleration for improved NoMachine remote desktop support. NoMachine is infinitely faster and better than VNC, and without an arm based version of TeamViewer it's the best thing going for remote desktop control.
  4. Thanks for the suggestions, Igor. By the time I saw your responses, I had already setup an Ubuntu virtual machine on my PC to build a two partition image for the Banana Pi. Was much more painless than I expected. But this is good to know for future reference. I like having /boot and / on separate partitions simply because I can more easily change the filesystem of root and encrypt it, post installation.
  5. One solution that's perhaps easier, that doesn't require as much edits to the build environment, is to simply go through the usual process (using the default ext4 for root) and convert post installation. This way you don't need to worry about partition resizing, and it gives you the option to encrypt root as well. You'll only want to ensure that the BOOTSIZE parameter is not 0, so that separate /boot and / partitions are created in the image. For the BananaPi, I used 16MB as you did. Once you've put the image on an SD card and gone through the initial boot, use a USB flash d
  6. just curious if there's a quick way to manipulate an existing Armbian build to have separate /boot and / partitions on my SD card, without needing to setup an Ubuntu build environment to compile everything myself. It's really the only thing I'd want to change about the pre-built image, and would like to avoid setting up the Ubuntu build box if I can. Thanks!
  7. Just wanted to chime in and mention that I'm seeing the same thing with a Banana Pi (M1) connected to a 4K monitor. Works fine with the legacy kernel.