You are not logged in.

Pages: 1

#1 2017-06-03 22:49:36

mfurquim
Member
From: Brazil
Registered: 2016-05-23
Posts: 11

[SOLVED] Issues connecting to network

Hi, my first post here.
Don't know whether to post here or at Laptop Issues, but here I go.

Few weeks ago I could connect to the internet using wifi-menu, but now it doesn't even identify wireless connections around.

$ sudo wifi-menu
Scanning for networks... failed
No networks found

I tried connecting to a manually configured network that I had already connected before, but with no luck.

$ sudo systemctl start netctl@unb_wireless
Job for netctl@unb_wireless.service failed because the control process exited with error code.
See "systemctl status netctl@unb_wireless.service" and "journalctl -xe" for details.

I can connect using dhcpcd though, while the ethernet cable is attached.

$ sudo dhcpcd -n eth0

The only thing I can think of is that something happend when I updated the system;

$ sudo pacman -Syu

Does anyone have seen this before? Or have any ideas of what the problem might be?
Any help would be appreciated.

Last edited by mfurquim (2017-06-11 13:18:05)

Mateus Furquim

Offline

#2 2017-06-03 22:53:09

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,722

Re: [SOLVED] Issues connecting to network

Welcome to Arch Linux.   Let us start with a sanity check.
What are the output of uname -a and pacman -Q linux   ?
Do the version numbers match?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2017-06-03 22:58:32

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] Issues connecting to network

mfurquim wrote:
Job for netctl@unb_wireless.service failed because the control process exited with error code.
See "systemctl status netctl@unb_wireless.service" and "journalctl -xe" for details.

And what are those error codes?



Moving to NC...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#4 2017-06-04 00:56:01

mfurquim
Member
From: Brazil
Registered: 2016-05-23
Posts: 11

Re: [SOLVED] Issues connecting to network

ewaller wrote:

Welcome to Arch Linux.

Thanks =]

ewaller wrote:

What are the output of uname -a and pacman -Q linux?
Do the version numbers match?

Yes, they do.

$ uname -a
Linux inspiron5452 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux
$ pacman -Q linux
linux 4.10.13-1

Mateus Furquim

Offline

#5 2017-06-04 01:13:34

mfurquim
Member
From: Brazil
Registered: 2016-05-23
Posts: 11

Re: [SOLVED] Issues connecting to network

jasonwryan wrote:
mfurquim wrote:
Job for netctl@unb_wireless.service failed because the control process exited with error code.
See "systemctl status netctl@unb_wireless.service" and "journalctl -xe" for details.

And what are those error codes?

The journalctl -xe command doesn't seem do have any meaningful information about the failure to connect to network.
These are the most recent activities, and there are no mentions about network before those.

$ journalctl -xe
Jun 03 21:35:02 inspiron5452 dbus-daemon[452]: Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.
Jun 03 21:35:02 inspiron5452 systemd[432]: Starting XFCE notifications service...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Jun 03 21:35:02 inspiron5452 dbus-daemon[452]: Successfully activated service 'org.freedesktop.Notifications'
Jun 03 21:35:02 inspiron5452 systemd[432]: Started XFCE notifications service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jun 03 22:08:27 inspiron5452 polkit-agent-helper-1[4168]: pam_unix(polkit-1:auth): authentication failure; logname= uid=1000 euid=0 tty=
lines 2220-2258/2258 (END)

The status error in netctl:

$ systemctl status netctl@unb_wireless.service
● netctl@unb_wireless.service - Networking for netctl profile unb_wireless
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-06-03 19:47:56 -03; 2h 8min ago
     Docs: man:netctl.profile(5)
  Process: 2228 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 2228 (code=exited, status=1/FAILURE)

Last edited by mfurquim (2017-06-04 01:15:25)

Mateus Furquim

Offline

#6 2017-06-04 01:21:24

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] Issues connecting to network

journalctl _PID=2228

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#7 2017-06-04 01:32:40

mfurquim
Member
From: Brazil
Registered: 2016-05-23
Posts: 11

Re: [SOLVED] Issues connecting to network

jasonwryan wrote:
journalctl _PID=2228

$ sudo journalctl _PID=2228
-- Logs begin at Fri 2016-11-18 19:34:02 -02, end at Sun 2236-04-24 22:41:55 -03. --
Jun 03 19:47:51 inspiron5452 network[2228]: Starting network profile 'unb_wireless'...
Jun 03 19:47:56 inspiron5452 network[2228]: Failed to bring the network up for profile 'unb_wireless'

I deleted my journal because it had some entries from years greater than 2200. So that's weird.
I re-ran the command to connect and (as expeceted) still didn't go through.
Here are the details.

$ sudo systemctl start netctl@unb_wireless
Job for netctl@unb_wireless.service failed because the control process exited with error code.
See "systemctl status netctl@unb_wireless.service" and "journalctl -xe" for details.

$ systemctl status netctl@unb_wireless.service
● netctl@unb_wireless.service - Networking for netctl profile unb_wireless
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2017-06-04 01:10:12 -03; 8min ago
     Docs: man:netctl.profile(5)
  Process: 8035 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 8035 (code=exited, status=1/FAILURE)

$ sudo journalctl _PID=8035
-- Logs begin at Sun 2017-06-04 01:10:12 -03, end at Sun 2017-06-04 01:19:30 -03. --
Jun 04 01:10:12 inspiron5452 network[8035]: Starting network profile 'unb_wireless'...
Jun 04 01:10:12 inspiron5452 network[8035]: Could not create a wpa config file for interface 'wlan0'
Jun 04 01:10:12 inspiron5452 network[8035]: Failed to bring the network up for profile 'unb_wireless'

$ sudo journalctl -xe
-- Logs begin at Sun 2017-06-04 01:10:12 -03, end at Sun 2017-06-04 01:11:26 -03. --
Jun 04 01:10:12 inspiron5452 sudo[8031]: mfurquim : TTY=pts/1 ; PWD=/home/mfurquim/projects/tcc/doc ; USER=root ; COMMAND=/usr/bin/syste
Jun 04 01:10:12 inspiron5452 systemd[1]: Starting Networking for netctl profile unb_wireless...
-- Subject: Unit netctl@unb_wireless.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@unb_wireless.service has begun starting up.
Jun 04 01:10:12 inspiron5452 sudo[8031]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 04 01:10:12 inspiron5452 network[8035]: Starting network profile 'unb_wireless'...
Jun 04 01:10:12 inspiron5452 network[8035]: Could not create a wpa config file for interface 'wlan0'
Jun 04 01:10:12 inspiron5452 network[8035]: Failed to bring the network up for profile 'unb_wireless'
Jun 04 01:10:12 inspiron5452 systemd[1]: netctl@unb_wireless.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 01:10:12 inspiron5452 systemd[1]: Failed to start Networking for netctl profile unb_wireless.
-- Subject: Unit netctl@unb_wireless.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@unb_wireless.service has failed.
-- 
-- The result is failed.
Jun 04 01:10:12 inspiron5452 systemd[1]: netctl@unb_wireless.service: Unit entered failed state.
Jun 04 01:10:12 inspiron5452 systemd[1]: netctl@unb_wireless.service: Failed with result 'exit-code'.
Jun 04 01:10:12 inspiron5452 sudo[8031]: pam_unix(sudo:session): session closed for user root

Do you have any lead jasonwryan?
I really appreciate your help guys smile

Last edited by mfurquim (2017-06-04 04:21:55)

Mateus Furquim

Offline

#8 2017-06-04 07:51:35

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,887

Re: [SOLVED] Issues connecting to network

Could not create a wpa config file for interface 'wlan0'

ip addr
lspci
lspci -v
lsusb

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2017-06-08 12:44:44

mfurquim
Member
From: Brazil
Registered: 2016-05-23
Posts: 11

Re: [SOLVED] Issues connecting to network

Sorry for the delay.

So this is me trying to connect.

The $ ip a command is to show the eth0 (physical interface) and wlan0 (wireless interface).

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f4:8e:38:e5:59:cf brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 40:49:0f:fd:12:53 brd ff:ff:ff:ff:ff:ff

$ sudo systemctl start netctl@unb_wireless trying to connect via a wireless connection that I could connect before.

$ sudo systemctl start netctl@unb_wireless
Job for netctl@unb_wireless.service failed because the control process exited with error code.
See "systemctl status netctl@unb_wireless.service" and "journalctl -xe" for details.

It fails, so I used $ sudo systemctl status netctl@unb_wireless.service as @jasonwryan sugested.

jasonwryan wrote:
mfurquim wrote:
Job for netctl@unb_wireless.service failed because the control process exited with error code.
See "systemctl status netctl@unb_wireless.service" and "journalctl -xe" for details.

And what are those error codes?

$ sudo systemctl status netctl@unb_wireless.service
● netctl@unb_wireless.service - Networking for netctl profile unb_wireless
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2017-06-07 13:10:24 -03; 8s ago
     Docs: man:netctl.profile(5)
  Process: 891 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 891 (code=exited, status=1/FAILURE)

