You are not logged in.
EDIT : The faulty part was wpa_supplicant, making almost all the network managers I used not working. TL;DR : Temporary fix : installing wpa_suplicant-git from AUR
Hello folks,
So, my Intel 6205 card cannot connect to Wifi network with netctl.
Everytime I launch a wireless netctl profile, it crashes. I have no issue using it with my wired profiles.
Wifi-menu is not able to scan anything.
I can set the card up and scan with iwlist without issue and Windows 10 has no issue using the card.
Issue appeared after I booted from Windows 10 then come back to Arch this morning. Was working without issue this morning and yesterday and I didn't do an update with pacman since a few days.
Here's the output of "systemctl status netctl@wlp6s0\\x2dVIDEOTRON5429_5GHz.service" after I tried "netctl start videotron5429_5GHz"
netctl@wlp6s0\x2dVIDEOTRON5429_5GHz.service - Networking for netctl profile wlp6s0-VIDEOTRON5429_5GHz
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-02-23 11:44:37 EST; 3min 12s ago
Docs: man:netctl.profile(5)
Process: 4187 ExecStart=/usr/lib/netctl/network start wlp6s0-VIDEOTRON5429_5GHz (code=exited, status=1/FAILURE)
Main PID: 4187 (code=exited, status=1/FAILURE)
Feb 23 11:44:36 cronos systemd[1]: Starting Networking for netctl profile wlp6s0-VIDEOTRON5429_5GHz...
Feb 23 11:44:36 cronos network[4187]: Starting network profile 'wlp6s0-VIDEOTRON5429_5GHz'...
Feb 23 11:44:36 cronos network[4187]: /usr/lib/netctl/globals: line 68: 4196 Segmentation fault (core dumped) "$@"
Feb 23 11:44:37 cronos network[4187]: The WPA supplicant did not start for interface 'wlp6s0'
Feb 23 11:44:37 cronos network[4187]: Failed to bring the network up for profile 'wlp6s0-VIDEOTRON5429_5GHz'
Feb 23 11:44:37 cronos systemd[1]: netctl@wlp6s0\x2dVIDEOTRON5429_5GHz.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 11:44:37 cronos systemd[1]: netctl@wlp6s0\x2dVIDEOTRON5429_5GHz.service: Failed with result 'exit-code'.
Feb 23 11:44:37 cronos systemd[1]: Failed to start Networking for netctl profile wlp6s0-VIDEOTRON5429_5GHz.
What I can do or should do ?
I'll try using another network manager real soon to be able to work wherever I go, but I really prefer netctl.
Last edited by CPU Gastronomy (2018-02-26 11:53:40)
Offline
Still haven't figured out how to solve this.
Here are some more infos :
I did a full system upgrade through pacman this morning, but issue still here.
When I booted from USB to solve another small issue, I did not have issue to connect to a wifi access point. The key was made back in december though.
I tried debugging all that, but I don't know really know how to do that. I tried using gdb and bash -x, but got nothing useful
Offline
Offline
Hey Seth,
When I switch back to Archlinux, I litterally swap hard drives on my laptop after doing a real shutdown of Windows 10.
Even if I wasn't turning it off completly, that doesn't change anything that only netctl with my wifi is not working on my system (but others network managers are fine) and was able to use it when I booted Arch Linux from USB.
Last edited by CPU Gastronomy (2018-02-24 18:16:40)
Offline
The HD would not matter here, the (any) device may be left in an inconsistent state during hibernation (what "fastboot" actually is)
Reading the failing script: Try another profile name (one w/o a dash)
Offline
As I said : I turned off completly Windows 10, avoiding hibernation/fastboot, my Windows 10 is already setted up like this and when I booted on an Archlinux usb media, netctl had no issue.
I tried with another profile without a dash in it and I got the same segmentation fault error.
I just swapped my intel wifi card with another one; same error.
Offline
This is not (directly) about the WIFI chip - what crashes it a shell script when expanding variables.
pacman -Qkk bash
/bin/bash --version
Offline
Here are the outputs :
pacman -Qkk bash
bash: 235 total files, 0 altered files
bash --version
GNU bash, version 4.4.19(1)-release (x86_64-unknown-linux-gnu)
Last edited by CPU Gastronomy (2018-02-25 21:17:23)
Offline
Well, I cannot manage to scan or anything with NetworkManager and Connman. Wicd, I can scan, but always bad password error whatever I do.
And when I try to start wpa_supplicant by hand like in the wiki, I get a segmentation fault.
Pretty sure it's related.
Will look more into that.
#cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/run/wpa_supplicant
update_config=1
#wpa_supplicant -B -i wlp6s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
[1] 20843 segmentation fault wpa_supplicant -B -i wlp6s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Last edited by CPU Gastronomy (2018-02-26 11:12:59)
Offline
I installed wpa_supplicant-git from the AUR and it solved my issue.
So the original wpa_supplicant was the faulty part, I don't know why. I'll update my post title.
Should I file a bug report for that or something ?
Offline
Don't file a bug report until you do some investigation.
At *very* least don't background wpa_supplicant. Run it in the foreground and watch the output (post it here). The add one or two debug flags. Then perhaps an strace.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline