that is actually what I did with dmesg. The grep thing was just to show there were no hits. On Fri, Aug 25, 2017 at 7:00 PM, Michael wrote: > I'll write it to a file and saearch with a word processor > ` > > On Fri, Aug 25, 2017 at 6:25 PM, Carruth, Rusty > wrote: > >> And you might want to do it case-INsensitive, just to be sure you don’t >> miss it. >> >> >> >> *From:* PLUG-discuss [mailto:plug-discuss-bounces@lists.phxlinux.org] *On >> Behalf Of *Bob Elzer >> *Sent:* Friday, August 25, 2017 3:11 PM >> *To:* Main PLUG discussion list >> *Subject:* Re: netis wf2118 >> >> >> >> doing a grep will not show adjacent lines that have errors on them. >> >> >> >> you need to use the less or more commands and search for those same >> things and read the lines before and after, to see if there are any errors. >> >> >> >> keep searching for the next occurrence, until you reach the end of file >> >> >> >> >> >> On Aug 25, 2017 1:43 PM, "Michael" wrote: >> >> The driver appears to be loading: >> >> >> >> $ lsmod| grep rt2x00 >> >> rt2x00pci 13287 1 rt2800pci >> >> rt2x00mmio 13603 2 rt2800pci,rt2800mmio >> >> rt2x00lib 55307 5 rt2x00pci,rt2800lib,rt2800pci, >> rt2800mmio,rt2x00mmio >> >> mac80211 626489 6 rtl_usb,rtlwifi,rt2x00lib,rt2x >> 00pci,rt2800lib,rtl8192cu >> >> cfg80211 484040 3 mac80211,rtlwifi,rt2x00lib >> >> >> >> and pci-id and RT5362 do not appear in dmesg: >> >> >> >> $ dmesg |grep RT5362 >> >> $ dmesg |grep pci-id >> >> $ >> >> >> >> >> >> On Fri, Aug 25, 2017 at 8:02 AM, Michael wrote: >> >> $ iwconfig >> >> lo no wireless extensions. >> >> >> >> >> >> On Fri, Aug 25, 2017 at 7:57 AM, Michael wrote: >> >> iwconfig doesn't see it >> >> >> >> On Thu, Aug 24, 2017 at 5:23 PM, Michael Butash >> wrote: >> >> Need to make sure the system sees it as a usable network device. Do: >> >> >> >> iwconfig ## verifies if the system sees it as a proper 802.11 device, >> and/or ap association >> >> ip link ## sees the nic as a real interface >> >> ip addr ## shows ip layer data, if it has an address >> >> cat /var/log/syslog | grep NetworkManager ## verfies if network-manager >> is trying to do anything with it >> >> >> >> Also, does the systray applet show the network scanning for any wifi >> devices? You should see *some* ssid's being found. >> >> >> >> -mb >> >> >> >> On Thu, Aug 24, 2017 at 1:45 PM, Michael wrote: >> >> or more as it is being detected just not transmitting data. what should I >> do? >> >> >> >> On Thu, Aug 24, 2017 at 4:34 PM, Michael wrote: >> >> lspci sees SOMETHING at least. It says >> >> 03:00.0 Network controller: Ralink corp. RT5362 PCI 802.11n Wireless >> Network Adapter >> >> >> >> so it is detected. >> >> >> >> The card in the other computer is almost identical It is pci-e wile the >> one not being detected is a pci card. >> >> >> >> On Thu, Aug 24, 2017 at 4:17 PM, Michael Butash >> wrote: >> >> Look at the pci devices with lspci, grep for network devices: >> >> >> >> >> lspci | grep Network >> >> >> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless >> Network Adapter (rev 32) >> >> >> >> You should see a like device there, your new card. If it's not being >> detected properly, search dmesg output looking for an unknown device, might >> be a firmware thing or something. Dmesg should at least tell you what >> pci-id, vendor, or model of chip to then google why that doesn't load under >> your os. >> >> >> >> -mb >> >> >> >> >> >> On Wed, Aug 23, 2017 at 4:30 PM, Michael wrote: >> >> I got two wireless cards (netis wf2118) for two computers. both computers >> have mint. One card is pci the other pci-e. the pci-e card works great. the >> pci not so much. the green connectivity light on the pci card is happily a >> solid green. Any ideas on how to get it to work?.... >> >> I just googled it and the one hit I got said he had a dead card. How can >> I tell if it is dead? >> >> >> >> -- >> >> :-)~MIKE~(-: >> >> >> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> >> >> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> >> >> >> >> -- >> >> :-)~MIKE~(-: >> >> >> >> >> >> -- >> >> :-)~MIKE~(-: >> >> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> >> >> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> >> >> >> >> -- >> >> :-)~MIKE~(-: >> >> >> >> >> >> -- >> >> :-)~MIKE~(-: >> >> >> >> >> >> -- >> >> :-)~MIKE~(-: >> >> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > > > > -- > :-)~MIKE~(-: > -- :-)~MIKE~(-: