ndis(4) is removed from DragonFly; it’s probably been years since it was applicable to any hardware. I don’t think it will affect anyone – but it’s an interesting tool from a historical perspective; for a while it was possible to use Windows XP drivers to create a BSD network driver, effectively.
If you’ve got unshielded disk cables in a tiny PC, you can run the AHCI link a bit slower to better handle interference.
The drivers amdsmn(4) and amdtemp(4) have received several updates. The output still may have issues, but this is useful if you have newer AMD hardware.
If you have an AR9485 wireless adapter, this bug report notes the appropriate config for DragonFly. Might work for other hardware too?
I’ve seen this a number of times over the years: if you’re installing DragonFly and the install drive seems to disappear, it might be the USB port you plug into.
Sascha Wildner has added the PCI IDs for various recent ichsmb(4) devices. This I think just means a correct device name in dmesg, but unidentified smbus devices has plagued me for years, even with other operating systems.
If you’re running an em(4)/emx(4) network card on DragonFly, Sepherosa Ziehau’s updated to the 7.7.8 release of the driver from Intel, and added a few more chipsets too.
,
If you have a Broadcom BCM57785/BCM5718 series network card, supported by the bnx(4) driver, there’s some new models supported. There’s some fixes for other models, too.
I am not sure if these Radeon cards are tested on DragonFly, but it’s a good base to start from.
If you edit /etc/fstab, and then later change something like the proc filesystem from OpenJDK, you might not boot normally. Antonio Olivares has a solution for you.
MAP_VPAGETABLE has been removed in DragonFly because of conflicts with recent pmap work. This has the unfortunate effect of breaking vkernel(7), but vkernels can be resurrected with changes to use hardware virtualization support.
Note that running DragonFly as a VM is unaffected; that’ll still work just fine. This breakage is DragonFly-vkernel-on-DragonFly specific.
So, if you find yourself in possession of an ADM-3A terminal, and want to attach it to a DragonFly machine, here is the /etc/ttys config (viewed on the ADM-3A itself of course) and the front switch settings that worked for me.
Remember, ^h deletes.
DRM in DragonFly has been updated to match Linux 4.15.18, along with recognizing some new hardware.
I realized I never followed up on the call for testing: re(4) driver updates from Sepherosa Ziehau were indeed tested and found good, so the driver has been updated.
If you have a Realtek network card supported by the re(4) driver, Sepherosa Ziehau has a new driver for you to test.
If you’ve got a Zen 2 / Ryzen 4000 APU, the amdsmn(4)/amdtemp(4) drivers in DragonFly now support it.
Well, it doesn’t fix anything, but it seems like an answer that almost always helps: running sysmouse usually fixes most X11 mouse problems.
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.