Getting FreeBSD 11 working on my Asus Zenbook UX31A

Sigh… not sure why this was so painful. After years away, I thought it would be nice to re-visit FreeBSD on my dedicated malware analysis laptop. While I had used FreeBSD for over a decade on personal server systems, I’ve never really used it as a desktop system, but I’m tired of the Linux disto situation. Besides, I’ve always been more comfortable on BSD-based systems.

But let’s face it, some Linux distros are much better at working as desktop systems. Here’s my (on-going) work to get FreeBSD 11.0RC2 going on my spare ultrabook.

During install make sure to configure the internal drive as GPT partition table and be sure the EFI partition is listed first.

After the install, enter the firmware to create “a new boot option” and indicate the location of the proper UEFI boot file.

Add boot option: Internal SSD
Select Filesystem: [accept default]
Path for boot option: \efi\boot\bootx64.efi

Form here, I’m basically just going to follow the FreeBSD desktop install instructions from CoolTrainer:

Next swap CapsLock and Ctrl keys, because that’s just better:

echo 'keymap="us.ctrl" >> /etc/rc.conf

Then go into the System->Preferences->Hardware->Keyboard->Layouts and select “swap ctrl and caps lock”.


Some additional things I had to do:

  • installed emacs (text editor)
  • installed redshift (like flux)
  • installed slim (login manager)
  • installed cairo-dock (like Mac OS X dock)
  • installed cairn-dock-plugins
  • installed launch (like Alfred/Quicksilver)
  • installed compton (compositing window manager)
  • installed Chromium

Things I still need to work out:

  • Removable Media
  • SD card
  • Touchpad
  • WiFi panel for Gnome
  • Gnome 2/Mate sound

QNAP 451+: Hardware Accelerated Transcoding

I’m having problems with Plex using too much CPU to transcode files. Actually, I’m not sure why it’s transcoding to an AppleTV 4, it should be able to Direct Stream .mkv files. I’m trying to go ahead and use the QNAP hardware accelerated transcoding engine.

First problem, all transcode requests are returning, “Failed: File read/ write error“. No logs for the failure, so off to ssh I go. The transcode command lives in: /mnt/ext/opt/medialibrary/bin. There are three commands we care about:

  • mfytranscodesvr
  • mytranscodecmd
  • myvatranscode

Running the first seems to indicate it already running, and the second seems to kick-off another failing transcode. The third command is interesting because it appears to the be accelerated version. It’s actually a symbolic link to: /mnt/ext/opt/QDMS/bin/myvatranscode.

A quick check shows that the entire /mnt/ext/opt/QDMS directory is missing. This is apparently because I turned off DLNA streaming. By re-activating the “Media Streaming Add-on”, the accelerated streaming appears to be working now.

We’ll have to see if Plex is smart enough to pick-up the transcoded version when available.

QNAP 451+: SABnzbd/Sickbeard setup

  1. Install the Python 2.7 from the QNAP app center.
  2. Install the following qpkg from the QNAP community app repository:
  3. Configure SABnzbd with Usenet servers, and SickBeard with shows to search.
  4. Make sure that SABnzbd is configured to post-process by using the script.This will also require configuring the values in: /share/Download/nzbToMedia/autoProcessMedia.cfg.

    • SickBeard integration had to be activated
    • The port had to be set to 7071 (based the SickBeard.qpkg config).
  5. If necessary, patch the first line of: /share/Download/ to use:
    #!/usr/bin/python2.7 -OO
  6. If necessary, patch: /share/CACHEDEV1_DATA/.qpkg/SABnzbdplus/ to fix a bug causing SSL timeouts while  fetching nzb files from indexers using HTTPS (as per this forum post):
    opt_out_of_certificate_verification = True
    if opt_out_of_certificate_verification:
            import ssl
            ssl._create_default_https_context = ssl._create_unverified_context
  7. If necessary, patch: /share/CACHEDEV1_DATA/.qpkg/SickBeard/SickBeard/sickbeard/ errors related to searching for nab files (from this forum post):On line 227, remove the str() from around the e.code so it reads like:
    logger.log(u"HTTP error " + e.code + " while loading URL " + url, logger.WARNING)

    Then, do similar down on line 234 so it reads like:

    logger.log(u"URL error " + e.reason + " while loading URL " + url, logger.WARNING)

3D Printer: Rigidbot

We purchased a Rigidbot during their Kickstarter campaign last year, and it arrived in the middle of last week.  It took 8.5 months longer than projected, but frankly by Kickstarter standards that’s not bad.

Since it was so close to the end of the kids’ school year, I saved it as a project for the weekend.  I spent Father’s Day assembling our new 3D printer with the 13 year old.  I think we both had quite a bit of fun!   We finished basic assembly late last night — so no test print yet.  This evening, we plan on tidying up the cabling, performing calibration, and running our first test print.  Pictures and comments to follow.

Seeking System 0.97

Lately, I have been dabbling with retro-computing (actually as part of co-adivsing a student group).  One of the old machines in my collection is an original Macintosh from 1984. For the sake of authenticity, I have been looking for the version of system software that shipped on release day – Jan 24, 1984.

That early in the Macintosh era, there were no official version numbers on the system disks, but the System and Finder files each had their own version number.  Various accounts indicate that I’m looking for System 0.97/Finder 1.0.  After a lot of searching I’ve turned up several candidate disk images, but each seems to have been modified over time.  Here’s one very common version:

sys097There are several problems with this version.  Most obviously, the version of the System font (Chicago-12) used here is quite different from the version seen in other system versions.  This includes the versions seen in pre-release publicity photos.  All of those other versions  used a more familiar looking variant.  Furthermore, the version of Chicago-10 included does match the more traditional version.  Other, more obvious problems exist. The SysVersion program is actually from 1986, and contemporary accounts indicate that Font Mover was included on the second disk, not the main system disk.  I believe this disk was created at a later date and does not represent what shipped with the first Macs.

The obvious thing to do it to go to the source.  Unfortunately, Apple no longer makes those early versions of the System software available on their website.  But various developer CDs have included System Software over the years.  One of the earliest was, Phil and Dave’s Excellent CD.

P&D filesJackpot! This developer disk lists versions of the System Software all the way back to v0.1.  Sadly, booting up the 0.1 System Tools image reveals that it’s really System 1.1/Finder 1.1g.

Screen Shot 2014-06-05 at 11.33.15 AMIn fact, looking at each version in turn, we get:

File Actual Version
0.1 System Tools System 1.1/Finder 1.1g
0.3 System Tools System 2.0/Finder 4.1
0.5 System Disk System 2.0/Finder 4.1
0.7 System Tools System 3.0/Finder 5.1 (800k image)
1.0 System Tools 512 & 128 System 3.2/Finder 5.3

I didn’t bother checking the rest of the disk images, since they were clearly >400K disks.  For the record, I’ve also checked the Apple Legacy Software CD and the September 1994 Service Software Restoration CD with similar results.

The hunt for a valid copy of System 0.97 continues…