Igor
-
Posts
13665 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
I just checked my setup - legacy kernel 3.10.105 and I have Skype operational, even BT headphones works. Kernel 4.x is under development ...
Up and downgrade should go with help of this: -
What about legacy kernel? Does it work there?
-
Quote
BRANCH=default
Switch to modern BRANCH=next and Bluetooth will be much better / stable. -
We only expose two images to cut down confusion, everything else you can find under: "Other images"
https://www.armbian.com/banana-pi-pro/
We will make this button larger ASAP since you are not the only one with this problem.
-
This fail is for bluetooth which while wifi must work. It used to when I try last time.
Wrote on mobile -
Well, I don't have hardware to test - if you want to get to the bottom of this:
1. Install build environment2. Remove this patch https://github.com/armbian/build/blob/master/patch/kernel/sun7i-default/0018-patch-3.4.112-113.patch and try again
3. If 2. doesn't help, go back with the kernel config.
4. Skip 1-3 and try modern kernel.
-
Than perhaps by using board configuration from older build, /boot/script.bin ...
-
One simple experiment - unplug monitor and use powered USB hub.
-
Since you said it was working before, this can't be the case. It's enabled: https://github.com/armbian/build/blob/master/config/kernel/linux-sun7i-default.config#L3009 and we haven't change this legacy kernel much. Here you can find all configs:
https://github.com/armbian/build/tree/master/config/kernel
ACM is enabled in modern kernel too (NEXT or DEV), so give it a try.
BTW. We can say Micro USB powering is a general design failure and even you use dedicated port, board might not get enough /stable power. It's something what board makers fool us and themselves. Putting into another words - most cables and mobile phone PSUs will fail to provide good enough power. If you have a SSD and a monitor attached and you are able to boot the board, you can consider yourself lucky. With USB devices you are getting to the area of extreme luck.
QuoteSo the problem is not hardware, but software
Could be, but where? -
3 minutes ago, chocorem said:
no change at all, board is powerd by micro USB port, running with attached monitor
Strange and un-explainable issues are in most cases related to power problems and powering via micro USB is a call for troubles. Your system might already be on the edge and altered u-boot with different power settings could ruin this edge power balance. Change PSU, cables, solder a LiPo battery ... than get back to the problem if it won't help. -
Nothing unusual. How do you power the board? Are you running this headless or with attached monitor?
-
From where / which version did you upgrade? Did you made any changes to default configuration? Without logs, we can't do anything. Type:
armbianmonitor -ufor a start.
-
-
2 hours ago, zador.blood.stained said:
What about putting "Known issues" block above the download buttions?
OK, let's try that ... I also plan to add a red box when clicking on nightly downloads ...
2 hours ago, zador.blood.stained said:And displaying "Desktop" video only if there are desktop builds for this board, can it be easily automated?
This is if there are desktop option possible- related to BUILD_DESKTOP variable and unrelated from recommended section.Now rebuild is also fast and will run in cron when finished.
-
1 minute ago, Tido said:
Some people might not be familiar with Torrent-Clients. How about recommending "Transmission" ?
Well, yes, probably .... but those should just proceed with a big buttonAdding few lines and/or pics to documentation and pointing there?
"Experimental" is now fixed. -
3 minutes ago, zador.blood.stained said:
So what are the "support status" bar ranges and names? For example H5 mainline builds should be marked as "experimental" rather than "testing"
This part is solved only technically. I am still not sure how to shape and name those values to provide valuable meaning.$PADCOLOR="w3-red"; $PADTEXT="Development"; if ($SUPPORT >= 50 && $SUPPORT<90){$PADCOLOR="w3-orange";$PADTEXT="Testing";} if ($SUPPORT >= 90){$PADCOLOR="w3-green";$PADTEXT="Stable";}We can also include if=nightly condition to set the text and colour.
-
-
5 hours ago, Cidirom Regrabable said:
I put on the folder sun8i-default but the process fail.
That's the source of our patch too and ours is already (almost) aligned with kernel source. Perhaps starting from a clean patch is a right way, but you need some expertise for doing this since patch will need adjustments and can't be just put in. Dig in or find a person who can. -
1 minute ago, boudicca said:
Is it worth trying the C2 image....?
I could not boot that image. -
Quote
I choose the option 5 (full real time) but crashes.
Yes, it's known that it crashes at some option. I don't recall which one is correct but I believe you can find it on forum ... or just do experiment.
This problem is unrelated to your host infrastructure. -
Hard to say where exactly is the problem without some logs ... and yes, it's possible that this particular WiFi chip doesn't work out of the box. Kernel could be without a a proper driver or perhaps only firmware is missing?
If you have driver sources: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver
-
Just download latest image or build from latest sources. When building, just make sure which RT option do you choose - one is breaking and you hit that one.
-
There is only one: interfaces, others are examples.
-
1 minute ago, LRiedel said:
As I said, the AP configuration from armbian-config didn't work, I can see the network, the password is accepted too, but it just keeps connecting forever.
This means your network configuration is wrong. You must either make a bridge or setup a DHCP server .... our armbian-config tool should do this, but it's WIP / buggy / unreleased and can't be blame for troubles
Check and properly setup /etc/network/interfaces
How to build my own image or kernel?
in Advanced users - Development
Posted
Please provide exact steps which you made + attach a (build)log of errors. Than we will be able to help you.
In the mean time check documentation regarding building. This: https://docs.armbian.com/Developer-Guide_Build-Preparation/ is all what we have right now and we need to add and change some stuff when possible.