Igor
-
Posts
13659 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
Do your have any web link about A20 fex file?
-
1. OK
2. Yes it works now, while cleaning the mess, as Thomas suggested, remain open.
3. Problems are only when something is on USB in all other cases I could not reproduce - when using a proper PSU. I suspect it has something to do with power stability. If some not so perfect source is used, board might not boot. There is nothing more to be done here.
4. I'll try to squeeze this into this release.
-
I made some tests with latest nightly Xenial with kernel 4.9
Firmware for the board is missing, since it's missing in our repository too (compiled without externals - my mistake - will be fixed in tomorrows build). After downloading it, things works as expected.
[ 4] 0.00-1.00 sec 1.98 MBytes 16.6 Mbits/sec 0 97.6 KBytes [ 4] 1.00-2.00 sec 2.02 MBytes 17.0 Mbits/sec 0 150 KBytes [ 4] 2.00-3.00 sec 2.04 MBytes 17.1 Mbits/sec 0 184 KBytes [ 4] 3.00-4.00 sec 2.21 MBytes 18.5 Mbits/sec 0 205 KBytes [ 4] 4.00-5.00 sec 2.27 MBytes 19.0 Mbits/sec 0 228 KBytes [ 4] 5.00-6.00 sec 2.03 MBytes 17.0 Mbits/sec 0 252 KBytes [ 4] 6.00-7.00 sec 2.04 MBytes 17.2 Mbits/sec 0 253 KBytes [ 4] 7.00-8.00 sec 2.15 MBytes 18.1 Mbits/sec 0 284 KBytes [ 4] 8.00-9.00 sec 1.97 MBytes 16.5 Mbits/sec 0 284 KBytes [ 4] 9.00-10.00 sec 2.25 MBytes 18.9 Mbits/sec 0 284 KBytes
Relevant log entries:
[ 11.567849] input: r_gpio_keys as /devices/platform/r_gpio_keys/input/input0 [ 11.698492] systemd-journald[288]: Received request to flush runtime journal from PID 1 [ 11.922987] xradio_wlan: unknown parameter 'macaddr' ignored [ 11.991440] thermal thermal_zone0: failed to read out thermal zone (-16) [ 12.311111] xradio_wlan mmc1:0001:1: missed interrupt [ 12.358444] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 12.946516] libphy: 1c30000.ethernet: probed [ 13.061659] Generic PHY 1c30000.ethernet:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1c30000.ethernet:01, irq=-1) [ 13.061699] sun8i-emac 1c30000.ethernet: device MAC address slot 0 02:20:48:b5:7f:05 [ 13.063208] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.660577] random: crng init done [ 16.063662] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.172021] sun8i-emac 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 16.172085] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.235921] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 16.237278] ieee80211 phy0: Interface ID:0 of type:2 added [ 16.238013] ieee80211 phy0: configuring tx for vif 0 [ 16.238480] ieee80211 phy0: configuring tx for vif 0 [ 16.238933] ieee80211 phy0: configuring tx for vif 0 [ 16.239370] ieee80211 phy0: configuring tx for vif 0 [ 16.239816] ieee80211 phy0: ignore IEEE80211_CONF_CHANGE_MONITOR (1)IEEE80211_CONF_CHANGE_IDLE (1) [ 16.240053] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 16.616302] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 120.078243] wlan0: authenticate with e8:de:27:fd:6d:25 [ 120.078347] ieee80211 phy0: ignore IEEE80211_CONF_CHANGE_MONITOR (0)IEEE80211_CONF_CHANGE_IDLE (1) [ 120.078364] ieee80211 phy0: Freq 2427 (wsm ch: 4). [ 120.078769] wlan0: send auth to e8:de:27:fd:6d:25 (try 1/3) [ 120.236605] wlan0: authenticated [ 120.240999] wlan0: associate with e8:de:27:fd:6d:25 (try 1/3) [ 120.244902] wlan0: RX AssocResp from e8:de:27:fd:6d:25 (capab=0x411 status=0 aid=1) [ 120.244995] ieee80211 phy0: configuring tx for vif 0 [ 120.245671] ieee80211 phy0: configuring tx for vif 0 [ 120.246359] ieee80211 phy0: configuring tx for vif 0 [ 120.246997] ieee80211 phy0: configuring tx for vif 0 [ 120.250970] wlan0: associated [ 120.251286] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 120.305960] ieee80211 phy0: vif 0: set_key cmd 0 [ 120.305985] ieee80211 phy0: CCMP_PAIRWISE keylen=16! [ 120.307309] ieee80211 phy0: vif 0: set_key cmd 0 [ 120.307329] ieee80211 phy0: CCMP_GROUP keylen=16! [ 251.211499] sun8i-emac 1c30000.ethernet eth0: Link is Down
I have to note that reconnecting to previously associated AP (after reboot as example) is slow so you need to wait some more time to get an IP. This is somehow strange ... Speed? It's a low cost chip ... from Allwinner.
One more thing to note: sometimes it doesn't see my AP even it's 1m away.
-
OK. Use stock Micro settings and exchange only video part (from Lime2 settings) and you should be fine ...
-
4k video accelerated playback is also a problem on Intel HD graphics which is overall the only HW that would fit into all of your needs almost fine: best linux support, good sata speed, more displays, enough power, more network cards, ...
Check also Jean-Luc tests of media players where you will see that virtually none of 4k media players is ready for smooth 4k video playing.
-
But after that, dhcp does not work. I use "ifconfig " to check eth interface. I can see the eth0 and it's MAC address,but no IP address.
I guess that DHCP is disable.
After setting new screen resolution or after changing .bin files? This is a temporally solution anyway. You need to adjust micro.bin (bin2fex, edit+save, fex2bin) here. Copy and past that section from file you are using now. New settings come into action at boot.
-
Omega v1 had Atheros chipset while current v2 uses MT7688 ... Atheros is at least OSS friendly while Mediatek is not and "wanna be" router class at best. C.H.I.P. has Realtek 8723DS ... which is also not router class hw. Same shit, just in different package. Remember that "routerboard" Banana R1 was also advertised to run Openwrt
Good things are extremely hard to find those days
-
Hmm... it seems xradio_wlan is missing in /etc/modules. Does it help if you manually do a 'sudo modprobe xradio_wlan' and then try again using 'sudo nmtui'?
Is this double loading already fixed? In case not, module must be loaded twice.
-
Hardware cryptographic accelerator support already exists: http://sunxi.montjoie.ovh It's something unrelated to "64bit"
A64, even it's poorly supported ATM is more or less only 64bit alternative under those conditions....so, no one can think of a native 64-bit under-$50 (USD) SBC as good as Odroid-C2?
-
I'm gladly suprised that armbian has this feature turned on,
Yep. It's so long here, since early days, that I forgot about
-
pratically the projects are very low prices ....this is because I'm choosing the orange pi
Anyway , it's a sin because the orange pi are very powerfull with ram , emmc and else
I will follow the tutorial where explains how to install the driver 8188eu .....
You can succeed with low cost devices to get a decent performance. But it's usually more painful, require hard work and / or deep knowledge - to debug and fix problems.
I honestly wish you good luck and remember to have fun
-
I guess you mean you have neutral or even a good feeling about Hardkernel ?
Yes, we could rephrase it this way.
-
Is there any way to change brightness settings on CAM500B? I can't get clear images fswebcam.
Using nanopi neo air with CAM500B and Ubuntu core.
:~# v4l2-ctl -l
error 25 getting ctrl White Balance, Automaticerror 25 getting ctrl Exposureerror 25 getting ctrl Horizontal Fliperror 25 getting ctrl Vertical Fliperror 25 getting ctrl Color EffectsThanksThere is different / patched driver within Armbian kernel. This problem might be the same or not ... We can't support 3rd party image builds.
-
Maybe I'll try to purge the full version and install the minimal one and see if it still works. Hopefully I won't break something on the way.
Full is what it said ... while normal armbian-firmware is handpicked. When you find a correct firmware, add / push it here and it will be in a small package for good:
https://github.com/igorpecovnik/lib/tree/master/bin/firmware-overlay
-
Have you checked all standard problems written in "How to start" in docs.armbian.com ?
-
I'm interested in 64 bit mode mostly because it seems to provide performance benefits.
If you rule out cryptographic instructions that comparison become more realistic. Is gain big enough to bother?
-
It looks like our configuration is broken. I don't have this particular board (closest is Lime2 and it works fine) - can you try this:
cp /boot/bin/lime2.bin /boot/bin/micro.bin reboot
If this works, than I must check why our board config is wrong.
-
Let's speculate that bad support for A64 is because it was introduced by a board maker(s), which does not understand this business. They know how to generate sales, but they completely fail to establish rapport with community, which is essential for such projects. Support is terrible and they expect that everything is done by community without any input except a bunch of free boards. On the other hand Hardkernel try ... harder
My first impression with Pine64 was - yet another cash collecting scheme, while for Hardkernel I can have neutral feelings at worst.- inexperienced vs experienced?
- raising popularity of Amlogic?
- right place at right time?
None of above?
-
This one could work: http://www.ebay.de/itm/AC1200-Dual-Band-WLAN-Adapter-WiFi-USB-3-0-WPS-802-11AC-Dongle-WINDOWS-10-DE-/222057434352 with this driver https://github.com/gnab/rtl8812au on mainline kernel.
But you need powered USB3 hub, otherwise it will not even start.If you want to use it as dual band AP, forget about. Not possible ... get a router or a router like board. Be aware that junk router boards also exists ...
-
Can I just use Igor's lib tool on the Orange Pi Lite?
Nope. It's a tool to run on a x86 desktop PC (cross compile).
-
Armbian supported boards with mPCI: Hummingboard and Clearfog in different variants. There are also Intel / AMD based but they are even more expensier. Recommended wifi card chipsets:
https://wireless.wiki.kernel.org/en/users/drivers/ath9k (fully OSS, up to 450 Mbps)
https://wireless.wiki.kernel.org/en/users/drivers/ath10k (firmware based, AC)
One more thing to mentioned. Not all mPCI cards support AP mode ... they are locked down by the firmware so you are forced to buy expensive "router class" cards. There is a hack for ath9k (already build into most Armbian kernels) since it's an OSS driver, while you have no choice with recent ath10k based cards ATM.
Linux wireless wiki is also a good start to know more about wifi.
https://wireless.wiki.kernel.org
For general stuff get this:
-
Is there a fast and simply possibility to set 1280x800 resolution in Armbian?
Nope. Calculation, kernel patching, recompilation, testing, recompilation, testing, ...
https://forum.armbian.com/index.php/topic/2991-opi-pc-2e-h3disp-1680x1050-dvi-display-issues/
-
I am just saying that you will face similar problems elsewhere because of Linux nature / architecture. Most wireless keys will work out of the box (or after driver install) only on your PC running Windows at best. (RPi running Windows is excluded)
What to do? Learn, explore and understand that things are not just granted to work. Someone must write a driver and someone must fix problems with that driver - support is essential ... Most chip makers does this job badly, half way. As I said, we try but already hardly manage to cope with on board WiFi chips ... which are mostly low cost.If you want some professional grade services, you'll need to switch for better hardware - check boards that fancy mPCI slot, where you can put a proper router class wireless card. (Only) Those wireless cards usually works how you expect.
-
v5.25
in Advanced users - Development
Posted
@vincele
Since you have a good eye in spotting such things - I just gave you commit rights for lib.docs ... quick fixing can be more convenient way. We are already filled with various tasks. Thanks.