-
Posts
14571 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
-
-
Can confirm only for Pinebook. No other Pine around.
Wrote on mobile -
1 hour ago, KuDeSnik33ra said:
Can some one help me, please, clarify
There is no support in legacy kernel for overlayroot because kernel is too old for this function, while mainline kernel is not on the (end user) level for using it. https://forum.armbian.com/index.php?/topic/4239-opi-zero-mac-address-issue-on-mainline-kernel/&do=findComment&comment=32623 -
Quote
To conserve resources we could rebuild packages daily but rebuild nightly images only once a week, and we could significantly cut down the number of nightlies.
OK, once per week and interessant only. I'll clear them out during this week. Will also push 5.30 updated images out.QuoteWe can leave this part as is - third parties are fully responsible for providing support to their users, but we can accept requests like adding options to kernel configuration since this will be beneficial to Armbian users too.
Fine with me.
QuoteAnd creating separate lists for each group IMO is the best way to go, adding switches like "show WIP" and "show obsolete" and mixing stable boards with everything else will create unneeded confusion and complication.
I made a third and I hope last adjustements. Now each one has it's own page, accessible from menu, below "Download". In /download, we only have stable, nothing else. I was only thinking to add links from there to WIP and deprecated section? Also some more explanation needs to be added to WIP and deprecated.
QuoteI am against adding any info for the hardware that we don't plan to support anytime soon. Who will maintain those lists and how?
Specific is to big waste of time for us ... no, perhaps some general infomation that users will
understandget some ideas / hints, why we don't support just every board on the market and that shitty boards exits and there is nothing much we can do about. -
Steps from 2015 might not work today ... btw. Why don't you use our script? It works out of the box. I think it should work also with two partitions.
-
13 minutes ago, op1tjaap said:
Would like to solve this because it would give me the freedom to compile a development kernel of my choise.
If you are using our build scrpit - you already can do that - just use the packaging adjustements we made. And those you did, they look o.k. to me. Well, the kernel branch you are using, might not be bootable? Try first with some stable branch, "known to work kernel". 4.12 and sun8i doesn't look close to fully stable branch. -
7 minutes ago, Vladimir Gamalian said:
lsusb did't show any devices but two hubs.
Well, as I said. You have to reconfigure header functions to your need. It'a not a job of Armbian to do so. Somebody else might have other needs and they will say "why I2C is not working out of the box?" or similar ... If you are using modern kernel, we use overlays ... check docs.armbian.com for manipulation those features. -
27 minutes ago, Vladimir Gamalian said:
it is armbian related problem
Have you check our stable build? Missing features in WIP images is normal situation.
Edit: disabled USB on header can be considered normal. It's up to you to reconfigure board upon your needs.
-
21 minutes ago, op1tjaap said:
This means that things maybe go wrong because of this.....
Exactly. This is a patch which adjust / fix Debian packaging process. Debug starts here ... and also it might be related to CONFIG_LOCALVERSION_AUTO kernel config.
-
10 hours ago, t-bob said:
then it's OK so i expect the issue is in armbian-firmware
Nightly / WIP / preview / development firmware (must) have bugs, otherwise we would call it "stable"
We provide those builds with purpose of bug hunting and since people expect that they should work (before job is done), we will stop providing them. We waste a lot of time explaining, that it's normal that things breaks, than fixing an actual problem. I made quick check, but can't find where is the problem.
Last time I was testing this feature, it worked as expected - from armbian-config, which does this: https://github.com/armbian/config/blob/dev/debian-config#L601-L615 when issuing "freeze kernel".
-
Until two weeks ago, we also didn't have bootlogo on Pinebook. You probably need one of the patch from here:
https://github.com/armbian/build/tree/master/patch/u-boot/u-boot-pine64-default
This update is not yet present in repository.
-
Installing KODI is not trivial on any general OS / Debian / Ubuntu, not even on x86 machine. Second, you try to install it on modern 4.x kernel, which arrived on XU4 months ago and it's not matured. I have no idea if this is already possible. Third. Armbian is not focused to provide multimedia / closed source drivers by default, while I think it should be possible to build KODI on top of Armbian. In any case, start rather with old legacy kernel, check (at hardkernel forum) which additional libraries are needed and than you have much better chances to succeed,
-
When "include beta and deprecated images" is checked, Why is my board not supported? link pop's out and that will be relinked to github or rendered here: https://www.armbian.com/unsupported/
That's really all for today. Have to do some barbecue

-
Bump. It's done in one page and communicated clearly.
-
22 hours ago, tkaiser said:
Since while supporting such devices might be absolutely wrong but board bring up could be fun we could treat these devices simply as 'WiP forever'.
What about having yet another section with "Limited support". This means they are still getting updates, but no end user support exists for those?
"No support" section will need some extra work for now and for the future - if we want to have it solved in same design as those boards. If only a link to some .md or forum post, than this is no problem. -
I push some update on text & colours.
-
What about this way? + some small print at each section? Dividing into more pages doesn't seem to be this century web design technology

https://www.armbian.com/download/
Which boards should also go to WIP section?
The rest I'll check in next days. -
4 hours ago, t-bob said:
Where do i log the other issues ?
Kernel features -> Github https://github.com/armbian/build/issues and we will slowly put them in. Always provide for which kernel you those features go. -
I attached temp meter to heat sink and can't get higher readings than 49°C, Clearfog is not in a box and ambient temp is around 22°C. Adjusted:
https://github.com/armbian/build/commit/e5579a0957fd7b394d3b418671b4f0f82b334be9
-
12 hours ago, Tido said:
Will you open a section in the forum '.unsupported' - so there is a place where those Threads can be put as well ?
What about just removing unsupported board(s) from forum description & closing new topics with "no more active support"? I don't expect much if any activity on those boards.If no objections pops out, those four will get last update with 5.30 and will be moved our from armbian mainline support.
-
IIRC it's a leftover from first kernel, which had wrong readings. I'll check and adjust values ...
-
On 28. 5. 2017 at 8:52 PM, zador.blood.stained said:
Prepare a list of boards that should be phased out and reasons for that (no HW samples, no vendor (BSP) development, no mainline development, no documentation, HW design flaws)
My proposal for removal:
https://www.armbian.com/orange-pi-mini/ (limited edition, no samples, never sold)https://www.armbian.com/orange-pi/ (limited edition, no samples, never sold)
https://www.armbian.com/lemaker-guitar/ (no development for some time, design flaws, no mainline)
https://www.armbian.com/roseapple-pi/ (no development for some time, design flaws, no mainline, never sold)
-
4 hours ago, Richard Fortuna said:
Word to the wise: Firefox maxes out the RAM and WILL freeze your Pi. Midori runs GREAT though!
Firefox arm64 is known to crash, so we used to add arm32 version which works, but the fastest is supplied Chromium. Midori is also good choice since its light.

AP limited to 5 clients on Cubietruck ?
in Allwinner sunxi
Posted
Yes, limited within firmware. Can't do it.