asp

Hello. I updated my system to 5.25 version, and ralink usb wifi stopped working. As i can see, there is no drivers (mt7601Usta), but drivers exists at system. I tried to download drivers and complied it, but it didn't help me. Does anybody use wifi ralink dongles on orange pi zero 5.25 (3.4.113 debian) ?

Didn't help apt-cache search linux-u-boot-orangepizero-dev linux-u-boot-orangepizero-dev - Uboot loader 2017.01 apt-cache search linux-$(lsb_release -cs)-root-dev-orangepizero linux-jessie-root-dev-orangepizero - Armbian tweaks for jessie on orangepizero (dev branch) apt-get update apt-get install linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero Reading package lists... Done Building dependency tree Reading state information... Done linux-jessie-root-dev-orangepizero is already the newest version. linux-u-boot-orangepizero-dev is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Thank you Igor for adding packages to repository, I already updated my debian jessie from 3.4.114 (5.24) to dev branch 4.9.4 (5.25). Before I tested 4.9.4 kernel on ubuntu, but debian is more friendly for me. BOARD=orangepizero BOARD_NAME="Orange Pi Zero" VERSION=5.25 LINUXFAMILY=sun8i BRANCH=dev ARCH=arm IMAGE_TYPE=stable But I note that I can use only 1 core and maximum frequency is 1.01 GHz.. why so? cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 100.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : Allwinner sun8i Family Revision : 0000 Serial : 02c00042d2041574 root@orangepizero:~# cpufreq-info cpufrequtils 008: cpufreq-info © Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4.24 ms. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 480 MHz, 624 MHz, 816 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 240 MHz and 1.01 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 1.01 GHz (asserted by call to hardware). cpufreq stats: 120 MHz:0.00%, 240 MHz:6.52%, 312 MHz:1.39%, 480 MHz:0.78%, 624 MHz:0.47%, 816 MHz:0.28%, 1.01 GHz:90.56% (368) root@orangepizero:~#

Ok, thank you. I'd like to ask you here about this kernels and wifi, although I created another topic about wifi on orange pi zero before. As I wrote on this topic ( https://forum.armbian.com/index.php/topic/3355-orange-pi-zero-wifi-apmanaged/) wifi as AP+Client (two virtual interfaces) works good on kernel 4.9.4.. Why so? Is it possible to configure wifi in such way on 3.4.113 ?

Hello. Yesterday i tried to switch kernel in debian jessie 5.24 from 3.4.113 to 4.x using this article: To make sure you won’t run into conflicts within newly installed packages, remove them all before upgrade: 1 2 aptitude remove ~nlinux-dtb ~nlinux-u-boot ~nlinux-image ~nlinux-headers aptitude remove ~nlinux-firmware ~narmbian-firmware ~nlinux-$(lsb_release -cs)-root Proceed with install: 1 2 3 4 apt-get install linux-image-dev-sun8i linux-dtb-dev-sun8i linux-headers-dev-sun8i apt-get install linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero apt-get install armbian-firmware sunxi-tools swconfig a10disp reboot https://www.armbian.com/orange-pi-zero/ But there is no linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero packages in default repository. I used apt-cache search to find this packages, so I found this dev. packages for other Orange pi models, but not dev. packages for orange pi zero. How to switch kernel on Orange pi zero?

As I understand, you need to configure wifi interface as access point.

What steps you did to switch kernel on debian? 2. Do you know how not to lose second virtual interface (wifi) after restart? I tried to create rules in udev, but it didn't help me (may be i wrote wrong rule)

I already done it using nmtui utility, but it works only on Mainline 4.9.3 Ubuntu Xenial (nightly releases). Hostapd didn't tried. So I conclude that something wrong with drivers in legacy 3.4.113

I would also like to know how you did it. https://forum.armbian.com/index.php/topic/3355-orange-pi-zero-wifi-apmanaged/

