How best to do that? I've been treating systemd like a rattlesnake which I've seen in record breaking size, 7 feet long and the size of my calf. I was about 6, my stepfather was farming, had come in for lunch, opened the door to go back out and plow, slammed the door, reached over it for a cheap busted shotgun and a shell. reopened the door and took the head off it. 85 years ago. I haven't had a whole lot of use for a rattlesnake since although I've seen hundreds. Blacksnakes OTOH are goodfellows. They keep the rodents away by eating them.

After applying the following two kernel patches which I understand are valid for mainline kernel only, I can use the display properly with a resolution 3440x1440 and refresh rate of 60Hz: patchwork.kernel.org [RFC,v1] drm/meson: venc: add support for HDMI DMT modes up to 3840x2160 -... github.com/chewitt/linux WIP: drm/meson: add support for higher bandwidth DMT modes committed Jan 5, 2026 xdarklight +3 -3 There's a report from a user with a DELL U3415W monitor and a Khadas VIM3 statin… - But having both patches applied or not does not matter, in general with mainline kernel the display is flickering/shaking only during boot, any idea how to get this addressed? thx

I've read that page and I can't seem to get it working with the image both jock and Victor Picinin recommended yet it doesn't boot off the eMMC nor the SD. I'm at the end of my rope!

I have burned the image "Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz" using Balena Etcher to an SD card, then put it in the box and the light is blue, but the screen is black. please help, thank you this is a photo of the board I used

I have experienced something similar in the past and it made me very puzzled until I figured out what was wrong in that situation. Make sure the clock on both systems are synchronized to an NTP server. IIRC SSH just threw a fit exactly like this without logging why, and it turned out to be a security feature where the ssh server suspected the communication to be intercepted by man-in-the-middle due to clocks not being synchronized. And if logging in physically to the system, apt refused to work as-well until clock was synced. Could be worth to check next time... As for dhcp and systemd. Check if systemd-resolved.service is messing something up for you, maybe try to disable it?