nicholes: The "load the driver first" basically means just that: Make sure you've got the normal driver unloaded, and lxp's driver loaded. If you HAVE lxp's driver, there's a basic load/unload script that can be easily launched from x-terminal that comes with all the modules/driver. (It's even in the same folder when you download and unpackage it.)

Hawaii: I ended up figuring out how to compile within scratchbox (couldn't figure out how to compile from outside scratchbox using its tools, but whatever, not a big deal), and eventually figured out where scratchbox was chrooted to, so I figured that part out as well. As a result, I was able to compile all the binaries from the SVN code.

The funny part? I have yet to figure out how to get those binaries out of the Debian VM I have set up. I tried SSH'ing out to my N900, but either my campus network or the host Windows Vista OS is causing problems (need to dig through all the firewall settings/logs, etc.), because it never gets a response. I CAN SSH to my Vista machine from either computer, but FreeSSHd, which is what I'm using as my Windows SSH server, can't do scp apparently.

After the toolchain-figuring-out phase of yesterday though, I know this is just a matter of time. I can still probably use my Windows as the client, SSH into the VM. *Shrug* Just thought the fact that I got all of that done only to be stumped on how to get the binaries out was amusing.

Technical question though: Do I need to copy over anything other than the binaries? (Are there some libraries that Aircrack-NG uses which the N900 won't have onboard, that I need to find wherever Scratchbox stuck them?)