You are not logged in.

#1 2017-01-17 00:46:53

AP-random472
Member
Registered: 2017-01-16
Posts: 18

Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

Hi everyone. This is my first post (cry for help) on this forum. I have been very reluctant to ask this question as I have been using Arch for about 3 months now, having installed it a number of times across 4 different computers and without fail every problem I have ever had I have found a solution for by just reading more: and primarily from this forum. I can also see some clear probable error messages and I apologise in advance for wasting anyone's time. I'm just not sure which thread to follow and it's all a little beyond my current understanding of where to look next. I would like to say a quick little back-dated thank you for all the help I've indirectly had from previous posts smile

Anyway, here goes...

BACKGROUND

I am using a Dell XPS 13, 2016 model 9630. It is the i5, FHD non-touch with 8gb ram, 256gb pci-e SSD, but i doubt any of those make a difference.

Wireless adapter is internal: Killer 1535 Qualcomm Atheros QCA6174.

I am trying to install Arch linux from a bootable USB but I have been unable to connect to wireless networks. To be clear, all the below is happening from the live boot

I have tried 3 different wireless networks, but I get exactly the same result. All are WPA.

I have tired the following using the current ISO (2017.01.01) and also ISO (2016.11.01). Again, I see exactly the same output in each case.

I tried using the older ISO as a double check that nothing has changed in the latest kernel / whatever else.

Frustratingly, as far as my little google legs can carry me, nobody appears to be having such a basic issue with this hardware set up. In fact, the wiki page for this model reports no issues.

CONNECTION ATTEMPTS AND OUTPUT

I usually use wpa_supplicant, but when this didn't work I also tried using wifi-menu. I'll show the output of both approaches below. However you pretty much get to see the same errors in slightly different format / order. I am copying all this stuff out from photos I took from the screen so please excuse typos.. I also do it all for completeness despite the repetition. I've replaced some repetitive or verbose things that don't look important (such as time and date stamps)

1. Checking if network adapter appears to work...

ip link reports normal looking stuff, and I can also scan for SSIDs using iw

# ip link set wlp58s0 up
#iw dev wlp58s0 scan | grep SSID
   SSID: NETWORK1
   SSID: NETWORK2

2. Checking hardware / drivers at boot

I'm not an expert here, but I believe the following shows that it has trouble finding firmware but that it then falls back to something and loads up OK. I suspect if anything this could be the area where I am not doing my research properly but the reason I have moved on is that I found examples of other people having issues with this network adapter, and when they pointed to this firmware loading, they were told it was OK (and subsequently their issues were found elsewhere)

The below I get from journlactl -b

archiso kernel: ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-oooo:3a:00.0.bin failed with error -2
archiso kernel: ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2
archiso kernel: ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
archiso kernel: ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware.bin': -2
archiso kernel: ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
archiso kernel: ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
archiso kernel: ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [is this the successful fall back??]
archiso kernel: ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7

3. Trying to connect using wpa_supplicant

wpa_supplicant -D n180211,wext -i wlp58s0 -c<(wpa_passphrase "NETWORK1" "PASSWORD")

Note: I have also simplifed to wpa_supplicant -i wlp58s0 -c<(wpa_passphrase "NETWORK1" "PASSWORD"), with no change in effect (diff output to console, log same/similar issues)

Console Output:

