RussianNeuroMancer
-
Posts
93 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by RussianNeuroMancer
-
-
On 8/29/2023 at 10:21 PM, viota said:
Has anyone been able to install a remote desktop on the R2S? If so I would be very interested in how that was achieved?
I didn't tried this on R2S specifically, but if it works inside systemd-nspawn - then it should work on headless SBC too.
1. Install Mate or XFCE via tasksel
2. Install gdm3 and tigervnc-standalone-server
3. Create these two files (don't forget to enable socket) and configure gdm3.
This is of course not only option - you can find other ways to get TigerVNC or xrdp works on headless system. I just told you what works for me, that it.
-
On 7/8/2023 at 6:08 AM, prahal said:
but as anybody disabled hs400 on rk339 at least nobody notice anymore
What do you mean? hs400 is still there.
-
Thanks for answers!
12.11.2022 в 08:57, SR-G сказал:not sure however what you are calling "DSF"
Dynamic Frequency Scaling
12.11.2022 в 08:57, SR-G сказал:this had nothing to do with disks - SSD or regular HDD
I never seen anyone with this issue and SSD, which is why I asked. (Assumed that it could be related to board's power supply somehow.)
19 часов назад, prahal сказал:I managed to run it for 61 days
Thank you for sharing your workaround.
-
So solution for this DFS issue was never found? Also is anyone got this issue with SSD drives? Or it happens only with HDD?
-
4 часа назад, Da Xue сказал:
@RussianNeuroMancer I didn't see this thread or I would have checked it out. This has to do with the delay in mmc initialization. Sometimes it's too fast and something hasn't stabilized. One method to delay it is to enable SPL debug. I have SD cards that just refuse to work but work flawlessly when I turn on debug. There's a delay somewhere that's missing in the u-boot code.
In sunxi_mmc.c sunxi_mmc_core_init, you need to raise the udelay to 5ms or 10ms. I didn't do extensive testing but it fixes nearly all mmc problems.
Hi! Thanks for advice, but unfortunately I don't have any Tritium H5 left on hands anymore, so I can't test this. If it works for you - maybe it makes sense to submit this change to upstream or at least ask for tests on mail-list?
-
-
25.05.2021 в 01:32, usual user сказал:
I use since long time pure mainline kernel for rt5651 support. The kernel hack that Armbian is still applying is not really required. If you like, I can upload a kernel for a quick test to see if it is also working for you. Or even easier, try this image for your NanoPC-T4, it should already have everything in place.
Unfortunately, this image does not load on my T4, get stuck here.
-
5 hours ago, jernej said:
Sometimes it seems that it helps if HDMI is unplugged
I had this idea but unplugging everything besides power doesn't help a bit.
-
3 minutes ago, lanefu said:
is a emmc v4 module? Allwinner H3 and h5 doesn't' support v5
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).
-
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?
On 4/15/2021 at 10:51 PM, RussianNeuroMancer said: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: http://ix.io/2Wbc
Tried this workaround but it does not help. Any other ideas?
-
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.)
-
On 4/24/2021 at 7:11 PM, thc013 said:
so i dont know wich distro he is using but he just could copy the patches from armbian
ony thig he had to do is choose a dtb or adjust it nothing more
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?
-
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: http://ix.io/3lMc
-
-
19 hours ago, Przemysław Sztoch said:
Could you explain what you had to do to solve problem?
Did you tried to update uboot via armbian-config?
-
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).
-
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: http://ix.io/2Wbc
-
-
-
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: http://ix.io/2Wbc
When I attach exactly same cable to any other Rockchip or AllWinner boards - issue no longer reproducible.
EDIT Another similar issue with meson8b-dwmac:
-
On 3/14/2021 at 9:27 PM, hive said:
the other interface either doesn't come up or shows up seemingly randomly as eth0 or eth1
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*
-
-
Is there any way to get DisplayPort over USB Type-C working on anything besides Firefly image? I tried Armbian legacy once again (this time I tested images for both of Renegade Elite and Station P1; latter image was tested with rk3399-roc-pc-mezzanine.dtb too) but unfortunately DisplayPort doesn't work at all (tested Dell DA300 and Belkin F4U093) - I guess due to difference in uboot version? Or maybe 4.4 tree by ayufan missing something for this board?
-
On 3/4/2020 at 12:55 AM, RussianNeuroMancer said:
While WD SSD, such as WDS200T3X0C, works just fine on both of Linux 4.4 and 5.3, SSD from Samsung, such as 970 EVO, works only with 4.4, but not with 5.3. Pci driver just fail to detect it, while on 4.4 same SSD works for half year without issues.
Issue with Samsung 970 EVO is no longer reproducible for me on uboot 2020.10 and Linux 5.10.
R4SE Armbian does not show second network interface
in NanoPi R4S
Posted
Put this into /etc/rc.local:
rmmod phy_rockchip_pcie && modprobe phy_rockchip_pcie exit 0
Don't forget to make it executable.
There was attempt to fix this, but it broke other boards.