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.
I had to type it that way because it rhymes. Sascha Wildner has committed an IPMI driver port, tested/watchdogged by Markus Pfeiffer. What’s it do? It’s a machine management standard.
If you’re using one of those Acer C720 or C720p Chromebooks with DragonFly, remember to set:
To automatically enter the right power-saving states on the CPU. You used to have to do it manually, and now you don’t.
Sascha Wilder ported over the urio(4) driver to DragonFly. It’s for the USB-based Rio mp3 players. Does anyone have one of these and is running DragonFly? That would be a startling coincidence.
Sascha Wildner has removed the old USB system from DragonFly; you’re getting USB4BSD no matter what now, after the 4.0 release. While we’re at it, xhci is now automatically loaded in the installer, so installer USB drives attached to USB3 ports will work.
Markus Pfeiffer has made usb_pf work on DragonFly, which means it’s possible to dump USB traffic and filter it, similar to tcpdump. This can be handy when debugging a USB device, and that’s like 90% of all devices anyway.
Imre Vadaz’s recent change to dev/drm, adding kqueue support, has (from anecdotal reports in IRC) made video performance much better. It’s committed to DragonFly 4.0, so it’ll be in the next release.
I said “USB ethernet drivers should work now” yesterday, but didn’t specify what works with the new USB structure in DragonFly. Sascha has fixed that by explicitly porting aue(4), cue(4), ipheth(4) and kue(4) from FreeBSD. As his commit notes, there’s still a few more devices to go.
If you’ve got a USB Ethernet device on DragonFly, it should work. Also, some cell phones tether correctly now, when they may have had trouble before.
Sascha Wildner brought in led(4) from FreeBSD. It’s a driver for flashing LEDs, as you might have guessed. I’d like to see someone make Blinkenlights, whether BeBox-style or just generally mysterious.
The powersaving page on dragonflybsd.org has seen a bunch of updates; this should be handy even if you aren’t on battery power that often.
Markus Pfeiffer has made it possible to control your laptop’s backlight using ACPI – if you have a i915 chipset and DragonFly. xbacklight does not work, but setting hw.acpi.video.lcd0.brightness does.
Thanks to Francois Tigeot, the drm/i915 driver now supports Haswell processors, and the special FDI and DDI ports they use. I am late posting this.
If you are using the ATI Mach64 drm driver on DragonFly, Francois Tigeot would like to know. He’s done something that breaks it, but he’s making the educated guess that this more-than-10-years-old card is no longer in use.
If you remember the earlier work to support DragonFly on An Acer c720 Chromebook, it’s been repeated for the c720p. The “p” means it’s a touchscreen.
If you have a DragonFly system with an iwn wireless chipset, and you are having trouble connecting and running in the 5Ghz part of the spectrum only, here’s a tip: the -ht switch may fix it.
There’s been good progress in Francois Tigeot’s work on Haswell graphics support in DragonFly. If you have one of those newer units, you should be able to use the i915 driver with it now – as long as you keep acceleration off. (You won’t notice any difference in 2D anyway.)
If you have a i915 video chipset (which appears to be most every recent laptop), Francois Tigeot would like you to try his huge patch. It doesn’t support Haswell chips yet, though it lays some of the groundwork for it.
A frequent question people ask when trying Hammer is “How can I do software RAID to cover a disk failure?” Hammer provides for streaming one volume to another, so you can duplicate drives, but there isn’t an automatic failover mechanism as there is with a RAID setup. The first answer is usually “get hardware RAID“; my preferred solution. The remaining software solutions are vinum, ccd, and lvm for DragonFly.
If you were looking for something to do, finishing Francois Tigeot’s sound update would help a lot of people. He’s currently tied up with i915 support work. The patches need device cloning to work with devfs, and midi removal.
As mentioned before, the mrsas(4) driver works best for ‘Thunderbolt’ RAID controllers. Now, the switch has happened.
Tethering now works via the urndis(4) device, from a patch contributed by Sascha Wildner/tested by Yellow Rabbit.
(Updated for correct attribution)
Francois Tigeot has been working on making i915 video support work better; with his latest update, it’s worth trying the Intel-specific driver instead of vesa if you have both the 915 chipset and are running X.
Matthew Dillon changed powerd on DragonFly so that the system is set to max performance if powerd is killed. Now you’ll know why your fans turned on!
The mfi(4) driver has had some data corruption problems on “Thunderbird” series RAID controllers. There’s a newer driver, mrsas(4), that replaces mfi(4) for these controllers and does not have these issues, but switching may mean new drive locations and therefore some work to get booting correctly again. Sascha Wildner has an extensive writeup about what this entails, and how to switch now if you have that hardware (recommended).
DragonFly now supports running on up to 256 CPUs. 256 is the initial limit on the basic interrupt controller, and it can be extended further. It’s been tested on 255 CPUs so far, since that’s the highest number of CPUs you can bring up in qemu.
The max number of CPUs on DragonFly just went from 63 to 64. This is really just a side effect of preparation to move up that limit, but I am entertained by the single-digit bump.
Did you try to install DragonFly relatively recently and it never made it past the bootloader? Apparently there’s a bug in some BIOS when using a smaller USB drive to install. The loader checks multiple places for information, and if it checks somewhere that’s ‘farther’ than the end of the disk (i.e. 6G on a 4G USB key), the machine locks up.
Matthew Dillon and Kyle Davis spent a good number of hours figuring this out today, and Matt committed a fix. So, if you were bit by this problem, try a -LATEST image about 24 hours from now and see if it works.
Sascha Wildner has added the mrsas(4) driver, which works on a variety of LSI Thunderbolt devices – a variety of RAID cards, names for which are listed in the commit message. Note that as of right now, these devices by default get taken by the mfi(4) driver, so you need to take extra steps to get mrsas(4) used.
If you have DragonFly on a laptop, and a docking station for that laptop, it may be better supported now. (no, I don’t know exactly what acpi_dock does.)
Alexandre Perrin contributed an upgrade of wpa_supplicant and hostapd for DragonFly, bringing it from 0.6.10 to version 2.1 – a 4-year jump.
A relatively calm week – probably because there were many people at BSDCan.
Sascha Wildner has updated ral(4) with support for RT2700/2800/3090 chipsets. If you have one of these, please try it out – these are untested.
Matthew Dillon brought in Adrian Chadd’s sleep state changes for the ath(4) driver from FreeBSD to DragonFly; you may see reduced power usage if you have the appropriate hardware.
If you’re using DragonFly in qemu, virtualbox, whatever – but not VMWare – there’s a new virtio-net driver to try out.
You know what always makes me happy? When someone shows up out of the blue and says “Here; I did this cause I needed it; everyone can share.” The latest example of that is Imre Vadasz porting bwn(4), for the Broadcom BCM43xx wireless chipset over from FreeBSD to DragonFly.
In a thread about video cards on DragonFly, Francois Tigeot listed good ATI cards to try, and pointed out the VESA driver is probably your best bet right now with NVidia cards.
The acpi_thinkpad module (section? code?) has been updated. Update if you are on DragonFly 3.7, or be patient if you are on 3.6.
I’ve been away because of some home construction taking up time, but this has actually been happening for a while: plenty of USB device drivers have been getting ported in to work with the new USB4BSD stack. My links for that are not comprehensive.
In part because I asked him, Sepherosa Ziehau benchmarked 10G ix(4) with 2 ports on DragonFly. The results? Good, both for bandwidth and for CPU usage.
DragonFly has moved from the old USB stack to USB4BSD by default. That means:
- If you are already using USB4BSD, you will want to remove WANT_USB4BSD from your kernel config.
- If you have trouble, switch back to the old USB.
- There’s some drivers that are not yet converted; help with them would be appreciated.
- A full kernel/world build and ‘make upgrade’ will be needed in either case.
Sascha Wildner’s announcement email has all the gory details, including the kernel config changes to move back to the old USB setup. This is of course in master; 3.6 users are unaffected.
Sascha Wildner has updated arcmsr(4), which brings in support for the Areca ARC1214, ARC1224, ARC1264, ARC1284, and ARC1883 models, from FreeBSD. Please test if you have the appropriate hardware.
If you’re using the i915 driver for xorg, and xorg dies with a “No monitor specified for screen” error, there’s a config change to fix that, or you can just update.
If you have i915 chipset-based video on DragonFly, and you get a “Output xxx has no Monitor section” complaint in your xorg logs, look at this fix using xrandr.
Here’s two recent changes in DragonFly that may interest you if you have an AMD processor: Compute Units are now supported, thanks to Mihai Carabas, and Imre Vadasz ported over km(4), for temperature monitoring on 14h and 15h CPUs. I’m still not totally clear on what Compute Units are.
Here’s a potential DragonFly and Summer of Code project: adding support for more than 63 cores to DragonFly. Matthew Dillon has already outlined how.
It’s now possible to reach deeper power-saving C-states with DragonFly, thanks to work from Sepherosa Ziehau. It’s possible to have it auto-adjusted by setting two sysctls.
If you have an Intel-based system, and are running DragonFly master, there’s new c-states (power-saving modes) for you to try. Sepherosa Ziehau posted a note about testing and feedback.
There’s been periodic commits updating the USB4BSD support in DragonFly; I haven’t been linking to them because they are generally incremental. However, it’s good to (re?)mention just how you can build DragonFly with that new USB support.
xf86-video-intel-2.21.15 should now work on your DragonFly system. I don’t see it in dports, yet, though.
There’s a new ACPI version in DragonFly, and Sascha Wildner wants you to update your BIOS, just to be sure.
With everyone buying tablets lately, the low end of computers is getting pretty low-cost indeed. Creating single-purpose computers is possible, and I was thinking of doing that to create a Go-testing system. (Though probably not necessary for me.) It got me to thinking, though…
How low-cost a system could run DragonFly? The master-slave and low system requirements of Hammer lead to some interesting possibilities. There’s no Arduino equivalent for DragonFly because there’s no DragonFly on ARM, despite all my wishing. DragonFly has been run on Soekris systems before, and might work on a PCEngines ALIX board. Ebay, my basement, or Craigslist are options too, but not as fun. Who has suggestions?
ACPI has been updated in DragonFly by Sepherosa Ziehau, to potentially support the very low-power sleep states available with Haswell CPUs.
Note: Sepherosa clarified that the lower power states are not available – yet.
Markus Pfeiffer has added more of his work on USB4BSD to DragonFly, and a reminder: if you want to try it out, there’s just a few options to set.
I didn’t post this before, and should have: Matthew Dillon posted a summary of all the trackpad improvements he added, and how to make use of the various features.
Matthew Dillon is continuing his work on chromebook hardware, and he’s been playing with the multi-touch touchpad. There’s a number of new features based on position and the number of fingers used.
Matthew Dillon acquired one of the Acer c720 Chromebooks recently. There were changes needed for the boot process, for the keyboard, an update from FreeBSD for the ath(4) wireless (g), smbus, and trackpad… but it works now, and he detailed exactly how to get it running, and even upgrade the drive.
‘M M’ had trouble with his “Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC” on DragonFly some time ago. He was able to get it working, and he documented the somewhat convoluted procedure here.
The ixgbe(4) driver, for a number of Intel 10Gb network cards, has been updated by Sepherosa Ziehau to version 2.5.15. Note that this changes the interface name to ‘ix’ by default. This driver is actually written by Intel.
The bnx(4) and bge(4) network drivers now have APE support, thanks to Sepherosa Ziehau. What’s that mean? Other than an opportunity for punning jokes, I don’t know.
ISA device support is really gone. Well, except for keyboard and some spots where it can’t be be removed. I don’t think I’ve even seen an ISA card in some years…
If you have a bge(4) network card and it’s giving you problems every time you configure it, there’s a fix on the way.
If you’re planning to run DragonFly in KVM, remember this post from Matthew Dillon, giving the settings he uses. This will save you a bit of time.
If you have a recent laptop with an iwn(4) wireless chipset, Matthew Dillon’s recent work getting an updated version of the driver together will probably help you. It was done specifically to support a Intel Centrino Wireless-N 2230, but many more should also now work.
Predrag Punosevac asked for good fileserver examples. Several people answered, including me – the best answer is from Francois Tigeot, but there’s discussion of IPMI support in the thread.
Related: I wonder if the Backblaze Storage Pod would work for DragonFly?
Multiple transmission queues are possible for the mxge(4) driver; I’m mentioning it because Sepherosa Ziehau’s post about this describes the exact tunables to configure this.
Chris Turner was curious about clock skew when running under a VM, and Sepherosa Ziehau very kindly explained the different types of internal clock for DragonFly, and how to control them – a topic I’ve never understood deeply.
I stole Sepherosa Ziehau’s email subject for the title of this post, because that’s exactly what has happened. Gigabit networking cards under DragonFly will perform very well under extreme load – all of them.
The Radeon KMS driver from FreeBSD has been imported to DragonFly by Francois Tigeot. It still has problems with ttm, but don’t let that stop you from taking advantage of it.
When Sepherosa Ziehau decides to improve something, he goes all out. For example, he recently improved the mxge(4) driver for Myricom 10G network cards – which is for relatively older hardware – and improved performance by 150Mbps.