Category Archives: Tools of the Trade

Tools of the Trade

Booting from a Samba share in old Supermicro IPMI

I picked up some older Supermicro machines from eBay (GREAT way to get some real server hardware, btw), but they have a VERY old IPMI firmware and no way to upgrade to a more modern version.

They can’t do standard virtual media — you have to specify a SMB share with an ISO on it to mount. Once you do that, you have to make it bootable in the BIOS and move it up the boot order.

I wasted about an hour trying to figure out why I couldn’t enable the device “PepperC Virtual Disc” in the boot order — the answer is, you have to use the ‘x’ key to remove unused devices from the 8 available boot slots, then you can select the PepperC device and use the ‘x’ key to enable it, and then you can move it up/down the boot order with the +/- keys.

Hopefully this saves someone else some grief, I was losing my mind trying to figure out the problem.

Resetting the web server on the Morningstar Tri-Star MPPT 60 Solar Charge Controller

I have a solar-powered communications tower site for my WISP running on the MPPT60 as listed in the title. That controller is way more charge controller than I needed for the site, and pricey too, but I bought that one because it has a built-in network-connected monitoring and management system.

Usually I just check the web interface to make sure everything is good. It can be a little flaky and today it stopped responding. I didn’t want to have to cut power to the device, maybe possible without taking down my tower equipment’s power for a few minutes, maybe not, and wanted to make sure it was still functioning correctly.

The solution for me, at least this time, was to connect to the device in MS View (it was still pinging), and right-click on the controller, then select ‘Properties’, then the ‘Control’ tab, and then select ‘Reset Communications Server’ and click ‘Force Coil On’.

A few minutes later I could access the web status page again. I hope this helps someone else because searching for this information turned up next to nothing.

Installing Debian Wheezy (7.0) Linux on the Chromebook Pixel

UPDATE 2013-04-29

I have created a github for this here. If you have patches please submit pull requests!

UPDATE: I continue to update the kernel as more fixes make it into git. You can check all of the Pixel-related files I’m posting in this Drive folder.

UPDATE 2013-03-27: New kernel with fix for the audio pops, see my G+ post from today.

The Chromebook Pixel is a very nice (if expensive) piece of hardware, designed to run Chrome OS, which is a variant of Linux. Since being noted as favored by Linus Torvalds, inventor and lead maintainer of Linux, support for the various Pixel hardware components has rapidly been added to the kernel git repository.

Not everything is working great just yet, but all of the essential features are working. Here’s a walkthrough that I hope will be sufficient, based almost entirely on other people’s work and howtos. I’ll link to those where I can. Several Google software engineers have been helpful on Google+, and a bunch of work has been done by Linux kernel maintainers.

This was my starting point: DaveM’s howto in his Linux git repo

  1. Get a chromebook pixel
  2. Enable developer mode
  3. Download the Debian Wheezy netinstall image (yes, it supports the wifi in the installer) (here)
  4. Boot from the installer (Ctrl-L at boot screen, escape when it says to press escape to choose a boot device, choose your USB drive with the Debian installer)
  5. Install as normal to the internal SSD. I used LVM/encryption and it worked just fine. When you reboot, pull the USB drive and it should boot from the internal SSD.
  6. Once booted, the trackpad will not work. A USB mouse will work just great. Download and install my build of the 3.9-rc1 kernel (.deb files and config, full source) built from Linus’ merging of patches and configured with help from Benson Leung
  7. To your /etc/modules add:
    ath9k
    atmel_mxt_ts
    chromeos_laptop
    tpm_tis force=1 interrupts=0
    

    Those are the modules for the wifi, the touchpad (both the atmel and chromeos_laptop), and the tpm chip, that to keep it from rebooting when you try to suspend (thanks Duncan Laurie!).

  8. This is no longer necessary with the updated downloads. To your /etc/rc.local, above exit 0, add echo TSCR > /proc/acpi/wakeup. This is a hack to keep it from waking right up after going to sleep (thanks, Benson Leung!)
  9. This appears not to be necessary, actually Create a file called 01i8042 in /etc/pm/sleep.d to properly sleep and wake the keyboard on suspend. It should have this as its contents.
    #!/bin/sh
    
    ###############################################################################
    # Pm-utils script to unbind i8042 on hibernate/suspend and
    # bind it on thaw/resume.
    #
    # Copyright: Copyright (c) 2009 Nicolay Doytchev
    # License:   GPL-3
    ###############################################################################
    
    ###############################################################################
    # INSTALL:
    #   1. Copy this script to /etc/pm/sleep.d/
    #   2. Make it executable:
    #       sudo chmod +x /etc/pm/sleep.d/01i8042
    #
    # UNINSTALL:
    #   1. Delete the script from /etc/pm/sleep.d/
    #       sudo rm /etc/pm/sleep.d/01i8042
    ###############################################################################
    
    case "$1" in
        hibernate|suspend)
            echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind
        ;;
        thaw|resume)
            echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind
        ;;
    esac
    

    Make it executable. Found this here

  10. You may need to install the firmware-atheros package for the bluetooth to work, which may require adding non-free to the end of the deb lines in /etc/apt/sources.list