Successfully Initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
wlp58s0: Trying to associate with 55:96:82:29:1b:66 (SSID='NETWORK1' freq=2412 Mhz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp58s0: Association request to the driver failed
wlp58s0: Authentication with 55:96:82:29:1b:66 timed out
ioctl[SIOCSIWMLME]: Transport endpoint is not connected
wlp58s0: CTRL_EVENT_DISCONNECTED bssid=55:96:82:29:1b:66 reason=3 locally_generated=1

Journalctl -xe output:

archiso kernel: IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
archiso kernel: wlp58s0: authenticate with 55:96:82:29:1b:66 (try 1/3)
archiso kernel: wlp58s0: authenticate with 55:96:82:29:1b:66 (try 2/3)
archiso kernel: wlp58s0: authenticate with 55:96:82:29:1b:66 (try 3/3)
archiso kernel: wlp58s0: authentication with 55:96:82:29:1b:66 timed out
archiso kernel: ath10k_pci 0000:3a:00.0: failed to flush transmit queue (skip 0 ar-state 1):0

Clearly from the above I can see that the "link is not ready" and the "device is busy", but I am not sure what I can do from here. I also note the 'Invalid Argument' lines but to be honest i always seem to have got those on other machines..

4. Trying using wifi-menu

Note: Between all these attempts I have rebooted into a clean live USB session. I am aware that using different network programmes can cause issues with hardware access

wifi-menu finds the networks OK, and I enter the password, and then I get a blank screen with blinking '_' before it fails out. I am advised then to check both systemctl status as well as journalctl -xe. I have copied them out below:

The output / errors here seem consistent with the wpa_supplicant approach

JOURNALCTL -XE

..........[long name string path-like] Broadband.service has begun starting up
archiso network[1391]: Starting network profile 'PROFILENAME' .
archiso kernel: IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready..
archiso kernel: wlp58s0: authenticate with 55:96:82:29:1b:66
archiso kernel: wlp58s0: send auth to 55:96:82:29:1b:66 (try 1/3)
archiso kernel: wlp58s0: send auth to 55:96:82:29:1b:66 (try 2/3)
archiso kernel: wlp58s0: send auth to 55:96:82:29:1b:66 (try 3/3)
archiso kernel: ath10k_pci 0000:3a:00.0: failed to flush transmit queue (skip 0 ar-state 1):0
archiso kernel: wlp58s0: authentication with 55:96:82:29:1b:66 timed out
archiso network[1391]: WPA association/authentication failed for interface 'wlp58s0'
archiso kernel: wlp58s0: aborting authenication with 55:96:82:29:1b:66 by local choice (reason: 3=DEAUTH_LEAVING)
archiso kernel: ath10k_pci 0000:3a:00.0: failed to flush transmit queue (skip 0 ar-state 1):0
archiso network[1391]: Failed to bring the network up for profile 'NETWORK1'
...[long name string path-like].. Broadband.service has failed

SYSTEMCTL STATUS [long name string path-like]Broadband.service

[long name string path-like]Broadband.service  - Networking for netctl profile PROFILENAMEMADEINWIFIMENU
Loaded: loaded (/usr/lib/systemd/system/netctl@service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since DATETIME 22s ago
Docs: man:netctl.profile(5)
Process: 1391 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 1391 (code=exited, status=FAILURE)

DATETIME archiso systemd[1]: Starting Networking for netctl profile PROFILENAMEMADEINWIFIMENU ...
DATETIME archiso network[1391]: Starting network profile PRFILENAMEMADEINWIFIMENU ...
DATETIME archiso network[1391]: WPA association/authentication failed for interface 'wlp58s0'
DATETIME archiso network[1391]: Failed to bring the network up for profile PROFILENAMEMADEINWIFIMENU
DATETIME archiso systemd[1]: netctl@[Long name string path-like]Broadband.service: Main process exited, code=exited, status=1/FAILURE
DATETIME archiso network[1391]: Failed to start Networking for profile PROFILENAMEMADEINWIFIMENU
DATETIME archiso systemd[1]: netctl@[Long name string path-like]Broadband.service: Unit entered failed state
DATETIME archiso systemd[1]: netctl@[Long name string path-like]Broadband.service: Failed with result 'exit-code'

I want to stress I am definitely getting SSIDs and PASSPHRASES correct. I've connected other arch installs to these same networks with the approaches above fine.

Thank you so much to the person that points out my obvious mistake smile

For reference here is the page on the laptop

https://wiki.archlinux.org/index.php/Dell_XPS_13_(9360)

Last edited by AP-random472 (2017-01-18 08:50:52)

Offline

#2 2017-01-17 15:15:26

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 16,763

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

What are the output of
lspci -nn
ip link
and
iw list   ?

I've a feeling you are missing firmware for your device.

Last edited by ewaller (2017-01-17 15:15:42)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2017-01-17 15:31:13

AP-random472
Member
Registered: 2017-01-16
Posts: 18

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

Thanks! bear with me.. this is going to take me sometime to copy out.. might try and find another USB stick and save a text file down...

Last edited by AP-random472 (2017-01-17 21:15:34)

Offline

#4 2017-01-17 15:36:43

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 16,763

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

Do you have a wired network?    If so, you can use a tool like wgetpaste.
If not, you might consider USB tethering a phone.  Share your wireless on the phone over USB and it will appear to Arch as a wired network.  To use it, just run dhcpcd as root.  Might save you a bunch of work.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2017-01-17 15:50:39

AP-random472
Member
Registered: 2017-01-16
Posts: 18

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

deleted to tidy up thread

Last edited by AP-random472 (2017-01-17 21:05:46)

Offline

#6 2017-01-17 16:14:03

AP-random472
Member
Registered: 2017-01-16
Posts: 18

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

deleted to tidy up thread

Last edited by AP-random472 (2017-01-17 21:05:30)

Offline

#7 2017-01-17 16:56:16

AP-random472
Member
Registered: 2017-01-16
Posts: 18

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

Hi. After a bit of faffing which I've deleted for clarity, please see the output for each below. Thanks in advance for you thoughts.

lspci -nn

Third from the bottom looks like the network controller is OK?

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916] (rev 02)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 02)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1)
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d18] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d58] (rev 21)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71] (rev 21)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
3a:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
3c:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:0115] (rev 01)

ip link

Please note that is can ip link set wlp58s0 up and it changes it to 'up'

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp58s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 9c:b6:d0:11:51:01 brd ff:ff:ff:ff:ff:ff

iw list

I'm not sure how to read this but it worried me I couldn't find any reference to WPA?

Wiphy phy0
    max # scan SSIDs: 16
    max scan IEs length: 195 bytes
    max # sched scan SSIDs: 0
    max # match sets: 0
    max # scan plans: 1
    max scan plan interval: -1
    max scan plan iterations: 0
    Retry short limit: 7
    Retry long limit: 4
    Coverage class: 0 (up to 0m)
    Device supports RSN-IBSS.
    Device supports AP-side u-APSD.
    Device supports T-DLS.
    Supported Ciphers:
        * WEP40 (00-0f-ac:1)
        * WEP104 (00-0f-ac:5)
        * TKIP (00-0f-ac:2)
        * CCMP (00-0f-ac:4)
        * CMAC (00-0f-ac:6)
    Available Antennas: TX 0x3 RX 0x3
    Configured Antennas: TX 0x3 RX 0x3
    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * monitor
         * mesh point
         * P2P-client
         * P2P-GO
         * P2P-device
    Band 1:
        Capabilities: 0x19ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-15
        Bitrates (non-HT):
            * 1.0 Mbps
            * 2.0 Mbps (short preamble supported)
            * 5.5 Mbps (short preamble supported)
            * 11.0 Mbps (short preamble supported)
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 2412 MHz [1] (20.0 dBm)
            * 2417 MHz [2] (20.0 dBm)
            * 2422 MHz [3] (20.0 dBm)
            * 2427 MHz [4] (20.0 dBm)
            * 2432 MHz [5] (20.0 dBm)
            * 2437 MHz [6] (20.0 dBm)
            * 2442 MHz [7] (20.0 dBm)
            * 2447 MHz [8] (20.0 dBm)
            * 2452 MHz [9] (20.0 dBm)
            * 2457 MHz [10] (20.0 dBm)
            * 2462 MHz [11] (20.0 dBm)
            * 2467 MHz [12] (20.0 dBm) (no IR)
            * 2472 MHz [13] (20.0 dBm) (no IR)
            * 2484 MHz [14] (disabled)
    Band 2:
        Capabilities: 0x19ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-15
        VHT Capabilities (0x339071b2):
            Max MPDU length: 11454
            Supported Channel Width: neither 160 nor 80+80
            RX LDPC
            short GI (80 MHz)
            TX STBC
            SU Beamformee
            MU Beamformee
            RX antenna pattern consistency
            TX antenna pattern consistency
        VHT RX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT RX highest supported: 0 Mbps
        VHT TX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT TX highest supported: 0 Mbps
        Bitrates (non-HT):
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 5180 MHz [36] (30.0 dBm) (no IR)
            * 5200 MHz [40] (30.0 dBm) (no IR)
            * 5220 MHz [44] (30.0 dBm) (no IR)
            * 5240 MHz [48] (30.0 dBm) (no IR)
            * 5260 MHz [52] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5280 MHz [56] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5300 MHz [60] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5320 MHz [64] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5500 MHz [100] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5520 MHz [104] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5540 MHz [108] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5560 MHz [112] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5580 MHz [116] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5600 MHz [120] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5620 MHz [124] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5640 MHz [128] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5660 MHz [132] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5680 MHz [136] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5700 MHz [140] (30.0 dBm) (no IR, radar detection)
              DFS state: usable (for 122 sec)
              DFS CAC time: 0 ms
            * 5720 MHz [144] (30.0 dBm) (no IR)
            * 5745 MHz [149] (30.0 dBm) (no IR)
            * 5765 MHz [153] (30.0 dBm) (no IR)
            * 5785 MHz [157] (30.0 dBm) (no IR)
            * 5805 MHz [161] (30.0 dBm) (no IR)
            * 5825 MHz [165] (30.0 dBm) (no IR)
    Supported commands:
         * new_interface
         * set_interface
         * new_key
         * start_ap
         * new_station
         * new_mpath
         * set_mesh_config
         * set_bss
         * authenticate
         * associate
         * deauthenticate
         * disassociate
         * join_ibss
         * join_mesh
         * remain_on_channel
         * set_tx_bitrate_mask
         * frame
         * frame_wait_cancel
         * set_wiphy_netns
         * set_channel
         * set_wds_peer
         * tdls_mgmt
         * tdls_oper
         * probe_client
         * set_noack_map
         * register_beacons
         * start_p2p_device
         * set_mcast_rate
         * channel_switch
         * set_qos_map
         * connect
         * disconnect
    Supported TX frame types:
         * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    Supported RX frame types:
         * IBSS: 0x40 0xb0 0xc0 0xd0
         * managed: 0x40 0xd0
         * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * mesh point: 0xb0 0xc0 0xd0
         * P2P-client: 0x40 0xd0
         * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * P2P-device: 0x40 0xd0
    WoWLAN support:
         * wake up on disconnect
         * wake up on magic packet
         * wake up on pattern match, up to 22 patterns of 1-148 bytes,
           maximum packet offset 128 bytes
    software interface modes (can always be added):
         * AP/VLAN
         * monitor
    valid interface combinations:
         * #{ managed } <= 2, #{ AP, mesh point, P2P-client, P2P-GO } <= 2, #{ P2P-device } <= 1,
           total <= 4, #channels <= 1
         * #{ managed } <= 2, #{ P2P-client } <= 2, #{ AP, mesh point, P2P-GO } <= 1, #{ P2P-device } <= 1,
           total <= 4, #channels <= 2
         * #{ managed } <= 1, #{ IBSS } <= 1,
           total <= 2, #channels <= 1
    HT Capability overrides:
         * MCS: ff ff ff ff ff ff ff ff ff ff
         * maximum A-MSDU length
         * supported channel width
         * short GI for 40 MHz
         * max A-MPDU length exponent
         * min MPDU start spacing
    Device supports TX status socket option.
    Device supports HT-IBSS.
    Device supports SAE with AUTHENTICATE command
    Device supports scan flush.
    Device supports AP scan.
    Device supports per-vif TX power setting
    Driver supports full state transitions for AP/GO clients
    Driver supports a userspace MPM
    Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
    Device supports static SMPS
    Device supports configuring vdev MAC-addr on create.
    Device supports VHT-IBSS.

