Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Wifi install - ATH10K
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 2613

PostPosted: Sat Jul 15, 2017 7:07 am    Post subject: Reply with quote

Do not start dhcpcd as a service when using netifrc ( which is /etc/conf.d/net )!

https://wiki.gentoo.org/wiki/Wpa_supplicant#Setup_for_dhcpcd_as_network_manager and
https://wiki.gentoo.org/wiki/Wpa_supplicant#Setup_for_Gentoo_net..2A_scripts
are different approaches.

Edit:
Even for NetworkManager you might unmerge net-misc/netifrc.
Have you compiled NetworkManager with the https://packages.gentoo.org/useflags/wifi USE flag?
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Jul 15, 2017 8:01 am    Post subject: Reply with quote

OK, I'll go through this carefully as since I've rebooted I can't get association happening - I thinkk the plasma network manager and wpa_gui are fighting or the conflict goes back to the dhcpcd as you mention.

It did work briefly there though...
_________________
]8P
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Jul 15, 2017 8:05 am    Post subject: Reply with quote

yes USE wifi was compiled in

Code:
=================================================================
                        Package Settings
=================================================================

net-misc/networkmanager-1.4.4-r1::gentoo was built with the following:
USE="bluetooth connection-sharing consolekit dhclient introspection json modemmanager ncurses nss ppp resolvconf wext wifi -audit -gnutls -ofono (-selinux) -systemd -teamd -test -vala" ABI_X86="(64) -32 (-x32)"

xps15 /etc/wpa_supplicant #

_________________
]8P
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Jul 15, 2017 8:12 am    Post subject: Reply with quote

I do recall the importance of separating the networkmanager components and not going with two conflicting methods.

Now I am not sure which to remove and the best way to do that - do I drop dhcpcd and go with net scripts dhcp?


so I'm removing dhcpdc and I'll try and hack it out again.
_________________
]8P
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Jul 15, 2017 8:18 am    Post subject: Reply with quote

OK removing dhcpcd and restaarting wpa_supp has brought things alive again when I launch wpa_gui

What I am confused about is what the plasma network setting/configuration tool in the system tray and system settings is using

since when I'm associated and all up and running on wpa_gui it has no configured interfaces but when I plug in the ethernet adapter it takes over managing that interface and when I go into that "Edit your Network Connections" and create and configure one of the available ssid's it keeps prompting for password but never initialises.
_________________
]8P
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Jul 15, 2017 8:48 am    Post subject: Reply with quote

OK, so I'm horribly confused now and going around in circles.

It did work for a while - I can now associate with my wlp2s0 and ssids but I get no IP address.

I have done a bunch of merge and unmerge dhcpcd and netifrc - but I'm confused - when I want to manage the network with the Gentoo net.* I still need dhcpcd don't I to handle the dhcp provisioning for the interface - it is just that this is _managed_ by the net scripts rather than the dhcpcd itself??

How do I work out what I have and how to reset the stack?

it would seem that I have two separate issues - one - there is no plasma kde launcher for the wpa_gui so I am starting that manually with regular user privs and I've done all the necessary things to include the wpa process in the wheel (I think). So the associations work just fine but there is no net script kicking off per my config in conf.d

Code:
xps15 /home/will # cat /etc/conf.d/net
config_enp10s0u1u4="dhcp"
# Prefer wpa_supplicant over wireless-tools
modules_wlp2s0="wpa_supplicant"
wpa_supplicant_wlp2s0="-Dnl80211"
config_wlp2s0="dhcp"



that use of the wlp2s0 is correct right? The wiki all use wlan0 but that is the interface name placeholder?

And then I created the symlinks to hook up the net.wlp2s0

Code:
xps15 /etc/init.d # ls -l net*
-rwxr-xr-x 1 root root  2043 Jun 22 16:26 net-online
lrwxrwxrwx 1 root root     6 Jul  5 18:38 net.enp10s0u1u4 -> net.lo
-rwxr-xr-x 1 root root 18514 Jul 15 18:46 net.lo
lrwxrwxrwx 1 root root    18 Jul 15 18:29 net.wlp2s0 -> /etc/init.d/net.lo
-rwxr-xr-x 1 root root  2071 Jun 22 16:26 netmount



