TP Link TL-WN8200ND not connecting - Ubuntu 13.04
up vote
1
down vote
favorite
I searched for the driver of rtl8192cu.
I tried with official driver. This is not for my Linux installation kernel:
uname -r
3.8.0-35-generic
I tried with fixes in github.
I tried with ndiswrapper and selecting XP driver that comes with CD.
None of these worked.
But after doing:
sudo modprobe rtl8192cu
Adapter detected networks, but when I click it just does not connect.
I have 2 adapters, but just the other one, a D-Link, is detected:
lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 2357:0100
Bus 002 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 002 Device 004: ID 07d1:3c0d D-Link System DWA-125 Wireless N 150 Adapter(rev.A1) [Ralink RT3070]
Bus 002 Device 005: ID 0458:012b KYE Systems Corp. (Mouse Systems)
I installed these too:
sudo dkms status
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58, 3.8.0-35-generic, x86_64: installed
The 8192cu was installed from github link I pasted.
Update
After upgrading to 13.10:
➜ ~ sudo dkms status
8192cu, 1.8, 3.11.0-15-generic, x86_64: installed
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58: added
➜ ~ uname -r
3.11.0-15-generic
➜ ~ sudo modprobe rtl8192cu
Again, networks detected, but no connection.
13.04 wireless networking drivers
asked Jan 29 '14 at 3:11
juanpastas
27658
add a comment |
up vote
1
down vote
favorite
I searched for the driver of rtl8192cu.
I tried with official driver. This is not for my Linux installation kernel:
uname -r
3.8.0-35-generic
I tried with fixes in github.
I tried with ndiswrapper and selecting XP driver that comes with CD.
None of these worked.
But after doing:
sudo modprobe rtl8192cu
Adapter detected networks, but when I click it just does not connect.
I have 2 adapters, but just the other one, a D-Link, is detected:
lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 2357:0100
Bus 002 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 002 Device 004: ID 07d1:3c0d D-Link System DWA-125 Wireless N 150 Adapter(rev.A1) [Ralink RT3070]
Bus 002 Device 005: ID 0458:012b KYE Systems Corp. (Mouse Systems)
I installed these too:
sudo dkms status
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58, 3.8.0-35-generic, x86_64: installed
The 8192cu was installed from github link I pasted.
Update
After upgrading to 13.10:
➜ ~ sudo dkms status
8192cu, 1.8, 3.11.0-15-generic, x86_64: installed
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58: added
➜ ~ uname -r
3.11.0-15-generic
➜ ~ sudo modprobe rtl8192cu
Again, networks detected, but no connection.
13.04 wireless networking drivers
asked Jan 29 '14 at 3:11
juanpastas
27658
Maybe some of your prior changes now conflict. Maybe you want to run a live system from usb to test?
– davidbaumann
Jan 29 '14 at 16:22
Could you remove ndiswrapper, and other changes, then give this one a try with 3.8 kernel code.google.com/p/…
– user.dz
Jan 30 '14 at 15:12
It is probably best if you either upgrade to version 14.04 LTS or 15.04, as 13.04 is EOL and it is easiest to troubleshoot if you have the latest version (LTS or normal) of Ubuntu.
– nixpower
Jul 1 '15 at 15:57
I ended up buying a Tp-link Tl-wn822n, that worked out of the box. And also I updated to 14.04
– juanpastas
Jul 2 '15 at 4:08
another one that worked for me was D-link DWA-125
– juanpastas
Jul 2 '15 at 4:09
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I searched for the driver of rtl8192cu.
I tried with official driver. This is not for my Linux installation kernel:
uname -r
3.8.0-35-generic
I tried with fixes in github.
I tried with ndiswrapper and selecting XP driver that comes with CD.
None of these worked.
But after doing:
sudo modprobe rtl8192cu
Adapter detected networks, but when I click it just does not connect.
I have 2 adapters, but just the other one, a D-Link, is detected:
lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 2357:0100
Bus 002 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 002 Device 004: ID 07d1:3c0d D-Link System DWA-125 Wireless N 150 Adapter(rev.A1) [Ralink RT3070]
Bus 002 Device 005: ID 0458:012b KYE Systems Corp. (Mouse Systems)
I installed these too:
sudo dkms status
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58, 3.8.0-35-generic, x86_64: installed
The 8192cu was installed from github link I pasted.
Update
After upgrading to 13.10:
➜ ~ sudo dkms status
8192cu, 1.8, 3.11.0-15-generic, x86_64: installed
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58: added
➜ ~ uname -r
3.11.0-15-generic
➜ ~ sudo modprobe rtl8192cu
Again, networks detected, but no connection.
13.04 wireless networking drivers
asked Jan 29 '14 at 3:11
juanpastas
27658
I searched for the driver of rtl8192cu.
I tried with official driver. This is not for my Linux installation kernel:
uname -r
3.8.0-35-generic
I tried with fixes in github.
I tried with ndiswrapper and selecting XP driver that comes with CD.
None of these worked.
But after doing:
sudo modprobe rtl8192cu
Adapter detected networks, but when I click it just does not connect.
I have 2 adapters, but just the other one, a D-Link, is detected:
lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 2357:0100
Bus 002 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 002 Device 004: ID 07d1:3c0d D-Link System DWA-125 Wireless N 150 Adapter(rev.A1) [Ralink RT3070]
Bus 002 Device 005: ID 0458:012b KYE Systems Corp. (Mouse Systems)
I installed these too:
sudo dkms status
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58, 3.8.0-35-generic, x86_64: installed
The 8192cu was installed from github link I pasted.
Update
After upgrading to 13.10:
➜ ~ sudo dkms status
8192cu, 1.8, 3.11.0-15-generic, x86_64: installed
8192cu, 1.8, 3.8.0-35-generic, x86_64: installed
ndiswrapper, 1.58: added
➜ ~ uname -r
3.11.0-15-generic
➜ ~ sudo modprobe rtl8192cu
Again, networks detected, but no connection.
13.04 wireless networking drivers
13.04 wireless networking drivers
asked Jan 29 '14 at 3:11
juanpastas
27658
asked Jan 29 '14 at 3:11
juanpastas
27658
edited Jan 29 '14 at 15:53
asked Jan 29 '14 at 3:11
juanpastas
27658
asked Jan 29 '14 at 3:11
juanpastas
27658
asked Jan 29 '14 at 3:11
juanpastas
27658
27658
Maybe some of your prior changes now conflict. Maybe you want to run a live system from usb to test?
– davidbaumann
Jan 29 '14 at 16:22
Could you remove ndiswrapper, and other changes, then give this one a try with 3.8 kernel code.google.com/p/…
– user.dz
Jan 30 '14 at 15:12
It is probably best if you either upgrade to version 14.04 LTS or 15.04, as 13.04 is EOL and it is easiest to troubleshoot if you have the latest version (LTS or normal) of Ubuntu.
– nixpower
Jul 1 '15 at 15:57
I ended up buying a Tp-link Tl-wn822n, that worked out of the box. And also I updated to 14.04
– juanpastas
Jul 2 '15 at 4:08
another one that worked for me was D-link DWA-125
– juanpastas
Jul 2 '15 at 4:09
add a comment |
Maybe some of your prior changes now conflict. Maybe you want to run a live system from usb to test?
– davidbaumann
Jan 29 '14 at 16:22
Could you remove ndiswrapper, and other changes, then give this one a try with 3.8 kernel code.google.com/p/…
– user.dz
Jan 30 '14 at 15:12
It is probably best if you either upgrade to version 14.04 LTS or 15.04, as 13.04 is EOL and it is easiest to troubleshoot if you have the latest version (LTS or normal) of Ubuntu.
– nixpower
Jul 1 '15 at 15:57
I ended up buying a Tp-link Tl-wn822n, that worked out of the box. And also I updated to 14.04
– juanpastas
Jul 2 '15 at 4:08
another one that worked for me was D-link DWA-125
– juanpastas
Jul 2 '15 at 4:09
Maybe some of your prior changes now conflict. Maybe you want to run a live system from usb to test?
– davidbaumann
Jan 29 '14 at 16:22
Maybe some of your prior changes now conflict. Maybe you want to run a live system from usb to test?
– davidbaumann
Jan 29 '14 at 16:22
Could you remove ndiswrapper, and other changes, then give this one a try with 3.8 kernel code.google.com/p/…
– user.dz
Jan 30 '14 at 15:12
Could you remove ndiswrapper, and other changes, then give this one a try with 3.8 kernel code.google.com/p/…
– user.dz
Jan 30 '14 at 15:12
It is probably best if you either upgrade to version 14.04 LTS or 15.04, as 13.04 is EOL and it is easiest to troubleshoot if you have the latest version (LTS or normal) of Ubuntu.
– nixpower
Jul 1 '15 at 15:57
It is probably best if you either upgrade to version 14.04 LTS or 15.04, as 13.04 is EOL and it is easiest to troubleshoot if you have the latest version (LTS or normal) of Ubuntu.
– nixpower
Jul 1 '15 at 15:57
I ended up buying a Tp-link Tl-wn822n, that worked out of the box. And also I updated to 14.04
– juanpastas
Jul 2 '15 at 4:08
I ended up buying a Tp-link Tl-wn822n, that worked out of the box. And also I updated to 14.04
– juanpastas
Jul 2 '15 at 4:08
another one that worked for me was D-link DWA-125
– juanpastas
Jul 2 '15 at 4:09
another one that worked for me was D-link DWA-125
– juanpastas
Jul 2 '15 at 4:09
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
I had many problems with this driver in 12.04, 12.10, 13.04 until I upgraded to 13.10.
Anyway, 13.04 is EOL.
If you want to keep using 13.04, you can use kernel backports.
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
askubuntu.com/questions/408821/…
– davidbaumann
Jan 29 '14 at 3:27
sudo apt-get install linux-generic-lts-saucydid not find the package. I will update my question with output
– juanpastas
Jan 29 '14 at 15:49
add a comment |
up vote
0
down vote
I have a TP-Link 300... something. Its "Atheros" whatever, BC garbage...
Anyways - it was all a pain in the *** until 14.x Then it stopped requiring manual driver installation.
However - I seem to recall someone saying that the stock driver was almost but "still wrong" and required that manual install.
BCM drivers requiring configuring with the script, then it patches the kernel
- or something.
answered Oct 10 '15 at 7:39
TardisGuy
389517
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f412401%2ftp-link-tl-wn8200nd-not-connecting-ubuntu-13-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had many problems with this driver in 12.04, 12.10, 13.04 until I upgraded to 13.10.
Anyway, 13.04 is EOL.
If you want to keep using 13.04, you can use kernel backports.
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
askubuntu.com/questions/408821/…
– davidbaumann
Jan 29 '14 at 3:27
sudo apt-get install linux-generic-lts-saucydid not find the package. I will update my question with output
– juanpastas
Jan 29 '14 at 15:49
add a comment |
up vote
0
down vote
I had many problems with this driver in 12.04, 12.10, 13.04 until I upgraded to 13.10.
Anyway, 13.04 is EOL.
If you want to keep using 13.04, you can use kernel backports.
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
askubuntu.com/questions/408821/…
– davidbaumann
Jan 29 '14 at 3:27
sudo apt-get install linux-generic-lts-saucydid not find the package. I will update my question with output
– juanpastas
Jan 29 '14 at 15:49
add a comment |
up vote
0
down vote
up vote
0
down vote
I had many problems with this driver in 12.04, 12.10, 13.04 until I upgraded to 13.10.
Anyway, 13.04 is EOL.
If you want to keep using 13.04, you can use kernel backports.
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
I had many problems with this driver in 12.04, 12.10, 13.04 until I upgraded to 13.10.
Anyway, 13.04 is EOL.
If you want to keep using 13.04, you can use kernel backports.
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
answered Jan 29 '14 at 3:22
davidbaumann
1,4061926
1,4061926
askubuntu.com/questions/408821/…
– davidbaumann
Jan 29 '14 at 3:27
sudo apt-get install linux-generic-lts-saucydid not find the package. I will update my question with output
– juanpastas
Jan 29 '14 at 15:49
add a comment |
askubuntu.com/questions/408821/…
– davidbaumann
Jan 29 '14 at 3:27
sudo apt-get install linux-generic-lts-saucydid not find the package. I will update my question with output
– juanpastas
Jan 29 '14 at 15:49
askubuntu.com/questions/408821/…
– davidbaumann
Jan 29 '14 at 3:27
askubuntu.com/questions/408821/…
– davidbaumann
Jan 29 '14 at 3:27
sudo apt-get install linux-generic-lts-saucy did not find the package. I will update my question with output– juanpastas
Jan 29 '14 at 15:49
sudo apt-get install linux-generic-lts-saucy did not find the package. I will update my question with output– juanpastas
Jan 29 '14 at 15:49
add a comment |
up vote
0
down vote
I have a TP-Link 300... something. Its "Atheros" whatever, BC garbage...
Anyways - it was all a pain in the *** until 14.x Then it stopped requiring manual driver installation.
However - I seem to recall someone saying that the stock driver was almost but "still wrong" and required that manual install.
BCM drivers requiring configuring with the script, then it patches the kernel
- or something.
answered Oct 10 '15 at 7:39
TardisGuy
389517
add a comment |
up vote
0
down vote
I have a TP-Link 300... something. Its "Atheros" whatever, BC garbage...
Anyways - it was all a pain in the *** until 14.x Then it stopped requiring manual driver installation.
However - I seem to recall someone saying that the stock driver was almost but "still wrong" and required that manual install.
BCM drivers requiring configuring with the script, then it patches the kernel
- or something.
answered Oct 10 '15 at 7:39
TardisGuy
389517
add a comment |
up vote
0
down vote
up vote
0
down vote
I have a TP-Link 300... something. Its "Atheros" whatever, BC garbage...
Anyways - it was all a pain in the *** until 14.x Then it stopped requiring manual driver installation.
However - I seem to recall someone saying that the stock driver was almost but "still wrong" and required that manual install.
BCM drivers requiring configuring with the script, then it patches the kernel
- or something.
answered Oct 10 '15 at 7:39
TardisGuy
389517
I have a TP-Link 300... something. Its "Atheros" whatever, BC garbage...
Anyways - it was all a pain in the *** until 14.x Then it stopped requiring manual driver installation.
However - I seem to recall someone saying that the stock driver was almost but "still wrong" and required that manual install.
BCM drivers requiring configuring with the script, then it patches the kernel
- or something.
answered Oct 10 '15 at 7:39
TardisGuy
389517
answered Oct 10 '15 at 7:39
TardisGuy
389517
answered Oct 10 '15 at 7:39
TardisGuy
389517
answered Oct 10 '15 at 7:39
TardisGuy
389517
389517
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f412401%2ftp-link-tl-wn8200nd-not-connecting-ubuntu-13-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Maybe some of your prior changes now conflict. Maybe you want to run a live system from usb to test?
– davidbaumann
Jan 29 '14 at 16:22
Could you remove ndiswrapper, and other changes, then give this one a try with 3.8 kernel code.google.com/p/…
– user.dz
Jan 30 '14 at 15:12
It is probably best if you either upgrade to version 14.04 LTS or 15.04, as 13.04 is EOL and it is easiest to troubleshoot if you have the latest version (LTS or normal) of Ubuntu.
– nixpower
Jul 1 '15 at 15:57
I ended up buying a Tp-link Tl-wn822n, that worked out of the box. And also I updated to 14.04
– juanpastas
Jul 2 '15 at 4:08
another one that worked for me was D-link DWA-125
– juanpastas
Jul 2 '15 at 4:09