• Content Count

  • 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. Yep, that did it - when HDMI support is disabled in uboot 2020.10 issue is not reproducible on Libre Computer ROC-RK3399-PC. Thank you for advice!
  2. Did you checked ssh? Could be something like this: I have similar issue, and ssh works for me, and even Xorg works.
  3. Hi, balbes150! Any idea what could cause the difference in HDMI output behavior I described in the post above. There is also a separate thread about this issue now.
  4. Forgot to mention: Issue is also reproducible on Armbian_20.11.7_Nanopct4_bionic_legacy_4.4.213_desktop.img, probably because modern uboot 2020.10 is there now in legacy images too. There is workaround for getting Xorg working (which does not help for Wayland, but at least this something).
  5. Hello! First, and foremost, how issue looks like: Initially I noticed this issue with Dell UP3017 (2560x1600) on Libre Computer ROC-RK3399-PC (post). However later I noticed this on fresh Armbian installations on NanoPC-T4 too (post). Later on I found that old Armbian installations on NanoPC-T4 is unaffected, probably because of older uboot (something from last Armbian 5.xx days) that already flashed on eMMC. Yesterday I compared a couple of old Armbian images (initially that was posted here) Armbian_20.05.7_Nanopct4_focal_current_5.4.49.img
  6. Oh, sure, I perfectly understand this, which is why I going to try to get Dell DA300 so we can proceed with this (I am just afraid it will get some time until I will get it on hands). I just explained why it would not help in my particular use-case, that all Right, I totally forgot I could try Armbian legacy builds too. Thanks for reminder! Armbian_20.11.7_Nanopct4_bionic_legacy_4.4.213_desktop.img: Can't setup desktop due to "Cannot execute /usr/bin/bash: No such file or directory" error. When only Type-C cable is attached - there is no picture on external disp
  7. Yes, sure. I guess all three 4.4 kernels (by Firefly, PINE64 and FriendlyARM) is based on Rockchip code? I could try to get Dell DA300 for testing (it probably will take a few weeks) but I would not be able to use it in practice for anything but just testing. In practice I'll still need Belkin F4U093, because there is not many docking stations out there that can charge anything PD-compatible. I tried several docks, from Dell WD15 to StarTech TB3CDK2DP, but after all I had to stick with Belkin F4U093, because Dell and Lenovo docks refuse to charge old HP laptops, StarTech refuse
  8. Flashed uboot, displayed version during changed from 2020.07-armbian to 2020.10 with zero timestamp, so I guess it's yours. Unfortunately, still same error: "typec_displayport port0-partner.0: No compatible pin configuration found:0000 -> 000c, 001c <- 0000". But it's seems like I shouldn't be using NanoPC-T4 for testing DP stuff at all. Turns out DP doesn't work for me on this board even with vendor's FriendlyDesktop image based on Rockchip 4.4 branch - getting "cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Not connected. Disabling cdn" error in dmesg. Perhaps there is some incompatibi
  9. Thanks for explanation! I tested this build and unfortunately DisplayPort still doesn't work (dmesg). HDMI issue I mentioned earlier is also there. Just in case, on vendor's 4.4 DisplayPort works work with same docking station (at least on ROCKPro64, but I could test it again on NanoPC-T4, if necessary).
  10. I guess you don't see rendering artifacts because your EDID is different from mine. Dell UP3017 resolution is 2560x1600 - so possibly drm driver trying to initialize output and fail to do so in my case, while for you it works. By the way I found a workaround HDMI issue I getting on vanilla Armbian (first paragraph). 1. Getting text console usable: boot board without HDMI cable attached, and attach cable when boot process is complete. 2. Getting GUI usable: in case of Gnome Shell I had to disable Wayland support in /etc/gdm3/custom.conf - then Xorg re-initialize output dur
  11. Balbes150 images with Linux 5.9 never worked for me - red light doesn't even turn on (I just checked images from your link, still doesn't work). Images with Linux 5.10 on other hand does work, but with rendering artifacts.
  12. I see menu but it's seems like it doesn't accept keyboard input, probably due to the fact that my keyboard is attached via USB dock. But since it separate board specifically for testing it's fine, really. During testing I found interesting difference between old Armbian installation running on first NanoPC-T4 that I been used for testing of your rk3399-nanopc-t4-tc.dtbo and fresh Armbian installation I running on second NanoPC-T4 where I tested this extlinux.conf. The difference is incompatibility with Dell UP3017, which I previously mentioned in first paragraphs of this message, i
  13. Turns out this issue is not ROC-RK3399-PC specific - seeing same issue on NanoPC-T4 too. Display model is Dell UP3017.
  14. ~# cat /proc/cmdline root=UUID=1381bbaa-1ce4-41e6-8e85-2ae1d4a974e2 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=7ac8d505-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 ~# ls -hal /boot итого 65M drwxr-xr-x 3 root root 4,0K дек 27 03:57 . drwxr-xr-x 19 root root 4,0K дек 12 17:46 .. -rw-r--r-- 1 root root 166 дек 27 03:57 armbianEnv.txt -rw-r--r-- 1 root root 1,5K дек 12 17:50 armbian_first_run.txt.template -rw-r--r-- 1 root root 38K дек 12 17:50 boot.bmp -
  15. Sure, we could try this, but for further test I will use one of spare NanoPC-T4 I have on hands (above I tested board running in production) with fresh image from downloads. It will probably take a few days until I find time to deploy the image to sd card and post output (hopefully I will manage to do so in Saturday) so in case you find free time earlier than I do - you probably could retrieve all needed information from Armbian image itself. Or, alternatively, I could try to build 5.10 with your config.