Re: Networkmanagre Refuses to use my Dlink DWA-192 USB Wifi Device in F24

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 19/1/17 3:43 am, Rick Stevens wrote:
On 01/18/2017 01:54 AM, Stephen Morris wrote:
On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if you haven't the firmware.  It may be blacklisted.
How do I determine if it or wifi has been blacklisted? On reflecting on
this issue there is a possibility that I may have manually disabled the
device or wifi, but I have forgotten how.
It'd be done by a file in your /etc/modprobe.d directory. Just
"grep -ri blacklist /etc/modprobe.d/*" to see if it's in there
somewhere.
I've checked /etc/modprobe.d and I don't have a blacklist.conf file, and the 2 .conf files that are there don't have any blacklist statements in them.

 From your previous message, the fact that ethtool can't find the device
is interesting and it sure looks like it didn't load the firmware. You
might try looking at the journals to see what sort of messages have
"firmware" or "wireless" in them. That might give you a clue.
I've had a look at /var/log/wpa_supplicant.log and the messages below that appear near the bottom are indicating to me that something is passing the wrong wpa key at connection time, but I'm not sure where as I have checked /etc/sysconfg/network-scripts/keys-Linksys07468 and that file has the correct wpa key for my router.

wlp4s6: SME: Trying to authenticate with c0:56:27:b8:94:6e (SSID='Linksys07468' freq=2417 MHz) wlp4s6: Trying to associate with c0:56:27:b8:94:6e (SSID='Linksys07468' freq=2417 MHz)
wlp4s6: Associated with c0:56:27:b8:94:6e
wlp4s6: CTRL-EVENT-DISCONNECTED bssid=c0:56:27:b8:94:6e reason=4 locally_generated=1
wlp4s6: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s6: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Linksys07468" auth_failures=1 duration=10 reason=WRONG_KEY
wlp4s6: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp4s6: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=AU
nl80211: deinit ifname=wlp4s6 disabled_11b_rates=0
wlp4s6: CTRL-EVENT-TERMINATING

regards,
Steve


On Tue, Jan 17, 2017 at 4:20 PM, Stephen Morris
<samorris@xxxxxxxxxxxxxxx <mailto:samorris@xxxxxxxxxxxxxxx>> wrote:

     On 18/1/17 6:50 am, Terry Polzin wrote:

         Is the device firmware getting loaded?

     Thanks Terry. At the moment I'm not sure. This device used to work
     so I am assuming the firmware is being loaded, but at the moment
     I'm not sure if the firmware extensions package has been
     uninstalled for some reason as part of standard system upgrades.

     regards,
     Steve


         On Tue, Jan 17, 2017 at 3:38 PM, Stephen Morris
         <samorris@xxxxxxxxxxxxxxx <mailto:samorris@xxxxxxxxxxxxxxx>
         <mailto:samorris@xxxxxxxxxxxxxxx
         <mailto:samorris@xxxxxxxxxxxxxxx>>> wrote:

             On 17/1/17 7:49 am, Rick Stevens wrote:

                 On 01/16/2017 12:22 PM, Joe Zeff wrote:

                     On 01/16/2017 12:17 PM, Stephen Morris wrote:

                         I am using kde at the moment and I have cut
         and pasted
                         the wifi password
                         back into the Networkmanager definition, and
         had the
                         new password stored
                         in Kwallet, but Networkmanager still refuses to
                         recognize that the
                         device is a device it can connect to.

                     Therefor the password isn't the issue. And, as it
         works
                     under Windows,
                     it's not hardware.

                 First try "ethtool -i <name-of-device>" to see what
         driver is
                 loaded
                 (if any). If you get data back then try "iwlist wlan0
         scan"
                 (replace
                 "wlan0" with your device) to see what access points
         are in the
                 area.

                 If all that works, then the wireless itself is working
         under
                 Linux and
                 there's something odd about the way NetworkManager
         (NM) and
                 your device
                 talk to each other. At that point you could try to
         disable NM
                 and use
                 the wpa_supplicant programs directly to try to get it
         up (such as
                 running wpa_supplicant in the background and using
         something like
                 wpa_supplicant_gui to manipulate it). If you're
successful
                 there, then
                 try to get NM to talk nice or bugzilla it to the NM list.

             Sorry Rick, how do I determine what the device name is?
         The only
             information I have been able to determine is that lsusb
         shows me
             that the usb device is there, and iwconfig says that there
         are no
             devices with wireless extensions, but I don't see a device
         in that
             list that I am expecting (I don't remember exactly what
         the device
             name was when it was being used but I think is started
         with 'wp').
             The only difference between the last time I used the wifi
         device
             (which was probably 6 months ago, I've been using an ethernet
             'Home Plug' device) and now is that I have put on multiple
         system
             upgrades for F24, plus at the moment I don't know whether the
             issue is NetworkManager, Kernels or something else.

             regards,
             Steve

----------------------------------------------------------------------
                 - Rick Stevens, Systems Engineer, AllDigital
         ricks@xxxxxxxxxxxxxx <mailto:ricks@xxxxxxxxxxxxxx>
         <mailto:ricks@xxxxxxxxxxxxxx <mailto:ricks@xxxxxxxxxxxxxx>> -
                 - AIM/Skype: therps2        ICQ: 226437340 Yahoo:
         origrps2 -
                 -           -
                 -      The moving cursor writes, and having written,
         blinks
                 on.      -
----------------------------------------------------------------------
                 _______________________________________________
                 users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>
                 <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>>
                 To unsubscribe send an email to
         users-leave@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx>
                 <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx>>

             _______________________________________________
             users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>
             <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>>
             To unsubscribe send an email to
         users-leave@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx>
             <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx>>




         _______________________________________________
         users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>
         To unsubscribe send an email to
         users-leave@xxxxxxxxxxxxxxxxxxxxxxx
         <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx>

     _______________________________________________
     users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
     <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>
     To unsubscribe send an email to
     users-leave@xxxxxxxxxxxxxxxxxxxxxxx
     <mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx>




_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux