Igor
-
Posts
14616 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
Perhaps you are using unsupported codec?
HW accelerated video should work with supplied mpv on this image: https://dl.armbian.com/orangepiplus2e/Ubuntu_xenial_default_desktop.7z
-
3 hours ago, tobias.faust said:
unfortunally, the update script is down
Yes, because it's deprecated. Updating on our system is: apt-get update && apt-get upgrade -
47 minutes ago, Charizard said:
So we cannot use a lot of programs with this kernel like hostapd or openvpn
I just made an WPA2 based AP with my Cubietruck running 4.11.5 and it's working fine ... ? -
10 minutes ago, Charizard said:
4.11 kernel has a broken crypto functions. So we cannot use a lot of programs with this kernel like hostapd or openvpn. Can you move mainline kernel to experimental for the Banana pi, please ?
Thank for notify - didn't know that. Is there a patch for this?
-
52 minutes ago, Stanislav Sinyagin said:
Now 4.11 kernel update is missing for nanopineo2.
This indicates that automated built process broke. Nothing unusual for development areas / work in progress ...
15 minutes ago, Stanislav Sinyagin said:with 4.11, there's still an issue that an attached WiFi dongle is not visible after reboot
Development process is based on volunteer contributions / time and it takes months before issues gets fixed.
-
6 hours ago, RSU said:
Update works fine for me, problem fixed! Thank you!
Too many people wanted to update their system at the same time and server could not handle requests any more. You had luck.
Now this "Too many open files" error at server side is solved. -
21 minutes ago, wanda said:
Is it easy to switch to the legacy kernel or do I have to reinstall completely ?
With latest image - run armbian-config -> Switch / Switch to alternative kernels -
12 minutes ago, Wolf2000 said:
Kommt der kram mit der SD-Karte und Stromversorgung das ist es sicher nicht!!!!!!
Und das löst das Problem nicht
Then we need to see a console log, otherwise we won't be able to solve anything. I can't reproduce. -
1 hour ago, Aux said:
Sorry guys but there is something completely wrong. Backup image recovered, update process from 5.25 to 5.30/31 started, reboot same errors.
I just test the upgrade once again. Starting with this image: https://dl.armbian.com/bananapi/archive/Armbian_5.25_Bananapi_Debian_jessie_next_4.9.7.7zapt update
apt upgrade
Zero problems.
Spoiler____ ____ _ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_) | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | | | |_) | (_| | | | | (_| | | | | (_| | | __/| | |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_| Welcome to ARMBIAN 5.31 stable Debian GNU/Linux 8 (jessie) 4.11.5-sunxi System load: 0.51 0.14 0.05 Up time: 0 min Memory usage: 5 % of 996MB IP: xxxxxxxx CPU temp: 41°C Usage of /: 8% of 15G [ General system configuration: armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.comLogs: http://sprunge.us/QjUT
-
Firefox 54 finally goes multi-process, eight years after work began
https://arstechnica.co.uk/information-technology/2017/06/firefox-multiple-content-processes
-
Most likely only UART port is disabled in board configuration, but it can also be something else ...
-
Repository just bumped to 5.31 which should fix the problem of this topic - updating. Affected images are in process of replacing.
-
2 hours ago, Charizard said:
Unfortunately I got the same issue as the Nanopi. LXC containers are freezing the system with 4.11.x kernel.
You are using development kernel, which we don't support for many reasons.6 hours ago, Aux said:I would like to describe more in detail.
The update from Armbian 5.25 to 5.30 / 4.9.12-sunxi does not work.
Using the u-boot-sunxi-with-spl.bin on / dev / mmcblk0 brings nothing.Have some pictures made, maybe this will help?
This indicate some problems with u-boot script. Check and change rootdev parameter in /boot/armbianEnv.txtsetenv rootdev "/dev/mmcblk0p1"
-
R1 with v5.31 legacy works.
Will rebuild in the morning.
-
Mainline
-
Quote
M1 and PRO are O.K., will check R1 and M1+ too
R1 it doesn't connect to network. -
4 minutes ago, Aux said:
but had not worked, Had possibly flashed wrong drive mmcblk0p1 instead of mmcblk0 ??
Correct is /dev/mmcblk0 -
59 minutes ago, zador.blood.stained said:
Please try testing after recompiling the u-boot now.
M1 and PRO are O.K., will check R1 and M1+ too
4 minutes ago, Aux said:same issue with update from Armbian 5.25 to 5.30 bootloop on Banana Pi.
Using u-boot from previous version is a way to go - you have to update it on another computer if you already issued an update.1 minute ago, Echo said:OrangePi PC update was successfully. A reboot succeeded. Thanks for the update!
You are welcome.
-
7 minutes ago, krzystke said:
maybe help with finding bugs and problems
That's very easy in this state since lo't of bugs are present
Fixing problems is what we all need. This kernel needs 6-12 months before "hunt for bugs without need for fixing them" will be desirable.
-
9 minutes ago, Echo said:
I've just upgraded my OrangePi PC, but didn't reboot yet.
This problem should not be related ... if you report the problem, we need all possible details -
Nightly builds are experimental automated builds made usually from development [4.12.x] kernel. On download page we expose Ubuntu desktop legacy and Debian server legacy. Those use standard stable kernel.
-
19 minutes ago, tkaiser said:
Can we agree on a process like https://forum.armbian.com/index.php?/topic/4451-example-support-proposal-for-rock64/ and if not what are your ideas?
I support the idea of protocol - if this is meant that way - but honestly I haven't been able to catch up - only quick scan.44 minutes ago, tkaiser said:and we always just talk and talk and talk but nothing happens.
My impression is different. A lot has been done, but also a lot can be done. The question is, what do we want and can we afford? Some things were made wrong, but in general we don't waste that much time either (if we rule out supporting Orange Pi zero wireless, similar pointless cases and perhaps support in general). We are already at a limit of what we can do with resources we have and that is one of the primary reasons, why all things weren't done yet. Even we cut off half of the board support ...
There is more than just clear comm and few rules to achieve greatness.
20 tools, each covering one aspect of a community or group by Pieter Hintjens:QuoteStrong mission -- the stated reason for the group's existence
Free entry -- how easy it is for people to join the group
Transparency -- how openly and publicly decisions are made
Free contributors -- how far people are paid to contribute
Full remixability -- how far contributors can remix each others' work
Strong protocols -- how well the rules are written
Fair authority -- how well the rules are enforced
Non-tribalism -- how far the group claims to own its participants
Self-organization -- how far individuals can assign their own tasks
Tolerance -- how the group embraces conflicts
Measurable success -- how well the group can measure its progress
High scoring -- how the group rewards its participants
Decentralization -- how widely the group is spread out
Free workspaces -- how easy it is to create new projects
Smooth learning -- how easy it is to get started and keep learning
Regular structure -- how regular and predictable the overall structure is
Positivity -- how far the group is driven by positive goals
Sense of humor -- how seriously the group takes itself
Minimalism -- how much excess work the group does
Sane funding -- how the group survives economically
21 minutes ago, tkaiser said:We support way too much boards to deal with, we scare away potential contributors
It could have impact or not. Perhaps our way of doing is too good, strict or perfect? It depend from which perspective do we look. I know that current scenario of engagement is not ideal and needs change if we don't want to get crazy and to level things up. This takes time and energy and we are going from one large project to another without stop. I see that more problematic than we failed to implement some protocol or feature.
QuoteUsing Armbian and having to fear an 'apt upgrade' really sucks. There was a lot of babbling about what has to happen prior to releasing major releases ('team testers' and stuff) but... today we're on 5.30 for whatever reasons (maybe I just missed discussion, call for testers and announcement?)
Actually we did testings, but this kind of issue could be found only if all boards were tested. We are not on that level, even 5 people (we have 8 people in total for testing from last call, but theirs board diversity is another problem) responded to assigned tasks. Testing protocol was not fixed yet, since we need few real world experiences, before we know what is important and to wrote all this down.We need to divide stable and latest builds, freeze non critical stuff (u-boot), ... yes.
I'll fix recent upgrade problems, when I'll fully understand them, but first I would need to get some sleep and recharge. I removed failed u-boot from repo but images for bananas are failed too. -
15 minutes ago, Wolf2000 said:
Hi Igor
With my Banana Pi 1 nothing more about HDMI I see only the cursor flashes.
What could I do?
Or is it death?
Even you wait until network timeouts ?
If you did an update, you need to rollback u-boot to 5.25 -
The more I test, the less I know
This test image works fine on M1+, while network doesn't come up (properly) on: M1, PRO and R1
Nightly images?
in Advanced users - Development
Posted
Conclusions:
- nightly kernel and BSP building yes, nightly images once per week
- focus more to provide simpler way for new developers to get in
- nightly images should be carefully picked to provide best "price performance" ratio
and another proposed actions:
- moving another three boards (Lamobo R1 / Cubieboard 1 / Lime A10) into deprecated sessions. All those boards get one last update with last known working configuration and frozen kernel packages
This a current project overview, which we try to follow. Is this time span perfectly o.k. ? Not sure. We will need to adjust it in the future, but it’s something to go with and stick to it, when and if we agree:
UPCOMING MILESTONES
Milestone Responsible Person Due On Feature developement --- Due in 81 Days Feature freeze --- Due in 90 Days Beta testing and bug fixing --- Due in 130 Days Writing release documentation --- Due in 142 Days Launch --- Due in 149 DaysWithing project management we manage to establish fully operating testing system – a person get’s an email, when and what to test – his report is clicking few check boxes + adding a note when necessarily. Technology was tested twice and it works, methodology needs broad discussion. Project manager is the one, who has overview and drive (volunteer) developers to fix this and that. In reality this means I was driving myself and Michael was assisting in this and solving problems which are out of my league. Since we were also testers, most of bugs were saved already on the way ...
Project management is yet another full time position, which waits to be
filleddeveloped and filled in. We deliberately use this hidden, because I was not sure if it’s the right way to go, because not everybody needs to be involved in everything and because not finished products are better to hide. Check email.Until there is no somebody who will take a full lead on this, I am moving it forward with (my) highest possible speed. Well, in fact it's already we. Tido is helping in this beta trial process.
We can add text to forum description, which board are officially supported – I know people will still fail to see.
Yes. This is at least much simpler to support and is to consider.
Yeah. At least we are highly motivated to end / limit at best as possible.
We would certainly need more moderators, which would take care of such questions appropriately. Technical knowledge about those boards is not a requirements. If @chwe wants to take care of general moderator duties, he is one click away
This is fine, but very hard to maintain.
The rest elsewhere. This one is already off topic.