megi

Members
  • Content Count

    63
  • Joined

  • Last visited

2 Followers

About megi

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Micro USB connector current rating is ~2A continuous current. Contact resistance ~2x30mOhm. I don't use it, mostly because most USB cables are usually too thin and not designed for power delivery to SBCs. (your mobile phone will not care when VBUS voltage drops to 4.5V at the end of the cable during charging, but your SBC will) Anyway, even with custom made low resistance cabling, I was able to achieve SSD stability only when routing 5V directly to the drive. Maybe SSDs have high peak current consumption, I don't know. So yeah, similar experience here.
  2. Heatsink may not help much if the air is not moving. Place a 12cm fan next to the board and you should not have any throttling even on 1.8GHz and 100% load on all cores. (no need for a heatsink in this case) I have my fan undervolted so that it doesn't make noise. Not much airflow is needed to keep Opi3 from throttling. Otherwise you need a bigger heatsink with larger area.
  3. I don't have Opi3 variant with eMMC, so I don't carry and eMMC related patches for H6 boards.
  4. The reason for gphy not working is this: INFO: PMIC: aldo2 voltage: 3.300V ATF is enabling aldo2 which is half of the phy supply, whithout enabling the other half. When Linux enables the other half later on, it's too late and phy is in a broken state. The phy regulators have to be enabled at the same time. This bug was discussed on IRC, but it looks like nobody fixed this, and the broken code got pushed to ATF master, where the Armbian is pulling it from. The fix is to downgrade ATF. The issue is basically that ATF is enabling all AXP regulators that are referenced by anything in the DTS, which is non-sensical. Device drivers should be enabling regulators for the devices they manage in a proper order.
  5. I don't think waiting will help. I almost never update non-rc branches after release, I only merge from linux-stable. Anyway, I can only see you're missing 1.8GHz, because Armbian changes my CPU OPP table to something else, because my OPP table has 1.8GHz operating point. https://megous.com/git/linux/commit/?h=ths-5.4&id=8bad58044be498d409400dbf9757f2ae25c6ad9d
  6. Bluetooth on Opi3 is already supported out of the box on Linux 5.5-rc1. For 5.4: https://megous.com/git/linux/commit/?h=opi3-5.4&id=00f1b53048ebeaec115d705d78a954c2bff944fe https://megous.com/git/linux/commit/?h=opi3-5.4&id=1f4e6be59748a1695ecf7453a70e1c0f9d73ac14
  7. ttyS numbers are assigned semi-randomly, unless you name them specifically in the "alias" section in DTS. So that's the problem here.
  8. Linux 5.4 now uses a different cpufreq driver for H6. I guess it needs to be enabled in Armbian's Linux defconfig.
  9. WiFi powers down on `ip link set wlan0 down` So if you don't have it configured, it should be off.
  10. Did you measure the heatsink/package temperature? It should be a few (~5°C, depending on the difference between room/die temps) centigrades lower than the die temperature that's reported by the driver. For example for me, I see 43°C idle (all cores at 1.8GHz) reported by the driver, and 37-38°C measured by the IR thermometer. (no heatsink, but I use a fan) Without a fan it would be close to 50-55°C idle. Thermal drivers and OPP tables maz be different between those two releases.
  11. Crypto can already be accelerated if you pick ciphers that can be accelerated with aarch64 AES instructions, because H6 has these, and they are fast. openssl speed -evp aes-128-cbc -bytes 4096 aes-128-cbc 1324171.04k that's > 1.2GiB/s on single core Maybe ecb is better for benchmarking: openssl speed -evp aes-128-ecb -bytes 4096 aes-128-ecb 537105.75k
  12. Linux 5.4 contains the code changes, dts changes will be included in 5.5. So yes, and no.