I think that’s it, but it’s always hard to correctly recreate these things after the fact without redoing it (and I’ve spent enough time on this already). Let me know if you have any problems or improvements, or go comment on Linus’ G+ post about it.

I want to add a special thank-you to Linus Torvalds for posting about his updates on Google+.

EDIT: More stuff
First, if you hate tap-to-click like me, here’s an xorg.conf with the correct dpi setup and multi-finger click.

Here is a folder containing all the relevant files and info (plus my other configs I decide to upload) discussed in this post and the comments.

Also, FYI the keyboard backlight does not come on after suspend right now.

EDIT 2013-03-11 20:33 MDT: By the way, if you run i3 or some other nerdy window manager like me, and you forgot how to make Debian sleep when the lid is closed, you just need to uncomment the appropriate line in /etc/default/acpi-support.

Finally I can use my ScanSnap S1500 in Linux!

I have been using Fujitsu ScanSnap double-sided auto-feeding scanner for years. I started with a Mac model (S300M I think? no Windows drivers?) and then moved to a Windows model, the S1500.

For the last couple of years I’ve been running a Windows virtual machine in VMWare Workstation primarily so that I can use my scanner and the included OCR features (turn scans into text).

Recently, I’ve been having a lot of trouble with VMWare Workstation, and I run libvirt/qemu-kvm on my web server, so I decided to try it on my workstation as well. It works pretty well for Windows 7, not a fast as VMWare when it worked properly, but the scanner will not function correctly using it.

Last time I looked into using the S1500 on Linux I found almost nothing. I could scan stuff but it wasn’t very useful for a paperless office workflow, the whole reason I have such a scanner.

I am happy to say that, on Debian Wheezy/Sid, gscan2pdf with the libsane-perl backend and tesseract for OCR seem to work nicely. Some caveats:

  • I downloaded the newest version of gscan2pdf and installed it. At the moment that is 1.0.6.
  • The ‘Page Options’ tab of the ‘Scan Document’ window only works properly when I choose options that don’t make much sense. I selected ‘ADF Duplex’ in the ‘Standard’ tab, and then in the ‘Source document’ section of the ‘Page Options’ tab, I have selected ‘Single-sided’ and ‘Side to scan: Facing’. Otherwise, the page numbers come out strange. I do still get double-sided scanning, though.

I couldn’t find a lot about this on the web, so I hope it helps someone else in my position. Happy scanning!

EDIT 2012-10-28 Strangely enough, I was able to get the scanner working just fine in my Windows VM using Spice USB redirection. It’s good to have the fallback, but I’ll try to stick with Linux, it’s much more convenient and removes a dependency.

Extracting certain lines from a file using Perl

As often happens to me when processing data, I needed to extract a specific set of lines from many files. If the files are small or few, or the list of lines is short, this can be done manually. If the list of lines or number of files are large, well, that’s what computers are for.

As Google will reveal, there are a number of ways to hack this up with bash, grep, sed, and other command-line tools, but none (that I know of) are really designed for this.

Here’s my script. It’s designed around some heart model stuff, and we use base-0 (first line is line 0, second line is line 1, etc), while many other tasks require base-1 (first line is line 1, second line is line 2, etc), and I’m sure there are other numbering schemes out there. Therefore, I included an optional base parameter. Without that it assumes base 1.

Note: I have no idea if this works on non-UNIX-like systems (i.e. Windows).

Use it like:

extract_lines.pl <file with list of lines> <file from which to extract lines> [optional base number]

And now, the code:

#!/usr/bin/env perl

use strict;

unless(@ARGV == 2 || @ARGV == 3){
    die "Usage: extract_lines.pl <line number file> <source file> [base]\n";
}

open(NUMBERS, "<$ARGV[0]") || die "Failed to open line number file $ARGV[0] for read: $!\n";
chomp(my @numbers = <NUMBERS>);
close(NUMBERS);

open(SOURCE, "<$ARGV[1]") || die "Failed to open source file $ARGV[1] for read: $!\n";
chomp(my @source = <SOURCE>);
close(SOURCE);

my $base = 1;

if(@ARGV == 3){
    $base = $ARGV[2];
}

# sort inputs just in case
my @sorted = sort { $a <=> $b } @numbers;

# save mem
undef @numbers;

my $nextline;

$nextline = shift(@sorted);
my $currline = $base;

foreach my $line (@source){
    if($nextline == $currline){
        print $line . "\n";
        if(@sorted > 0){
            $nextline = shift(@sorted);
        }
    }
    $currline++;
}

Bug reports welcome, just leave a comment.