Here is the output of that, AlbertP:
(within a Terminal window in the directory I extracted the compat-drivers-3.8.3.2 to):
./scripts/driver-select ath9k_htc
make
sudo make install
Code: Select all
make -C /lib/modules/3.2.0-23-generic/build M=/home/stuart/compat-drivers-3.8.3-2 modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-23-generic'
Building modules, stage 2.
MODPOST 6 modules
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-23-generic'
make -C /lib/modules/3.2.0-23-generic/build M=/home/stuart/compat-drivers-3.8.3-2 "INSTALL_MOD_DIR=updates" \
modules_install
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-23-generic'
INSTALL /home/stuart/compat-drivers-3.8.3-2/compat/compat.ko
INSTALL /home/stuart/compat-drivers-3.8.3-2/compat/sch_codel.ko
INSTALL /home/stuart/compat-drivers-3.8.3-2/compat/sch_fq_codel.ko
INSTALL /home/stuart/compat-drivers-3.8.3-2/net/mac80211/mac80211.ko
INSTALL /home/stuart/compat-drivers-3.8.3-2/net/rfkill/rfkill-regulator.ko
INSTALL /home/stuart/compat-drivers-3.8.3-2/net/wireless/cfg80211.ko
DEPMOD 3.2.0-23-generic
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-23-generic'
depmod will prefer updates/ over kernel/ -- OK!
Now run:
sudo make unload to unload all: wireless, bluetooth and ethernet modules
sudo make wlunload to unload wireless modules
sudo make btunload to unload bluetooth modules
Run sudo modprobe driver-name to load your desired driver.
If unsure reboot.
I then ran the following commands (please correct me if I can doing this wrong):
sudo make unload
Code: Select all
Stoping bluetooth service..
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service bluetooth stop
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) utility, e.g. stop bluetooth
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service bluetooth status
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status bluetooth
bluetooth stop/waiting
Unloading rtlwifi...
FATAL: Module rtlwifi is in use.
Unloading mac80211...
FATAL: Module mac80211 is in use.
Unloading cfg80211...
FATAL: Module cfg80211 is in use.
(At which point my TP-Link wireless adaptor stopped working).
sudo make wlunload
Code: Select all
Unloading rtlwifi...
FATAL: Module rtlwifi is in use.
Unloading mac80211...
FATAL: Module mac80211 is in use.
Unloading cfg80211...
FATAL: Module cfg80211 is in use.
sudo make btunload
Code: Select all
Stoping bluetooth service..
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service bluetooth stop
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) utility, e.g. stop bluetooth
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service bluetooth status
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status bluetooth
bluetooth stop/waiting
And then...
sudo modprobe ath9k_htc
...at which point the TP-Link network adapter started working again.
Unfortunately, when I started the Skype software, the same problem happened that I originally described: it did not connect to Skype, and the connection disconnected.
(Maybe this is not surprising? I believe I originally installed my driver through that same compat-drivers archive...)
My current problem
Anyway, my current problem is the USB adapter is not yet working, even after about 6 system reboots. (I am posting this forum message from another PC).
In the first reboot I was getting the same black screen
ath: Chip reset failed messages, as described in
my first post. Unfortunately, the problem is now not resolving itself after a system reboot.
For the subsequent reboots, I am getting a message saying something about an error with "
modem-manager[931]" in there.
(Any guides to access a log file with these full error messages, once I reboot the computer?)
Any suggestions on how to 1) restore network adapter functionality right now, and 2) fix Skype from behaving in this way?