[Eee Pad Transformer Q&A, Help & Troubleshooting] mb02:
VICTORY!!!!!!! I finally figured out my problem after a bit of googling and better understanding the correlation between the protocols and whatnot entered in wpa_supplicant.conf/interfaces files. Also, some of the portions of the guides already given in this thread are missing some key details for getting this set up. After understanding everything properly, I have /etc/network/interfaces configured and am now posting this from my Ubuntu OS on my TF!!!

For those that are still stuck, I will provide some help here really quick to give a better understanding of configuring /etc/network/interfaces to work with WPA2 and AES encryption (and TKIP if you use that instead). Here is a quick paste of my interfaces file:

# interfaces(5) file used by ifup(8) and ifdown(8)

auto lo

iface lo inet loopback

auto wlan0

iface wlan0 inet dhcp

wpa-driver wext

wpa-ssid BigWiFi <---your SSID would go here

wpa-key-mgmt WPA-PSK

wpa-proto RSN

wpa-pairwise CCMP

wpa-group CCMP

wpa-psk "hex key that i will not provide here" (will explain this one in a moment)

wpa-ap-scan 2

Now for a little breakdown of this file.

wpa-driver is set to wext, this simply states that "wireless extension" be used for driver to connect to network

ssid is straightforward, this is where you would put your router's ssid. BTW, no quotations are needed in this file anywhere.

wpa-key-mgmt is set to WPA-PSK for pre-shared keys, otherwise it would be EAP for enterprise authentication server

proto: RSN designates that network is WPA2, if you use WPA you would put WPA here

pairwise & group: these two go hand-in-hand. CCMP designates that encryption is AES, for TKIP these would both be TKIP.

ap_scan: the two options for this is either 1 or 2. 1 designates that SSID is being broadcasted by the router, while 2 designates that broadcasting is off. With the current state of our wireless not being able to scan and identify networks, the only viable option is 2 because, according to our TFs modules, no SSIDs are being broadcasted.

now for the actual psk. You do not actually put your routers password here. You have to translate that ASCII password into hex. This is done easily in terminal. In terminal, simply type:

wpa_passphrase your_SSID your_password

and press enter. Terminal will then receive and display your hex version of the password which you will enter into the psk line in the interfaces file. My example of this process is this:

mike@Durzo-Tab:~$ wpa_passphrase BigWiFi password

network={

ssid="BigWiFi"

#psk="password"

psk=c1b38eb11b58a287f89b0559683db65a2494e683f43a59b68f7f90f61c4cdd8

}

That long line of hex is what would go into interfaces.

And that is the explanation of somewhat understanding these interfaces/wpa_supplicant.conf files. With this interfaces file setup, once you have your file set up and saved, in terminal you will want to do these commands first to ensure no previous attempts at connecting to wifi interfere with any new attempts:

sudo rm /etc/wpa_supplicant/wpa_supplicant.conf

sudo rm /var/run/wpa_supplicant/wlan0

sudo ifdown wlan0

after running these three commands, thus cleaning out all previous settings and whatnot, you can then attempt a connection with your new setup by executing:

sudo ifup wlan0

Once this command is executed in terminal, there will be no output or confirmations of any kind, there will simply be a pause in terminal as it runs the command and the prompt will return. Then just try using Internet, and if successful, it will work. I got this to work on my first attempt so have no experience with failures to get this set up lol. So, here you go. Hopefully anyone still struggling with wifi can get it to work with this setup like I did. Good luck!

Furthermore, I am wanting to permanently enable touchpad through using foxtrot5's boot.img, anyone know how I can use his kernel and get wifi modules working again on it??