On 01/17/2017 01:12 PM, Stephen Morris wrote:
> On 18/1/17 6:40 am, Rick Stevens wrote:
>> On 01/17/2017 12:12 PM, Stephen Morris 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').
>> First, try (as root) "ifconfig -a". A simple "ifconfig" will only show
>> interfaces that are "up" and have an IP address.
>>
>> You could also try (again as root) "iw dev". You should see something
>> like:
>>
>> [root@golem4 ~]# iw dev
>> phy#0
>> Interface wlan0
>> ifindex 3
>> wdev 0x1
>> addr bc:77:37:51:11:5c
>> type managed
>> channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
>>
>> That shows that my laptop has one physical wireless device whose
>> physical ID is "phy#0". As far as networking is concerned, the NIC
>> (network interface card) is called "wlan0" and it has a hardware MAC
>> (media access controller) address of bc:77:37:51:11:5c. It is currently
>> associated with a wireless network over channel 6, which means it's got
>> an IP address on that network and "ifconfig" will display that:
>>
>> ---------------- CUT HERE -------------------------------------
>> [root@golem4 ~]# ifconfig
>> 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 1 (Local Loopback)
>> RX packets 4195 bytes 355528 (347.1 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 4195 bytes 355528 (347.1 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.52 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid
>> 0x20<link>
>> ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
>> RX packets 703055 bytes 437801892 (417.5 MiB)
>> RX errors 0 dropped 1 overruns 0 frame 0
>> TX packets 419055 bytes 34250049 (32.6 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
>> inet 192.168.122.1 netmask 255.255.255.0 broadcast
>> 192.168.122.255
>> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
>> RX packets 51562 bytes 6038644 (5.7 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 55954 bytes 54927745 (52.3 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.247 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid
>> 0x20<link>
>> ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
>> RX packets 158408 bytes 20391376 (19.4 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 397 bytes 80743 (78.8 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> ---------------- CUT HERE -------------------------------------
>>
>> Note the entry starting with "wlan0". Also, just for reference, here's
>> the "ifconfig -a" output:
>>
>> ---------------- CUT HERE -------------------------------------
>> [root@golem4 ~]# ifconfig -a
>> 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 1 (Local Loopback)
>> RX packets 4195 bytes 355528 (347.1 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 4195 bytes 355528 (347.1 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.52 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid
>> 0x20<link>
>> ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
>> RX packets 703836 bytes 437862421 (417.5 MiB)
>> RX errors 0 dropped 1 overruns 0 frame 0
>> TX packets 419752 bytes 34301624 (32.7 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
>> inet 192.168.122.1 netmask 255.255.255.0 broadcast
>> 192.168.122.255
>> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
>> RX packets 51562 bytes 6038644 (5.7 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 55954 bytes 54927745 (52.3 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
>> ether 52:54:00:95:7c:a1 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
>>
>> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.247 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid
>> 0x20<link>
>> ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
>> RX packets 158425 bytes 20393862 (19.4 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 397 bytes 80743 (78.8 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> ---------------- CUT HERE -------------------------------------
>>
>> Note the data for "virbr0-nic" in the "iwconfig -a" output that is
>> missing from the regular "ifconfig" output. That's because that
>> interface is not "up" and is not associated with a network. Don't worry
>> about why, I'm just trying to show that "iwconfig" only returns "up"
>> interfaces. If you want to see ALL of them, you must use "ifconfig -a".
>>
>> Now, with all that being said, if you don't have an appropriate driver
>> or firmware for the device, the "iw dev" or "ifconfig -a" commands may
>> not find it. Yes, physically it's in your USB port and "lsusb" sees it,
>> but that's just the USB part of the hardware. Without firmware, it may
>> not work on the network.
>>
>> Can you send me the USB ID (e.g. the four digit hex "idVendor" and the
>> four digit hex "idProduct" values from "lsusb -v")? That way we can see
>> if it's actually supported and what (if any) firmware is required. It
>> may even be just that there is an appropriate driver but doesn't
>> recognize the USB ID so the system won't automatically load it. We can
>> force a load of the driver and set up the system so it gets loaded even
>> if the system can't automatically associate that device with that
>> driver.
>>
>>> 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.
>> That's why we want to see if the kernel actually sees it. If the kernel
>> doesn't see it, why? If the kernel does see it, why won't NM talk to it?
> Thanks Rick. The ifconfig -a output is below, the last device listed,
> wlp4s6 is the usb wifi device.
>
> enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.138 netmask 255.255.255.0 broadcast 192.168.1.255
> inet6 fe80::d250:99ff:fe14:547d prefixlen 64 scopeid 0x20<link>
> ether d0:50:99:14:54:7d txqueuelen 1000 (Ethernet)
> RX packets 1923 bytes 558919 (545.8 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 1275 bytes 172001 (167.9 KiB)
> 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 1 (Local Loopback)
> RX packets 20 bytes 1736 (1.6 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 20 bytes 1736 (1.6 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast
> 192.168.122.255
> ether 00:00:00:00:00:00 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
>
> virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
> ether 52:54:00:5d:b8:54 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
>
> wlp4s6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether d8:5d:4c:b4:48:47 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
>
> The iw dev output is also below.
>
> phy#0
> Interface wlp4s6
> ifindex 3
> wdev 0x1
> addr d8:5d:4c:b4:48:47
> type managed
>
> The lsusb output for that device is also below.
>
> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>
> I did find a command once, when I was trying to determine why for this
> AC device Linux refused to use the 5GHz channel, that told me the driver
> that had been auto loaded for this device, but I don't remember what the
> command was. From memory this command told me the device was using the
> ATH9K driver. At the time I was also trying to work out why this driver
> was being assigned rather than the ATH10K driver, which some information
> I found and again I don't remember where, indicated that the ATH10K
> driver may have support the 5GHz channel.
Well, it certainly appears the NIC is seen by the system (it's NIC
name is "wlp4s6"). So, to see what driver is actually being used, as
root:
ethtool -i wlp4s6
As to why NM isn't talking to it, you can try manually configuring NM
to use it. My instructions (using Xfce):
1. Right-click on the NM icon and select "Edit Connections"
2. In the next window, click "Add"
3. In the next window ("Choose a Connection Type"), select
"Wi-Fi"
4. Authenticate
5. In the next window:
a. Set the "Connection name:" appropriately
b. In the "SSID:" box, enter the SSID of the network you
wish to join
c. In the "Mode:" box, select "Client"
d. In the "Device:" box, put in "d8:5d:4c:b4:48:47" (the MAC
address of the device)
e. Leave the rest set to default
f. Click "Create"
That should set up a profile you can use. Close everything down,
left-click on the NM icon and select the network profile you created
(what you entered in step 5b).
>From what I can see, that's a D-Link DWA-192 or something, based on
Realtek's 8188 chipset. I'd expect it to be using the rtlwifi driver
and its support items.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- The Theory of Rapitivity: E=MC Hammer -
- -- Glenn Marcus (via TopFive.com) -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
