I tried to build this SDK on more variants of linux than I care to admit. It only works successfully out of the box on Ubuntu. Specifically, Ubuntu 12.04.5.  I compiled this for use with my AR Drone 2, but I don’t see why it couldn’t be used with the AR Drone as well. There’s nothing here that makes the SDK specific to either model.

  1. Download Ubuntu 12.04.5 32bit. It probably works with 64bit (although I didn’t test it), if you really must use 64bit.
  2. Either install Ubuntu 12.04.5 alongside (dual boot) with another operating system, or in a virtual machine. I installed it in a VMware Fusion virtual machine on macOS. The Ubuntu operating system is agnostic, so it doesn’t really matter how you choose to virtualise it, if you do.
    1. Don’t install Ubuntu 12.04.5 updates during the installation process (leave the option unticked).
    2. Don’t install updates or upgrade Ubuntu to the next release when asked after the first login.
  3. Download the SDK (or copy it from somewhere to the Desktop).
  4. Open a terminal and change to your Desktop directory.
    1. # cd Desktop
  5. Unzip the SDK.
    1. # unzip ARDrone_SDK_2_0_1.zip
  6. Change to the ARDrone_SDK_2_0_1 directory
    1. # cd ARDrone_SDL_2_0_1 directory
  7. Run the following command (using sudo) to compile and install dependencies.
    1. # sudo ARDroneLib/Soft/Build/check_dependencencies.sh
      1. You’ll be asked to confirm installation of some packages, be sure to say Yes (y).
  8. Run the following command (using sudo) to compile the linux binaries.
    1. # cd Examples\Linux
    2. # sudo make
      1. Wait for the SDK binaries to be compiled
  9. The binaries are built in /home/<username>/Desktop/ARDrone_SDL_2_0_1/Examples/Linux/Build/Release/. Move them to you desktop and make them accessible as follows.
    1. # sudo mv /home/<username>/Desktop/ARDrone_SDL_2_0_1/Examples/Linux/Build/Release/ /home/<username>/Desktop/ARDroneApps
    2. # sudo chown -R <username>:<username> /home/<username>/Desktop/ARDroneApps
  10. Run the apps! You’ll need to be connected to your AR Drone 2 WiFi network first of course. Make sure you don’t have the Free Flight app open on any smart phones or tablets at the same time, as this will interfere with communications between your computer and your drone.
    1. # cd /home/<username>/Desktop/ARDroneApps
    2. # ./ardrone_navigation
    3. # ./linux_sdk_demo
    4. # ./linux_video_demo
    5. # ./sym_ardrone_testing_tool

Over the past three weeks, I have spent considerable time trying to get Apple’s latest Mac OS X offering (Mavericks) working on non-apple hardware. Mainly because Apple had released it for free (are you coming to the show, Microsoft?) and my old Snow Leopard OS X computer was starting to get… well, long in the tooth 😉

As I said, three weeks. Obviously I wasn’t working on it for three weeks night and day, but I did spend a fair amount of time to get to the configuration I am using to write this very post. Not much of this post actually pertains to the fact that I installed Mac OS X Mavericks on a Toshiba Laptop, it’s more that I couldn’t find many posts that mentioned any type of PC or laptop, so I figured there had to be others like me out there, possibly with a Toshiba laptop, trying to install Mac OS X Mavericks on it.

Warning!

The following is my journey. It comes with absolutely no warranty of any kind and I do not accept any responsibility at all, regardless of you following my instructions to the letter or not, if this results negatively for you in some way. Back up all data and proceed at your own risk.

Installation Media

To get the installation media from Apple, you need an existing Mac with at least Mac OS X 10.6 and AppStore installed. My 10.3 SL, was not going to cut it. Why couldn’t I update? My 10.3 SL machine, has an Intel atom processor that is no longer supported in newer releases of Mac OS X. I tried anyway, it failed. Thankfully, I was able to restore from a Time Machine backup. Use Time Machine! It’s awesome!

