Problems to connect via wifi on my Arch Linux

cypro · 2014-05-13 12:53:30

Hello evreyone,
I am using the latest Arch Linux, on my HP Mini 101. I am connecting via ethernet fine, when its comes to wifi I have problem to connect to.
First I tried with the command sudo wifi-menu, the wifi card found successful all the available wifi stations, but was unable to connect with a message:

"Job for netctl@........ service failed. See 'systemctl status netctl@......service' and 'journalctl -xn' for details'

I run the above command from the message to get more details and is the following:
for systemctl status..:

Loaded: loaded(/usr/lib/systemd/system/netctl@.service; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)

After that, I installed the wifi-radar to get a GUI to connect to a Wifi but when I am choosing a wifi, I can observe a message saying: "could not get IP address!".

Moreover, to run the wifi-radar I have to do it with the terminal and the command sudo wifi-radar while from the menu can't open (may need root permissions?)

I don't think that the problem is to the hardware, while the wifis are listed correct, the problem is to establish a connection.

Thank you in advance.

ondoho · 2014-05-13 20:15:48

by installing wifi-radar you made the problem more complicated and harder to trace.

i'd like to search for a solution with netctl; most archers seem to be using that, anyway.

so if you don't mind uninstalling wifi-radar, rebooting, trying to connect with netctl, then posting both outputs (the systemctl status... and journalctl -xn).

you can also try

sudo wifi-menu

from a terminal.

cypro · 2014-05-14 00:49:45

I do remove the wifi-radar and reboot. Then I follow the wiki for the netctl and I did the following command:

cp /etc/netctl/examples/wireless-wpa /etc/netctl/profile1

Below are the messages:

$sudo netctl start profile1
Job for netctl@profile1.service failed. See 'systemctl status netctl@profile1.service' and 'journalctl -xn' for details.

$systemctl status netctl@profile1.service
netctl@profile1.service - Networking for netctl profile profile1
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Wed 2014-05-14 03:39:52 EEST; 59s ago
     Docs: man:netctl.profile(5)
  Process: 754 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 754 (code=exited, status=1/FAILURE)

May 14 03:39:52 user network[754]: Starting network profile 'profile1'...
May 14 03:39:52 user network[754]: Interface 'wlan0' does not exist
May 14 03:39:52 user network[754]: Failed to bring the network up for profile 'profile1'
May 14 03:39:52 user systemd[1]: netctl@profile1.service: main process exited, code=exite...LURE
May 14 03:39:52 user systemd[1]: Failed to start Networking for netctl profile profile1.
May 14 03:39:52 user systemd[1]: Unit netctl@profile1.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

$ journalctl -xn
-- Logs begin at Tue 2014-01-28 02:18:46 EET, end at Wed 2014-05-14 03:39:52 EEST. --
May 14 03:39:52 user systemd[1]: Starting system-netctl.slice.
-- Subject: Unit system-netctl.slice has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit system-netctl.slice has begun starting up.
May 14 03:39:52 user systemd[1]: Created slice system-netctl.slice.
-- Subject: Unit system-netctl.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit system-netctl.slice has finished starting up.
-- 
-- The start-up result is done.
May 14 03:39:52 user systemd[1]: Starting Networking for netctl profile profile1...
-- Subject: Unit netctl@profile1.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@profile1.service has begun starting up.
May 14 03:39:52 user network[754]: Starting network profile 'profile1'...
May 14 03:39:52 user network[754]: Interface 'wlan0' does not exist
May 14 03:39:52 user network[754]: Failed to bring the network up for profile 'profile1'
May 14 03:39:52 user systemd[1]: netctl@profile1.service: main process exited, code=exited, stat
May 14 03:39:52 user systemd[1]: Failed to start Networking for netctl profile profile1.
-- Subject: Unit netctl@profile1.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@profile1.service has failed.
-- 
-- The result is failed.
May 14 03:39:52 user systemd[1]: Unit netctl@profile1.service entered failed state.
May 14 03:39:52 user sudo[748]: pam_unix(sudo:session): session closed for user root

