You are not logged in.
Pages: 1
Trying to make an older laptop work with wifi. The driver was loaded. A wireless interface was created. I brought it up with no error. dmesg shows the firmware loaded.
I am trying netctl as a manager. I used wifi-menu -o to create a profile. Attempting to start the profile yields:
[root@dellap netctl]# netctl start Wireless2
Job for netctl@Wireless2.service failed because the control process exited with error code.
See "systemctl status netctl@Wireless2.service" and "journalctl -xe" for details.journalctl -xe yields:
Mar 17 12:08:10 dellap systemd[1]: Starting Networking for netctl profile Wireless2...
-- Subject: Unit netctl@Wireless2.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@Wireless2.service has begun starting up.
Mar 17 12:08:10 dellap network[4647]: Starting network profile 'Wireless2'...
Mar 17 12:08:10 dellap network[4647]: The interface of network profile 'Wireless2' is already up
Mar 17 12:08:10 dellap systemd[1]: netctl@Wireless2.service: Main process exited, code=exited, status=1/FAILURE
Mar 17 12:08:10 dellap systemd[1]: netctl@Wireless2.service: Failed with result 'exit-code'.
Mar 17 12:08:10 dellap systemd[1]: Failed to start Networking for netctl profile Wireless2.
-- Subject: Unit netctl@Wireless2.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@Wireless2.service has failed.
--
-- The result is RESULT.and
netctl@Wireless2.service - Networking for netctl profile Wireless2
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2018-03-17 12:13:51 CDT; 11min ago
Docs: man:netctl.profile(5)
Process: 4684 ExecStart=/usr/lib/netctl/network start Wireless2 (code=exited, status=1/FAILURE)
Main PID: 4684 (code=exited, status=1/FAILURE)
Mar 17 12:13:51 dellap systemd[1]: Starting Networking for netctl profile Wireless2...
Mar 17 12:13:51 dellap network[4684]: Starting network profile 'Wireless2'...
Mar 17 12:13:51 dellap network[4684]: The interface of network profile 'Wireless2' is already up
Mar 17 12:13:51 dellap systemd[1]: netctl@Wireless2.service: Main process exited, code=exited, status=1/FAILURE
Mar 17 12:13:51 dellap systemd[1]: netctl@Wireless2.service: Failed with result 'exit-code'.
Mar 17 12:13:51 dellap systemd[1]: Failed to start Networking for netctl profile Wireless2.I execute "netctl stop Wireless2" and there is no output, but starting it again yields the same results as before- the journal showing an error because Wireless2 is already up. Is there a way to bring it down so that this will work? I don't see any other relevant info in there.
Also:
[root@dellap netctl]# systemctl list-unit-files --state=enabled
UNIT FILE STATE
acpid.service enabled
autovt@.service enabled
getty@.service enabled
remote-fs.target enabled
4 unit files listed.Last edited by Don Coyote (2018-03-19 14:49:13)
Offline
Netctl requires the interface to be down before it is started...
ip link set <interface> downOffline
I had also done:
[root@dellap netctl]# ip link set wlp12s0 downbut the results are the same.
Offline
How can the results be "the same"?
The original complaint is about the interface being "up" (and stopping the profile won't work, because it's not active itfp)
The initial sin is "I brought it up with no error", so unless there's another network managing service running, you should be able to successfully bring it down (check whether it worked) and then the particular error should not occur (what doesn't mean there could be no other issue, but that would to be a different error as well)
Offline
Results were the same at the time, starting the profile produced an error and the journal showed the same line saying that the interface was already up.
However, upon reboot the wireless connection came up automatically and seems to be working fine.
Offline
Pages: 1