The GA-Z170N-Gaming 5 motherboard was purchased during Amazon Prime Day at a steep discount and had several months of use in another case stress testing before I put it into it’s home in the Dan-Cases A4-SFX case.
32 GB of RAM was selected to provide plenty of headroom when using creative applications like Premiere and Photoshop.
This build originally stated with a GTX980 but evolved into the GTX1080 because of the long wait for the case’s Kickstarter campaign.
The 950 Pro NVMe SSD was purchased during a coupon campaign from jet.com – I originally wanted to keep the machine fully SSD but the price of a 2TB NVMe SSD was cost-prohibitive.
Due to the low profile requirements to jam a HSF into the case, I selected the Cryorig C7 cooler. However, there was excessive fan noise from this cooler – particularly when overclocked
The processor was then delidded with a Rockit Cool delidding tool and the thermal compound was replaced with Coollaboratory’s Liquid Pro interface material. This was able to provide over a 30 degree drop in temperatures and allowed me to keep the fan speed very low to keep noise down.
This was more something that was bothering me than anything absolutely necessary, but I wanted to get a properly signed certificate installed on my remote Windows 7 machine that’s hosted in a datacenter as a VM. Every time I connected to it, the RDP client would display an error that the RDP server wasn’t providing a proper security certificate:
More annoying than anything, really. However, since I do have several certificates that are signed this was a problem I could remedy.
Enabling SLI on non-nVidia approved platforms has less of a pain-in-the-ass since nVidia allowed SLI on Intel chipsets, but enabling SLI on a workstation designed to take Quadro cards so it will work with Geforce cards is a little more of a pain in the ass.
In my configuration, I’m trying to enable SLI on an older Dell Precision 690 workstation with an SLI riser card. Normally, nVidia and Dell only allow with very expensive Quadro video cards in this configuration. However, I got myself a pair of GTX260 Core 216 video cards for very cheap and so I wanted to do a little experimenting to get this to work.
Plenty of modifications exist to enable SLI on non-supported configurations, and the solution I chose was DifferentSLI. However, this software patches the nVidia kernel-mode driver and then signs it with a self-signed certificate that obviously isn’t chained to Microsoft’s CA. This means for Windows to load, it has to be put into Test Mode to allow the kernel to accept a self-signed certificate and load the driver.
Since I already had Class 2 validation with StartCom, I embarked on a poorly-documented journey to sign the modified driver file with my Code Signing Certificate from StartSSL and load it, so I wouldn’t have to put Windows into that ever-annoying Test Mode.
Qualys SSL Labs has some great tools to check your server’s SSL/TLS installation to make sure they don’t fall victim to common vulnerabilities or exploits that seem to be discovered every month. If you’re running an Apache2 installation, securing your server against most SSL/TLS vulnerabilities is as easy as enabling the headers Apache module, and then a few lines to your SSL configuration.
First, enable the headers module so Apache2 can modify headers sent to the client:
pengc99@alpha:~$ sudo a2enmod headers
Enabling module headers.
To activate the new configuration, you need to run:
service apache2 restart
Then add the following lines to your SSL configuration:
# Make the server secure
SSLProtocol all -SSLv2 -SSLv3
Android Lollipop 5.1.1 was recently released for the Nexus 5 as a maintenance update to the latest OTA update of 5.1.0 to fix numerous issues, such as an intermittent non-response camera and excessive memory usage leading to crashing applications.
If you have a rooted phone or a phone with a custom recovery, you may find that the OTA update doesn’t work on your phone – this is because the update process now checksums and verifies partitions such as recovery before performing the update. If the partitions don’t match the expected stock ROM, the update process will terminate. Having a rooted phone (with the su binaries), modified radio, modified recovery, or custom ROM may all contribute to an update failing and bombing out.
Bought another USB flash drive the other day, and suddenly it clicked in my head that I purchased a storage device that was $40, reads and write at well over 100mbyte/sec, and holds 128gbytes, in the palm of my hand.
Benchmarked my old and new drive. Technology has come a long way since 1.44mbyte floppy disks.
While configuring a few servers I noticed some strange behavior with mode 4 channel bonding (LACP / 802.3ad) and DHCP. You might get the following error message, no matter what you do:
Determining IP information for bond0… failed; no link present. Check cable?
The problem appears to exist in how the interface responds to link status on LACP / 802.3ad ports. The computer is trying to send DHCP packets when the interface itself isn’t ready, causing Linux to think the interface isn’t configured or has no network cable plugged in. This appears to only happen when you use mode 4 channel bonding. Mode 6 works fine. The (band-aid) solution appears to be to trick the system into thinking the interface is already configured. This enables Linux to continue sending DHCP packets until the interface is configured and negotiated successfully with 802.3ad, at which point everything works as planned. Simply insert this at the end of /etc/sysconfig/network-scripts/ifcfg-bond0 – I should note this particular example is for CentOS and RHEL so I haven’t confirmed if this workaround works for Debian based distributions.