-
Posts
1331 -
Joined
-
Last visited
Reputation Activity
-
lanefu reacted to martinayotte in Switching SUNXI-DEV to 5.2.y
Since the two last days, I'm working on switching SUNXI-DEV to 5.2.y ...
I'm almost done, tested few of my boards, I will do more boards and probably commit my work tomorrow !
-
lanefu got a reaction from gprovost in [RFC 001] Changes for boards and features implementing
I've made it easier to apply RFC tags on the forum itself. That will make it easier to search.
A slight tweak: Instead of assigning a [00x] sequence number to "approved" RFC, I'm going to give RFCs the issue number generated by github.
-
lanefu reacted to stareintheair in Automating armbian-config
Hello,
I'm setting up my Odroids with Ansible and managed to automated almost everything. I just got a HC1 and read on the download page that I should load optimized board configuration in armbian-config. Sadly, armbian-config seems to be an interactive only tool. Are there ways to automate armbian-config? The easiest way would be command line arguments.
I also tried to understand what the DTB menu options actually do from the source code but was unsuccessful.
My best idea now is to use expect, but that doesn't seem stable:
#!/usr/bin/expect set timeout 10 spawn armbian-config sleep 5 # Enter System menu send "\n" sleep 5 # Enter DTB menu send "d\n" sleep 5 # Choose HC1 option send "h\n" sleep 5 # Cancel reboot send "c" Am I overlooking something? Any other ideas?
Thanks and kind regards.
-
lanefu got a reaction from Werner in Special considerations upgrading Debian release (Stretch to Buster)?
Freeze your kernel in armbian-config may be a good idea.
-
lanefu got a reaction from BCMM in Special considerations upgrading Debian release (Stretch to Buster)?
Freeze your kernel in armbian-config may be a good idea.
-
lanefu got a reaction from NightMean in [SOLVED] Help booting armbian on Mini M8S II
....but you have a fantastic username
-
-
lanefu reacted to Stuart Naylor in Software RAID testing Rockpi4 Marvell 4 port sata
Forgot to set the RockPi4 to pcie2 doh!
Also if you are a plonker and forget to edit `/boot/hw_intfc.conf` from `#intfc:dtoverlay=pcie-gen2` to `intfc:dtoverlay=pcie-gen2` you will be running on pcie-gen1
RAID 10
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 11719 15447 55220 53720 25421 12773 102400 16 39410 54840 139482 145128 81258 43792 102400 512 228002 220126 334104 339660 265930 225507 102400 1024 244376 243730 451377 462467 397566 258481 102400 16384 270088 304411 597462 610057 615669 297855
RAID 5
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 6133 6251 47505 46013 25046 8190 102400 16 17103 17134 113272 133606 79753 20420 102400 512 61418 50852 241860 246467 244030 58031 102400 1024 79325 73325 363343 359830 361882 83655 102400 16384 127548 124702 625256 642094 650407 136680
RAID 1
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 23713 29698 45608 45983 23657 30381 102400 16 79205 82546 138060 144557 82126 93921 102400 512 212859 221943 307613 304036 259783 179355 102400 1024 235985 243783 366101 369935 317354 198861 102400 16384 289036 290279 410520 398875 399868 295329
RAID 0
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 33519 47927 52701 51023 26700 46382 102400 16 105763 132604 138080 155514 87026 135111 102400 512 276220 320320 311343 294629 267624 335363 102400 1024 493565 522038 463105 470833 398584 522560 102400 16384 687516 701200 625733 623531 555318 681535 4 individual disks conurrent
Command line used: iozone -l 4 -u 4 -r 16k -s 512M -F /srv/dev-disk-by-label-sda/tmp1 /srv/dev-disk-by-label-sdb/tmp2 /srv/dev-disk-by-label-sdc/tmp3 /srv/dev-disk-by-label-sdd/tmp4 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. Min process = 4 Max process = 4 Throughput test with 4 processes Each process writes a 524288 kByte file in 16 kByte records Children see throughput for 4 initial writers = 884590.91 kB/sec Parent sees throughput for 4 initial writers = 701620.17 kB/sec Min throughput per process = 195561.27 kB/sec Max throughput per process = 234457.59 kB/sec Avg throughput per process = 221147.73 kB/sec Min xfer = 437344.00 kB Children see throughput for 4 rewriters = 822771.77 kB/sec Parent sees throughput for 4 rewriters = 701488.29 kB/sec Min throughput per process = 180381.25 kB/sec Max throughput per process = 232223.50 kB/sec Avg throughput per process = 205692.94 kB/sec Min xfer = 408720.00 kB Children see throughput for 4 readers = 755252.30 kB/sec Parent sees throughput for 4 readers = 753357.02 kB/sec Min throughput per process = 169105.11 kB/sec Max throughput per process = 198976.81 kB/sec Avg throughput per process = 188813.07 kB/sec Min xfer = 445664.00 kB Children see throughput for 4 re-readers = 753492.39 kB/sec Parent sees throughput for 4 re-readers = 750353.64 kB/sec Min throughput per process = 160626.64 kB/sec Max throughput per process = 201223.11 kB/sec Avg throughput per process = 188373.10 kB/sec Min xfer = 418528.00 kB Children see throughput for 4 reverse readers = 780261.86 kB/sec Parent sees throughput for 4 reverse readers = 778761.55 kB/sec Min throughput per process = 58371.02 kB/sec Max throughput per process = 254657.08 kB/sec Avg throughput per process = 195065.47 kB/sec Min xfer = 120192.00 kB Children see throughput for 4 stride readers = 317923.62 kB/sec Parent sees throughput for 4 stride readers = 316905.36 kB/sec Min throughput per process = 63171.63 kB/sec Max throughput per process = 98114.27 kB/sec Avg throughput per process = 79480.91 kB/sec Min xfer = 337600.00 kB Children see throughput for 4 random readers = 798898.78 kB/sec Parent sees throughput for 4 random readers = 794905.95 kB/sec Min throughput per process = 57059.89 kB/sec Max throughput per process = 391248.59 kB/sec Avg throughput per process = 199724.70 kB/sec Min xfer = 76480.00 kB Children see throughput for 4 mixed workload = 647158.06 kB/sec Parent sees throughput for 4 mixed workload = 491223.65 kB/sec Min throughput per process = 28319.04 kB/sec Max throughput per process = 305288.75 kB/sec Avg throughput per process = 161789.51 kB/sec Min xfer = 48720.00 kB Children see throughput for 4 random writers = 734947.98 kB/sec Parent sees throughput for 4 random writers = 544531.66 kB/sec Min throughput per process = 167241.00 kB/sec Max throughput per process = 207134.38 kB/sec Avg throughput per process = 183737.00 kB/sec Min xfer = 424704.00 kB Children see throughput for 4 pwrite writers = 879712.72 kB/sec Parent sees throughput for 4 pwrite writers = 686621.58 kB/sec Min throughput per process = 186624.69 kB/sec Max throughput per process = 236047.30 kB/sec Avg throughput per process = 219928.18 kB/sec Min xfer = 415856.00 kB Children see throughput for 4 pread readers = 777243.34 kB/sec Parent sees throughput for 4 pread readers = 773302.81 kB/sec Min throughput per process = 184983.08 kB/sec Max throughput per process = 203392.77 kB/sec Avg throughput per process = 194310.84 kB/sec Min xfer = 476896.00 kB Children see throughput for 4 fwriters = 820877.50 kB/sec Parent sees throughput for 4 fwriters = 693823.17 kB/sec Min throughput per process = 194228.28 kB/sec Max throughput per process = 217311.28 kB/sec Avg throughput per process = 205219.38 kB/sec Min xfer = 524288.00 kB Children see throughput for 4 freaders = 1924029.62 kB/sec Parent sees throughput for 4 freaders = 1071393.99 kB/sec Min throughput per process = 268087.50 kB/sec Max throughput per process = 970331.94 kB/sec Avg throughput per process = 481007.41 kB/sec Min xfer = 524288.00 kB Single disk sda reference
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 35191 45728 56689 53307 27889 48508 102400 16 104379 122405 154385 157484 88670 113964 102400 512 315788 347042 351932 348604 271399 288430 102400 1024 358399 366194 388893 379453 338470 369888 102400 16384 353154 443256 425396 422384 410580 444530
-
lanefu reacted to Igor in Please share working orange pi one plus image
Since
they are paying attention that it works on Armbian.
I got message few hours ago saying:
"20190702 is released, which should work on all your kernels."
-
lanefu got a reaction from NicoD in Experience working with Linaro or have Linaro contacts?
I'd really like to build a relationship with Armbian and Linaro... even a small one. Although most of the SBC manufactures we support aren't a member of Linaro... Armbian is a huge win for Arm as a whole, and impacts influencers who can choose to use ARM products in enterprise settings etc.
-
-
lanefu reacted to MartyPG13 in La Frite (AML-S805X-AC)
La Potato has a different SoC - I did try the Armbian image for that on the Frite when the board first turned up on the off chance that it might have some compatibility, but it just boot loops.
Libre Comps posted up on the Kickstarter page that the images would be available in 24-48 hours time, two days ago. It's a no show of course. Given how delayed the board was, I expect Armbian to become available before the official images turn up I've got a Pi4 to play with till then, but I did quite like the idea of Frite being cheap and more open.
Edit: A headless image is available now apparently: http://share.loverpi.com/board/libre-computer-project/libre-computer-board/image/debian/libre-computer-aml-s805x-ac-debian-stretch-headless-mali-4.19.56%2B-2019-06-26.img.xz (343 MB)
-
lanefu got a reaction from Igor in [RFC 001] Changes for boards and features implementing
Okay... Here's a start!
https://github.com/orgs/armbian/projects/1
Adding a step is as simple as "create a note" in the todo column. Then we can convert it to an issue, add PR's etc.
Feel free to add directly, or just ask me to add, adjust, sort etc, and i will
-
lanefu got a reaction from gprovost in [RFC 001] Changes for boards and features implementing
@igor I really would like to capture the all the tasks for refactoring the build scripts and track them as a project in github.
To your point, if the tv boxes branch is no longer solving problems, then we may not want to invest effort into that branch
Sent from my iPad using Tapatalk -
lanefu reacted to Igor in [RFC 001] Changes for boards and features implementing
Development is stalled, it also seems to need some revision and rethinking. Perhaps its going to wrong direction, perhaps its already too big (for one person) to handle? Perhaps moving chunk by chunk of what has for sure been done better to the master? Build system should become less complex, but it seems its getting more. I would propose to move kernel patches 1st out from the main script first, then perhaps do the same with BSP recipes packaging as well? And a good manual has to be done on the way, otherwise it will remain very costly to maintain .. which again leads nowhere.
-
lanefu got a reaction from Werner in SBC recommendations for a wireless router
please read this thread and understand the limitations of the espressobin... and its current stability
-
lanefu reacted to gprovost in [RFC 001] Changes for boards and features implementing
Can we have an update status on this RFC. What's the plan / roadmap ?
-
lanefu reacted to Zaf9670 in Introduction
Just thought I would introduce myself and start on my 5 approved posts requirements.
ETAPrime is the reason I found out about this project and it's something I'd like to help out with when/where I can.
I currently have a few Raspberry Pi 3 B and 3 B+. I also have two Libre ROC-RK3399-PC that I'm looking forward to future support on with the community. I also enjoy gaming and 3D printing as my other hobbies.
Ask me anything? I guess?
-
lanefu got a reaction from gprovost in Helios4 Support
Have you created the filesystem, share, and the added the share to a service (SMB or NFS) and then enabled the service? (it's kind of a long chain)
can you run
armbian-monitor -u and share the link?
-
lanefu got a reaction from TonyMac32 in Daily (tech related) news diet
That is NOT how I want to die.
-
lanefu got a reaction from gprovost in Helios4 Support
The Helios will keep up for that just fine. DLNA might be another option to consider over samba
Sent from my iPad using Tapatalk -
lanefu reacted to AZClusterboard in SOPINE build
I would love to help. I have SOPINE stuff and an original Pine64 from the kickstarter.
-
lanefu reacted to windysea in A64 date/time clock issue
An ntp stratum is not related to accuracy nor precision - it is simply an indication of how many "hops" a given NTP server is from a reference clock. A stratum-0 is a reference clock (IE: atomic clock, GPS receiver, etc). A stratum-1 is the NTP server directly using that reference clock for time synchronization. An SBC with a serial GPS indeed can be a stratum-1 (the GPS would be stratum-0), and there are many public postings on doing this. In fact the NTPsec team is doing "research" on this topic and has published documentation regarding this.
The nature of the reference implementation of NTPd is specifically to maintain accurate time regardless of any hardware timers. Today's "50-cent" parts are still more stable than those orders-of-magnitude more expensive decades-ago when NTPd was first developed.
Google's NTP project may use their own "atomic clocks", but their public NTP servers tend to be on the poor end with respect to jitter. They're intended to be "close-enough", stable, and highly-available. They are not intended to be highly accurate. Their public NTP servers, for instance, implement leap-smearing rather than advertise a leap-second (when appropriate). For this reason Google strongly recommends not mixing their public NTP servers in a configuration with other NTP sources (bad things can happen, and in fact have happened in the past). Google's NTP servers also are behind anycast load-balancers. While this improves availability and end-device configuration simplicity it actually degrades performance.
In my own testing google's ntp servers typically have higher jitter than most of the larger NTP pool project pools, the latter of which are already commonly used as defaults in many OS distributions.
Configuring and building a non-tickless kernel is required in order to enable kernel-pps (aka "hard pps"), which typically has far less jitter than "soft pps". However, doing so even with the latest 5.1.y (DEV) kernels results in an unstable platform where the issue noted in this thread will manifest fairly frequently. It may just be that A64-based SBCs are not suitable to host NTP reference clocks and stratum-1 NTP servers but earlier kernels did not seem to have this issue so it may just be that a previous mitigation got lost along the way.
-
lanefu reacted to TonyMac32 in Overlays
I'm not sure what will and won't be a worthy overlay to put directly into Armbian itself with the current script structure, I intend to document the ones I add here, @martinayotte may as well if he's bored. :-P
I will be focusing on RPi GPIO compatibles, since those are nice pre-packaged devices in general. I have Tinker, RockPi 4, Le Potato/K2/C2, Tritium H2+/3/5, Rock64, Renegade, and some others.
Everything here is a placeholder at the moment.
Status Tinker Le Potato Meson64 Renegade Tritium Automation Hat Generic DAC (Pi) MCC 118 DAQ MicroDot PHAT Inky WHAT (e-ink) ENC28J60 for Pi
-
lanefu reacted to TonyMac32 in Overlays
I agree, which is why this is not under normal development as a topic. There is the reality, however, that people buying RPi-shaped boards want support for RPi peripherals and accessories, so my thought is to discuss ways to support that, while implementing a few on a platform that only has 1 board with gpio anyway (Rockchip). If it must be that I have a fork of the build system and stuff all of this in "user patches" then so be it, but I think we need to come up with a way to handle this per board rather than per family.