Craig Thrall

Windows 10 Power Management and Connected Standby

Dec. 14, 2016, 7:02 p.m.

We've been piloting the Microsoft Surface Book, which runs Windows 10. By default, these devices are running Microsoft's Connected Standby feature for power management. Connected Standby allows devices to remain running at a reduced power level while sleeping and still process data. The tradeoff is you lose advanced power management features, such as the ability to configure the wifi adapter to always maximize power. I also believe I've found an issue with either the way Connected Standby manages wifi adapter power, or the Cisco AnyConnect VPN client's ability to handle the wifi adapter going up and down. We ran into an issue where multiple versions where the Cisco VPN client will think it is connected, but the device will not be able to connect to any internal or external computers, including the VPN gateway. We resolved this issue by making the following changes: * Disabled "Connected Standby" by setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power to 0 in the registry, and rebooting the Surface device. * Open "Device Manager" and browse to the Marvell wifi adapter properties. You'll now find an additional tab named "Power Management." * Uncheck "Allow the computer to turn off this device to save power."


Feb. 29, 2016, 5:49 p.m.

To get usbip to run on Ubuntu 14.04, use the script found here:

bokeh, matplotlib, and twinx

Feb. 9, 2016, 11:53 p.m.

The best way to have multiple Y ranges on a plot, and use Bokeh, is to not use matplotlib. The library that Bokeh uses does not translate the multiple ranges correctly. I found others with this issue. What worked for me is to skip matplotlib (I was lucky, this is new code), and "extra_y_ranges" to add additional Y ranges to my plot.

Computer Swap with Ubuntu

Oct. 26, 2015, 5:16 p.m.

If you swap a hard drive into a spare computer with identical hardware specs, remember the MAC address on your ethernet ports will be different. The OS will see them as new and rename them, and they will not match your configured device in /etc/network/interfaces. Before you swap the drive, delete any lines that exist in /etc/udev/rules.d/70-persistent-net.rules. The OS will add lines for the ethernet devices in the new computer. If you've already swapped the drive in, just delete the lines with the old device names, and rename the new renamed devices with the old device names.