mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.8K
active users

#arm64

8 posts8 participants0 posts today

The recording of the April 23rd, 2025 #bhyve Production User Call is up:

youtu.be/msJp73WRLq4

We discussed truncating large disk images, OpenPower planning, a new ESXi release, Haiku, a long-term networking issue and its progress, #FreeBSD 15.0-RELEASE goals, uboot/squashfs/uboot under #ARM64, debugging with GDB and bhyve, joining Production User Calls with FreeBSD and Wayland, and more!

"Don't forget to slam those Like and Subscribe buttons."

Continued thread

#gvim #arm64. A few steps down the rabbit hole and the gating factor seems to be availability of #windows #github CI machines for open source projects. All of the tool maintainers who maintain things for free aren’t going to jump on windows ARM until github opens that door. This seems like a huge opportunity for #microsoft to drop the ball here ;). @dsyme ?

Lately I've been doing more #SelfHosting again due to the current situation. Of course, I'm paying particular attention to power consumption and noise. After good experiences with the #ARM64 architecture, even with power-hungry applications such as Mastodon, I'm now using the smartphone technology for my homeservers, too.

There are #SBCs with more open hardware, but the #RaspberryPi is widely available, well documented, powerful and inexpensive. And it is available with up to 16 GB of RAM.

Anyone operating a server on the Internet must install #security updates quickly. However, many people forget to restart running software so that the new version runs instead of the old one. The #needrestart tool helps with this on Debian-based Linux systems, which unfortunately is usually not pre-installed.

On my Raspberry Pi 4, needrestart always runs correctly (automatically after apt upgrade). On my Raspberry Pi 5, however, I first had to create a configuration file as described by the main developer here:
github.com/liske/needrestart/b
Previously, the tool always claimed that a reboot was necessary because it thought an outdated Linux kernel was running.

Next, I want to activate #LUKS hard drive encryption on both raspis. Unfortunately, this is not as easy under #Raspbian or #RaspberryPiOS as on other Debian systems. If you have managed this: Please let me know how you did it!

Mastodon, gehostet auf fedifreu.deFedifreudeDiese Mastodon-Instanz wird vom überregionalen netzaktivistischen Zusammenhang Datenfreude <https://datenfreu.de> betrieben. Dazu zählen https://datenpunks.de und https://kleindatenverein.org.
#rpi#rpi5#raspi

In letzter Zeit mache ich aus gegebenem Anlass wieder mehr #SelfHosting. Natürlich achte ich dabei besonders auf den Stromverbrauch. Nach guten Erfahrungen mit der #ARM64-Architektur selbst bei leistungshungrigen Anwendungen wie Mastodon setze ich jetzt auch zuhause auf auf die aus Smartphones bekannte Technologie.

Es gibt zwar #SBCs mit offenerer Hardware, aber der #RaspberryPi ist überall erhältlich, gut dokumentiert, leistungsfähig und preiswert. Und es gibt ihn mit bis zu 16 GB RAM.

Wer einen Server am Internet betreibt, muss zügig #Sicherheitsupdates einspielen. Viele vergessen aber, laufende Software neuzustarten, damit die neue Version läuft statt der alten. Dabei hilft auf debianbasierten Linux-Systemen das Tool #needrestart, das leider meist nicht vorinstalliert ist.

Auf meinem Raspberry Pi 4 läuft needrestart schon immer korrekt (automatisch nach apt upgrade). Auf meinem Raspberry Pi 5 musste ich aber erst eine Konfigurationsdatei anlegen, wie es der Hauptentwickler hier beschreibt:
github.com/liske/needrestart/b
Bis dahin behauptete das Tool immer, dass ein reboot nötig sei, weil ein veralteter Linux-Kernel laufe.

Als nächstes will ich auf beiden Raspis die Festplattenverschlüsselung aktivieren. Das ist unter #Raspbian bzw. #RaspberryPiOS leider nicht so einfach wie auf anderen Debian-Systemen. Wenn ihr das geschafft habt: Schreibt gern eure Tipps!