Jun 07 13:10:24 inspiron5452 systemd[1]: Starting Networking for netctl profile unb_wireless...
Jun 07 13:10:24 inspiron5452 network[891]: Starting network profile 'unb_wireless'...
Jun 07 13:10:24 inspiron5452 network[891]: Could not create a wpa config file for interface 'wlan0'
Jun 07 13:10:24 inspiron5452 network[891]: Failed to bring the network up for profile 'unb_wireless'
Jun 07 13:10:24 inspiron5452 systemd[1]: netctl@unb_wireless.service: Main process exited, code=exited, status=1/FAILURE
Jun 07 13:10:24 inspiron5452 systemd[1]: Failed to start Networking for netctl profile unb_wireless.
Jun 07 13:10:24 inspiron5452 systemd[1]: netctl@unb_wireless.service: Unit entered failed state.
Jun 07 13:10:24 inspiron5452 systemd[1]: netctl@unb_wireless.service: Failed with result 'exit-code'.

And $ sudo journalctl _PID=891, as I learned with him as well. Thanks for that smile

$ sudo journalctl _PID=891
-- Logs begin at Sun 2017-06-04 01:10:12 -03, end at Wed 2017-06-07 13:10:44 -03. --
Jun 07 13:10:24 inspiron5452 network[891]: Starting network profile 'unb_wireless'...
Jun 07 13:10:24 inspiron5452 network[891]: Could not create a wpa config file for interface 'wlan0'
Jun 07 13:10:24 inspiron5452 network[891]: Failed to bring the network up for profile 'unb_wireless'

Right now, I connected via $ sudo dhcpcd -n eth0, that's why I have an IP address on eth0.
But here it is what @seth requested. It is a bit long, though.

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f4:8e:38:e5:59:cf brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.10/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::e79d:f785:5bdb:22f6/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 40:49:0f:fd:12:53 brd ff:ff:ff:ff:ff:ff


$ lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
06:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07)


$ lspci -v
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
	Subsystem: Dell Device 06ae
	Flags: bus master, fast devsel, latency 0
	Capabilities: <access denied>
	Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Dell Device 06ae
	Flags: bus master, fast devsel, latency 0, IRQ 46
	Memory at f6000000 (64-bit, non-prefetchable) [size=16M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
	Subsystem: Dell Device 06ae
	Flags: bus master, fast devsel, latency 0, IRQ 47
	Memory at f7214000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI])
	Subsystem: Dell Device 06ae
	Flags: bus master, medium devsel, latency 0, IRQ 42
	Memory at f7200000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
	Subsystem: Dell Device 06ae
	Flags: bus master, fast devsel, latency 0, IRQ 44
	Memory at f721c000 (64-bit, non-prefetchable) [size=32]
	Capabilities: <access denied>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
	Subsystem: Dell Device 06ae
	Flags: bus master, fast devsel, latency 32, IRQ 45
	Memory at f7210000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 00002000-00002fff [size=4K]
	Memory behind bridge: df800000-df9fffff [size=2M]
	Prefetchable memory behind bridge: 00000000dfa00000-00000000dfbfffff [size=2M]
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
	I/O behind bridge: None
	Memory behind bridge: f7100000-f71fffff [size=1M]
	Prefetchable memory behind bridge: None
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
	I/O behind bridge: 0000e000-0000efff [size=4K]
	Memory behind bridge: f7000000-f70fffff [size=1M]
	Prefetchable memory behind bridge: 00000000f0000000-00000000f00fffff [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
	I/O behind bridge: None
	Memory behind bridge: None
	Prefetchable memory behind bridge: None
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) (prog-if 20 [EHCI])
	Subsystem: Dell Device 06ae
	Flags: bus master, medium devsel, latency 0, IRQ 21
	Memory at f721a000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
	Subsystem: Dell Device 06ae
	Flags: bus master, medium devsel, latency 0
	Capabilities: <access denied>
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich

00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) (prog-if 01 [AHCI 1.0])
	Subsystem: Dell Device 06ae
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 43
	I/O ports at f0b0 [size=8]
	I/O ports at f0a0 [size=4]
	I/O ports at f090 [size=8]
	I/O ports at f080 [size=4]
	I/O ports at f060 [size=32]
	Memory at f7219000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
	Subsystem: Dell Device 06ae
	Flags: medium devsel, IRQ 18
	Memory at f7218000 (64-bit, non-prefetchable) [size=256]
	I/O ports at f040 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

06:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
	Subsystem: Dell Device 020e
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at f7100000 (64-bit, non-prefetchable) [size=512K]
	Expansion ROM at f7180000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: ath9k
	Kernel modules: ath9k

07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07)
	Subsystem: Dell Device 06ae
	Flags: bus master, fast devsel, latency 0, IRQ 48
	I/O ports at e000 [size=256]
	Memory at f7000000 (64-bit, non-prefetchable) [size=4K]
	Memory at f0000000 (64-bit, prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169


$ lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 005: ID 0cf3:e005 Qualcomm Atheros Communications
Bus 002 Device 002: ID 064e:920b Suyin Corp.
Bus 002 Device 008: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 007: ID 258a:0001
Bus 002 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Mateus Furquim

Offline

#10 2017-06-08 14:41:52

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,887

Re: [SOLVED] Issues connecting to network

rfkill list

You've an atheros chip in pci and usb, is your wifi a dongle or integrated? one might be wifi and the other one bluetooth, and you could try (disabling it) btcoex_enable=0
Also, if rfkill is unspecific, try "ps_enable=0"

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2017-06-10 22:10:25

mfurquim
Member
From: Brazil
Registered: 2016-05-23
Posts: 11

Re: [SOLVED] Issues connecting to network

seth wrote:
rfkill list
$ rfkill list 
0: phy0: Wireless LAN
	Soft blocked: yes
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
seth wrote:

You've an atheros chip in pci and usb, is your wifi a dongle or integrated?

It is an integrated wifi. I do not have any dongle.
The only things that are connected via usb are my keyboard and mouse (over an usb hub).

seth wrote:

one might be wifi and the other one bluetooth, and you could try (disabling it) btcoex_enable=0
Also, if rfkill is unspecific, try "ps_enable=0"

I'm sorry, but I did not get it.

From what I serched, ps_enable font=0
Enable wifi-BT coexistence (int), is it correct?.
I actually have never used the bluetooth on this laptop (I didn't even know it had bluetooth).

And the btcoex_enable=0
- The ps_enable=0 option disables power saving mode, or
- ps_enable=0 reduce power usage, might cause freezes and dropouts.
I don't see how this can help, but I've done it nevertheless.

Still, when I try to connect, 

$ sudo wifi-menu 
Scanning for networks... failed
No networks found

This is so weird. I can't find ANY wireless network around, and I know there are many sad

Mateus Furquim

Offline

#12 2017-06-11 06:51:46

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,887

Re: [SOLVED] Issues connecting to network

sudo rfkill unblock phy0
rfkill list

Does "Soft blocked" turn "no"? And does scanning suddenly work?

modinfo ath9k | grep -E '^parm:'

https://wiki.archlinux.org/index.php/Ke … le_options

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2017-06-11 13:13:41

mfurquim
Member
From: Brazil
Registered: 2016-05-23
Posts: 11

Re: [SOLVED] Issues connecting to network

seth wrote:
sudo rfkill unblock phy0
rfkill list
$ sudo rfkill list 
0: phy0: Wireless LAN
	Soft blocked: yes
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no

$ sudo rfkill unblock phy0
Bogus unblock argument 'phy0'.

That didn't work, but then I tried 0 instead of 'phy0' and it worked! big_smile
I can't believe it.

$ sudo rfkill unblock 0

$ sudo rfkill list 
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
seth wrote:

Does "Soft blocked" turn "no"? And does scanning suddenly work?

Yes! It did big_smile
The sudo wifi-menu works now.



This is pretty cool, thanks your time guys (@jasonwryan and @ewaller), specially you @seth.
I really appreciate it. I sure did learn a lot with this.

Btw, here it is the last command you requested.

$ sudo modinfo ath9k | grep -E '^parm:'
parm:           debug:Debugging mask (uint)
parm:           nohwcrypt:Disable hardware encryption (int)
parm:           blink:Enable LED blink on activity (int)
parm:           led_active_high:Invert LED polarity (int)
parm:           btcoex_enable:Enable wifi-BT coexistence (int)
parm:           bt_ant_diversity:Enable WLAN/BT RX antenna diversity (int)
parm:           ps_enable:Enable WLAN PowerSave (int)

Last edited by mfurquim (2017-06-11 13:15:06)

Mateus Furquim

Offline

#14 2017-06-11 13:28:00

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,887

Re: [SOLVED] Issues connecting to network

Cool.
That's btw. not been a request but just more teaching about module parameters ;-)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB