The simplest thing is to try to take a working u-boot from any working Armbian image (for details on how to pull out u-boot and use it in another image, see this topic earlier).
Starting from USB is possible, but with the described two options. I think the TWRP startup comes from u-boot which is in eMMC (in service mode).
To completely clean eMMC, you can use the USB Burn Tool (with certain options, the firmware file is not needed).
This is cheating. H6 can't work with 4 GB , this is a hardware limitation. See the topic in the section Allwinner H6, where the developers describe this problem.
Never had any issues with python when playing with Panfrost AFAIR...
Try to install the module with pip3 install Mako
Maybe do a pip3 install --upgrade pip before to update the installer itself.
Depending on your OS the command might be different or not available at all. If necessary search apt for python3 pip and install it.
Nice board. Clean and simple.
I like this SoC a lot, very power efficient and good thermals.
What will be the price? When will it be sold?
I'd like to see wifi/BT on-board. But not everyone needs that for their tasks, I understand why not to have it.
I also like to have a barrel jack for power. Type-C is ok. But still a lot of issue's with bad cables and bad contacts.
Good luck.
I'm not sure if this will help at all, but figured I'd mention it just in case: These traps look somewhat similar to some that I fixed for the RTL8812AU driver (see https://github.com/aircrack-ng/rtl8812au/pull/704). I don't have an RTL8188EU, but the changes are simple enough to try if you have some spare time - see https://github.com/aircrack-ng/rtl8812au/pull/704/commits/94340760e7d6144a2099eccbebb21dc53fe9fdeb. Obviously you'll have to find the related lines in the 8188 sources to make the changes, but this should be pretty easy to try.
Note: I am new the forums and there is a posting rate limit in place. Currently it looks like I can only post once every 24 hours for the moment so my turn around is slow.
There are a couple issues that I ran into with the newer kernel builds.
The kernel 5.8.y builds do not reliably startup for me. I have to push reset or unplug-plug-in a few times for it to boot. I suspect but have not proven that it is this issue, I experience it right out of the box which may be different: https://forum.armbian.com/topic/15209-rockpi-s-crashing-at-startup-with-memory-errors/
I intend to use the I2C interface and the overlays do not appear to be present in the newer kernel builds. I can just manually add them, so not a big issue.
The USB-A port is not recognizing the device I have connected to it. The same device works just fine with the 4.4.y kernel builds. Maybe there is an easy solution to this like the I2C overlay that I am just not aware of.
Just an observation, the newer builds result in a 10C increase in idle CPU temperature (as reported in htop). It does not appear to affect anything and it could just be a reporting issue.
Yes it is present in their Debian Buster build as well.
The image improved it quite a lot but like you said, the issue is still there. With the test build the hang was only observable for about a second.
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=4.46 ms
64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=6.54 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=648 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=3.74 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=6.43 ms
...
64 bytes from 192.168.1.1: icmp_seq=163 ttl=64 time=6.54 ms
64 bytes from 192.168.1.1: icmp_seq=164 ttl=64 time=8.53 ms
64 bytes from 192.168.1.1: icmp_seq=165 ttl=64 time=1426 ms
64 bytes from 192.168.1.1: icmp_seq=166 ttl=64 time=418 ms
64 bytes from 192.168.1.1: icmp_seq=167 ttl=64 time=8.88 ms
...
64 bytes from 192.168.1.1: icmp_seq=226 ttl=64 time=4.66 ms
64 bytes from 192.168.1.1: icmp_seq=227 ttl=64 time=10.4 ms
64 bytes from 192.168.1.1: icmp_seq=228 ttl=64 time=1281 ms
64 bytes from 192.168.1.1: icmp_seq=229 ttl=64 time=274 ms
64 bytes from 192.168.1.1: icmp_seq=230 ttl=64 time=4.77 ms
64 bytes from 192.168.1.1: icmp_seq=231 ttl=64 time=6.73 ms
You dont have to. I have the same "conflict" in my system but it does not even matter.
I even think there is an issue with the oibaf repositiory and the libs from their packages are being installed in the wrong place.
See my post above where you can find libs in /usr/lib as well as /usr/local/lib
I did glmark2 twice. In between I built the latest mesa from scratch and had a different version string which matched the latest commit. Therefore I assume the oibaf libs are (partially at least) not being used.
tl;dr:
apt build-dep mesa
Grab sources
Compile like described here: https://panfrost.freedesktop.org/building-panfrost-mesa.html
Restart X
Done.
We added acronyms to the forums. Commonly used abbreviation like SoC are now marked and their meaning can be highlighted by simply moving the cursor over it.
If you do have ideas for missing acronyms feel free to comment here:
We added acronyms to the forums. Commonly used abbreviation like SoC are now marked and their meaning can be highlighted by simply moving the cursor over it.
If you do have ideas for missing acronyms feel free to comment here:
Banana Pi BPI-M5 is a new generation single board computer design , use Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor. Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz). support 4GB LPDDR4 and 16G eMMC flash. it have 4 USB 3.0 port,1GbE LAN port.
main spec:
* Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor
* Mali-G31 GPU
* 4GB LPDDR4
* 16GB eMMC flash on board.
* 4 USB 3.0 port
* 1 GbE LAN por
* HDMI output
hardware interface:
more please see wiki page, we will keep update on wiki documents.
http://wiki.banana-pi.org/Banana_Pi_BPI-M5
embedded,
VPU - video processing unit (encoding/decoding)
GPU - graphic processing unit (3D acceleration)
SoC - System on a Chip
SBC - Single Board Computer
WIP - Work in progress
NAND - Flash storage
GPIO - general purpose input/output
CSC - the weirdo.. no support abbreviation
EOS - End of Support - Hey Werner, die beiden schreien nahe zu nach einer Zusammenführung.
We have too small resources (we can't pay, you don't see this as a cost) to deal more with this hw and its users so its more or less down to "community support only".
Probably armbian-config bug, related to:
https://armbian.atlassian.net/browse/AR-396
Check if speeds are correct with:
cpufreq-info
Modern kernel with full blown support that will satisfy all of your needs will exists when greater Linux community develops / port feature (very late, often never) or if you pay that features are ported / developed. We can only invest 30-50 of our private hours per day. For more:
https://github.com/armbian/build#support
https://github.com/armbian/build#contribute
https://www.armbian.com/donate/
So in short in upstream the kernel module is there but in Armbian it is not.
Either it is not available for ARM or (and I am pretty sure about that) it is just not enabled in the equivalent Armbian kernel config. Bringing these configs closer to upstream is still WIP and a lot of work (and therefore nobody wants to do it ).
The fastest way for you at the moment to get it running is to build your own kernel package using the build script available here: https://github.com/armbian/build
Checkout the documentation how to get started: https://docs.armbian.com/
It is not that complicated as it sounds. To break it down real quick: clone repo, run ./compile.sh, select your board and that you want to adjust the kernel config. Select the mentioned module and let it build.
Install the generated kernel package (and I recommend to install the headers, dtb and u-boot too) with dpkg -i.
Reboot and check if it is working now.
It is no longer possible to add tags, either custom or pre-defined, to topics in General Chit Chat and Feature Requests (already existing tags are kept). Latter received the option to add a "solved" prefix for fulfilled feature requests. Btw. if you want to see more "solved" prefixes consider getting involved .
Announcements forums tags have been replaced with proper prefixes (the first page at least, older topics most likely nobody reads anyways )