Last edited by AP-random472 (2017-01-17 21:14:51)

Offline

#8 2017-01-18 05:30:09

blahhumbug
Member
Registered: 2016-10-08
Posts: 64

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

I have the same laptop and Atheros wifi card.  The following works for me with archiso.

wpa_supplicant -B -D nl80211 -i wlp58s0 -c<(wpa_passphrase "NETWORK1" "PASSWORD")
dhcpcd

Note that it is the letter 'l' in the 2nd character of the driver.  Your post had the number 1.

Last edited by blahhumbug (2017-01-18 05:31:27)

Offline

#9 2017-01-18 08:48:39

AP-random472
Member
Registered: 2017-01-16
Posts: 18

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

blahhumbug wrote:

I have the same laptop and Atheros wifi card.  The following works for me with archiso.

wpa_supplicant -B -D nl80211 -i wlp58s0 -c<(wpa_passphrase "NETWORK1" "PASSWORD")
dhcpcd

Note that it is the letter 'l' in the 2nd character of the driver.  Your post had the number 1.

Amazing. It was the 'l'. I can't believe how many times I've written that '1. I guess wifi-menu doesn't automatically use that driver.

Thank you good sir. I feel like a chump.

Will mark as solved

Offline

#10 2017-01-18 21:00:41

AP-random472
Member
Registered: 2017-01-16
Posts: 18

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

Haha. You could not make this up.

It turns out, the one attempt I made this morning before work with the changes above was a complete fluke. It does not work. I spent 2 hours sat by the router trying to replicate the connection...

So. I spent the rest of the evening using the internet on the windows preinstall and low and behold the wifi is awful. It regularly cannot find any networks, drops connections and is completely useless.

I'm pretty certain I have a ropey wifi card. Bit of googling shows lots of people with the same problem, even on the 9630s.

So I've had it, I've ordered an INTEL AC8265 card and hope that fixes the problem.

Got to laugh when 4 evenings are wasted due to potentially duff hardware

Thanks again for all help

[IT WAS THE CARD. THE INTEL IS PERFECT]

Last edited by AP-random472 (2017-10-19 15:24:06)

Offline

#11 2017-04-02 00:27:56

potuz
Member
Registered: 2009-10-23
Posts: 13

Re: Unable to connect to wireless network (Dell XPS 13 9630) [SOLVED]

I am having the exact same problem as the OP with the same computer that I just got. I couldn't get the card to connect to anything with Ubuntu live nor with the Archiso from today. The wpa_supplicant command above does not work for me either. I do not think this is a faulty card since it works under windows without any trouble.

Offline

Board footer

Powered by FluxBB