Matthew Dillon and Adrian Chadd have updated the wifi setup in DragonFly, incorporating Adrian’s FreeBSD changes (and merging back some of Matt’s from DragonFly). This affects the ath, rum, iwm, iwn, run, bwn, urtwn, wi, ral, iwi, ndis, and wpi drivers. The ‘an’ driver has been removed, too. I’m not going to even try to link to all the commits.
If you’re on DragonFly master and are using one of these devices, now is the time to update and try. Note that this removes the separate network interface that’s specific to the device and creates only a wlanX device.
Update: Matt reminded me that at least half the work came from Imre Vadasz; I missed it because I was only looking at the commit email names – mea culpa.
Read this email thread for how to mount devices (e.g. USB drives) in DragonFly when you aren’t root.
If you get “libGL error: failed to open drm device: Permission denied” when using direct rendering, make sure to add your user id to the ‘video’ group.
The drm/i915 driver has been updated by Francois Tigeot to match what’s in Linux kernel 4.3. His commit post has the general detail; you will especially want this if on DragonFly-current and running on Skylake architecture.
If you’ve ever wondered how having multiple swap devices can work, here’s your DragonFly-specific answer.
If you remember this Baytrail problem, Daniel Bilik has gone and found a fix, as this appears to be a cross-platform bug, and he has patches for DragonFly. If it’s affecting you, you don’t have to wait for the patches to be added in; he’s made them available directly.
Update: it’s committed to DragonFly now.
Do you have a Cherry Trail SoC? For example, a HP x2 210? Imre Vadasz’s recent commit may be useful for you, if you are running DragonFly on this detachable … thing?
Tim Darby is looking for motherboard recommendations. Specifically, mini-ITX with 4 SATA ports and at least one decent network link. Who’s got hardware to recommend? There’s already one set of suggestions.
If you have a Radeon video card in your DragonFly system, and are running bleeding-edge, there’s an update for you. This is a partial sync with Radeon code for Linux 3.18, with no additional notes in the commit but you can always check elsewhere.
If you somehow have a device with multiple SD/MMC card slots, you can now access all of them under DragonFly. (Apparently done to make a tablet run DragonFly better, going by IRC conversation)
John Marino rearranged how GCC5 handles CPUTYPE settings. If you are specifically setting the target CPU when compiling, his commit will give you an exact list of what to target.
Note that I am not saying another architecture – this is all x86_64. I also don’t recommend doing this unless you have a specific use for it – compiler overoptimizations often create more problems than they fix.
Daniel Bilik has found there’s an issue with i915 acceleration, Baytrail CPUs, and some AUTODEEP low-power states. This will only affect you if you are using that specific hardware combo and setting certain low power modes. Interestingly, it affects other platforms, too, as it appears to be a symptom of how the video is addressed, not a DragonFly-specific bug.
Francois Tigeot has again updated Intel i915 video support in DragonFly, bringing it even with what’s in Linux 4.2. This will be very useful for Broadwell and Skylake users, and even Broxton, apparently the newest Atom platform.
These probably apply cross-BSD, but in this case, it’s DragonFly tips for printing with CUPS.
If you have a Core2 processor in a DragonFly system, it may not work with accelerated video. If that happens to you with this (admittedly old) processor, switch to VESA for now.
For those of you with i915 video on your DragonFly system, there’s another update bringing DragonFly support to match what’s in the Linux 4.1 kernel. ValleyView and Skylake processor owners will benefit, along with a slew of other bugfixes and improvements.
Are you using a i915 video chipset? Are you using the DisplayPort? Imre Vadasz has added a tunable that may make it work better.
Sepherosa Ziehau has an update to the em/emx(4) (or other Intel NICs) driver, for testing. Hey, remember what I said the other day about Skylake support?
New CPU support in DragonFly is continuing, and Matthew Dillon will be testing one of the newer Intel ‘Skylake‘ processors soon. That may mean even more accelerated graphics support at some point, too.
This is a little thing, but so useful: the Wi-Fi indicator light on your iwm(4)-using device will now show its status under DragonFly.