animone.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
So I'm getting somewhere as I can launch them both if I start them like below.
doas seatd -u $(whoami) -l debug & mango
I know this is wrong but it seems like seatd isn't running as my user if I try and start mango or sway without that line hence the permission errors for the keyboard.
I have even followed the OpenBSD seatd man page and added my user justine to the _seatd group and then started seatd with doas rcctl start seatd but still the same no keyboard. If I look in /etc/group I see _seatd:*:564:justine so what am I doing wrong ?
OK #OpenBSD friends, Why when I install Sway or Mango ( #Wayland ) can I not get any keyboard control ? I can run them fine on #FreeBSD but on OpenBSD they both start but the keyboard does nothing on the mouse seems to work on waybar. I'm using known working configs for both.
I do see errors like permission denied for /dev/wskb* . I'm at a loss as I'm sure I had sway running last year ??
Even copied the startsway.sh and modified for mango but still no keyboard ???
Please boost for a larger reach. ❤️
@vlkrs@bsd.network Are you able to assist at all ? TIA
doas PKG_add -Dsnap -u .Once, someone asked what was the weirdest platform you run GtS on. Well...
This message was sent from
#GoToSocial running on an
#OpenBSD #arm64 board (#ODROID HC4).
Who needs gparted on #OpenBSD to change partitions layout from
# size offset fstype [fsize bsize cpg]
a: 1.0G 64 4.2BSD 2048 16384 12960 # /
b: 1.2G 2097216 swap # none
c: 50.0G 0 unused
d: 3.3G 4685888 4.2BSD 2048 16384 12960 # /tmp
e: 5.2G 11520928 4.2BSD 2048 16384 12960 # /var
f: 5.4G 22392384 4.2BSD 2048 16384 12960 # /usr
g: 1.0G 33701024 4.2BSD 2048 16384 12960 # /usr/X11R6
h: 6.9G 35798176 4.2BSD 2048 16384 12960 # /usr/local
k: 26.0G 50250272 4.2BSD 2048 16384 12960 # /home
to
OpenBSD area: 64-104857600; size: 50.0G; free: 0.0G
# size offset fstype [fsize bsize cpg]
a: 1.0G 64 4.2BSD 2048 16384 12960 # /
b: 1.2G 2097216 swap # none
c: 50.0G 0 unused
d: 2.0G 4685888 4.2BSD 2048 16384 12960 # /tmp
e: 5.0G 8883936 4.2BSD 2048 16384 12960 # /var
f: 5.0G 19374368 4.2BSD 2048 16384 12960 # /usr
g: 1.0G 29864832 4.2BSD 2048 16384 12960 # /usr/X11R6
h: 4.0G 31969344 4.2BSD 2048 16384 12960 # /usr/local
j: 30.7G 40371328 4.2BSD 2048 16384 1 # /home
when only a 6 times spells like:
# mount <mp>
# tar cpf <wherespaceis> <mp>
# umount <mp>
# disklabel -E -F /etc/fstab <disk>
# newfs <part>
# mount <mp>
# tar xpf <wherearchiveis> -C /
are enough? #RhetoricalQuestion
I can confirm that on my #OpenBSD -current #367 machine hw.blockcpu=L works for enabling SMT instead of the soon to be obsolete hw.smt=1
#RunBSD Recent obsession is about reusing #arm64 boards that sleep unplugged.. So today, here are two sets of notes regarding
#OpenBSD support.
Running on the #ODROID HC4 is pretty decent now. It already runs the DHCP, DNS and the WireGuard gateway. More is to come, if everything goes well.
https://www.tumfatig.net/2026/running-openbsd-7.8-on-odroid-hc4/
Running on the #Raspberry Pi Zero 2W is fairly unstable as-of now.
https://www.tumfatig.net/2026/openbsd-7.8-on-raspberry-pi-zero-2w/
It takes aaaaaaaaaaages to compile #GoToSocial for #OpenBSD on a #Raspberry Pi Zero 2 W... but it's a good stableness benchmark. So far, it has not hanged - now that I use another Ethernet Hat and POE adapter.
EDIT OK thanks to @r1w1s1@snac.bsd.cafe I'm now at 39 lines long. π€£

TIL that, if you have a USB soundbar connected to your #OpenBSD laptop, it is better to use sndiod -f rsnd/0 -F rsnd/1 than sndiod -f rsnd/1 (to force USB only). The first one works nice. The second seems to bring high latency on mpv and weird sound rendering on vlc.
Our friends from https://openbsdjumpstart.org published a nice article about bsd.rd.
Lab: Anatomy of bsd.rd β No Reboot Required