dochawk

ok, record time for answering my own question. google just caught an update in my search, and the answer is that the "xauth" package must be installed on armbian. with that done, exiting the session, reconnecting, running"ssh -X" and setting DISPLAY to "mymac.local:0" gives me my X connection.

I am trying to connect to my armbian install (on an orange pi 4 LTS) from OSX (with Xquartz) to run the mythtv backend setup. I didn't install the desktop version of armbian; just the base version, and with the image for this model of pi. connecting by SSH is not a problem, I happily get through. The problem is, both with the -X and -Y options, I can't forward X successfully. DISPLAY doesn't get passed. On the Mac side, it's variously ":0" or something like "/private/tmp/com.apple.launchd.Cvf3IlZ6rM/org.xquartz:0" (which would have no meaning to another machine). I've set to :0 , :0.0 , mymac.local:0 (after entering the ip in /etc/hosts). I've used scp to transfer the .Xauthority file, and also to delete at armbian end. I've used "/opt/X11/bin/xhost + mythbackend" and the reckless "/opt/X11/bin/xhost +" In pretty much every combination, I get "xterm: Xt error: Can't open display: 10.0.1.11:0" or similar when trying to launch. (when I set to mymac.local:0 it takes a couple of minutes before the similar message). on the armbian, I've altered /etc/ssh/ssh_d to add "ForwardX11 yes". Am I missing something? 25 years ago, I was blithely running into computer labs wherever I was and using terminals to connect to the box on my desk. It's kind of frustrating to fail across the family room! any ideas as to what I'm missing?

FWIW, I've found that armbian-install, booting off the SD armbian system, will copy over to the EMMC--but still isn't bootable. Theres's another option to rewrite the boot loader for "SD/EMMC", but I'm really not sure which/how it will target, so I won't touch that until I find someone who knows it better. I'm toying with the idea of somehow writing a different linux over the bootable armbian SD, but I haven't figured quite how. In your case, that might lead to getting the workable pi SD, and then copying a live ubuntu over?

The answer seems to be that the usbc connector either isn't really usbc, or that it won't supply power to a connected device. . I connected it to the type A usbc, and it was instantly found and appeared as /dev/sda

it seems that oranges are picky about distributions. On a 4 LTS, I flashed both ubuntu and raspbian on multiple cards, to no avail. They were all ignored, and it booted android from EMMC. I used both the raspian tool and direct write with dd. Also, android was able to see the and manipulate the SD once it booted. then I used balena etcher with armbian, and it booted--but I still can't see the ssd connected to the usbc connector.

I was happy to find the Orange pi 4 armbian; it ignores raspbian an ubuntu images on sd and boots into android from its EMMC instead. The pi is an orange 4 LTS with 3gb RAM and 16gb EMMC. I have a 2tb crucial SSD attached through the usbc port. It is powered by a 4A supply through the DC port. it's purpose is to be a dedicated mythtv back end; it is wired by ethernet but also has wifi active. armbian-hardware-monitor.log is at https://paste.armbian.com/axayequliz it isn't showing up as a disk, as near as I can tell: the first is the EMMC, I believe, and the second my sandisk card. I haven't used linux since the late 90s when I switched to FreeBSD, and so much has changed . . .