| View previous topic :: View next topic |
| Author |
Message |
Cleverson
n00b
Joined: 11 Jun 2020
Posts: 9
Location: Brasil
|
 Posted: Fri Sep 25, 2020 10:22 pm Post subject: Wireless: Can't connect; tried a few things, results here... |
 |
|
Hi all,
I consider myself to be not even at an intermediate level regarding network subjects, so I'm asking help here:
I have an HP 246g-7 laptop, which I'm trying to connect to a router via wi-fi. My environment is a pure console, with openRC as the init system. I'm trying to connect at the command line, with dhcpcd at its defaults.
The laptop's wi-fi card is Intel's, and has been propperly detected already, as can be seen in this lspci output:
| Code: | Clev-HP /home/clevlim # lspci -nnkv | sed -n '/Network/,/^$/p'
02:00.0 Network controller [0280]: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:24fb] (rev 10)
Subsystem: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:2110]
Flags: bus master, fast devsel, latency 0, IRQ 128
Memory at b1000000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-5e-37-ff-ff-fd-68-e4
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi |
The card seems propperly initialized, as can be seen in this dmesg output:
| Code: | Clev-HP /home/clevlim # dmesg | grep -i -E '02:00.0|wlp|iwl|80211'
[ 0.374560] pci 0000:02:00.0: [8086:24fb] type 00 class 0x028000
[ 0.374665] pci 0000:02:00.0: reg 0x10: [mem 0xb1000000-0xb1001fff 64bit]
[ 0.375066] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[ 2.834478] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 2.843975] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 2.865493] iwlwifi 0000:02:00.0: loaded firmware version 29.163394017.0 op_mode iwlmvm
[ 2.884706] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 3168, REV=0x220
[ 2.906169] iwlwifi 0000:02:00.0: base HW address: e4:5e:37:fd:68:e4
[ 2.936540] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 2.937653] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[ 3.739517] iwlwifi 0000:02:00.0: BIOS contains WGDS but no WRDS |
When I issue an ip link command, it indicates that the corresponding interface is DOWN, as follows:
| Code: | Clev-HP /home/clevlim # ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether b0:5c:da:9c:70:ab brd ff:ff:ff:ff:ff:ff
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
4: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether e4:5e:37:fd:68:e4 brd ff:ff:ff:ff:ff:ff |
Issuing ip link set dev wlp2s0 up gives no output, but doesn't change anything at all in the result above. Neither explicitly starting the interface's service changes anything:
| Code: | Clev-HP /home/clevlim # rc-service net.wlp2s0 restart
net.wlp2s0 | * Bringing up interface wlp2s0
net.wlp2s0 | * Caching network module dependencies
net.wlp2s0 | * Starting wpa_supplicant on wlp2s0 ...
net.wlp2s0 |Successfully initialized wpa_supplicant [ ok ]net.wlp2s0 | * Starting wpa_cli on wlp2s0 ... [ ok ]net.wlp2s0 | * Backgrounding ... ...
net.wlp2s0 | * WARNING: net.wlp2s0 has started, but is inactive |
The contents of my /etc/conf.d/net file is:
| Code: | | modules="wpa_supplicant" |
As for /etc/wpa-supplicant/wpa-supplicant.conf, I had hadded my connection's data, but it didn't work, so I commented it out in order to try wpa-cli:
| Code: | ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
#ap_scan=1
#network={
# ssid="Clev-WF_5GHz"
# psk="password"
#} |
Then wpa-cli went as follows (wiping out irrelevant information):
| Code: | Selected interface 'wlp2s0'
Interactive mode
> scan
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
> scan_results
bssid / frequency / signal level / flags / ssid
54:a6:5c:90:d0:3f 2437 -57 [WPA-PSK-CCMP][WPA2-PSK-CCMP][ESS] CLEV-WF_2.4GHz
54:a6:5c:90:d0:40 5260 -79 [WPA2-PSK-CCMP][ESS] CLEV-WF_5GHz
> add_network
0
> set_network 0 ssid "Clev-WF_2.4GHz"
OK
> set_network 0 psk "password"
OK
> enable_network 0
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
> quit |
I don't know what this "CTRL-EVENT-NETWORK-NOT-FOUND" means exactly, but the connection was not established:
FYI, I have already set rc_depend_strict="NO" at /etc/rc.conf.
In case it helps, here is the ifconfig -a output:
| Code: | Clev-HP /home/clevlim # ifconfig -a
enp1s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b0:5c:da:9c:70:ab txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Loopback Local)
RX packets 8 bytes 592 (592.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 592 (592.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1000 (IPv6 sobre IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e4:5e:37:fd:68:e4 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
I have checked, and there is no blocked devices:
| Code: | Clev-HP /home/clevlim # rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no |
Any hint please?
Thanks,
_________________
Cleverson |
|
| Back to top |
|
 |
RayDude
Advocate
Joined: 29 May 2004
Posts: 2093
Location: San Jose, CA
|
| Posted: Sat Sep 26, 2020 4:35 pm Post subject: |
|
|
Is there a BIOS controlled or physical enable/disable switch on the wifi? Has it been disabled outside the OS?
_________________
Some day there will only be free software. |
|
| Back to top |
|
|
Cleverson
n00b
Joined: 11 Jun 2020
Posts: 9
Location: Brasil
|
| Posted: Sat Sep 26, 2020 4:49 pm Post subject: |
|
|
Hi, no, wi-fi works fine in other OSes. I'm able for example to boot into an Ubuntu Mate live image and update the Gentoo installation from within chroot. That's how I installed Gentoo in the first place.
thanks for answering anyways.
_________________
Cleverson |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54822
Location: 56N 3W
|
| Posted: Sat Sep 26, 2020 7:59 pm Post subject: |
|
|
Cleverson,
Please don't filter logs, except to redact sensitive information. That should be rare too.
What should be there and isn't is just as important as what is actually there.
If you expect wifi to start at boot, reboot and check.
If wifi did not start, try starting it by hand, Just once, however you like.
Now put all of dmesg onto a pastebin.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sat Sep 26, 2020 8:48 pm Post subject: |
|
|
| Cleverson wrote: | The contents of my /etc/conf.d/net file is:
Code:
modules="wpa_supplicant"
|
It appears you are using gentoo's default wifi setup as in https://wiki.gentoo.org/wiki/Netifrc .
I've been using DHCPCD style networking for long enough to have lost a step but think /etc/conf.d/net needs more content - specifically
config_wlp2s0="dhcp" (presuming for a notebook, static ip may be specified) (dns _servers=" ip ip ..." may be specified)
In the old days putting wpa_supplicant in a run level was wrong, the assorted network managers including gentoo default networking wanted to start wpa_supplicant themselves and would fail if it was found running.
dhcpcd should not be in a run level if gentoo default networking is to be used as it will attempt to run as a network manager and conflict will result.
net.wlp2s0 symlink exists?
_________________
Defund the FCC. |
|
| Back to top |
|
|
Cleverson
n00b
Joined: 11 Jun 2020
Posts: 9
Location: Brasil
|
| Posted: Sun Sep 27, 2020 1:04 am Post subject: |
|
|
Thank you all for helping out.
I didn't know that case-sensitivity matters for the SSID. Actually, when I've set up the connection's name (i.e. SSID), I wasn't on a Linux system, but on Windows, which doesn't care for case-sensitivity. So, I've set the SSID as "Clev-WF", but on Linux, it appears I must respect the way wpa_supplicant displays it, which is "CLEV-WF".
It's working now.
_________________
Cleverson |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
