Wired driver installs? Yes if you are using the newest of chip sets from Atheros, it might not be in the kernel yet and you could be facing no interface found when attempting to configure the network. The driver patch is pretty easy to install if a few steps are followed while using wireless or from another computer.
Before you start run the command lspci in a terminal window to determine what driver you need. You will see something similar to this at the bottom of the output window:
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
03:00.0 Ethernet controller: Atheros Communications Inc. AR8162 Fast Ethernet (rev 10)
In my case I have the Broadcom BCM4313 wireless controller and the Atheros AR8162 Ethernet controller installed as hardware. I am using kernel 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux in this Linux Mint 14 XFCE edition. In my case the wireless was indeed supported right away but the wired controller was not.
I first found the instructions here on the Linux Foundation but for me they were missing the crucial step of installing Linux headers build-essentials which is explained in this Ubuntu forum post here. The wget command in the instructions will pull drivers from this index. On the Linux Foundation site you will see a list of two chip sets, alx and atl1c. These instructions are for the alx series of chips. If you have the atl1c chip it might be as easy as replacing the alx in the command with atl1c but I have no way in which to test. These are the instructions I followed in a terminal window for the alx controller:
sudo apt-get install linux-headers-generic build-essential
tar -xf compat-wireless-3.6.8-1-snpc.tar.bz2
sudo make install
sudo modprobe alx
Note the line starting with wget is wrapped to the next line. If all went well you now have a wired connection active. For some they will already have the build-essential files installed and can skip this step but for me this was the one line missing in other instructions that made this work. It does not hurt to run it again since if they are installed the command will tell you. Also note that if this is being done on another computer, follow the instructions to get the driver patch and transport it to the computer needing it. Once copied to the target computer start again at the tar command. Since this is a kernel patch, if you update the kernel you will need to run this again until the patch becomes part of the kernel.
I hope having this all in one place will help someone get connected until this patch makes it into the kernel itself.