Matthew Dillon’s made several changes to improve support for AMD SB850 chipsets (for AHCI) and also for 880/890 chipsets. If you have one of these systems, it may be bootable/more reliable. Don’t start messing with the hot-plug capability yet, though.
Naoya Sugioka had trouble booting DragonFly on his Dell M4400. He updated ACPICA with this patch, and was able to boot. I link to it in case someone else with a recent Dell model (or perhaps just a laptop with the same chipset?) has the same issues.
Chris Turner is working on ral(4) support, specifically the eee901’s 2860 network chip.
Chris Turner posted details of how he gets jack (“a low-latency audio server”) to run on DragonFly. Your mileage may vary.
YONETANI Tomokazu wrote out a nice explanation of acpi(4) and the myriad ACPI subsystems which can be enabled or disabled at boot time. If you do have booting problems, it’s usually ACPI, and it’s usually only one small part. Finding that small part is easier with this list.
If you were thinking of buying a Western Digital Passport USB drive, it’s supported on DragonFly, thanks to Dylan Reinhold and Alex Hornung.
Matthias Schmidt has set up a x86_64 DragonFly machine at uther.dragonflybsd.org. Anyone wanting to try 64-bit testing can use a vkernel on that machine. Mail him for an account.
Hasso Tepper posted a link to something I had only heard about when it didn’t exist in physical form: the Open Graphics Device v1. It’s possible to get one if you’re going to write support for it.
In an effort to support a new system with an AMD 880G chipset, Matthew Dillon has updated the AHCI driver. If you have SATA drives using AHCI, please test. (with any chipset, not just 880G.)
Sascha Wildner has brought in some changes to twa(4), for various 3ware RAID controllers, from FreeBSD. Also, YONETANI Tomokazu has added PCI IDs fixed up files for Adaptec ServeRAID 7x ips (4) devices.
Due to changes in networking, most of the wireless drivers in 2.7 stopped working a few days ago. Joe Talbott’s “brought back” iwi, ral, and wi. If you’re running 2.7 and using one of those drivers, it should be safe, relatively, to upgrade to a newer 2.7.
Well, technically not ripped out, just serialized roughly. This means if you update your DragonFly 2.7 machine in the next few days, the wireless drivers may not work, except for (I think) ath(4). They should return, better, by next week.
Apparently the recently committed support for Areca RAID cards came with some help directly from Areca, facilitated by Venkatesh Srinivas. Perhaps next time you’re searching for a RAID card, consider Areca in light of the effort they are willing to contribute for an open-source project…
Sascha Wildner has brought in arcmsr(4), an Areca RAID controller driver. Please try it if you have the right hardware.
Among other things, Joe Talbott has brought in support for the 6000 and 6050 series of iwn(4) wifi devices.
Sascha Wildner has pulled in a bunch of updates for twa(4), adding more devices for this SATA RAID device driver. There’s a list of what’s supported now on the man page.
Joe Talbott’s ported over iwn(4), which is the “driver for Intel 1000, 5100, 5150, and 6000 wifi chipsets.”
EHCI support is now always on, for 2.7 users, and will be for 2.8 when released. It’s possible to turn it off if it causes a problem, but it should generally just mean better USB performance.