Kalobok

  • Content Count

    14
  • Joined

  • Last visited

  1. Well, if it's possible, why not to include it? Especially that it's almost 30% increase in frequency. Since the board doesn't tend to overheat, there should be no thermal issues. Also (and it's quite subjective, I admit), I have an impression that the board is somewhat slow when it has to generate web content for rpimonitor. PS Tried usb with custom-built kernel - the same result (USB hubs are present but devices are not recognized).
  2. @ashthespy, thanks for the hint. USB hubs are now available: But USB devices are not recognized. Also, max frequency is limited to 1008000
  3. Well, I'm not that familiar with kernel and device tree patching. Could you provide some explanations on how I can test it?
  4. There were several 5.8.16 lines, I've selected the topmost (assuming it's the latest), and the LEDs are back! Thanks a lot!
  5. After recent upgrade of Debian Buster stable on Orange Pi Zero Plus 2 leds entries disappeared from class directory: Could anybody provide some guidance on how to get them back?
  6. Just checked Armbian_21.02.0-trunk.4_Rockpi-s_buster_current_5.9.11_minimal image. Wifi works, USB doesn't (lsusb gives no output). Also, available frequencies are limited to 1008000, while with the legacy kernel max freq is 1296000. Here's the report: +BOOT=yes +VERSION=21.02.0-trunk.4 +KERNEL=5.9.11-rockchip64 +NETWORK=NT +WIRELESS=yes +HDMI=NA +USB=no +DVFS=NT +ARMBIANMONITOR=http://ix.io/2G2R
  7. OK, tried on mainline kernel. /etc/default/crda: REGDOMAIN=NL iw reg get shows NL after reboot, but the board still doesn't see SSIDs on Control Channel 13.
  8. WiFi behaviour may depend on what kernel you are using. Does the board see any SSIDs at all (nmcli device wifi)? I faced a situation with mainline kernel when SSIDs with Control Channel set to 13 are not seen by the board.
  9. Checked with legacy kernel (5.35 user-built Ubuntu 16.04.3 LTS 3.4.113-sun8i). Country is also set to 00: DFS-UNSET, but iw reg set NL has no effect, country remains set to 00. The board, however, sees my AP on Control Channel 13 and successfully connects. So it's driver, not AP6212 chip. After upgrading legacy to 5.36 reg set and reg get work. @guidol, for upgraded legacy kernel setting region in /etc/default/crda works. Will check with mainline kernel later.
  10. @tkaiser thanks for the hint. Initially country is set to 00, and is changed with iw reg set: anton@BPI-M2p:~$ sudo iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, NO-IR (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, NO-IR (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, NO-IR (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, NO-IR (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR (5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR (57240 - 63720
  11. Hi all! I'm new to Armbian so share my experience in this section. After several failures I managed to find an image that boots on my Banana Pi M2+ (Armbian_5.34.171121_Bananapim2plus_Debian_stretch_next_4.13.14_desktop). Everything worked nicely from the box, thanks all developers for a great job (but indeed, huge penguin looks a bit frightening on 55" TV). While setting up WiFi I found that the board doesn't "see" my AP (while all neighbours' were there). After playing with AP's settings i figured out that it's not visible if Control Channel is set to 13. W