Code:
xps15 /etc/init.d # rc-service net.wlp2s0 restart
 * Executing: /lib64/rc/sh/openrc-run.sh /lib64/rc/sh/openrc-run.sh /etc/init.d/net.wlp2s0 start
 * Bringing up interface wlp2s0
 *   Skipping module adsl due to missing program: /usr/sbin/adsl-start /usr/sbin/pppoe-start
 *   Skipping module br2684ctl due to missing program: br2684ctl
 *   Skipping module clip due to missing program: /usr/sbin/atmsigd
 *   Skipping module ethtool due to missing program: ethtool
 *   Skipping module netplugd due to missing program: /sbin/netplugd
 *   Skipping module ifplugd due to missing program: /usr/sbin/ifplugd
 *   Skipping module ipppd due to missing program: /usr/sbin/ipppd
 *   Skipping module firewalld due to missing program: firewall-cmd
 *   Skipping module pump due to missing program: /sbin/pump
 *   Loaded modules: apipa arping bonding l2tp tuntap bridge ccwgroup dummy hsr macvlan macchanger macnet wpa_supplicant ssidnet iproute2 pppd system vlan dhcpcd ip6rd ip6to4
 *   ip link set dev wlp2s0 up
 *   Configuring wlp2s0 for MAC address 92:CA:A6:B1:8B:9D ...                                                 [ ok ]
 *   Starting wpa_supplicant on wlp2s0 ...
 *   start-stop-daemon: fopen `/run/wpa_supplicant-wlp2s0.pid': No such file or directory
 *   Detaching to start `/usr/sbin/wpa_supplicant' ...
Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlp2s0' manually if it is not used anymore
Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=wheel'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

