-
Posts
14692 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
I revert cubox and clearfog, for sunxi I am bit confused what to remove and what to leave due to overlay support ... and Tinkerboard / MiQi @TonyMac32, shall we go back to 4.9 with NEXT too?
-
We have idea, but lack of time, to provide IOT / slim version, which means rework (put under switch) those sections + conduct few tests ...
https://github.com/armbian/build/blob/master/configuration.sh#L103-L139
https://github.com/armbian/build/blob/master/distributions.sh#L105-L106
Other option is do uninstall certain - non relevant to your case - packages.
-
11 minutes ago, zador.blood.stained said:
Client or AP? Can it be easily reproduced on any other boards (sunxi-next, sun8i-dev branches) so I could try to capture a crash log?
Client, ath10, crashed also on Clearfog with 4.11. Will do more test and provide logs ... currently out of office.
-
9 hours ago, zador.blood.stained said:
Well, also I could reproduce on Hummingboard when trying to connect wireless - it instantly crashed on 4.11.5 while working fine on 4.9.33 ...9 hours ago, tkaiser said:but for whatever reasons Armbian tries to introduce update drama every few months. Why exactly?
Of course there is risk when upgrading, especially u-boot, because worse case boot breaks ... but kernel upgrades are more flexible since it "only" breaks some part of functionality at worse. Like in this example. Perhaps this upgrade procedure should be divided and provide more selective relevant upgrades. That should limit down problems.
9 hours ago, zador.blood.stained said:I believe we have an option now
Also possible to apply it to images by default and we gain stability - user must act to get latest updates. Like on deprecated boards. -
Another small example:
https://forum.armbian.com/index.php?/topic/4557-blank-password/#comment-34201
This question was posted to Allwinner H3 section but it's unrelated to hardware - it's very general question - better to be moved one level up, to general section. -
6 hours ago, t-bob said:
something like:
wifi - working since 1/6/2017
usb - working since 1/4/2017
bluetooth - NOT working. No ETA. Developer assigned
hdmi - Not working. No ETA. See https://linux-sunxi.org/blahblah for more information
gpio - not working. no eta. no developer assigned
12c - not working. no eta. no developer assigned
This job is for anyone with minimal inside knowledge. Related or unrelated to Armbian.Again - "no support" means we will not provide any information regarding state and problems of moving experimental things. It's expensive and provide negative results. Double negative from our perspective.
When things are good enough for bare server usage, similar kind of report is found at download page - this and that is not working, ... Currently there are too much problems and no one out of five active developers would like to have yet another burden. We don't want that experimental images are used by end users in first place. Some even use those unfinished work in production and are saying that we are losers and idiots, because upgrade break their wonderfully working system. Yes it happens. It happens way to often and there is no compensation. They don't support as in any way but expect full support from us.
We came to conclusion that we will not share any information (for end users) regarding WIP work. Developers can find and acquire information from Github commits, from ours an upstream. Everything relevant is written there, but to write a summary ... anyone can.
-
Shall we go back with sunxi and cubox NEXT to 4.9.x and push update out since:
https://forum.armbian.com/index.php?/topic/4254-cryptdisks-fail-with-new-kernel-41012/#comment-31614
Any other critical thing? -
Recent hot debates sparked many ideas, but no need to rush. Rome was not built in a day

Rearrangement outdated forum structure should also improve the situation - at least we have to get the best out of forum, even it has limitations, which were exposed and I am aware of it.
Few concrete ideas for reshaping the structure - what if we clearly divide support forum into stand alone section - we isolate section "Technical support" only for: "Allwinner A10/A20 Allwinner H2/H3 Allwinner A64/H5 Amlogic Freescale i.MX6x Other boards"
Than we have section, which does not live very much and should also be redesigned:Projects and services
Reviews
Support of deprecated boards / old board support
3rd party armbian builds, etc.
Development
I propose to merge / remove Armbian build framework and Armbian Tasks into Development.
Free / rearrange
Move everything up to corresponding forums, what can be moved. This part was never meant for technical stuff but more for casual stuff like: "I have a new cat - what do you think?" stuff
-
On 20. 6. 2017 at 9:38 AM, 8BALL_SA said:
Using the network manager, if I disable and then enable the wifi then everything works for a while.
It looks like a network-manager issue. I could reproduce ... but it only failing when trying to connect from windows machine
while working fine when connecting from Linux.
-
54 minutes ago, Asterion said:
That is, card erased and distro image burnt on SD, first boot into system, enter root then 1234, enter a new root password, goes away a few seconds and then the error comes up.
username: rootpassword: 1234
repeat the password: 1234
new password: xxxxxxxxxxxxxx
repeat new password: xxxxxxxxxxxxxx
-
3 minutes ago, zador.blood.stained said:
In my opinion this is too much, so we should disable some nightlies fron this list too.
Yes, let's move all out and enable upon developers requests? -
Compilation usually hangs / takes hours if SD media is from other century (extremely poor 4k performances). This one looks o.k. which probably means this: https://forum.armbian.com/index.php?/topic/3915-upgrade-time-cross-compile-kernel-on-another-machine/&do=findComment&comment=28620
-
35 minutes ago, znoxx said:
What do you think, which kernel to pick for downgrade ?
I guess roll back to previous version (4.9.7) should do the job.
apt install linux-image-next-sunxi=5.25 linux-dtb-next-sunxi=5.25Than go to armbian-config and freeze kernel upgrades until this is not solved ...
-
If your power supply is below 1.5A / low quality, than strange random problems might happen in such configuration: board + mouse + keyboard + HDMI screen + wireless ... and we are back to basic hardware problems written in https://docs.armbian.com/User-Guide_Getting-Started/
Quotea proper power supply according to the board manufacturer requirements (basic usage example: 5V/2A with DC Jack barrel OR thick USB cable)
Even you have a good one, just make sure to test with different one and remove all from USB ...
Is this the case?
-
50 minutes ago, 8BALL_SA said:
What ssh server does Armbian use by default?
Default / standard open-ssh server which works perfectly well for millions of people. Problems are not on this level ... Dietpi is illusion of choice, copy of Armbian, it uses our kernel, builds system, everything what is relevant and it should behave the exact same way. Bugs present in Armbian (if this is a bug at all?) will be present there as well.
I hope you don't use experimental images? They are not ready for usage. -
-
I put torrent server on Lime 2 and some stress testing scripts on Cubietruck with 4.11.5-sunxi ... I want to see then crash
... only one day up time, so hard to make any conclusions yet.
-
You mean that you will start directly in desktop?
You need to login once to create a username, than desktop goes on and next time you will be running desktop ... if you downloaded desktop image in first place, otherwise you need to repeat the job. Check docs.armbian.com for basics. -
18 minutes ago, blaster_56 said:
I'll try anyway and if its not working i'll contact aliexpress to stop selling this default product until problem fixed.
I am almost 100% that it won't work - there are zero relevant changes to sources between 5.30 and today. Still wanna try?
Those are development boards and if something is not working perfectly fine, nobody cares since most such things are fixed with software ... We have one (few?) known case(s) and there are 10.000+ happy Orange pi Zero users. Nobody will believe ... even I was initially very sceptical. It also could be some hardware damage, which can happen.
-
Just now, blaster_56 said:
I have the version 1.4, Ethernet not working 100% on version 5.30, i'll try to build from source and try the new Image.
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. -
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.

Partial bugfix update
in Advanced users - Development
Posted
It works for me to, cubox-next, ath10 and brcmfmac.
@tonymac32
Reboot reboots.
http://sprunge.us/CaOj
U-boot on eMMC:
U-Boot SPL 2017.05-rc3-armbian (May 04 2017 - 15:10:29)
Returning to boot ROM...
U-Boot 2017.05-rc3-armbian (May 04 2017 - 15:10:29 +0200)