DragonFly-current, that is. Some newer multi-processor systems use X2APIC to boot, and DragonFly can now use it.
If you have a serial card add-in, DragonFly can now output the console to it – a way to run completely headless. It’s not quite like a normal on-motherboard serial port boot, so look at the commit notes for implementation details.
Here’s something that doesn’t have an immediate impact now, but will be useful down the road: Francois Tigeot has been working on DRM support in DragonFly, and has been quite successful with Intel video support. His strategy has been to adopt Linux methods where possible, to reduce the amount of support work. The payoff has been excellent, and prompt, accelerated video support in DragonFly. The most recent work is “git: drm: Implement parts of the Linux irq subsystem“, which is going to come in handy for someone, I’m sure.
Some nice tech explanations this week.
- OpenBSD on my fanless desktop computer. Read to find out more about the RUNBSD stickers. (via)
- OpenBSD Community Goes Gold for 2018!
- Hardware accelerated AES/HMAC-SHA on octeons.
- Caddy Web Server on FreeBSD.
- free command for OpenBSD. I’d love to see a deep dive into the various BSD *stat commands. (via)
- Call for Papers | EuroBSDcon 2018. (via)
- Towards Secure System Graphics: Arcan and OpenBSD. (via)
- NetBSD 8.0RC1 is out.
- Running my own git server. On OpenBSD. (via)
- Perl @INC – customizing it for FreeBSD.
Shutdowns are a bit faster in DragonFly, thanks to the addition of a QUICKHALT shortcut. How much faster? It depends on what devices you have mounted, I suspect. I haven’t yet updated and tried.
This is a sort of nice non-report report, cause EFI booting just works fine, as you’d hope/expect.
For your Monday entertainment: the boot log from DragonFly on a system with 11 sockets, 10 cores per socket, for 110 CPUs. Plus 8 TB of RAM.
(Skip past the control codes at the start)
The default kernel config for DragonFly has changed: Sascha Wildner has added the acpi, gpio_acpi, gpio_intel, smbus and smbacp devices. If you are using a custom kernel, you’ll probably want to add these. If you aren’t using a custom kernel – you should have no negative effect.
The title really says it all – if you have a Coffee Lake series Intel chipset, your video is accelerated on DragonFly.
One side effect of Meltdown/Spectre are CPU microcode (firmware) updates. For future needs: sysutils/devcpu-data is the port that has the updates for Intel, and cpucontrol(8) is the program you run on DragonFly to add them.
I haven’t used this myself, yet, so I can’t tell you how necessary an immediate update could be – but you will probably want to use it soon.
Update: Newer CPUs might require this sizing change.