It will be great if you try to done this too. Yes, network manager and spa_supplication are on. I note, that if I want to start wifi as AP (hostapd) mode or client mode (wpa_cli utility) on wlan0 - it works. "arp flux" - may be, but it's not a problem, because i can see connection to home_wifi, wifi link is up. The same operations on second wifi interface didn't work (don't matter, ap or client mode). This is some information: Orange PI zero , armbian 5.24 (latest) wpa_cli: Selected interface 'wlan1' Interactive mode <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH > add_network 0 > set_network 0 ssid "Rocks" OK <3>CTRL-EVENT-SCAN-STARTED 1 <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH > set_network 0 psk "********" OK > enable_network 0 OK <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>SME: Trying to authenticate with e4:8d:8c:e0:de:db (SSID='Rocks' freq=2412 MHz) <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>SME: Trying to authenticate with e4:8d:8c:e0:de:db (SSID='Rocks' freq=2412 MHz) <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>SME: Trying to authenticate with e4:8d:8c:e0:de:db (SSID='Rocks' freq=2412 MHz) <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>SME: Trying to authenticate with e4:8d:8c:e0:de:db (SSID='Rocks' freq=2412 MHz) <3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Rocks" auth_failures=1 duration=10 reason=CONN_FAILED <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>CTRL-EVENT-SCAN-STARTED <3>Reject scan trigger since one is already pending <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>CTRL-EVENT-SSID-REENABLED id=0 ssid="Rocks" <3>SME: Trying to authenticate with e4:8d:8c:e0:de:db (SSID='Rocks' freq=2412 MHz) <3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Rocks" auth_failures=2 duration=23 reason=CONN_FAILED <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE-AUTH <3>CTRL-EVENT-SSID-REENABLED id=0 ssid="Rocks" <3>SME: Trying to authenticate with e4:8d:8c:e0:de:db (SSID='Rocks' freq=2412 MHz) <3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Rocks" auth_failures=3 duration=46 reason=CONN_FAILED iwconfig: wlan1 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on wlan0 IEEE 802.11bgn Mode:Master Frequency:2.412 GHz Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:on 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) (no IR) * 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. Commands: iw dev wlan0 del 74 iw phy phy1 interface add wlan0 type __ap 110 iw phy phy1 interface add wlan1 type managed systemctl status hostapd.service Б≈■hostapd.service - LSB: Advanced IEEE 802.11 management daemon Loaded: loaded (/etc/init.d/hostapd) Active: active (running) since Mon 2016-11-14 09:52:12 CET; 5min ago Process: 845 ExecStop=/etc/init.d/hostapd stop (code=exited, status=0/SUCCESS) Process: 852 ExecStart=/etc/init.d/hostapd start (code=exited, status=0/SUCCESS) CGroup: /system.slice/hostapd.service Б■■Б■─855 /usr/sbin/hostapd -B -P /run/hostapd.pid /etc/hostapd.conf Nov 14 09:52:12 orangepizero hostapd[852]: Starting advanced IEEE 802.11 management: hostapd. Nov 14 09:52:12 orangepizero systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon. systemctl status wpa_supplicant.service Б≈■wpa_supplicant.service - WPA supplicant Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled) Active: active (running) since Mon 2016-11-14 09:50:58 CET; 7min ago Main PID: 681 (wpa_supplicant) CGroup: /system.slice/wpa_supplicant.service Б■■Б■─681 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

At first i deleted wifi interface using utility iw. Then I create two interfaces: iw phy phy1 interface add wlan0 type __ap iw phy phy1 interface add wlan1 type managed First interface for hostapd - working good. Second interface for connection my Opi Zero to internet. Question is why my second interface didn't want to connect to internet(gome wifi AP), i got always wrong key. home wifi AP working using WPA2. I want to ask, may be someone done the same already.

Thank you for your response. I want to use OPi zero for mqtt+openhab2+wifi_ap_mode for esp8266+same_wifi as client to connect to the internet. If i want to connect to AP which uses WPA2, how i need to configure my connection? What I need use instead wpa_supplicant ? 2. After reboot, OPi zero missing second virtual wifi interface, how to save it?

Hello! I tried to configure built-in wifi module to work as two wifi interfaces at the same time. I had already configured hostapd+dhcpd at the first interface, at the second interface (...iw add interface...) I could scan my home wifi network (wpa2), but I couldn't connect to it (wrong key). I used utilities to connect like wpa_cli, wpa_supplicant, iwconfig, iw. Did anybody done that, I mean is it possible? What i'm doing wrong?