hojnikb Posted November 11, 2016 Posted November 11, 2016 Nice to hear things are progressing on the H2+ front. Hopefully H5 and PC2 get the same love as well Question: Is armbian gonna switch to 64 bit images for H5 boards ? Would that even make sense on a 1GB board ?
zador.blood.stained Posted November 11, 2016 Posted November 11, 2016 Question: Is armbian gonna switch to 64 bit images for H5 boards ? Would that even make sense on a 1GB board ? We already have 64bit images for Pine64 and for Odroid C2. Images for H5 boards should be 64-bit too unless lack of documentation doesn't allow to properly run 64-bit kernel yet.
tkaiser Posted November 11, 2016 Posted November 11, 2016 Probably we should need to power WiFi in u-boot ... This might be related. So maybe just wait how she solves it and then 'port' the fix back to BSP driver the next days? I also wonder whether this xradio thingie needs special module load options to work in AP mode? And does anyone already have a clue whether monitor mode should also work?
msev Posted November 11, 2016 Posted November 11, 2016 Has anyone tested if Wiring-OPI works with this board? Thanks! 1
tkaiser Posted November 11, 2016 Posted November 11, 2016 Wireless driver works now out of the box. I let an image build an hour ago and there firmware wasn't included which prevented loading of driver and also new firstrun workaround. Since someone asked for 'iw list' output: root@orangepizero:~# iw list Wiphy phy1 Band 1: Capabilities: 0x110 HT20 Static SM Power Save RX Greenfield RX STBC 1-stream Max AMSDU length: 3839 bytes No DSSS/CCK HT40 Maximum RX AMPDU length 32767 bytes (exponent: 0x002) Minimum RX AMPDU time spacing: No restriction (0x00) HT TX/RX MCS rate indexes supported: 0-7 Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) (no IR) * 2472 MHz [13] (20.0 dBm) * 2484 MHz [14] (20.0 dBm) (no IR) Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps max # scan SSIDs: 2 max scan IEs length: 2257 bytes Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * AP/VLAN * monitor * mesh point * P2P-client * P2P-GO software interface modes (can always be added): * AP/VLAN * monitor valid interface combinations: * #{ managed } <= 2, #{ AP } <= 1, total <= 3, #channels <= 1 * #{ managed } <= 3, total <= 3, #channels <= 1 * #{ managed } <= 2, #{ P2P-client, P2P-GO } <= 1, total <= 3, #channels <= 1 Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * new_mpath * set_mesh_config * set_bss * authenticate * associate * deauthenticate * disassociate * join_ibss * join_mesh * remain_on_channel * set_tx_bitrate_mask * frame * frame_wait_cancel * set_wiphy_netns * set_channel * set_wds_peer * probe_client * set_noack_map * register_beacons * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 WoWLAN support: * wake up on anything (device continues operating normally) * wake up on disconnect Device supports AP-side u-APSD. HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing Device supports TX status socket option. Device supports HT-IBSS. Has anyone tested if Wiring-OPI works with this board? Thanks! Why should anyone test? WiringOP for H3 will work but requires pin adjustments. Simply compare pins on the header here with the 40 pin Oranges.
Fan KunPeng Posted November 12, 2016 Posted November 12, 2016 cool! where can I download the 4.9 kernel image? In http://image.armbian.com/betaimages/, there is only kernel 3.4 version.
tkaiser Posted November 12, 2016 Posted November 12, 2016 cool! where can I download the 4.9 kernel image? In http://image.armbian.com/betaimages/, there is only kernel 3.4 version. Beta images is for us getting valuable feedback from users. We're currently only interested in legacy builds, vanilla will follow (there not even Wi-Fi is working now). In case you want to use 4.9 in a reasonable way you would have to use our build system. But I switched the kernel repo for my tests (see here for details) and also my image is made not with ext4 but a fixed size btrfs rootfs (4 GB in size). So any feedback on this is useless. But in case you want to give it a try: https://transfer.sh/dck4H/armbian-5.24-orangepizero-ubuntu-xenial-4.9.0.7z Known problem: cpufreq scaling is working, throttling not. Using a heatsink is mandatory! 1
msev Posted November 12, 2016 Posted November 12, 2016 So are you saying it should be plug and play and work out of the box, no messing with the code, I should just know which pin I should connect to? Why should anyone test? WiringOP for H3 will work but requires pin adjustments. Simply compare pins on the header here with the 40 pin Oranges.
tkaiser Posted November 12, 2016 Posted November 12, 2016 So are you saying it should be plug and play and work out of the box Quite the opposite, I think you would have to tweak code to be able to use WiringOP with this board. Please have a look through https://github.com/BPI-SINOVOIP/BPI-WiringPi/commit/149207ce9dd8eccc17fb38951f03246f1390c90c (the adoptions BPi folks made to WiringPi after they discovered that their 40 pin header has different mappings) http://tech.scargill.net/size-matters-neo-air/#comment-26973 (me trying to explain stuff I never used) $Someone with all the H3 boards on his desk could maybe provide an universal WiringOP lib?
martinayotte Posted November 13, 2016 Posted November 13, 2016 It seems that Icenowy is working to port the XRadio WiFi driver into mainline. Not ready yet, but should be there soon. https://github.com/Icenowy/xradio
tkaiser Posted November 13, 2016 Posted November 13, 2016 It seems that Icenowy is working to port the XRadio WiFi driver into mainline. True, but currently she struggles a bit: https://irclog.whitequark.org/linux-sunxi/2016-11-13#18161915; So in case anyone can provide help... (me not being able to help any more with WiFi since it seems I damaged my Zero somehow yesterday when trying to test out several antennas with XR819, doing mean overheating tests or glueing a heatsink on H2+)
ErwinH Posted November 14, 2016 Posted November 14, 2016 I ordered the OPi Zero as well and will do my best to help out the community wherever I can once I receive the board. I have an USB-TTL adapter ready so debugging will also be an option. My goal is to have a small, low power, server able to give me access to remote networks over SSH. Low power will be key. I also ordered a OPi PC 2, which I will use for development/testing/etc.
dgp Posted November 15, 2016 Posted November 15, 2016 I have a mainline kernel and device tree that is running debian pretty well except for some random crashing (memory corruption?) if anyone is interested.
willcooke Posted November 15, 2016 Posted November 15, 2016 Hi, My Orange Pi Zero arrived this morning and I was very happy to find an Armbian image ready to play with, so thank you! I wanted to try and install some Ubuntu snaps but there are some AppArmor kernel patches needed, the message is: Kernel needs AppArmor 2.4 compatibility patch. I haven't done any digging to find exactly what these patches are, but if I find them is there any chance of them making their way in to the Armbian kernel? Cheers, Will
Igor Posted November 15, 2016 Posted November 15, 2016 @willcooke Apparmor is not on our 2do list but if you do the work, we will add patch. I made some Google search and found one success on Odroid c1, kernel 3.10 ... Wrote on mobile phone 1
zador.blood.stained Posted November 15, 2016 Posted November 15, 2016 I added some kind of AppArmor patches and enabled it in kernel config. Testing now to confirm that it doesn't break the compilation. After that (if all is OK) it needs to be tested on newer beta images since patches are for newer AppArmor version and I have no idea if they are backwards compatible.
willcooke Posted November 15, 2016 Posted November 15, 2016 I added some kind of AppArmor patches and enabled it in kernel config. Testing now to confirm that it doesn't break the compilation. After that (if all is OK) it needs to be tested on newer beta images since patches are for newer AppArmor version and I have no idea if they are backwards compatible. Wow! Thanks! More than happy to test. 1
frosticecold Posted November 15, 2016 Posted November 15, 2016 Offtopic: How much days until the package arrived? I'm expecting atleast 15-20 for me.
rajprakash Posted November 16, 2016 Posted November 16, 2016 Offtopic: How much days until the package arrived? I'm expecting atleast 15-20 for me. Feels like a crap shoot. I ordered a 512MB OPi Zero and OPI PC+case+powersupply on the 4th of November, it arrived in the US on the 13th, and still in transit to my location. I ordered a 256MB OPi Zero on the 2nd of November, and tracking information says it has not yet left China as of the 12th.
haiqu Posted November 16, 2016 Posted November 16, 2016 Please let's keep this thread focused on OPi Zero. There's absolutely no need to build an OS image yourself, simply use the one we provide now! https://www.armbian.com/orange-pi-zero/ This helps both you and us since we can focus on real problems. So you're saying that reporting build problems with the toolchain for the OPi Zero is off-topic for the subject of OPi Zero? Thptptptpt. Wow, I guess I had better find some "real problems" then, whatever they might be.
Igor Posted November 16, 2016 Posted November 16, 2016 So you're saying that reporting build problems with the toolchain for the OPi Zero is off-topic for the subject of OPi Zero? @haiqu Yes, this should go into development section. In most cases build problems are not related to a single board and are on different level than using the board. https://forum.armbian.com/index.php/forum/4-development/ No offence. We only try to keep forum readable.
willcooke Posted November 16, 2016 Posted November 16, 2016 Offtopic: How much days until the package arrived? I'm expecting atleast 15-20 for me. I ordered mine from Ali Express on the 5th November (a Saturday) and it arrived yesterday - so 10 days total. It was shipped from a UK fulfilment centre by registered post, 48hour. This was *much* quicker than I was expecting.
frosticecold Posted November 16, 2016 Posted November 16, 2016 Thanks for the feedback, it's been 8days and still hasn't left china.
tkaiser Posted November 21, 2016 Posted November 21, 2016 Out of tree Wi-Fi driver that works with mainline kernel: https://github.com/fifteenhex/xradio (DT bits here)
frosticecold Posted November 21, 2016 Posted November 21, 2016 Wonderful news, we should have a mainline image with the driver ready to download anytime soon
tkaiser Posted November 21, 2016 Posted November 21, 2016 Wonderful news, we should have a mainline image with the driver ready to download anytime soon There's no need to hurry, better fix stuff first in a reasonable way (eg. use a permanent MAC address or implement throttling which currently doesn't work with most recent mainline kernel branches)
martinayotte Posted November 21, 2016 Posted November 21, 2016 Hoping that fifteenhex will send a PR to Icenowy for his work.
tkaiser Posted November 21, 2016 Posted November 21, 2016 Hoping that fifteenhex will send a PR to Icenowy for his work. It seems it was just config: https://irclog.whitequark.org/linux-sunxi/2016-11-21#18231020 Now all that's needed is MAC address also based on SID (and a clear license for the firmware ) and we can remove this ugly hack.
martinayotte Posted November 21, 2016 Posted November 21, 2016 No, he did a lot more work that Icenowy has not done yet. Many empty stubs were still there in her branch. https://github.com/Icenowy/xradio/compare/master...fifteenhex:master For the MAC, he merged a commit from her : https://github.com/fifteenhex/xradio/commit/911c488ebab45d075215ae4967044134df358ad7
tkaiser Posted November 21, 2016 Posted November 21, 2016 No, he did a lot more work that Icenowy has not done yet. Yes, you're right. In the meantime the MAC address change has been reverted and now the driver sets an absolutely random address. I would prefer that it's implemented just like with 8189FTV now. Use the SID based information from u-boot and generate MAC addresses for both Ethernet and Wi-Fi based on that: root@orangepipcplus:~# ifconfig | grep HWaddr eth0 Link encap:Ethernet HWaddr d6:06:6c:2f:a1:85 wlan0 Link encap:Ethernet HWaddr d6:06:6c:2f:a1:84 Both addresses valid locally administered ones and Wi-Fi is like Ethernet - 1.
Recommended Posts