#
✕ nick:supae
#asahi-alt · 2023-12-11 04:23
supaeif anyone else is running OpenBSD on a Macbook (I'm sure there are tons lol) and could share how they do it I'd be incredibly appreciative
#asahi-alt · 2023-12-11 04:22
supaeI'm sorry for the beginner question, but I can't seem to find an answer anywhere after a few hours total of searching. How do I set the scaling/resolution in OpenBSD so that it doesn't look unreadable on my Macbook (I'm using xenodm/fvwm as per the defaults)? I've tried using xrandr and a variety of things mentioned all over the internet with no luck.
#asahi-alt · 2023-12-10 07:32
supaeI believe it was on /dev/sd0m due to me making a blank 60GB APFS container, so that I could just tell OpenBSD to use my whole disk without it actually taking up the whole disk. I could be wrong though lol, but maybe that needs a patch?
#asahi-alt · 2023-12-10 07:29
supaeoh damn I patched it myself somehow! the issue is in how install.md works, the line "if mount -o ro /dev/sd0l /mnt2 2>/dev/null; then" makes an assumption that the EFI partition will be on sd0l while mine was on sd0m
#asahi-alt · 2023-12-09 01:42
supaeI have a handtyped log of the panic message/backtrace and could put it in a pastebin along with my system info if needed
#asahi-alt · 2023-12-09 01:41
supaeI'm on firmware "14.1.2 (23B92)" and have an identical panic message as that post (file "/usr/src/sys/arch/arm64/dev/rtkit.c", line 553), and I'm not sure if OpenBSD handling >=13.5 firmware has been fixed or not? If anyone else knows anything I'd appreciate it too
#asahi-alt · 2023-12-09 01:38
supaehey tobhe, I'm having a kernel panic issue of the same variety as (https://www.mail-archive.com/bugs@openbsd.org/msg20150.html), and I noticed you have a custom version of the asahi installer, is it still usable?