Mastodon, gehostet auf fedifreu.deFedifreudeDiese Mastodon-Instanz wird vom überregionalen netzaktivistischen Zusammenhang Datenfreude <https://datenfreu.de> betrieben. Dazu zählen https://datenpunks.de und https://kleindatenverein.org.
#rpi#rpi5#raspi

💻 FreeBSD Snapdragon X1E-78-100 💻

@dexter Revisiting the ThinkPad T14s Snapdragon with FreeBSD 15, here's where I left off. Do you know if there's been substantial momentum for the chipset (iirc, similar underlying requirements for your X13s)?

Two items stand out from my perspective, which may point to missing aspects in the "Fixed ACPI Description Table (FADT)", which should map the HPET .. hmmm..

1. No PSCI/SNCCC call function found
2. panic: No usable event timer found!

@crest this might be of interest?

From the original discussion months ago, some aspects from Linux World, specific to the X1E, which .. while not new-news etc etc you know where this goes... perhaps references something-something technical aspects. 😊 The T13s has almost full support for hardware enablement on 6.12/13 and branched.

- aarch64-laptops.github.io/
- github.com/aarch64-laptops/aar
- github.com/aarch64-laptops/aar
- git.codelinaro.org/linaro/qcom

FreeBSD verbose boot output:

```
No PSCI/SNCCC call function found
Enabling DIC à IDC ICache sync
Enabling LSE atomics in the kernel
Enabling BT1
randon: registering fast source Brave rndr RHG
randon: fast provider: "Brave rndr RNG"
randon: no preloaded entropy cache
randon: read 2848 bytes from platform bootloader
randon: unblocking device.
VIMAGE (virtualized network stack) enabled
hostuuid: using 88888888-8888-8888-8888-888888888888
ULE: setup cpu

random: entropy device external interface
feeder_register: snd unit=-1 snd_saxautovchans-16 latency 2 feeder_rate_ain-1 feeder_rate_nox-2816888 feeder_rate_round-25
firmware: "tegra218 xush fu' version 8: 132688 bytes loaded at @xffff080088b2c658

kbde et kbdn
nes: <nesory>
null: (full device, null device, zero device>
openfira: <Open Firmware control device>
top_log: top_log device
crypto: <crypto core>
Device configuration finished.
procfs registered
panic: No usable event timer found!
cpuid = 8
tine 1

KDB: stack backtrace:
db_trace_self) at db_trace_self
do_trace_self urapper() at db_trace_self_urapper+0x38
vpanic() at vpanic-Bxiac
panic() at panic-x48
cpu_initclocks bsp() at cpu_initclocks_bsp+b5f4
initclocks() at initclocks Bbx28
ai startup() at ni startup-bddc
virtdone() at virtdone x6c
KDB: enter: panic
I thread pid B tid 199000 1
Stopped at kob_enter+x48: str хаг, (x19, 12848)
```

> Note: The log output was screen grabbed from the attached image, using Google Gemini to identify the text for copy/paste. There are some conversion aspects which are likely not fully correct, but it's rather helpful vs not using automated OCR.

Replied in thread

@JessTheUnstill @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii Exactly...

Coincidentially, that's why #Android (and #iOS) doesn't let users have #root access because billions of devices owned by mostly "#TechIlliterates" that hardly get #SecurityUpdates would be an even bigger risk if they didn't boot a locked-down #ROM image, thus only allowing for #malware in user-privilegued userspace!

Cuz having a mobile OS that shoves everything through #Tor and only allows #userspace-Apps in the form modern web technologies would be a big #security and #privacy gain.

  • Not to mention #amd64 is on it's way out and inevitably they gotta have to transition to supporting #arm64 and eventually #RISCv-#64bit at some point.
#64bit#riscv#arm64