• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

RussianNeuroMancer's Achievements

  1. Unfortunately, this image does not load on my T4, get stuck here.
  2. I had this idea but unplugging everything besides power doesn't help a bit.
  3. Yes. My idea with uboot and /boot on microSD, and rootfs on eMMC works out on all three boards, by the way (which probably means that there is no hardware issues regarding eMMC).
  4. Xorg does not start on both of buster and focal xfce images. I didn't investigated this further because it was easier to install vanilla-gnome-desktop and vanilla-gnome-default-settings on focal image. Ethernet cable detection issue (that is discussed here) is still reproducible with uboot 2021.04, as it was with uboot 2020.10 (same workaround still applies). Another problem I noticed is not working HDMI Audio (unless I missing something). Yes, I tried to tinker around alsamixer and codec's i2s/pcm/spdif options, as well as boost levels, but this doesn't change anything. Is anyone got HDMI audio working on this board with Armbian images? Tried this workaround but it does not help. Any other ideas?
  5. Hello! I have three Libre Computer Tritium H5 boards and three eMMC modules on hands. All three eMMC modules is flashed with exactly same Armbian image and exactly same uboot. I also use exactly same PSU and cable for all three boards (however I reproduced this issue with four PSU and three microUSB cables, no difference in behavior was found). All three boards start just fine from microSD (so it's not exactly "Your board doesn't work?" case). One board never boot from eMMC on first power up, but almost always boot on second power up. That reproducible with all three eMMC modules. Two other boards just never boot from any eMMC module. When board can not boot from eMMC it just stuck there: U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 That five power up attempt as you can see. I tried to rollback uboot to 2020.04, but it behave in exactly same way.` All three boards was ordered at the same time, in one package. Is anyone can reproduce this? Is there anything else to try, or I should just give up and stick with microSD for now? (Although I probably could left uboot and /boot on microSD and then put rootfs on eMMC, but that another story.)
  6. I not sure about this. On NanoPC-T4 (which also equipped with rt5651) there is same issue, which same errors messages in dmesg. So maybe something else (besides rk3399-add-sclk-i2sout-src-clock.patch) is missing in Armbian? Actually, can you check if 3.5mm jack output works for you on RK3399 boards with rt5651?
  7. Also, it's just me, or it's looks like analog audio is broken out of the box on Linux 5.x images? Tried old image (from Linux 5.4 days) with manually installed Gnome and today stable image with preinstalled XFCE - in both cases there is no audio via integrated audio adapter (HDMI Audio works fine). Logs:
  8. Is anyone tested DisplayPort via USB Type-C on fresh Armbian images?
  9. Tested Armbian with Linux 5.10.32 (just downloaded fresh focal gnome image from device page and then boot it from microSD; emmc is clear so uboot from microSD is in use) that should include this commit, as I understand (at least CONFIG_EXTCON_USBC_VIRTUAL_PD is y in /boot/config-5.10.32-rockchip64). Unfortunately, Type-C video output does not work with adapter (Dell DA300) dock (Belkin F4U093) and even Type-C display (Lenovo L27m-28). I aways end up with [ 261.588312] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn [ 261.610196] typec_displayport port0-partner.0: No compatible pin configuration found:0000 -> 000c, 001c <- 0000 And yes, I tried to attach cable upside down with every tested device - error is still the same. (logs) @TonyMac32 any idea why it could fail for me? Hardware is fine - issue it not reproducible with legacy kernel. [ 174.603036] fusb302 4-0022: attention, dp_status 9a [ 174.603174] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn [ 174.893175] rockchip-vop ff8f0000.vop: [drm:vop_crtc_enable] Update mode to 2560x1600p0, type: 10 And then picture appear on the screen (attached via Type-C).
  10. Is anyone noticed that screen sometimes turns black for a second or two, at least on Gnome Shell Wayland session? With Dell UP3017 display (2560x1600) on Linux 5.10 I seen this issue frequently. After upgrade to 5.11 and changing screen resolution to 1920x1200 it's happens rarely, but still happens. Actually, I seen this issues even with ODROID C4 and N2+ (originally reported on Hardkernel forum). Logs:
  11. It's seems like rollback to uboot 2020.04 (specifically, I used this package) fixed it (found this idea here).
  12. Try to detach and then attach Ethernet cable, and see if it helps. In my case - it does.
  13. Getting similar issue with meson8b-dwmac on Libre Computer AML-S905X-CC. Cable definitely plugged in (orange and green leds light up), DHCP is totally fine, and even meson8b-dwmac report that link in up in dmesg. Yet systemd-networkd could not receive IP address from DHCP. Detaching and attaching cable back let me workaround this issue, but if I just reboot - it's almost always happening again. Tested both of currnet 5.10.21 and edge 5.11.11 kernels, reproducible in both cases, although with 5.11 success rate (of getting address from DHCP server) is noticeable higher, yet it's not 100% stable yet. Logs: When I attach exactly same cable to any other Rockchip or AllWinner boards - issue no longer reproducible. EDIT Another similar issue with meson8b-dwmac:
  14. I didn't have this issue yet (at least on 5.10.21) but just in case I configured two networkd-based bridges, one with slave with Name=enp* and another slave with Name=eth*