I ended up a little off course, but to get Apple OS X Mavericks, I downloaded a VMWare Virtual Machine image with Mac OS X Mavericks already installed. Your adventure with VMWare Workstation and OSX Mavericks, starts here: http://www.souldevteam.net/blog/2013/10/06/os-x-mavericks-10-9-retail-vmware-image-release-notes-links/. There is a video on the blog post, Watch It And Pay Attention!

You will also need VMWare Workstation. The 30 day trial is completely unrestricted and works perfectly fine. I am running VMWare Workstation 10.0.1 at the time of writing. You’ll see in the video (and downloaded files) that earlier versions of VMWare Workstation are also supported. Your adventure with VMWare Workstation, starts here: https://my.vmware.com/web/vmware/info/slug/desktop_end_user_computing/vmware_workstation/10_0.

Note: You must use VMWare Workstation for Windows, on Windows. VMware Workstation will need to be patched (unlocked), to be able to run Mac OS X Mavericks. The patch that accompanies the VMWare Workstation image is designed for Windows, not for Linux. Sorry, Linux users. If you’re clever enough, you might be able to get it to work on Linux. I haven’t look into this at all. Let me know if you are successful.

Once you have VMWare Workstation installed with your Mac OS X Mavericks virtual machine running, use the AppStore to download Mac OS X Mavericks 10.9, for free!

Of course, if  you have access to an actual Mac or a Hackintosh with Mac OS X 10.6 or higher, you are home free. Install the AppStore if you haven’t done so already and download Mac OS X Mavericks, for free!

Note: To download Mac OS X Mavericks, you will need to be signed into an Apple account. Just an FYI. It’s no big deal. An account is free and you don’t need to have a credit card or any payment options set up to download Mac OS X Mavericks. It’s free, really!

Once you have Mac OS X Mavericks downloaded, don’t install it. It looks like an App, and may try to install itself (even though you may be on Mac OS X Mavericks already). If it does, just cancel the install.

Read More →

A little while ago (and again more recently) I updated my kernel to 3.7.3-101 and was stumped as to why VMware Workstation was unable to find the matching kernel headers, despite confirming they were indeed correct and installed. After lots of searching and some reading, I found the following command:

ln -s /usr/src/kernels/3.7.3-101.fc17.x86_64/include/generated/uapi/linux/version.h /usr/src/kernels/3.7.3-101.fc17.x86_64/include/linux/version.h

This basically creates a symbolic link in the /usr/src/kernels/<version>/include/linux/ directory for the version.h file that the VMware Workstation compiler is looking for. After running this command, I started VMware Workstation again and was greeted by the GUI compiling the necessary modules to run VMware Workstation.

I suspect the requirement for this command has something to do with re-arrangement of kernel source files in recent releases. It seems likely that VMware will update the compiler in new releases of their Workstation product.

Here’s a more recent upgrade, using the same step:

ln -s /usr/src/kernels/3.7.9-101.fc17.x86_64/include/generated/uapi/linux/version.h /usr/src/kernels/3.7.9-101.fc17.x86_64/include/linux/version.h

So long as you have the matching kernel headers installed, the above command should work for you just fine.

Note: On the second time around, I had troubles when running VMware Workstation as a normal user (just the compiling step, afterwards it was fine). For some reason there was an issue elevating the user to root (this happened to me on Fedora 17 x86_64) to complete the compiler process. To work around this, I simply opened a console/terminal, became root (sudo, or su – , whatever suits you) and then typed just: vmware – The compiler GUI appeared and completed, followed by VMware Workstation starting. I then closed ‘that’ VMware Workstation and started it my usual way (KDE menu for me) and it worked just fine.

Update (2013-03-25): VMware has recently released VMware Workstation 9.0.2 (2013-03-07) which has the above issue resolved. I am currently running VMware Workstation 9.0.2 build-1031769 on Fedora 17 (Kernel 3.8.3-103) and I did not have to carry out any additional steps to compile the kernel modules.

Update 2 (2013-07-10): I updated my kernel today, all the way up to 3.9.6-200-fc18 – Afterwards I was unable to compile the module again. After much searching, trouble-shooting and attempts to roll back to previous kernels, I checked something a little more fundamental; was gcc installed? Nope! It wasn’t! A quick browse through my yum logs showed it removed as a dependency when I removed something else earlier in the year. After installing gcc again, the kernel module compiled normally again 😉

