RussianNeuroMancer

Members
  • Content Count

    36
  • Joined

  • Last visited

About RussianNeuroMancer

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. This issue is fixed since version 1.10.1+dfsg-4 and Ubuntu 20.10 already ship newer package (1.10.1+dfsg-7). You can use TigerVNC 1.10.1+dfsg-7 on Ubuntu 20.04 as well, but this will require manual downloading of tigervnc packages here: https://launchpad.net/ubuntu/+source/tigervnc Relevant bugreports: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932499 https://github.com/TigerVNC/tigervnc/issues/1023
  2. No, unfortunately I never needed it on this device, so I didn't saved it.
  3. Please try DisplayPort kernel for NanoPC-T4 published here. DisplayPort function does not work, but there is good chances that at least Ethernet adapters or flash-drives could work. Patches used for building this kernel is published here, so please redirect your feedback regarding this kernel to Oleksii thread.
  4. You can find it here. Like you, I also have to keep 5.4.49 on one of my NanoPC-T4, because newer kernels does not detect Samsung 970 EVO (although I didn't tested 5.8.1 yet). I also keep 5.4.43 on ROCKPro64 because USB Audio was broken somewhere between 5.4.43 and 5.4.49 (USB Speaker is detected, audio playback, but speaker stay silent; rollback to 5.4.43 - and it works again) so I froze it until I find time to test newer kernels (newer kernels on ROCKPro64 looks problematic).
  5. On resolutions above FullHD - yes. Seen on NanoPi-M1 and NanoPi K1 Plus. Issue is there even without installed DE, as far I remember.
  6. This stuff is implemented only in legacy kernel. Oleksii tried to implement DP support at least for NanoPC-T4, but didn't succeed so far (I tested this code on NanoPC-T4 with Dell DA300, Belkin F4U093, Dell WD15 docks, with several different cables).
  7. Smartbuy Stream E13T Pro (P/N: SBSSD-128GT-PH13P-M2P4, identified as "Smartbuy PS5013-2280T") works on Linux 5.7.6.
  8. I briefly tested 5.7.6 kernel and found that Samsung 970 EVO still doesn't work with same PCIe link training gen1 timeout error. Rollback to 5.4.49, and it works again.
  9. A bit of offtopic, but if anyone is interested Hardkernel is more open about RMA.
  10. Try to contact sales from different e-mail, say you would like to place new order, ask them if something (for example if NEO2 Black is available for order directly from their store, or if K1 Plus fits into RPi3 cases, etc.; but don't copy this blindly, come up with your own questions) when sales answer, continue asking them about other items for your new order. Then say that before placing your new order you need to resolve issue with board from previous order (mention order number here) describe how board died, attach video of attempt to power on the board, describe troubleshooting steps
  11. One of my NanoPC T4 also died a four months ago for no apparent reason, some symptoms was similar to description from Oleksii post. Initially it always printed long stack trace to serial console during rockchip_drm initialization, and then reboot on emmc initialization attempt. Later it stopped booting from emmc as if it's empty, but attempts to boot from microsd always lead to same outcome - boot loop. And finally it stopped even trying to boot from microsd with only red light. FriendlyARM send replacement for this board, but making them doing so certainly wasn't easy - when all t
  12. Hello! I found that on NanoPi K1 Plus there is issues with both of integrated audio adapter (H3 Audio Codec) and HDMI Audio (allwinner-hdmi 1c22800.i2s-i2s-hifi) 1. With H3 Audio Codec I getting only silence, altrought there is short click on starting and end of playback. "Stereo" mode was chosen in pavucontrol for this audio adapter. 2. With allwinner-hdmi audio playback is working, but left and right channels is swapped. Like above "Stereo" mode was chosen in pavucontrol for this audio adapter. Tests was performed from Mate desktop installed on top of Armbian 20.05
  13. To achieve what specifically? As you can see in this post launching chrony manually works, what doesn't work is automatic start via systemd service.
  14. Two lines appear in journalctl -xe after every attempt to start chrony.service: May 14 03:15:58 nanopim1 chronyd[1334]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG) May 14 03:15:58 nanopim1 chronyd[1334]: Frequency 25.014 +/- 0.137 ppm read from /var/lib/chrony/chrony.drift Nothing else besides that and service log chrony.service log I posted yesterday. btw, I noticed that Ubuntu Server 19.10 and 20.04 (I tested generic aarch64 build of Ubuntu Server) ship systemd-timesynd by default, and it sync with n
  15. I checked this issue once again today - it start on boot on bionic image, but no longer works after upgrade to focal. Focal image doesn't even boot (no uboot on HDMI, solid green led; I didn't checked serial). Log: May 13 03:04:42 nanopim1 systemd[1]: Starting chrony, an NTP client/server... May 13 03:04:42 nanopim1 chronyd[8395]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG) May 13 03:04:42 nanopim1 chronyd[8395]: Frequency 20.659 +/- 0.346 ppm read from /var/lib/chrony/chrony.drift May 13 03:04:43 nanopim