train_wreck · 2014-05-14 04:21:12

so netctl is telling you that there is no interface on your system named 'wlan0'. did you edit /etc/netctl/profile1 before you started netctl?

cypro · 2014-05-14 13:27:38

Yea I do edit the file:

The file:

  GNU nano 2.2.6                 File: /etc/netctl/profile1                                         

Description='A simple WPA encrypted wireless connection'
Interface=wlan0
Connection=wireless
Security=wpa

IP=dhcp

ESSID='myroutername'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='67736f736d'
# Uncomment this if your ssid is hidden
#Hidden=yes

Also this may help:

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:21:cc:55:f2:5e brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 70:f3:95:6f:72:11 brd ff:ff:ff:ff:ff:ff

and also this one:

$ lspci
00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 04)
01:00.1 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Barossa PCI Express Card Reader (rev 01)
02:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe

Thank you.

Trilby · 2014-05-14 13:30:34

cypro wrote:

Interface=wlan0

3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP>

There's your problem. You set it to use interface wlan0, but you have no such interface. Your wireless interface is wlp2s0

cypro · 2014-05-14 14:06:56

Trilby wrote:

cypro wrote:
Interface=wlan0
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP>
There's your problem. You set it to use interface wlan0, but you have no such interface. Your wireless interface is wlp2s0

Thanks for your reply, I saw this point you are saying, and I do change the interface to wlps2s0 but the problem is the same as my first post message.

Trilby · 2014-05-14 14:20:43

I doubt it's the same. The problem was that the interface didn't exist. Are you getting the message now that "Interface 'wlp2s0' does not exist"?

cypro · 2014-05-14 15:31:34

The message steel the same mate:

$sudo netctl start profile1
Job for netctl@profile1.service failed. See 'systemctl status netctl@profile1.service' and 'journalctl -xn' for details.

henk · 2014-05-14 15:55:51

I think Trilby referred to the output of 'systemctl status netctl@profile1.service'. After you changed the device name and the service
is still not starting, there will be a different output as to why the service didn't start.

cypro · 2014-05-14 16:13:30

Oh sorry about that, here you go:

$ systemctl status netctl@profile1.service
netctl@profile1.service - Networking for netctl profile profile1
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Wed 2014-05-14 18:32:38 EEST; 40min ago
     Docs: man:netctl.profile(5)
  Process: 868 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 868 (code=exited, status=1/FAILURE)

May 14 18:32:38 user network[868]: Starting network profile 'profile1'...
May 14 18:32:38 user network[868]: The interface of network profile 'pr...up
May 14 18:32:38 user systemd[1]: netctl@profile1.service: main process ...RE
May 14 18:32:38 user systemd[1]: Failed to start Networking for netctl ...1.
May 14 18:32:38 user systemd[1]: Unit netctl@profile1.service entered f...e.
Hint: Some lines were ellipsized, use -l to show in full.

henk · 2014-05-14 16:34:43

Could you give the output again but then with 'systemctl status -l netctl@profile1.service' To show the lines in full?

May 14 18:32:38 user network[868]: The interface of network profile 'pr...up
May 14 18:32:38 user systemd[1]: netctl@profile1.service: main process ...RE

is not really usefull

cypro · 2014-05-14 16:49:20

Yes here you go:

$ systemctl status -l netctl@profile1.service
netctl@profile1.service - Networking for netctl profile profile1
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Wed 2014-05-14 18:32:38 EEST; 1h 17min ago
     Docs: man:netctl.profile(5)
  Process: 868 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 868 (code=exited, status=1/FAILURE)

May 14 18:32:38 user network[868]: Starting network profile 'profile1'...
May 14 18:32:38 user network[868]: The interface of network profile 'profile1' is already up
May 14 18:32:38 user systemd[1]: netctl@profile1.service: main process exited, code=exited, status=1/FAILURE
May 14 18:32:38 user systemd[1]: Failed to start Networking for netctl profile profile1.
May 14 18:32:38 user systemd[1]: Unit netctl@profile1.service entered failed state.

ewaller · 2014-05-14 16:50:28

What if you stop the service first, then start it?

cypro · 2014-05-14 17:24:19

Same thing.

henk · 2014-05-14 17:33:27

Do you already have a network service running?
What is the output of 'systemctl --type=service --no-pager'?

ewaller · 2014-05-14 17:39:31

cypro wrote:

Same thing.

So, you stopped it, and when you started it the same

The interface of network profile 'profile1' is already up

message was logged when you restarted it?

cypro · 2014-05-14 18:43:19

Oh I had install the NetworkManager, but now I have uninstall it and reboot. The problem is the same again :\

Last edited by cypro (2014-05-14 18:45:37)

cypro · 2014-05-14 21:19:24

Isn't a bit confuse that my interface is not wlan0 and that the wifi scan is successful but the establish of the connection fail? I search for drivers for rt3090 but are out of date and the one that is not out of date can't be installed.
Please help.

train_wreck · 2014-05-14 21:33:40

what's "ip link show" say now? probably not "wlp2s0" for the WiFi interface name.

you are probably running into the devices getting renamed upon each reboot. you probably need to create a file /udev/rules.d/10-network.rules with the following:

SUBSYSTEM=="net", ATTR{address}=="<your wifi MAC address>", NAME="wlan0"

then make sure the "Interface" line in the netctl profile says:

Interface=wlan0

cypro · 2014-05-14 21:55:24

I did what you suggest but here I have to note that the directories: /udev/rules.d and the file 10-network.rules didn't exist so I create the path and the file I append the line in that file and then I did the change and to the netctl file, reboot but now even the wifi-menu won't start :S
Now if I try to run the sudo wifi-menu I get the message in red:

 Invalid interface specification

And for the netctl command the message steel the same.

Trilby · 2014-05-14 22:39:18

You really need to show us the *actual* error messages you are getting at each stage. I have no doubt that it is still not working, but now it is 'not working' for a different reason.

First was the interface name problem - that is fixed. Next was the fact that another service was already running - that should now be fixed. Now there is a new problem, but we can't guess what it is until we see the error message output from the systemctl status output for that service.

cypro · 2014-05-14 23:37:01

Okay,
Here are the outcomes:

$ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:21:cc:55:f2:5e brd ff:ff:ff:ff:ff:ff

$ sudo netctl start profile1
Job for netctl@profile1.service failed. See 'systemctl status netctl@profile1.service' and 'journalctl -xn' for details.

$ systemctl status -l netctl@profile1.service
netctl@profile1.service - Networking for netctl profile profile1
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Thu 2014-05-15 02:32:15 EEST; 1min 26s ago
     Docs: man:netctl.profile(5)
  Process: 680 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 680 (code=exited, status=1/FAILURE)

May 15 02:32:15 router network[680]: Starting network profile 'profile1'...
May 15 02:32:15 router network[680]: Interface 'wlan0' does not exist
May 15 02:32:15 router network[680]: Failed to bring the network up for profile 'profile1'
May 15 02:32:15 router systemd[1]: netctl@profile1.service: main process exited, code=exited, status=1/FAILURE
May 15 02:32:15 router systemd[1]: Failed to start Networking for netctl profile profile1.
May 15 02:32:15 router systemd[1]: Unit netctl@profile1.service entered failed state.

$ sudo wifi-menu
Invalid interface specification
Usage: wifi-menu [-h | --help] [-o | --obscure] [INTERFACE]

Interactively connect to a wireless network on INTERFACE using netctl.
If only one wireless interface is available, INTERFACE can be omitted.

Arguments:
  -h, --help     Show this help
  -o, --obscure  Show asterisks for the characters of the password
                 and store the password as a hexadecimal string

$ journalctl -xn
-- Logs begin at Tue 2014-01-28 02:18:46 EET, end at Thu 2014-05-15 02:34:20 EEST. --
May 15 02:32:15 router network[680]: Starting network profile 'profile1'...
May 15 02:32:15 router network[680]: Interface 'wlan0' does not exist
May 15 02:32:15 router network[680]: Failed to bring the network up for profile 'profile1'
May 15 02:32:15 router systemd[1]: netctl@profile1.service: main process exited, code=exited, stat
May 15 02:32:15 router systemd[1]: Failed to start Networking for netctl profile profile1.
-- Subject: Unit netctl@profile1.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@profile1.service has failed.
-- 
-- The result is failed.
May 15 02:32:15 router systemd[1]: Unit netctl@profile1.service entered failed state.
May 15 02:32:15 router sudo[674]: pam_unix(sudo:session): session closed for user root
May 15 02:34:20 router sudo[692]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr
May 15 02:34:20 router sudo[692]: pam_unix(sudo:session): session opened for user root by user(u
May 15 02:34:20 router sudo[692]: pam_unix(sudo:session): session closed for user root

Last edited by cypro (2014-05-14 23:37:25)

train_wreck · 2014-05-14 23:41:10

are you sure that's the complete output of "ip link"? you listed 2 physical interfaces when you posted that before.... now you're only showing 1

Last edited by train_wreck (2014-05-14 23:41:27)

Trilby · 2014-05-14 23:48:29

Also, the output now says it can't find wlan0 again. So it seems you've *undone* the fix to the previous step.

Please realize that troubleshooting will often have multiple steps - each one building on the last. We are not trying random things hoping one will work. So the progress we had already made was important ... we need to keep your interface name and profile settings matching and then work on the next step.

Arch Linux

#1 2014-05-13 12:53:30

Problems to connect via wifi on my Arch Linux

#2 2014-05-13 20:15:48

Re: Problems to connect via wifi on my Arch Linux

#3 2014-05-14 00:49:45

Re: Problems to connect via wifi on my Arch Linux

#4 2014-05-14 04:21:12

Re: Problems to connect via wifi on my Arch Linux

#5 2014-05-14 13:27:38

Re: Problems to connect via wifi on my Arch Linux

#6 2014-05-14 13:30:34

Re: Problems to connect via wifi on my Arch Linux

#7 2014-05-14 14:06:56

Re: Problems to connect via wifi on my Arch Linux

#8 2014-05-14 14:20:43

Re: Problems to connect via wifi on my Arch Linux

#9 2014-05-14 15:31:34

Re: Problems to connect via wifi on my Arch Linux

#10 2014-05-14 15:55:51

Re: Problems to connect via wifi on my Arch Linux

#11 2014-05-14 16:13:30

Re: Problems to connect via wifi on my Arch Linux

#12 2014-05-14 16:34:43

Re: Problems to connect via wifi on my Arch Linux

#13 2014-05-14 16:49:20

Re: Problems to connect via wifi on my Arch Linux

#14 2014-05-14 16:50:28

Re: Problems to connect via wifi on my Arch Linux

#15 2014-05-14 17:24:19

Re: Problems to connect via wifi on my Arch Linux

#16 2014-05-14 17:33:27

Re: Problems to connect via wifi on my Arch Linux

#17 2014-05-14 17:39:31

Re: Problems to connect via wifi on my Arch Linux

#18 2014-05-14 18:43:19

Re: Problems to connect via wifi on my Arch Linux

#19 2014-05-14 21:19:24

Re: Problems to connect via wifi on my Arch Linux

#20 2014-05-14 21:33:40

Re: Problems to connect via wifi on my Arch Linux

#21 2014-05-14 21:55:24

Re: Problems to connect via wifi on my Arch Linux

#22 2014-05-14 22:39:18

Re: Problems to connect via wifi on my Arch Linux

#23 2014-05-14 23:37:01

Re: Problems to connect via wifi on my Arch Linux

#24 2014-05-14 23:41:10

Re: Problems to connect via wifi on my Arch Linux

#25 2014-05-14 23:48:29

Re: Problems to connect via wifi on my Arch Linux

Board footer