This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To start OpenBSD on Raspberry Pi 4, you need to set the device to boot in DeviceTree mode. | |
UEFI 1.19 doesn't work, but using 1.18 from the same location works. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This setting is quite useful on slow machines where security is not very important. | |
# rcctl disable library_aslr |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I've faced slight issue with watchdog on Raspberry Pi 3 and OpenBSD, which turned out to be my fault, but for future | |
reference, or if somebody happens to be equally stupid as me. | |
It seems that prefered way of starting watchdog in OpenBSD is to run watchdogd daemon, which sets | |
kern.watchdog.period=30 sysctl setting. Seeing that "it just sets the sysctl variable", I've set it myself | |
in /etc/sysctl.conf, which turned out to be the problem as /etc/sysctl.conf gets processed quite early in the | |
boot process, while watchdogd daemon is late in the boot process. | |
This setting caused that watchdog has been killing Raspberry Pi during the "reordering libraries..." phase. | |
Not sure why that is happening though, but not setting the kern.watchdog.period in sysctl.conf and only letting | |
the watchdogd deal with it solves the issue. |