wizetek

Armbian_23.8.2_Orangepi3b_bookworm_edge_6.5.2.img boots, runs, and installs OK on Orange Pi 3B. Tested on 4GB RAM model with 256GB eMMC. - WiFi works* - HDMI audio works - 3D acceleration Panfrost driver works I installed xorg, mesa, x11vnc, jwm, pulseaudio, and flatpak native packages, which was followed by adding Kodi flatpak. Everything worked - with one caveat: there is a delay between keystrokes and output. Typing locally is fine, the problem manifests itself during an inbound SSH connection or when using a remote control app for Kodi on Android mobile. I have tried first replacing pulseaudio with pipewire (no change), making sure that WiFi powersave was disabled (it is by default through NetworkManager conf.d override), then I decided to disable IPv6 in NM system-connections. This had no immediate effect but after some time, likely when the previous IPv6 lease had expired, the delay problem was resolved. [edit] The input delay problem is still there. Looks like it sort of "unclogs" itself once continuous network data flow is received but is always stuck on initial input when characters are not repeated. Any ideas what else to check? [edit 2] This network input delay problem is not exclusive to Armbian. I see the same outcome with Orangepi3b_1.0.0_debian_bookworm_desktop_xfce_linux5.10.160.img and RaspiOS Bullseye kernel 5.10.160. There are no issues when using a third party USB WiFi adapter instead of the onboard chip. Good job Armbian! 👍 So now OPi3B build needs a maintainer.

I'd take a look inside /usr/lib/modules/5.10.110-rockchip-rk3588/kernel/drivers/net/wireless and base my purchasing decision on that; something based on Atheros (old), Ralink (old), Zydas (old), Realtek, or MediaTek (my personal preference). To name a few available modules: ath10k (Atheros) ath11k mt7601u (MediaTek) mt76x0u (x=0,1,2...) mt76x2u mt7663u rt2500 (Ralink) rt2800 rt2x00 rt73 rtl8187 (Realtek) rtl8192cu rtl8xxxu zd1201 (Zydas) Useful link: https://teamgloomy.github.io/armbian_wifi.html

Yes, software cursor causes flickering when moving around, unfortunately. But it hasn't disappeared on me yet. It may be worth exploring to add some other X optimizations, like these ones: https://github.com/JeffyCN/meta-rockchip/blob/master/recipes-graphics/xorg-xserver/files/20-modesetting.conf

The disappearing mouse cursor problem seems to be triggered after idle time, or after screensaver/DPMS has kicked in, or after monitor input source switch. Looks like this X config may work around it until a better solution is provided: /etc/X11/xorg.conf.d/99-swcursor.conf Section "Device" Identifier "GPU" #Driver "modesetting" #Driver "rockchip" Option "SWCursor" "True" EndSection I tested with the Driver portion commented out but it may be necessary to specify one.

Tested Armbian_23.02.0-trunk.0179_Orangepi5_jammy_legacy_5.10.110_xfce_desktop.img (+) Console rows/columns calculation on 1440p display is confirmed fixed. X server resolution is now capable of going to native 2560x1440 - fixed. (-) Xfce: Appearance > Settings > Window Scaling defaults to 2x making everything look huge. Mouse cursor disappears intermittently while mouse continues to function.

@Avatar Ng@Nodon For the sake of completeness and for the benefit of others – the KingSpec M.2 2242 NVMe SSD comes in different variants: NX series PCIe M-key NT series SATA III (marketed as NGFF which really means M.2) B+M key older NE series sold as PCIe with B+M key From https://semiconductor.samsung.com/consumer-storage/support/faqs/nvmessd/ B key is 6 narrow + the rest wide M key is wide + 5 narrow B+M key is 6 + wide + 5

My experience so far: 1. Booting up (Jammy/Bullseye) from SD, HDMI out to 1440p display cuts off text at the bottom. It affects installation and later use. I need to press ENTER several times to all questions until text moves up in the buffer and becomes visible, and then blindly type the answer to proceed to the next step, then several ENTERs to scroll again, and so on. Looking at fbset and stty output: me@opi:~$ fbset -i mode "2560x1440" geometry 2560 1440 2560 1440 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : rockchipdrmfb Address : 0 Size : 14745600 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 1 YPanStep : 1 YWrapStep : 0 LineLength : 10240 Accelerator : No me@opi:~$ stty size 28 100 After installation, I can set proper console columns and rows corresponding to the font size: me@opi:~$ stty rows 67 cols 240 And to make it persist on boot: /etc/default/console-setup SCREEN_HEIGHT="67" SCREEN_WIDTH="240" 2. X server resolution only goes up to 1920x1080 on the same 2560x1440 display. 3. After switching monitor inputs and going back to OPi5, X server resets the resolution from 1920x1080 to 720x576. 4. In 1920x1080 everything looks abnormally scaled and huge. Decreasing DPI below the "default" 96 in Xfce helps a little but it still doesn't look right. 5. Finally, there are file conflicts among packages: firmware-misc-nonfree vs armbian-firmware and armbian-firmware-full. This was reported back in 2019 but not addressed. https://github.com/armbian/build/issues/1359

@Avatar Ng The interface on the board is PCIe – not SATA, so this may explain why it's not detected.