Update 3 (2013-08-30): I updated my kernel again today, just a standard yum update with all the usual packages. My kernel ended up on 3.10.9-200.fc18.x86_64 (I haven’t upgraded to Fedora 19 yet). This time, the vmware kernel modules kept failing to compile (different to the previous issues). I did a quick google search for “vmware kernel 3.10.9-100” and found this article. If you follow the instructions, verbatim, the issue is solved straight away. For reference, I’ve copied the main content of the article below. Kudos to the author at http://guide.ecsmy.com/ for getting this one out there!

# tar xf /usr/lib/vmware/modules/source/vmnet.tar
# cd vmnet-only
# wget  http://communities.vmware.com/servlet/JiveServlet/download/2239207-108590/procfs.patch
# patch -p1 < procfs.patch
# cd ..
# tar -cvf vmnet.tar vmnet-only/
# cp vmnet.tar /usr/lib/vmware/modules/source/

This will patch the procfs interface.

Secondly download the vmnet patch from http://mysticalzero.blogspot.com/2013/07/vmblock-patch-for-linux-310-vmware.html. The link of the patch is here.

Or you can use the following command:

# tar xf /usr/lib/vmware/modules/source/vmblock.tar
# cd vmblock-only
# wget  https://sites.google.com/site/mysticalzerotmp/vmblock.3.10.patch
# patch -p1 < vmblock.3.10.patch
# cd ..
# tar -cvf vmblock.tar vmblock-only/
# cp vmblock.tar /usr/lib/vmware/modules/source/

Then, issue this command to compile and install the vmware player module

# sudo vmware-modconfig –console –install-all

I know it says ‘vmware player’ but trust me, it works for VMware Workstation just the same.

Update 4 (2013-10-20): I updated my kernel again today, just a standard yum update with all the usual packages. My kernel ended up on 3.11.4-101.fc18.x86_64 (I haven’t upgraded to Fedora 19 yet). This time, the vmware kernel vmblock module kept failing to compile (similar but different to the previous issue). I did a quick google search for “vmware kernel 3.11” and found this article. If you follow the instructions, verbatim, the issue is solved straight away. For reference, I’ve copied the main content of the article below. Kudos to the author (dibl) at siduction.org for getting this one out there!

The VMware module source needs to be patched to build on kernel 3.11. If you have already patched for 3.10, then only a single patch is needed. Here is the procedure:

Download the “vmblock.3.11.patch” from here.

In a root terminal, give these commands:

# cd /usr/lib/vmware/modules/source
# tar xvf vmblock.tar
# cd vmblock-only
# patch -p1 < /path/to/vmblock-3.11.patch
# cd ..
# tar cvf vmblock.tar vmblock-only/
# vmware-modconfig –console –install-all

You should see an error-free completion of the build.

Update 5 (2013-12-14): While still on Fedora 18 (I know, Fedora 19 is well and truly out, and Fedora 20 (celebrating 10 years of Fedora Linux!) is less than three weeks away from release!), I just upgraded to Kernel 3.11.10-100. I also upgrade from VMware Workstation 9.0.2 to VMware Workstation 10.0.1 – After a reboot, no additional work required. VMware Workstation 10.0.1 simply worked ‘straight out of the box’ so to speak 😉

I recently had a requirement to remove vmware tools manually from a windows 2003 server. This is what I had to do.

  • Remove any keys with a DisplayName of VMware Tools anywhere in the following keys:
    • HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionuninstall
    • HKEY_LOCAL_MACHINESoftwareClassesInstallerProducts

 

  • Remove the keys with a ProductName of VMware Tools in the following keys HKEY_CLASSES_ROOTInstallerProducts
  • Delete the branch named VMware Tools in HKEY_LOCAL_MACHINESoftwareVMware
  • Delete the "VMware Tools" directory within in the Vmware directory under Program Files
  • Restart the server.

Props to WarOnErrors.