I also tried and couldn't reproduce the failure in a 32-bit chroot on #Gentoo's #aarch64 development machine, so I was stuck doing all the debugging (and loooooong #gcc builds) on my very slow single-core 800MHz Solid Run #CuBox.

Diff'ing the assembly output between the non-working and working gcc versions I saw:

> - vmov.f64 d0, #6.:e+0
> + vmov.f64 d0, #7.0e+0

Naturally, binutils' assembler fails to recognize "6.:e+0" as a floating-point constant. Where is the ":" coming from?

Disconnecting the hdmi-cable for a few seconds made it boot.

This is a know issue I already had read about during initial setup (and didn't remember it). When I changed the connected client from a #cubox to my #Librem5 it hit me.

Thanks for the quick reminder and help and the interesting information about the development process of the #PiKVM!

It turned out that having the mentioned jumper No14 closed doesn't make much sense, because there seems to be no negative effect known and opening the jumper does rule out the hdmi issue I ran into.

BTW: Looking forward to Pi-Cast!

PiKVM does not boot with device connected · Issue #986 · pikvm/pikvm

Describe the bug When I switch on the power to my PiKVM the power led inside the case switches on and nothing happens - no output on the oled, no blinking of the ACT led. To Reproduce Steps to repr...

GitHub
Positive update this time 🙂 I figured out the problem with my eSATA drive. There wasn't sufficient power. Now I reinstalled #armbian, ran #nextcloud via onion script and everything seems to be working just fine. Finally, I installed #pihole on top of that. So even though #cubox is not the newest piece of hardware it will do for now. Great success! 😎 #selfhosting
Well, I'm sad to say that no progress so far. I managed to transfer the root partition to external drive (via eSATA) but something's wrong since the whole system is slower than before. I suspect it's either a faulty cable or perhaps #Cubox (i2ex) is simply not up to the task. Or it's something else entirely. I'll investigate next week. It's quite possible that I'll have to replace Cubox with a #RaspberryPi eventually. Anyway, wish me luck 🙄
Remember when I told you about #nextcloud via #tor? Well, I did a little research and it turns out that my old #cubox supports eSata drives. So I instantly ordered a 500GB HDD along with a proper cable. When I receive the package I'm gonna set #armbian to use HDD as a primary (root) partition. I guess we'll see how it goes. The plan is to use HDD as Nextcloud instance (behind Tor) for me and my wife. Keep your fingers crossed 😉 Anyway, I'll try to inform you on my progress. #diyproject
#TIL you can actually run #nextclolud as an onion service. Big advantage is that you don't need a public IP to access your cloud from anywhere. The traffic goes entirely through #Tor. I tried it today just for fun on my #cubox + #armbian combo. Everything works except it's a little slow because of an old and small SD card. I think I'm gonna explore this solution more as soon as I have a board with bigger and faster storage. #diyproject
So yesterday I managed to install #PiHole on my old and dusty #Cubox. Another achievement unlocked! 🙌🏻 BTW, can you recommend any good block lists? I'd especially use some lists for Polish sites.
@barszczyk #yunohost nawet chwilę testowałem, ale porzuciłem bo nie mam 'wyjścia' na zewnętrzne IP. Ogólnie mi się podobało bo większości rzeczy można wyklikać. Jednak daleko nam jeszcze do pełnej wygody jeśli chodzi o self-hosting. W tym momencie chyba wolę zapłacić za szyfrowaną chmurę / email / ogólnie hosting bo to prostsze i nie muszę tym zarządzać. Aktualnie korzystam tylko z #syncthing na #cubox którego kupiłem parę lat temu. Swoją drogą polecam #Armbian jeśli korzystasz z jakiegoś komputerka z procesorem ARM.
#Cubox + #Armbian + #Syncthing = cute little home server 🆒 🤓
Finally got #Syncthing to work on #Cubox. I even managed to sync photos from my phone. Small steps but the idea of self hosting makes me so damn hyped.