If you have a TP-Link TL-WN722N v2 wireless adapter, you are in luck.
This is mostly an ID change, but the Mercusys MW150US USB wifi adapter is now supported in DragonFly.
If you are running a headless DragonFly system, you may find this new ‘ifexists’ option for ttys helpful.
I may have missed this if it’s been committed, but if you have a Mercusys MW150US, aka a RealTek USB wifi dongle, there’s a patch to support it in Dragonfly.
For some reason smbios device support always gave me trouble on every laptop I worked on for the 2000s. So, this support for smbios identification on EFI-only boots is good news to me.
It’s not possible right now, but there’s people looking to implement it.
You can now set a description for a network interface on DragonFly. Don’t use ETH0, please.
If you are using AMD graphics on DragonFly, Aaron LI’s “how I set this up” post may be useful to you.
If you have a NVMe disk that happens to let’s say report inaccurate capabilities (i.e. lie cause it was built cheap), the NVMe driver in DragonFly can now attempt to survive the surprise.
DragonFly and Hyper-V’s virtual disk support do not appear to co-operate well, according to this bug report. Anyone have a Hyper-V host where they can confirm?
The amdgpu driver, equivalent to Linux 4.19, has been committed along with supporting changes in ttm. Credit goes to Sergey Zigachev, Francois Tigeot, and Matthew Dillon for the work. The module is now built by default in bleeding edge DragonFly. Note the amdgpu commit message lists some options that need to be set.
Yep, it’s probably there depending on your chipset.
Apparently a commit that I can’t find (“e8de9e9“?) disabled acceleration for R5 240 Radeon cards, but causes an error for R7 models. If you’ve got an R5 and you want accelerated video, try taking it out – assuming it’s not working already. Any other Radeon model, it may not make a difference.
The version of qemu in dports is not set up to support this, yet. Until then, you can download a prebuilt version.
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.