To optimize our future eBlockerOS development strategy we are surveying the hardware platform you are currently using. Please help us to plan the future. Your vote counts 👍
Um unsere zukünftige eBlockerOS-Entwicklungsstrategie zu optimieren, möchten wir wissen, welche Hardware-Plattform du derzeit verwendest. Bitte hilf uns, die Zukunft zu planen. Deine Stimme zählt 👍
the small white cube is refreshingly durable 😀
If it were to fail, I would want to use my own dedicated hardware again, probably a Raspberry PI 4, but with more than 2 GB so that I could potentially use the device for other things as well. Overall, I also pay attention to the basic consumption of the device, because of 24/7 for eblocker.
The poll is closed. Here are the results:
I completely agree. The problem is money. We cannot invest into marketing to reach out to new users since we can barely cover the operational costs with donations.
Today probably less than 1% of our users are donating. Even less are willing to spread the word about eBlocker. If all users would help spreading the word, life would be easy.
We love to continue and add more features to eBlockerOS. But the White Cube hardware is outdated (>7 years old), has too less cpu power and worse: not enough memory. That was the actual background behind the poll.
If you @julius feel like helping: you are very welcome. Spreading the word in your circles would be a great start for example. Joining the team for increased guerilla marketing tactics another. Any help is highly appreciated.
Thanks very much for yours 👍🙏
do provide eblocker os image for Orange Pi Zero 3,
which will encourage a lot sbc hobbyist to utilise the eblocker os
how to compile and build eblocker os from github for Orange Pi Zero 3
kindly guide me to How to generate the image for Orange Pi Zero3
@jones I'm not a developer and can't help. All I know is that building an OS images needs deep IT knowledge and quite some time. It's not a simple "make install" 😉
Maybe @bpr (the core maintainer) could guide you.
If you are a software developer I'd personally recommend to join the team first to see how we work in the background and contribute with your Orange Pi knowledge. Then this engagement could be leveraged more easily into a new OS image for Orange Pi.
THX!
@jones If you have a Debian Buster image for the Orange Pi you could try to install the eBlocker software with the Ansible scripts and files we use to build our eBlocker VM:
https://github.com/eblocker/eblocker-build/tree/main/eblocker-vm
If anything does not work, feel free to add an issue on GitHub.
Dear Boris,
currently my OPi-Z3 (1G) , i need to run eblocker os on my hardware directly, not on vm
do i have another OPi-Z3 (2G) , when i try to load eBlockerOS for Banana Pi M2+ (568 MB) os image on SD card its getting blank console screen while booting, its not even throwing any error messages completely blank
its due to uboot code (Banana Pi) not matching up with OPi -Z3
so kindly guide me on how to install eblocker directly on hardware(OPI-Z3)with existing ubuntu
i can clone source code from GitHub, how to compile the download eblocker source code on OPI-Z3
**** uname -a
Linux hostname 6.1.31-sun50iw9 #1.0.2 SMP Mon Sep 25 13:54:37 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
******* cat /etc/*version *******
bookworm/sid
* cat /etc/os-release **
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL=" removed link "
SUPPORT_URL=" removed link "
BUG_REPORT_URL=" removed link "
PRIVACY_POLICY_URL=" removed link "
UBUNTU_CODENAME=jammy
************** cat /etc/*release ***************
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepizero3
BOARD_NAME="OPI Zero3"
BOARDFAMILY=sun50iw9
BUILD_REPOSITORY_URL= removed link
BUILD_REPOSITORY_COMMIT=2dbd451-dirty
DISTRIBUTION_CODENAME=jammy
DISTRIBUTION_STATUS=supported
VERSION=1.0.2
LINUXFAMILY=sun50iw9
ARCH=arm64
IMAGE_TYPE=user-built
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=next
IMAGE_UUID=50d7340c-f367-46f3-8314-8a5f4f541cd2
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepizero3
BOARD_NAME="OPI Zero3"
BOARDFAMILY=sun50iw9
BUILD_REPOSITORY_URL= removed link
BUILD_REPOSITORY_COMMIT=2dbd451-dirty
DISTRIBUTION_CODENAME=jammy
DISTRIBUTION_STATUS=supported
VERSION=1.0.2
LINUXFAMILY=sun50iw9
ARCH=arm64
IMAGE_TYPE=user-built
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=next
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL=" removed link "
SUPPORT_URL=" removed link "
BUG_REPORT_URL=" removed link "
PRIVACY_POLICY_URL=" removed link "
UBUNTU_CODENAME=jammy
i have another OPi-Z3 (2G) , when i try to load eBlockerOS for Banana Pi M2+ (568 MB) os image on SD
Each image is individually build for each hardware platform. So your trial is doomed to fail. Same if you try to run Windows apps under macOS.
As Boris stated above, you need to run Debian Buster(!) and use the Ansible scripts(!) to build the image for Orange Pi.
Again, this process is for tech savvy users only who are familiar with Ansilbe and have a strong Linux backgound. Please check out the scripts. It's all there.
THX!