Wifi not working with Arch Linux
I have a Lenovo Thinkpad X220. I recently changed my hard disk drive to an SSD and installed Arch Linux on it.
What happens is that, when I try to connect to a Wifi Network via wifi-menu
, it doesn't connect. wifi-menu
shows me the different networks that are available to connect, and when typing the password it immediately fails.
Not sure what drivers I should install, and the only way I can connect to the Internet is through a wired connection.
I think this can be useful:
> $ lspci -nnk | grep -iA2 net
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit
Network Connection (Lewisville) [8086:1502] (rev 04)
Subsystem: Lenovo ThinkPad T520 [17aa:21ce]
Kernel driver in use: e1000e
--
03:00.0 Network controller [0280]: Intel Corporation Centrino
Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34)
Subsystem: Intel Corporation Centrino Advanced-N 6205 (802.11a/b/g/n)
[8086:1311]
Kernel driver in use: iwlwifi
So this is the output for when trying to connect manually using wpa_supplicant
> $ sudo wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp3s0
Successfully initialized wpa_supplicant
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=3 locally_generated=1
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:36 (SSID='CATEGORIES' freq=2412 MHz)
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=82:2a:a8:31:9c:51)
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=1 locally_generated=1
wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CATEGORIES" auth_failures=1 duration=10 reason=CONN_FAILED
^Cnl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
wlp3s0: CTRL-EVENT-TERMINATING
arch-linux wifi iwlwifi
add a comment |
I have a Lenovo Thinkpad X220. I recently changed my hard disk drive to an SSD and installed Arch Linux on it.
What happens is that, when I try to connect to a Wifi Network via wifi-menu
, it doesn't connect. wifi-menu
shows me the different networks that are available to connect, and when typing the password it immediately fails.
Not sure what drivers I should install, and the only way I can connect to the Internet is through a wired connection.
I think this can be useful:
> $ lspci -nnk | grep -iA2 net
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit
Network Connection (Lewisville) [8086:1502] (rev 04)
Subsystem: Lenovo ThinkPad T520 [17aa:21ce]
Kernel driver in use: e1000e
--
03:00.0 Network controller [0280]: Intel Corporation Centrino
Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34)
Subsystem: Intel Corporation Centrino Advanced-N 6205 (802.11a/b/g/n)
[8086:1311]
Kernel driver in use: iwlwifi
So this is the output for when trying to connect manually using wpa_supplicant
> $ sudo wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp3s0
Successfully initialized wpa_supplicant
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=3 locally_generated=1
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:36 (SSID='CATEGORIES' freq=2412 MHz)
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=82:2a:a8:31:9c:51)
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=1 locally_generated=1
wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CATEGORIES" auth_failures=1 duration=10 reason=CONN_FAILED
^Cnl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
wlp3s0: CTRL-EVENT-TERMINATING
arch-linux wifi iwlwifi
Connect manually: it will provide more detailed debugging information.
– jasonwryan
Mar 5 at 15:09
How did you create the conf file? What commands did you use? Can you post the conf (with the passphrase redacted)?
– jasonwryan
Mar 6 at 20:13
add a comment |
I have a Lenovo Thinkpad X220. I recently changed my hard disk drive to an SSD and installed Arch Linux on it.
What happens is that, when I try to connect to a Wifi Network via wifi-menu
, it doesn't connect. wifi-menu
shows me the different networks that are available to connect, and when typing the password it immediately fails.
Not sure what drivers I should install, and the only way I can connect to the Internet is through a wired connection.
I think this can be useful:
> $ lspci -nnk | grep -iA2 net
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit
Network Connection (Lewisville) [8086:1502] (rev 04)
Subsystem: Lenovo ThinkPad T520 [17aa:21ce]
Kernel driver in use: e1000e
--
03:00.0 Network controller [0280]: Intel Corporation Centrino
Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34)
Subsystem: Intel Corporation Centrino Advanced-N 6205 (802.11a/b/g/n)
[8086:1311]
Kernel driver in use: iwlwifi
So this is the output for when trying to connect manually using wpa_supplicant
> $ sudo wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp3s0
Successfully initialized wpa_supplicant
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=3 locally_generated=1
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:36 (SSID='CATEGORIES' freq=2412 MHz)
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=82:2a:a8:31:9c:51)
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=1 locally_generated=1
wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CATEGORIES" auth_failures=1 duration=10 reason=CONN_FAILED
^Cnl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
wlp3s0: CTRL-EVENT-TERMINATING
arch-linux wifi iwlwifi
I have a Lenovo Thinkpad X220. I recently changed my hard disk drive to an SSD and installed Arch Linux on it.
What happens is that, when I try to connect to a Wifi Network via wifi-menu
, it doesn't connect. wifi-menu
shows me the different networks that are available to connect, and when typing the password it immediately fails.
Not sure what drivers I should install, and the only way I can connect to the Internet is through a wired connection.
I think this can be useful:
> $ lspci -nnk | grep -iA2 net
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit
Network Connection (Lewisville) [8086:1502] (rev 04)
Subsystem: Lenovo ThinkPad T520 [17aa:21ce]
Kernel driver in use: e1000e
--
03:00.0 Network controller [0280]: Intel Corporation Centrino
Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34)
Subsystem: Intel Corporation Centrino Advanced-N 6205 (802.11a/b/g/n)
[8086:1311]
Kernel driver in use: iwlwifi
So this is the output for when trying to connect manually using wpa_supplicant
> $ sudo wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp3s0
Successfully initialized wpa_supplicant
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=3 locally_generated=1
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:36 (SSID='CATEGORIES' freq=2412 MHz)
wlp3s0: SME: Trying to authenticate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Trying to associate with 82:2a:a8:31:9c:51 (SSID='CATEGORIES' freq=2437 MHz)
wlp3s0: Associated with 82:2a:a8:31:9c:51
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp3s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=82:2a:a8:31:9c:51)
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:31:9c:51 reason=1 locally_generated=1
wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CATEGORIES" auth_failures=1 duration=10 reason=CONN_FAILED
^Cnl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
wlp3s0: CTRL-EVENT-TERMINATING
arch-linux wifi iwlwifi
arch-linux wifi iwlwifi
edited Apr 4 at 21:11
asked Mar 5 at 14:13
sant016
2315
2315
Connect manually: it will provide more detailed debugging information.
– jasonwryan
Mar 5 at 15:09
How did you create the conf file? What commands did you use? Can you post the conf (with the passphrase redacted)?
– jasonwryan
Mar 6 at 20:13
add a comment |
Connect manually: it will provide more detailed debugging information.
– jasonwryan
Mar 5 at 15:09
How did you create the conf file? What commands did you use? Can you post the conf (with the passphrase redacted)?
– jasonwryan
Mar 6 at 20:13
Connect manually: it will provide more detailed debugging information.
– jasonwryan
Mar 5 at 15:09
Connect manually: it will provide more detailed debugging information.
– jasonwryan
Mar 5 at 15:09
How did you create the conf file? What commands did you use? Can you post the conf (with the passphrase redacted)?
– jasonwryan
Mar 6 at 20:13
How did you create the conf file? What commands did you use? Can you post the conf (with the passphrase redacted)?
– jasonwryan
Mar 6 at 20:13
add a comment |
3 Answers
3
active
oldest
votes
Try to check the state of your wifi interface with ip link
. If it is down, you can bring it up with sudo ip link set dev [your interface name] up
.
As jasonwryan stated, connecting manually (you can use wpa_supplicant
) might give you more information on the problem.
When usingwpa_supplicant
I'm seeing authentication problems but I'm totally sure I'm using the right key for the right ESSID.
– sant016
Mar 5 at 16:44
Did you form a config file withwpa_passphrase
?
– corsel
Mar 5 at 16:52
Yes, and the information put there is correct.
– sant016
Mar 5 at 16:57
1
@sant016 "authentication problems" is not a helpful description, nor an error message. Edit your question with full output.
– jasonwryan
Mar 5 at 17:14
@jasonwryan now edited. Sorry.
– sant016
Mar 6 at 15:40
add a comment |
In the begginig I have the same Problem with wifi-menu, then I mannualy connect with the internet like this:
1) Discover what is your interface with the follow command: iwconfig
Normally, your wifi interface is like this construct: wlp2s0
I'll put where you need to put your interface
2) Put the interface up: ip link set <interface name> up
3) Scan your interface to see if he is enable: iwlist <interface name> scan | less
4) If he is in the list, down the interface: ip link set interface down
5) Go the netctl examples Directory: cd /etc/netctl/examples
6) Copy the wireless-wpa to netctl Directory with the name you want:
cd /etc/netctl/examples/wireless-wpa /etc/netctl/wifi_name
7) Open the wireless-wpa file to edit with nano(you can use VIM):
sudo nano /etc/netctl/wifi_name
8) Alterate the following infos:
Interface: <Interface name>
ESSID: <your internet name>
key: <your internet password>
Save with CTRL+O and CTRL+X
9) Run the netctl with the following commands:
cd /etc/netctl
netctl start wifi_name
10) If appearing a error message, try this commad: ip link set dev <interface name> down
11) try run your internet: ping -c 3 www.google.com
12) If working, enable your internet to run all the time: netctl enable wifi_name
add a comment |
Try installing the NetworkManager
package using chroot
in the install media and use nmtui
.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f428277%2fwifi-not-working-with-arch-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try to check the state of your wifi interface with ip link
. If it is down, you can bring it up with sudo ip link set dev [your interface name] up
.
As jasonwryan stated, connecting manually (you can use wpa_supplicant
) might give you more information on the problem.
When usingwpa_supplicant
I'm seeing authentication problems but I'm totally sure I'm using the right key for the right ESSID.
– sant016
Mar 5 at 16:44
Did you form a config file withwpa_passphrase
?
– corsel
Mar 5 at 16:52
Yes, and the information put there is correct.
– sant016
Mar 5 at 16:57
1
@sant016 "authentication problems" is not a helpful description, nor an error message. Edit your question with full output.
– jasonwryan
Mar 5 at 17:14
@jasonwryan now edited. Sorry.
– sant016
Mar 6 at 15:40
add a comment |
Try to check the state of your wifi interface with ip link
. If it is down, you can bring it up with sudo ip link set dev [your interface name] up
.
As jasonwryan stated, connecting manually (you can use wpa_supplicant
) might give you more information on the problem.
When usingwpa_supplicant
I'm seeing authentication problems but I'm totally sure I'm using the right key for the right ESSID.
– sant016
Mar 5 at 16:44
Did you form a config file withwpa_passphrase
?
– corsel
Mar 5 at 16:52
Yes, and the information put there is correct.
– sant016
Mar 5 at 16:57
1
@sant016 "authentication problems" is not a helpful description, nor an error message. Edit your question with full output.
– jasonwryan
Mar 5 at 17:14
@jasonwryan now edited. Sorry.
– sant016
Mar 6 at 15:40
add a comment |
Try to check the state of your wifi interface with ip link
. If it is down, you can bring it up with sudo ip link set dev [your interface name] up
.
As jasonwryan stated, connecting manually (you can use wpa_supplicant
) might give you more information on the problem.
Try to check the state of your wifi interface with ip link
. If it is down, you can bring it up with sudo ip link set dev [your interface name] up
.
As jasonwryan stated, connecting manually (you can use wpa_supplicant
) might give you more information on the problem.
answered Mar 5 at 16:15
corsel
7519
7519
When usingwpa_supplicant
I'm seeing authentication problems but I'm totally sure I'm using the right key for the right ESSID.
– sant016
Mar 5 at 16:44
Did you form a config file withwpa_passphrase
?
– corsel
Mar 5 at 16:52
Yes, and the information put there is correct.
– sant016
Mar 5 at 16:57
1
@sant016 "authentication problems" is not a helpful description, nor an error message. Edit your question with full output.
– jasonwryan
Mar 5 at 17:14
@jasonwryan now edited. Sorry.
– sant016
Mar 6 at 15:40
add a comment |
When usingwpa_supplicant
I'm seeing authentication problems but I'm totally sure I'm using the right key for the right ESSID.
– sant016
Mar 5 at 16:44
Did you form a config file withwpa_passphrase
?
– corsel
Mar 5 at 16:52
Yes, and the information put there is correct.
– sant016
Mar 5 at 16:57
1
@sant016 "authentication problems" is not a helpful description, nor an error message. Edit your question with full output.
– jasonwryan
Mar 5 at 17:14
@jasonwryan now edited. Sorry.
– sant016
Mar 6 at 15:40
When using
wpa_supplicant
I'm seeing authentication problems but I'm totally sure I'm using the right key for the right ESSID.– sant016
Mar 5 at 16:44
When using
wpa_supplicant
I'm seeing authentication problems but I'm totally sure I'm using the right key for the right ESSID.– sant016
Mar 5 at 16:44
Did you form a config file with
wpa_passphrase
?– corsel
Mar 5 at 16:52
Did you form a config file with
wpa_passphrase
?– corsel
Mar 5 at 16:52
Yes, and the information put there is correct.
– sant016
Mar 5 at 16:57
Yes, and the information put there is correct.
– sant016
Mar 5 at 16:57
1
1
@sant016 "authentication problems" is not a helpful description, nor an error message. Edit your question with full output.
– jasonwryan
Mar 5 at 17:14
@sant016 "authentication problems" is not a helpful description, nor an error message. Edit your question with full output.
– jasonwryan
Mar 5 at 17:14
@jasonwryan now edited. Sorry.
– sant016
Mar 6 at 15:40
@jasonwryan now edited. Sorry.
– sant016
Mar 6 at 15:40
add a comment |
In the begginig I have the same Problem with wifi-menu, then I mannualy connect with the internet like this:
1) Discover what is your interface with the follow command: iwconfig
Normally, your wifi interface is like this construct: wlp2s0
I'll put where you need to put your interface
2) Put the interface up: ip link set <interface name> up
3) Scan your interface to see if he is enable: iwlist <interface name> scan | less
4) If he is in the list, down the interface: ip link set interface down
5) Go the netctl examples Directory: cd /etc/netctl/examples
6) Copy the wireless-wpa to netctl Directory with the name you want:
cd /etc/netctl/examples/wireless-wpa /etc/netctl/wifi_name
7) Open the wireless-wpa file to edit with nano(you can use VIM):
sudo nano /etc/netctl/wifi_name
8) Alterate the following infos:
Interface: <Interface name>
ESSID: <your internet name>
key: <your internet password>
Save with CTRL+O and CTRL+X
9) Run the netctl with the following commands:
cd /etc/netctl
netctl start wifi_name
10) If appearing a error message, try this commad: ip link set dev <interface name> down
11) try run your internet: ping -c 3 www.google.com
12) If working, enable your internet to run all the time: netctl enable wifi_name
add a comment |
In the begginig I have the same Problem with wifi-menu, then I mannualy connect with the internet like this:
1) Discover what is your interface with the follow command: iwconfig
Normally, your wifi interface is like this construct: wlp2s0
I'll put where you need to put your interface
2) Put the interface up: ip link set <interface name> up
3) Scan your interface to see if he is enable: iwlist <interface name> scan | less
4) If he is in the list, down the interface: ip link set interface down
5) Go the netctl examples Directory: cd /etc/netctl/examples
6) Copy the wireless-wpa to netctl Directory with the name you want:
cd /etc/netctl/examples/wireless-wpa /etc/netctl/wifi_name
7) Open the wireless-wpa file to edit with nano(you can use VIM):
sudo nano /etc/netctl/wifi_name
8) Alterate the following infos:
Interface: <Interface name>
ESSID: <your internet name>
key: <your internet password>
Save with CTRL+O and CTRL+X
9) Run the netctl with the following commands:
cd /etc/netctl
netctl start wifi_name
10) If appearing a error message, try this commad: ip link set dev <interface name> down
11) try run your internet: ping -c 3 www.google.com
12) If working, enable your internet to run all the time: netctl enable wifi_name
add a comment |
In the begginig I have the same Problem with wifi-menu, then I mannualy connect with the internet like this:
1) Discover what is your interface with the follow command: iwconfig
Normally, your wifi interface is like this construct: wlp2s0
I'll put where you need to put your interface
2) Put the interface up: ip link set <interface name> up
3) Scan your interface to see if he is enable: iwlist <interface name> scan | less
4) If he is in the list, down the interface: ip link set interface down
5) Go the netctl examples Directory: cd /etc/netctl/examples
6) Copy the wireless-wpa to netctl Directory with the name you want:
cd /etc/netctl/examples/wireless-wpa /etc/netctl/wifi_name
7) Open the wireless-wpa file to edit with nano(you can use VIM):
sudo nano /etc/netctl/wifi_name
8) Alterate the following infos:
Interface: <Interface name>
ESSID: <your internet name>
key: <your internet password>
Save with CTRL+O and CTRL+X
9) Run the netctl with the following commands:
cd /etc/netctl
netctl start wifi_name
10) If appearing a error message, try this commad: ip link set dev <interface name> down
11) try run your internet: ping -c 3 www.google.com
12) If working, enable your internet to run all the time: netctl enable wifi_name
In the begginig I have the same Problem with wifi-menu, then I mannualy connect with the internet like this:
1) Discover what is your interface with the follow command: iwconfig
Normally, your wifi interface is like this construct: wlp2s0
I'll put where you need to put your interface
2) Put the interface up: ip link set <interface name> up
3) Scan your interface to see if he is enable: iwlist <interface name> scan | less
4) If he is in the list, down the interface: ip link set interface down
5) Go the netctl examples Directory: cd /etc/netctl/examples
6) Copy the wireless-wpa to netctl Directory with the name you want:
cd /etc/netctl/examples/wireless-wpa /etc/netctl/wifi_name
7) Open the wireless-wpa file to edit with nano(you can use VIM):
sudo nano /etc/netctl/wifi_name
8) Alterate the following infos:
Interface: <Interface name>
ESSID: <your internet name>
key: <your internet password>
Save with CTRL+O and CTRL+X
9) Run the netctl with the following commands:
cd /etc/netctl
netctl start wifi_name
10) If appearing a error message, try this commad: ip link set dev <interface name> down
11) try run your internet: ping -c 3 www.google.com
12) If working, enable your internet to run all the time: netctl enable wifi_name
answered May 16 at 19:11
F4NT0
438
438
add a comment |
add a comment |
Try installing the NetworkManager
package using chroot
in the install media and use nmtui
.
add a comment |
Try installing the NetworkManager
package using chroot
in the install media and use nmtui
.
add a comment |
Try installing the NetworkManager
package using chroot
in the install media and use nmtui
.
Try installing the NetworkManager
package using chroot
in the install media and use nmtui
.
answered Apr 3 at 3:29
SealsRock12
178
178
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f428277%2fwifi-not-working-with-arch-linux%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
Connect manually: it will provide more detailed debugging information.
– jasonwryan
Mar 5 at 15:09
How did you create the conf file? What commands did you use? Can you post the conf (with the passphrase redacted)?
– jasonwryan
Mar 6 at 20:13