If you buy a Lenovo Yoga 500, or any laptop with an iwm(4) chipset, here’s how to get it going with DragonFly.
Apparently DragonFly used to disable IOAPIC when booting in a virtual machine. This helped with some old virtual machines, but broke newer ones. It’s now enabled, which helps boot DragonFly on Google Cloud.
If you’ve got a newer i219 ethernet chipset – it’s now supported in DragonFly.
I didn’t know this, but the label in disklabel(8) is called “pack ID” in the man page, and there’s only one way to update it right now in DragonFly. You may only need to know this a few times in your life.
Something I didn’t know but also never tried: ttyv0, the base terminal when booting up DragonFly, can extend to a max of 160 characters. Given that I am used to 80, that seems like overkill.
For those with a different keyboard layout – different than US English, I mean – and running xorg 1.20 or later: setxkbmap is the command you need.
If you have an AMD processor, support for the System Management Network and CPU temperature readings are now available in DragonFly as amdsmn(4) and amdtemp(4).
If you’re running a very recent HP laptop, this recent DMAP change may get DragonFly to boot on it.
EDIT: this MSIX fix, too.
DragonFly’s direct rendering has been updated to match Linux 4.12.15, which means improved support for a number of Intel processors.
If you have an Intel-based system and it has trouble reading some USB ports, or odd behavior with some virtual machines, this recent bugfix in DragonFly-current may help you. I know, my description is vague, but I haven’t encountered this directly.
DragonFly now has the wsp(4) device, for Wellspring touchpads on Apple laptops.
Daniel Fojt has fixed something that has bothered me for years: you no longer need to manually create wlan interfaces; devd does it for you.
If you happen to have an APU2, here’s some tips on the boot process.
The serial port in DragonFly is now set by default to 115200, not 9600 as anyone over 40 probably has memorized (along with the numbers 640, 1024, and 4.3M).
If you have UEFI hardware, there’s been an update in DragonFly of the TianoCore EDK II headers. If you are like me, you will find the tianocore.org site helps to understand what this is for.
Another network fix: if you have an iwm(4) wireless Intel device, here’s how you get it to stop saying “no carrier”.
If you’ve got an urtwn(4) device (RealTek USB wireless), and you are getting errors on altq_maxlen, take a look at this solution.
If you want to work on Bluetooth on DragonFly, there’s more people adding to the bounty.
sysmouse, the one mouse driver for X that always works for me, now has evdev support.
Related: why is there no evdev man page in DragonFly?