the nvme(4) driver now prints a detailed message about I/O errors. It’s great that it does that, hope you never see it.
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.
If you are using urtwn(4) for your USB network connection, it now supports the Edimax EW-7811Un chipset? model?.
It’s not possible right now, but there’s people looking to implement it.
When you are setting up a DragonFly machine on Hetzner, pay attention to this bug report for dhcp setup. The short answer is “use dhcpcd”.
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 WhiskeyLake Intel CPU, the i915 driver on DragonFly now recognizes it for hardware acceleration. This will be in the upcoming release.
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.
Update: Pierre Alain-TORET found the correct commit.
Aaron LI’s added NVMM, hardware acceleration for virtual machines, to DragonFly.
The version of qemu in dports is not set up to support this, yet. Until then, you can download a prebuilt version.
Since NVMM originated on NetBSD, the NetBSD documentation page for it describes how to use it quite well. There’s a man page in DragonFly for it too, of course. There’s even basic machines to try.
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.