Igor
-
Posts
14666 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
We don't think to push this experimental feature into the kernel, but you can try on your own. Patches are here:
https://github.com/armbian/build/tree/master/patch/kernel/sunxi-dev, but disabled and perhaps they need some adjustments. BTW. current 4.12. dev kernel is broken upstream for Allwinner boards which bring some more troubles to start.
-
2 hours ago, tkaiser said:
I was talking about why we behave like idiots and start to support boards solely based on the fact that a hardware vendor sent us dev samples worth few bucks.
I thing we got the point. Not sure if we really behave exactly that way, but yes, we need to change pattern and not jumping up when boards arrive. Agree on that. It's in our own good. No doubts about that.
2 hours ago, tkaiser said:No polls/votes
On my proposal, developers has last word, but we still get valuable data when asking community what do they think - we can limit voting to old users with this much posts ... it's just a proposal.I agree that the most cheap is also among most popular ones ... but those is hard to avoid - I am referring to Orangepi / Friendlyarm boards in general.
2 hours ago, tkaiser said:And again: Board bring up is fun
It's fun but some pain always comes in the package. We can to cut it down and play smarter not harder
Well - what about community supported boards - which does not need our approval? It should be in our interest to provide opportunity for anyone who want's to bring board into Armbian and benefit from anything what build script offers ... but we have to make clear that there is no support within the build process, at first login, don't provide downloads, ... etc. One good example are balbes150 creations, which we even think to merge in once, but it's some work ... -
On 7. 6. 2017 at 6:02 PM, tkaiser said:
IMO we need a transparent process to decide whether to support new devices or not weighing pros/cons for both developers and users and estimate efforts especially if it's a new platform. Even if hardware vendors send out free dev samples we should not automatically start with new boards but discuss and evaluate first since we already deal with way too much boards with a crew just too small.
It could be done simply via (double) voting. Once (first) from developers perspective and once (second) from general public and where is the match (third) ... Questions which goes up - How often / when shall we repeat this? Will boards without any interest be ever back to the list? How many we will accept into next round / some initial state? Wanting to support (being elected in this voting) does not provide warranty that we will actually come to the full level. We might still ditch the board while trying to support it.
Right now we can come up with 5-10 boards which can be put on vote (and you can choose up to 3):
- Rock64- Olimex A64
- Esspressobin
- Nanopi K2
- Bananapi M3
- Orangepi Win
- Orange 2G IOT
- Helios4
-
-
We have strengthen moderator team and we can ask them to conduct regular board popularity contests? Somebody has to update those lists, the rest is more or less automatic.
I think 10 boards / round is o.k. and it's o.k. to put exotics, let's try again and failed boards too. You already know that there will be no vote for those, at least from developers perspective
-
18 hours ago, zador.blood.stained said:
If it's an obvious spam - just use The Banhammer
This function is (was) not enabled by default - just hover over the username -> "More options" -> "Flag as spamer" / "Warn user" . When flagging someone as spammer - posts are also hidden and AFAIK user info goes upstream to general spam database. Spammers busted on any IPB forum are blocked everywhere ... with one click. In reality there are some problems with this service - sometimes prevents humans to login - and it's currently disabled. I'll check again upon next major forum upgrade.1 hour ago, StuxNet said:I've done my reading of the requirements
Welcome on board
- this requirements above shell be updated but remained simple, unambiguous and understandable to everyone, not just to us.
I guess I will need to rewrite the text saying "rare" to "extremely rare" since forum crew expanded this quickly Closing recruitment for this year or until someone decides to have enough of this.
-
-
We have dispute in less than one day ?
When moving, leave a pointer - it deletes auto in 30 days.
-
I assume you upgraded from 4.9.7 ? Than go back, until we find out where is the problem.
Install those two:http://apt.armbian.com/pool/main/l/linux-4.9.7-sunxi/linux-dtb-next-sunxi_5.25_armhf.deb
http://apt.armbian.com/pool/main/l/linux-4.9.7-sunxi/linux-image-next-sunxi_5.25_armhf.deb
-
Than get one small H3 board and perhaps try adding this 4 USD value circuit:
http://www.ebay.com/itm/282352753274
... but don't know if and how its reliable.
-
I made another test with exact same image: http://sprunge.us/aGEB + iperf test. I switched ports, first time was gigabit, second fast Ethernet.
Spoiler[ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 11.7 MBytes 98.0 Mbits/sec 110 266 KBytes [ 4] 1.00-2.00 sec 11.1 MBytes 92.8 Mbits/sec 54 215 KBytes [ 4] 2.00-3.00 sec 11.3 MBytes 94.9 Mbits/sec 27 168 KBytes [ 4] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 0 187 KBytes [ 4] 4.00-5.00 sec 10.8 MBytes 90.7 Mbits/sec 6 153 KBytes [ 4] 5.00-6.00 sec 11.4 MBytes 95.3 Mbits/sec 0 177 KBytes [ 4] 6.00-7.00 sec 10.8 MBytes 90.8 Mbits/sec 0 191 KBytes [ 4] 7.00-8.00 sec 11.1 MBytes 93.3 Mbits/sec 0 205 KBytes [ 4] 8.00-9.00 sec 1.49 MBytes 12.5 Mbits/sec 2 202 KBytes [ 4] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 1 202 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 90.9 MBytes 76.2 Mbits/sec 200 sender [ 4] 0.00-10.00 sec 90.9 MBytes 76.2 Mbits/sec receiver [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 12.7 MBytes 106 Mbits/sec 0 691 KBytes [ 4] 1.00-2.00 sec 11.2 MBytes 94.4 Mbits/sec 0 1.34 MBytes [ 4] 2.00-3.00 sec 11.2 MBytes 94.1 Mbits/sec 0 1.78 MBytes [ 4] 3.00-4.00 sec 11.5 MBytes 96.4 Mbits/sec 0 1.95 MBytes [ 4] 4.00-5.00 sec 11.4 MBytes 95.3 Mbits/sec 0 2.02 MBytes [ 4] 5.00-6.00 sec 10.7 MBytes 90.0 Mbits/sec 0 2.04 MBytes [ 4] 6.00-7.00 sec 11.8 MBytes 99.0 Mbits/sec 0 2.05 MBytes [ 4] 7.00-8.00 sec 10.6 MBytes 89.0 Mbits/sec 0 2.06 MBytes [ 4] 8.00-9.00 sec 11.7 MBytes 98.4 Mbits/sec 0 2.06 MBytes [ 4] 9.00-10.00 sec 11.0 MBytes 92.1 Mbits/sec 0 2.07 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 114 MBytes 95.5 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 114 MBytes 95.5 Mbits/sec receiver
My board is Orange Pi Zero 1.1 as you can see on the pic. My zero works with zero problems. Change cables, inspect PCB, which version is yours?
-
2 hours ago, rufik said:
Ups, Lime2 price is about 55 euro, so somehow expensive when compared to $25 for NanoPi Air...
Lime2 (and some other boards) has what you asked for: battery backup, while Air does not have that and its probably wrong board for this job?, regardless of the price and small / sexy size. Why bother with price difference? If this would be a commercial project, imagine how much money you saved by choosing the right board for the job at the very early start
If you need battery backup, options gets limited.
-
42 minutes ago, blaster_56 said:
i'v test your image, writing it with live linux, same problem about ethernet, wifi work very well but ethernet is not working, it didnt take the dhcp and dont working in static IP, link is ok from ethtool, ethernet cable work with my computer.
If you have network problems with all images and also with preinstalled Android, that makes me think on rare hardware issues, which we can't help much. I have seen bad soldering causing them - check your PCB for possible defects. Try once again with Zero - network stack is exactly the same and board must works - with image for it.
I can assure you that network in our images works (this is a very basic condition for development images too, unless broken) - I made a test on the image which I propose you for download. Just to make sure.
-
10 minutes ago, rufik said:
s there any overview/list of SBCs with PMIC/PMU support?
OLinuXino-Lime2, C.H.I.P.?
Most boards with: A10/A20/A33/A64 ... probably I forgot some, but that's good enough. Lime2emmc seems like the best choice to me, because A64 is not that ready yet. -
OK. Also remind / warn me and other moderators and vice versa when we go out of topic or made some invalid post. Humans do mistakes
-
Granted! Thank you.
Some more general thoughts:
We have a very strong spam protection, so you won't have much job dealing with robots, but human creations which sometimes are spam. Since our moderator team got stronger now, we can keep forum in better condition - keeping posts on topics, which was somehow neglected.Our job is also to limit down repeated questions the best way possible with as little impact as possible - with tools mentioned above and procedures which should be summed above. You have right for post editing - use it to update "Moderator duties", when we come up with something to add. I'll do so, but sometimes I won't be able to react promptly. Don't edit other people posts unless it's really necessary.
And remember we need to stay humble. We are all just people with ability to make certain moves, which shall be in common interest. Authority will be needed in case of troubles.
Prohibiting (ban) and deleting content should be last option - if warnings does not produce any effect - our forum is in general very good in this manner - we issued one temporal ban and currently we don't have banned users.
-
5 hours ago, Stanislav Sinyagin said:
I can help with Perl or shell scripting, if needed
Help is welcomed and needed. Of course.On any of those three major projects:
- build engine https://github.com/armbian/build (shell)- configuration utility https://github.com/armbian/config (shell)
- general documentations https://github.com/armbian/documentation (text)
Start something simple to get you going - configuration utility needs some fine touch / adding new features rework into cleaner code, than proceed to hard nuts
-
Try to change to this u-boot first:
http://apt.armbian.com/pool/main/l/linux-u-boot-lime2-next/linux-u-boot-next-lime2_5.25_armhf.deb
-
23 hours ago, chwe said:
As you can imagine, my time & know how (in this area) is somehow limited, but if it helps you and other developers to do the hard stuff that I'm for sure not able to do, we can give it a try.
https://forum.armbian.com/index.php?/topic/4519-moderator-duties/
More volunteers for this job? Not much to do but still it's better if load is shared. -
6 minutes ago, martinayotte said:
Since he was the OP, he still had the right to change the thread title from "dwmac-sun8i" to "problems-with-orange-pc" within minutes after I said that he hijacked the thread ...
That was me ... since I cut those posts out and move them under new topics.
-
What shall moderators do on our forum.
Basics:
- job should be invisible
- spam control and clean up (rare)
- approve posts from new users (daily)
- Warning: editing topic tittle change it's URL
- move topic to appropriate forum (rare) (tick "Leave a link to the new location" - it deletes auto in 30 days)- recognise and tag tutorials & researches. Move them into "Research Guides & Tutorials"
- merge, pin and lock topics (rare, with caution)
- cut and move posts to new topics (rare, with caution)
Intermediate:- Warn User for:
- spamming,
- inappropriate language,
- signature violation,
- abusive behaviour,
- topic bumping.
Stop being a moderator:
- when you don't want
- on multiple complains
To study and add more:
https://bubbajuju.com/forum-moderating/ -
A20 boards are generally just fine, while R1 ... we all know it's shitty by design and If we had EOS section since start, it would be already long gone simply because it sucked so much of our time, more than any other board, without any point & value.
There are four images for R1 for download - all are working now - I remake last image with last working mainline kernel (4.9.7) and that's all. EOS means we will officially not deal anymore with the board, but this does not prohibit anyone to make moves. Kernel updates will continue to run out so their is still hope for the board.
I also added two A10 boards there too. Why? They are working O.K., they are stable, but make just enough troubles on upgrades. Do we need to deal with them? No. They are rare and we don't have more than one sample around.9 minutes ago, Tido said:no one ever beside TK complained
Well, I would complain too, but it doesn't make any goodQuoteLaunch --- Due in 149 Days (or when it is ready)
and please put that somewhere were we can see that, like here (it is already written just needs a link to the lines above)
Countdown instead of frozen numbers ?
Yes, I'll update and make it more visible asap. In any case nothing major before September. -
On 17. 6. 2017 at 11:40 AM, Igor said:
Lamobo R1 / Cubieboard 1 / Lime A10
Gone to EOS -
25 minutes ago, scimmiettarossa said:
thanks for your reply.. but it is already installed.... seems it is not the cause of my issue
This is the cause - on my CB1 was the same.Just replace the boot loader and reboot is no longer a power off.
-
31 minutes ago, blaster_56 said:
I'm not the only one who face this kind of problem, i can garantee you that the Debian Jessie Image was not tested and Ethernet Driver is corrupted. (version 5.25 and 5.30)
There are lots of problems with experimental kernel which is this topic about and which we don't support.If you have Opi PC+ and you want Debian Jessie: https://dl.armbian.com/orangepipcplus/Debian_jessie_default.7z (tested!)
-
Install attached u-boot and you will be fine.
Problems with Orange PC+
in Allwinner sunxi
Posted
You will only waste time - building from sources won't make any difference.
If this new hw revision is changed to the degree that Ethernet stop working, than we have a problem which need close examination. First I'll wait for others to confirm non working network on v1.4 than I'll ask board maker what was changed and why.