nl80211: Failed to open /proc/sys/net/ipv6/conf/wlp2s0/drop_unicast_in_l2_multicast: No such file or directory
nl80211: Failed to set IPv6 unicast in multicast filter
nl80211: Failed to open /proc/sys/net/ipv6/conf/wlp2s0/drop_unicast_in_l2_multicast: No such file or directory
nl80211: Failed to set IPv6 unicast in multicast filter
nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
 *     start-stop-daemon: failed to start `/usr/sbin/wpa_supplicant'                                          [ !! ]
 * ERROR: net.wlp2s0 failed to start

and with netifrc in place starting the interface fails on numerous levels (again is this becuase I;'m using dhcpcd as well??)

restarting wpa_supp then seems to go ok but no IP...

Code:
xps15 /etc/init.d # rc-service wpa_supplicant restart
 * Executing: /lib64/rc/sh/openrc-run.sh /lib64/rc/sh/openrc-run.sh /etc/init.d/wpa_supplicant stop
 * Stopping WPA Supplicant Daemon ...
 * Will stop /usr/sbin/wpa_supplicant
 * Will stop processes of `/usr/sbin/wpa_supplicant'
 * Sending signal 15 to PID 6306 ...                                                                          [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Sending signal 0 to PID 6306 ...                                                                           [ ok ]
 * Executing: /lib64/rc/sh/openrc-run.sh /lib64/rc/sh/openrc-run.sh /etc/init.d/wpa_supplicant start
 * Starting WPA Supplicant Daemon ...
 * Detaching to start `/usr/sbin/wpa_supplicant' ...
Successfully initialized wpa_supplicant                                                                       [ ok ]
xps15 /etc/init.d #



las update for a bit - so it seems to be a matter of getting the order correct.

I kiolled wpa_supp and then let it get kicked off by starting the net script and it all worked!

Code:
xps15 /etc/init.d # rc-service net.wlp2s0 start
 * Executing: /lib64/rc/sh/openrc-run.sh /lib64/rc/sh/openrc-run.sh /etc/init.d/net.wlp2s0 start
 * Bringing up interface wlp2s0
 *   Skipping module adsl due to missing program: /usr/sbin/adsl-start /usr/sbin/pppoe-start
 *   Skipping module br2684ctl due to missing program: br2684ctl
 *   Skipping module clip due to missing program: /usr/sbin/atmsigd
 *   Skipping module ethtool due to missing program: ethtool
 *   Skipping module netplugd due to missing program: /sbin/netplugd
 *   Skipping module ifplugd due to missing program: /usr/sbin/ifplugd
 *   Skipping module ipppd due to missing program: /usr/sbin/ipppd
 *   Skipping module firewalld due to missing program: firewall-cmd
 *   Skipping module pump due to missing program: /sbin/pump
 *   Loaded modules: apipa arping bonding l2tp tuntap bridge ccwgroup dummy hsr macvlan macchanger macnet wpa_supplicant ssidnet iproute2 pppd system vlan dhcpcd ip6rd ip6to4
 *   ip link set dev wlp2s0 up
 *   Configuring wlp2s0 for MAC address 92:CA:A6:B1:8B:9D ...                                                 [ ok ]
 *   Starting wpa_supplicant on wlp2s0 ...
 *   start-stop-daemon: fopen `/run/wpa_supplicant-wlp2s0.pid': No such file or directory
 *   Detaching to start `/usr/sbin/wpa_supplicant' ...
Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device                                                                     [ ok ]
 *   Starting wpa_cli on wlp2s0 ...
 *   start-stop-daemon: fopen `/run/wpa_cli-wlp2s0.pid': No such file or directory
 *   Detaching to start `/usr/bin/wpa_cli' ...                                                                [ ok ]
 *   Backgrounding ... ...
 * WARNING: net.wlp2s0 has started, but is inactive


...

Code:
wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.24  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 92:ca:a6:b1:8b:9d  txqueuelen 1000  (Ethernet)
        RX packets 2572  bytes 608365 (594.1 KiB)
        RX errors 0  dropped 220  overruns 0  frame 0
        TX packets 50  bytes 7419 (7.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

xps15 /etc/init.d #

_________________
]8P
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 2613

PostPosted: Sat Jul 15, 2017 8:57 am    Post subject: Reply with quote

stardotstar wrote:
I do recall the importance of separating the networkmanager components and not going with two conflicting methods.

Now I am not sure which to remove and the best way to do that - do I drop dhcpcd and go with net scripts dhcp?

You remember something like One and only one of the following ... ?
Also means only one of "net scripts" or "NetworkManger".
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Jul 15, 2017 9:12 am    Post subject: Reply with quote

yes, I do. Now I'm posting from my wireless interface now so I've got a working state - but what then is the system behind the kde-plasma network management? Is that NetworkManager? In which case I am guessing I need to drop netifrc and revert to networkmanager - though that is still installed.

Code:
Calculating dependencies... done!
[ebuild   R    ] net-misc/networkmanager-1.4.4-r1

Would you like to merge these packages? [Yes/No]


Code:
*  net-misc/netifrc
      Latest version available: 0.5.1
      Latest version installed: 0.5.1
      Size of files: 77 KiB
      Homepage:      https://www.gentoo.org/proj/en/base/openrc/
      Description:   Gentoo Network Interface Management Scripts
      License:       BSD-2



Code:
*  net-misc/dhcp
      Latest version available: 4.3.4
      Latest version installed: 4.3.4
      Size of files: 9,085 KiB
      Homepage:      http://www.isc.org/products/DHCP
      Description:   ISC Dynamic Host Configuration Protocol (DHCP) client/server
      License:       ISC BSD SSLeay GPL-2

*  net-misc/dhcpcd
      Latest version available: 6.11.3
      Latest version installed: 6.11.3
      Size of files: 191 KiB
      Homepage:      http://roy.marples.name/projects/dhcpcd/
      Description:   A fully featured, yet light weight RFC2131 compliant DHCP client
      License:       BSD-2


so if I want this to all play nice with plasma I need to remove netifrc, dhcpcd and retain networkmanager?
_________________
]8P
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 2613

PostPosted: Sat Jul 15, 2017 9:12 am    Post subject: Reply with quote

stardotstar wrote:
I have done a bunch of merge and unmerge dhcpcd and netifrc - but I'm confused - when I want to manage the network with the Gentoo net.* I still need dhcpcd don't I to handle the dhcp provisioning for the interface - it is just that this is _managed_ by the net scripts rather than the dhcpcd itself??

How do I work out what I have and how to reset the stack?

My very personal preference:
I strictly go with Network management using DHCPCD every step, from top to bottom, including
https://wiki.gentoo.org/wiki/Network_management_using_DHCPCD#Migration_from_Gentoo_net..2A_scripts and
https://wiki.gentoo.org/wiki/Network_management_using_DHCPCD#Graphical_User_interface

No NetworkManger, no netifrc, no /etc/conf.d/net

No experience at all with plasma, gnome, kde and the likes...

Doesn't this chapter clearly tell about what NM needs?
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Sat Jul 15, 2017 10:58 am    Post subject: Reply with quote

Looking this through I think that adding the global use networkmanager and doing a big remerge could be good *but* I don't understand how networkmanager interplays with wpa_supplicannt - or is wpa_supp redundant if networkmanager is used?


OK, looks like networkmanager requires wpa_supp but handles all the config itself.

So I'm doing a big changed-use rebuild now and have taken the net.* scripts and netifrc and dhcpcd out of play as I'll revert back to only net-misc/dhcp, wpa_supp and networkmanager. That should then see global networkmanager performance in place - how well that works with my card remains to be seen.

fingers crossed.

Thanks for all the helpful prompting and guidance
_________________
]8P
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43175
Location: 56N 3W

PostPosted: Sat Jul 15, 2017 2:12 pm    Post subject: Reply with quote

stardotstar,

wpa-supplicant is used by all of the applications that control wireless networking.

You must ensure that you only start a single wireless network control application as they will fight over wpa-supplicant.
When that happens, dmesg is filled with messages about associating, authenticating and shutting down and wifif won't work.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Mon Jul 17, 2017 2:42 am    Post subject: Reply with quote

Yes, this is what I have now that I have begun the untangling

Code:
[   95.942435] wlp2s0: authenticate with 58:6d:8f:7a:0d:38
[   96.008863] wlp2s0: send auth to 58:6d:8f:7a:0d:38 (try 1/3)
[   96.010609] wlp2s0: authenticated
[   96.011272] wlp2s0: associate with 58:6d:8f:7a:0d:38 (try 1/3)
[   96.014659] wlp2s0: RX AssocResp from 58:6d:8f:7a:0d:38 (capab=0x411 status=0 aid=3)
[   96.018382] wlp2s0: associated
[   96.018514] wlp2s0: deauthenticating from 58:6d:8f:7a:0d:38 by local choice (Reason: 3=DEAUTH_LEAVING)
[  100.475767] vgaarb: this pci device is not a vga device
[  100.479480] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.479536] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.479570] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.479601] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.479632] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.479679] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.479710] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.487839] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[  100.685294] nvidia-modeset: Allocated GPU:0 (GPU-9c8d090b-8532-6ae7-617b-c2e0eb3f4abb) @ PCI:0000:01:00.0
[  100.685383] nvidia-modeset: Freed GPU:0 (GPU-9c8d090b-8532-6ae7-617b-c2e0eb3f4abb) @ PCI:0000:01:00.0
[  100.801673] vgaarb: this pci device is not a vga device
[  103.772691] vgaarb: this pci device is not a vga device
[  126.497242] wlp2s0: authenticate with 58:6d:8f:7a:0d:38
[  126.563995] wlp2s0: send auth to 58:6d:8f:7a:0d:38 (try 1/3)
[  126.580536] wlp2s0: authenticated
[  126.581199] wlp2s0: associate with 58:6d:8f:7a:0d:38 (try 1/3)
[  126.586036] wlp2s0: RX AssocResp from 58:6d:8f:7a:0d:38 (capab=0x411 status=0 aid=3)
[  126.589340] wlp2s0: associated
[  126.589489] wlp2s0: deauthenticating from 58:6d:8f:7a:0d:38 by local choice (Reason: 3=DEAUTH_LEAVING)
[  131.378312] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  131.381808] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  131.388929] wlp2s0: authenticated
[  131.389155] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  131.397006] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  131.401172] wlp2s0: associated
[  131.401365] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
[  186.194272] wlp2s0: authenticate with 58:6d:8f:7a:0d:38
[  186.262657] wlp2s0: send auth to 58:6d:8f:7a:0d:38 (try 1/3)
[  186.264333] wlp2s0: authenticated
[  186.265130] wlp2s0: associate with 58:6d:8f:7a:0d:38 (try 1/3)
[  186.268500] wlp2s0: RX AssocResp from 58:6d:8f:7a:0d:38 (capab=0x411 status=0 aid=3)
[  186.271502] wlp2s0: associated
[  186.271651] wlp2s0: deauthenticating from 58:6d:8f:7a:0d:38 by local choice (Reason: 3=DEAUTH_LEAVING)
[  191.061421] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  191.064924] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  191.083813] wlp2s0: authenticated
[  191.084102] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  191.087542] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  191.090486] wlp2s0: associated
[  191.090668] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
[  201.882542] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  201.951810] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  201.959803] wlp2s0: authenticated
[  201.960096] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  201.963467] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  201.966234] wlp2s0: associated
[  201.966357] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
[  211.438717] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  211.504054] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  211.512073] wlp2s0: authenticated
[  211.513106] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  211.522921] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  211.525703] wlp2s0: associated
[  211.525784] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
[  239.641732] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  239.707281] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  239.715170] wlp2s0: authenticated
[  239.716076] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  239.719453] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  239.722197] wlp2s0: associated
[  239.722278] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
[  249.194436] wlp2s0: authenticate with 58:6d:8f:7a:0d:38
[  249.260550] wlp2s0: send auth to 58:6d:8f:7a:0d:38 (try 1/3)
[  249.262203] wlp2s0: authenticated
[  249.263040] wlp2s0: associate with 58:6d:8f:7a:0d:38 (try 1/3)
[  249.266425] wlp2s0: RX AssocResp from 58:6d:8f:7a:0d:38 (capab=0x411 status=0 aid=3)
[  249.269536] wlp2s0: associated
[  249.269638] wlp2s0: deauthenticating from 58:6d:8f:7a:0d:38 by local choice (Reason: 3=DEAUTH_LEAVING)
[  254.056553] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  254.060133] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  254.068075] wlp2s0: authenticated
[  254.069036] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  254.079071] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  254.081896] wlp2s0: associated
[  254.082073] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
[  264.523765] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  264.593676] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  264.601987] wlp2s0: authenticated
[  264.603057] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  264.629121] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  264.631873] wlp2s0: associated
[  264.631960] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
[  274.104203] wlp2s0: authenticate with 10:0d:7f:e3:8d:6a
[  274.170271] wlp2s0: send auth to 10:0d:7f:e3:8d:6a (try 1/3)
[  274.177989] wlp2s0: authenticated
[  274.179023] wlp2s0: associate with 10:0d:7f:e3:8d:6a (try 1/3)
[  274.182380] wlp2s0: RX AssocResp from 10:0d:7f:e3:8d:6a (capab=0x411 status=0 aid=7)
[  274.185358] wlp2s0: associated
[  274.185448] wlp2s0: deauthenticating from 10:0d:7f:e3:8d:6a by local choice (Reason: 3=DEAUTH_LEAVING)
xps15 /home/will


So far I have tried to ensure that I only have networkmanager installed and trying to take care of my networking.

It is showing in Plasma and successfully scans the ssids running as well as prompting for password auth - repeatedly. Clearly something is still interfering.


1) dhcpcd is not installed
2) dhcp is installed
3) netifrc is not installed; net.* all gone from rc
4) user is in plugdev group, polkit policy added for plasma-nm
_________________
]8P
Back to top
View user's profile Send private message
ronaldoc
n00b
n00b


Joined: 03 Jul 2017
Posts: 15

PostPosted: Mon Jul 17, 2017 7:32 am    Post subject: Reply with quote

charles17 wrote:
stardotstar

The Qualcomm has been described to be working. Try again exactly step-by-step what's written in https://wiki.gentoo.org/index.php?title=Dell_XPS_13_9360&oldid=581812#Wireless. Then reboot and grep the dmesg.

EDIT:
Sorry, that article was written regarding =sys-kernel/linux-firmware-20161205 whereas the presently stable version is =sys-kernel/linux-firmware-20170314. And also the kernel version seems to have been an older one. I think it is necessary to find out what d63955b33b3b, ca996ec56608 stated in https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware?s%5b%5d=qca6174 means.

The article was very helpful for me, thanks:)
Back to top
View user's profile Send private message
stardotstar
l33t
l33t


Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU

PostPosted: Mon Jul 17, 2017 7:32 am    Post subject: Reply with quote

I think this thread is exhausted and I'll start a new query about getting NetworkManager and wpa_supp to work in plasma.

Thanks for all the assistance getting the card going and up to this point
_________________
]8P
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page Previous  1, 2, 3
Page 3 of 3

 
Jump to:  
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