Category: Please test

Lag!


Markus Pfeiffer has imported FreeBSD’s if_lagg to DragonFly.  It’s for talking LACP over multiple network ports, so that the traffic from those multiple ports can be aggregated – if what’s on the other end generally understands LACP.  (Failover mode may not count.)  Please test if you have that sort of surfeit of network ports.

Posted by     Categories: Committed Code, DragonFly, Please test     2 Comments

DragonFly 3.8 release candidate available


I’ve branched DragonFly 3.8, and tagged a release candidate.  Please try the release candidate if you can.  I have links in my post to users@/kernel@.  Don’t forget the remaining issues!  Planned release date is June 4th.

Posted by     Categories: DragonFly, Goings-on, Heads Up!, Please test     2 Comments

ral(4) updates


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.

Posted by     Categories: Device support, DragonFly, Please test     2 Comments

How do you test a balloon memory driver?


I’ve wanted more support for virtualized DragonFly systems.  Sascha Wildner put together an experimental balloon memory driver to test out, and I ran it on two virtual machines separately, one with it loaded and one without, on the same host system.  The problem is, I can’t tell what it does.  The two machine reported almost the exact same RAM usage during a buildworld.

Any VMWare/virtualization experts out there able to tell me what needs to be tested to verify this?

Posted by     Categories: DragonFly, Please test     4 Comments

In Other BSDs for 2014/03/22


I have a list of commits I’ve saved between the various BSDs of licenses getting corrected to the 2-clause BSD license; that would definitely be a good cross-BSD project to sync.

IPv6 test patch


Sepherosa Ziehau has an IPv6 patch for you to try.  What’s it do?  I think it improves performance under multiple streams of traffic, but that’s from looking at the code and totally guessing.

Posted by     Categories: DragonFly, Please test     0 Comments

New USB on by default


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.

Posted by     Categories: Device support, DragonFly, Please test     0 Comments

Do you have ACPI _PMM?


Grep /var/run/dmesg.boot for PMM, and if it turns up, Sepherosa Ziehau has a patch he’d like you to try.

Posted by     Categories: DragonFly, Please test     0 Comments

Better ACPI C-State support


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.

Posted by     Categories: Device support, DragonFly, Please test     0 Comments

ACPICA update for testing


If you want to test out the latest (20131218) update to ACPICA, Sepherosa Ziehau’s got a patch for you.  This will be good for anyone who wants to use less electricity.  (updated to reflect this doesn’t enable deeper C-states as I thought it did.)

Posted by     Categories: DragonFly, Goings-on, Please test     0 Comments

A vkernel addon task


Sepherosa Ziehau suggests this relatively easy task: adding a TSC cputimer to vkernels.   Apparently most of the framework to do this is already in place.

Posted by     Categories: DragonFly, Please test     0 Comments

Do you have a wpi(4) or iwi(4) device?


If you have an ath(4), wpi(4) or iwi(4) wireless network link, and you’re running DragonFly-master, please update.  Sepherosa Ziehau has pushed Johannes Hoffman’s wlan_serialize branch, which means bringing up wlan0 is a bit easier – and less crashy.

It needs to be tested for wpi(4) and iwi(4), however, so if you have success or failure with those devices, please say so in reply.

(new post category starting now: “Please test”)

Posted by     Categories: Device support, DragonFly, Please test     0 Comments