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.
Francois Tigeot has updated DragonFly to match the video support found in the Linux 4.0 kernel. This will benefit you most if you are running Skylake, Cherryview, or Valleyview chipsets. Don’t ask me how to tell; the improvement has been so rapid I’ve lost track of which model codename is which.
I was going to point at a new igb(4) update for testing, but Sepherosa Ziehau has already merged it. Try it if you have the right Intel networking hardware.
Sepherosa Ziehau has a new version of drivers for em/emx(4) and igb(4). The initial versions had trouble, but testing is ongoing. Try it if you have the correct hardware.
Update: never mind.
If you have a em(4), emx(4), or igb(4), Sepherosa Ziehau would like you to try out his Intel NIC driver update. He’s already updated the ix(4) driver to support more hardware.
I’m combining two items because news happens faster than I can post: Tomohiro Kusumi has added a ‘dm-flakey’ target to the disk mapper, so you can simulate an unreliable disk, reliably.
Also, the DRM support for radeon chipsets has been updated to match the Linux 3.18 kernel, same as i915. Remember, you can control backlight brightness with it now.
Did you need to use SLIP on DragonFly? Do you remember what SLIP is? Well, it’ll work with a USB modem on DragonFly, even if you are making a face right now and saying, “SLIP? Who uses that?”
Sascha Wildner has brought over support for the Realtek 8168H. This may be useful because at least one low-cost server provider – Kimsufi, I think? – uses them by default in their product line.
For those of you with DragonFly and an Intel i915 chipset, Francois Tigeot has moved support up another notch, to match Linux 3.18. This will help Cherryview and Broadwell chipset users the most.
Imre Vadász has put together an initial port of Wayland / Weston for DragonFly. You can look at his pull request for dports to see how to install, though I’d imagine this is only for people who like to experiment at this point. It’s still work in progress, as is Wayland itself.
Tomohiro Kusumi has added a dm-delay target, which means you can simulate poor disk performance, without having to have poor disks. His commit message includes some benchmarks that shows it doing a good job creating a bad job.
There’s a new version of the Intel video driver in dports – xf86-video-intel-2.99.2015.09.09. If you update to this and you experience an xorg-server crash, Matthew Dillon found that changing the acceleration method from SNA to XAA fixes the problem. Don’t change it unless you actually see the problem, of course.
MIDI support has been (re) added in DragonFly, if I read this recent commit correctly. You may have supported hardware and not even realize it.
There’s been a lot of improvements to DragonFly and graphics support recently, and Francois Tigeot gave a talk at the 2015 X.Org Developer’s Conference outlining just how much has changed. He’s posted the slides.
Matthew Dillon brought over the FreeBSD iwm(4) driver to DragonFly, with some changes. This is useful to anyone with Intel “Dual Band Wireless AC” 3160, 7260, or 7265 units.
Noticed both in a commit message and in tonight’s BSDNow, Imre Vadasz has added Panel Self Refresh (power saving) capabilities, set with a sysctl.
Francois Tigeot has stepped i915 support in DragonFly even farther, this time bringing it to match Linux 3.17. This may be most useful for those with Broadwell and Cherryview chipsets.
Francois Tigeot has pushed in some significant updates from Rimvydas Jasinskas, updating the radeon driver to match Linux 3.17. Try it if you have the corresponding hardware.
Most of the news is about Intel video support, but Radeon direct rending improvements are coming too. ‘zrj’ have brought up drm/radeon support to match what is in Linux 3.12. Worth trying if you’ve had problems with your Radeon and audio, going by what I’ve seen people report in IRC.
If your DragonFly-running c720p (the touchscreen model) occasionally decides to go perma-bonkers, Matthew Dillon has added a method to reset it, either on reboot or by setting debug.atmel_mxt_reset=1.
Sepherosa Ziehau posted some information on a project for anyone interested: ACPI Collaborative Processor Performance Control. It’s an extension of p-state power management, and he’s already done a lot of groundwork to support that in DragonFly.
Francois Tigeot has updated i915 support to match what’s functionally in Linux 3.16. Accelerated video on Broadwell chipsets is now fully supported, plus a bunch of other changes mentioned in his commit message.
If your DragonFly machine can do it, it will now run an accelerated console by default.
Francois Tigeot has a new i915 video branch for testing, if you are running DragonFly-current. It will be especially useful for people on a Broadwell chipset.
If you’ve previously tried to install DragonFly using a USB thumb drive, and it would somehow not be found to boot from, there’s a potential fix.
Sepherosa Ziehau has been doing a lot of work with various processors states to save power on DragonFly. He’s published a summary of how well the various P-state/C-state/mwait settings work. He found that setting a lower C-state can perversely improve performance.
For those saying “but how do I set these lower power states?”:
sysctl machdep.mwait.CX.idle: AUTODEEP
sysctl machdep.cpu_idle_hlt: 1 (or higher)
Do you have a ValleyView GPU? It now works much better in DragonFly, and there’s a new accelerated rendering branch to try out, too, if you follow that link.
Here’s how you test the console frame buffer on DragonFly, even though X is the way to go.
Some time ago, I acquired a Chromebook with the help of all you kind readers. Here’s a mini-report on how DragonFly works as a desktop.
The hardware: what I have is an Acer c720 Chromebook. The C720p is the touchscreen model, and is equally well-supported by DragonFly. A larger-capacity M.2 SSD (which is relatively easy to install) is the only real need, as the installed one is only 16G. It’s easy enough to see what the laptops look like; it’s nothing fancy but it’s suitably light.
The software: There’s a wide-ranging and complete install/tweak guide for the c720 and c720p on the DragonFly site. Note that it goes down to the point of even changing the keymap for the special keys on the keyboard.
Things I don’t like:
- The mousepad needs a physical click, not a tap, which decreases accuracy.
- There’s only 2G of RAM, and not expandable. You will notice this if you tend to open a lot of tabs when web browsing.
- I’ve had mousepad trouble, but I’m the only one reporting it, so I think it’s just bad hardware luck on my part.
Things I do like:
- pkg is a godsend, making installation and upgrades almost effortless. I’ve gone binary-only so far.
- Many things Just Work – for example, the xfce4 battery plugin.
- xscreensaver works great; even the 3D modules. I don’t know why it entertains me so.
- I haven’t run the battery out to make sure, but it looks like it would last a few hours. Suspend/hibernate are not supported, but low power modes are.
- There’s a lot of multi-touch shortcuts built into the touchpad.
It’s an excellent BSD laptop, for light use, at low cost. The next step up would be into Thinkpad territory, which raises the cost or increases the age – and may not be as consistently supported.
Sascha Wildner has been removing the no-longer-needed bits of i386 support in DragonFly. One of the things going away is APM, the 32-bit power management superseded by acpiconf. If you still type ‘apm’ out of habit, it’s aliased so you won’t be surprised.
Now that DragonFly can (in most cases) offer video outside of X with KMS, not just text, more console options are possible. By default, your accelerated console will scale to 80×25, but you can now tell it how many columns you want and it’ll automatically scale to fit your resolution. Or you can turn it off.
Thanks to Sepherosa Ziehau, powerd will now start the shutdown process if you are down to 2% battery on your DragonFly laptop. It also will delay for 60 seconds if you just booted up and are desperately searching for a power cable.
Matthew Dillon’s already using a 4K monitor on DragonFly, and he’s written notes on the various performance tweaks that went with it.
Right now, if you have a USB port and a need to get networked, axe(4) is your best bet.
In addition to all the Intel video updates that have gone into DragonFly, there’s been work on radeon support from Michael Neumann. This will show in the next release, coming soon. (Just a few patches more…)
There’s a new ‘ifconsole’ option for /etc/ttys on DragonFly that may help you if your serial output device is a bit strange.
A recent commit from Matthew Dillon means users of Intel Haswell or later CPUs will see reduced power usage, if I’m reading this commit correctly.
If you want to use a scanner on DragonFly, install SANE. That is apparently all you need to do.
This may not be a huge surprise, but the Minnowboard MAX can run DragonFly just fine, modulo some dmesg complaints.
Francois Tigeot has committed his Broadwell work, which has a longer-than-I-realized list of benefits. Does anyone have a 4k screen to try?
I’m late posting about these, but they go together: Sepherosa Ziehau has added the ability to read CPU temperature through various sysctls, and the same for DIMM temperature readings.
Matthew Dillon bought a system with a Broadwell series CPU, installed DragonFly, and wrote up his experience. Read it if you plan on purchasing this hardware any time soon.
Francois Tigeot has a new update to the drm/i915 driver for testing. It matches, feature-wise, what’s in Linux 3.12. Try it if you’ve got the hardware. (and dragonfly-master)
Matthew Dillon pulled in a new USB update from FreeBSD to DragonFly. What does it change? I’m not completely sure, but he did it to get apcupsd working, so that may be a hint.
If you’ve been sitting with a Radeon-based video card and wishing you had all the nice updates i915 users are getting, today is your lucky day. Michael Neumann has brought Radeon support equivalent to Linux 3.9 into DragonFly, and he has a 3.10 branch for testing if you feel adventurous.
I admit I never thought about it much, but I’ve also never had enough RAM to matter: there’s a memtemp(4) tool that monitors temperature sensors for your system’s memory. Sepherosa Ziehau has updated it on DragonFly to support some newer processor setups.
If you have a em(4)/emx(4) card, AKA ‘Intel(R) PRO/1000’, Michael Neumann has an update for you. It’s from Intel’s 7.2.4 release of the code. This is to support the new I218 cards. Initial reports are positive.
Matthew Dillon brought in some wireless networking updates – the ath(4), iwn(4), and wpi(4) drivers are updated. There’s porting notes if you need them, too. In related news, rum(4) is also improved. The updates apparently benefited DragonFly and FreeBSD at the same time.
Francois Tigeot has updated the i915 drivers in DragonFly (remember the call for testing) to match what’s in Linux 3.10, which means you should get excellent accelerated video performance on most any recent Intel video chipset, on DragonFly.
If you have very recent alc(4) hardware, it may be supported now. If you are booting over NFS, it may be faster now. These changes are unrelated other than both being recent – NFS is improved for any chipset.
powerd now can be adjusted on DragonFly, for quicker returns to high CPU frequencies, or slower … slowdowns? It’s quickly quick or slowly slow. That’s not the best explanation, but I like rhymes. For a less stupid description, look at the man page, which now includes usage examples.
Francois Tigeot has updated the drm/i915 code again, matching Linux 3.10 for feature level… but it’s a big update. If you are
- Running DragonFly-master
- Using a i915 chipset
- (optional) On a chipset that is not Haswell or Ivy Bridge
… He could use your testing and feedback.
Matthew Dillon purchased some Haswell-based motherboards, and documented his hardware setup, for anyone who is looking to build a decent, new DragonFly system.
Thanks to Sascha Wildner porting from FreeBSD, mixer(8) now remembers state. This is something I’ve wanted for a long time.
For whatever reason, I’ve seen several people in the last week or so have mouse problems on install, and they were often solved by running moused. So, there’s your little reminder.
The short answer is ath(4) and iwn(4), via this post. There’s an update coming for the wireless infrastructure in DragonFly; Matthew Dillon and Adrian Chadd (on the FreeBSD side) are working together for improvements.
While I’m mentioning recommendations, the Silicon Image 3132 chipset is apparently excellent for eSATA drives on DragonFly.
Francois Tigeot has performed a major upgrade of DragonFly’s sound system. If you had sound problems or unsupported hardware before, this may fix them. It will require a full buildworld+buildkernel.
Romick posted some more tips on setting up various special keys on an Acer c720 Chromebook, running DragonFly of course, and Matthew Dillon also has backlight key configuration. I wish I had a spare $200 right now for one of these.
Do you remember the BSDNow story a while ago about a Tanzanian community effort using FreeBSD to build a library? They’re looking at DragonFly, too, because of the low resource requirements. From that discussion: a hardware reason for an ‘indefinite wait buffer’ error, and a note on how to most efficiently download packages for multiple machines.