wireless card
James Mcphee
jmcphe at gmail.com
Wed Nov 22 19:40:22 MST 2017
[ 15.881957] ieee80211 phy0: rt2800_init_eeprom: Error - Invalid RF
chipset 0x5362 detected
says it hates your driver
probably should check the forums of whatever distro you're using for that
device to see if anyone else has problems. a google of the device name as
it shows in lspci shows lots of folk with various fiddliness with like
chips.
On Wed, Nov 22, 2017 at 7:22 PM, Michael <bmike1 at gmail.com> wrote:
> ~ $ lsmod |grep 2800pci
> rt2800pci 13606 0
> rt2800mmio 20986 1 rt2800pci
> rt2800lib 89076 2 rt2800pci,rt2800mmio
> rt2x00pci 13287 1 rt2800pci
> rt2x00mmio 13603 2 rt2800pci,rt2800mmio
> rt2x00lib 55307 5 rt2x00pci,rt2800lib,rt2800pci,
> rt2800mmio,rt2x00mmio
> eeprom_93cx6 13344 1 rt2800pci
>
>
> On Wed, Nov 22, 2017 at 9:17 PM, James Mcphee <jmcphe at gmail.com> wrote:
>
>> does lsmod show rt2800pci?
>>
>> On Wed, Nov 22, 2017 at 7:06 PM, Michael <bmike1 at gmail.com> wrote:
>>
>>> ~ $ sudo lspci
>>> [sudo] password for kodi:
>>> 00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller
>>> (rev 02)
>>> 00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root
>>> Port (rev 02)
>>> 00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI
>>> Controller (rev 02)
>>> 00:03.2 IDE interface: Intel Corporation 82Q35 Express PT IDER
>>> Controller (rev 02)
>>> 00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT
>>> Controller (rev 02)
>>> 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #4 (rev 02)
>>> 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #5 (rev 02)
>>> 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
>>> Controller #2 (rev 02)
>>> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
>>> Controller (rev 02)
>>> 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
>>> Port 1 (rev 02)
>>> 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #1 (rev 02)
>>> 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #2 (rev 02)
>>> 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #3 (rev 02)
>>> 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
>>> Controller #1 (rev 02)
>>> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
>>> 00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface
>>> Controller (rev 02)
>>> 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6
>>> port SATA Controller [AHCI mode] (rev 02)
>>> 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller
>>> (rev 02)
>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
>>> [AMD/ATI] Caicos PRO [Radeon HD 7450]
>>> 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI
>>> Audio [Radeon HD 6400 Series]
>>> 03:00.0 Network controller: Ralink corp. RT5362 PCI 802.11n Wireless
>>> Network Adapter
>>> kodi at kodi-OptiPlex-755 ~ $
>>>
>>> On Wed, Nov 22, 2017 at 8:17 PM, James Mcphee <jmcphe at gmail.com> wrote:
>>>
>>>> response with lspci output for wireless device would help. maybe it's
>>>> a known funky chipset. it's probably in the wall of text somewhere, but
>>>> lspci is a good tool for grabbing your peripherals.
>>>>
>>>> On Wed, Nov 22, 2017 at 5:05 PM, Michael <bmike1 at gmail.com> wrote:
>>>>
>>>>> My wireless card isn't working (never has). Could someone take a look
>>>>> and tell me what I need to do to get it to work? Here is a link to dmesg
>>>>> and and /var/log/syslog:
>>>>> https://drive.google.com/drive/folders/1ZkeLVAytkRQW1q57Ykt
>>>>> gOh4lL8VbfDwa?usp=sharing
>>>>>
>>>>> after inspecting the syslog I see that actually sees the wireless
>>>>> router but according to the gui there is 'no network connection' available.
>>>>> I believe things start falling apart around 7:1:20....
>>>>> that was this morning! When I started it this afternoon the network
>>>>> starts initiating around 17:23:19. or another start was around 17:42:01
>>>>>
>>>>> dmesg was a bit more helpful! (perhaps- look at the last line_
>>>>>
>>>>> [ 15.729249] ACPI Warning: 0x0000000000000828-0x000000000000082f
>>>>> SystemIO conflicts with Region \GLBC 1 (20131115/utaddress-251)
>>>>> [ 15.729254] ACPI Warning: 0x0000000000000828-0x000000000000082f
>>>>> SystemIO conflicts with Region \SACT 2 (20131115/utaddress-251)
>>>>> [ 15.729257] ACPI Warning: 0x0000000000000828-0x000000000000082f
>>>>> SystemIO conflicts with Region \SSTS 3 (20131115/utaddress-251)
>>>>> [ 15.729260] ACPI: If an ACPI driver is available for this device,
>>>>> you should use it instead of the native driver
>>>>> [ 15.729263] ACPI Warning: 0x00000000000008b0-0x00000000000008bf
>>>>> SystemIO conflicts with Region \GIC2 1 (20131115/utaddress-251)
>>>>> [ 15.729266] ACPI: If an ACPI driver is available for this device,
>>>>> you should use it instead of the native driver
>>>>> [ 15.729268] ACPI Warning: 0x0000000000000880-0x00000000000008af
>>>>> SystemIO conflicts with Region \GIC1 1 (20131115/utaddress-251)
>>>>> [ 15.729270] ACPI: If an ACPI driver is available for this device,
>>>>> you should use it instead of the native driver
>>>>> [ 15.729272] lpc_ich: Resource conflict(s) found affecting gpio_ich
>>>>> [ 15.747472] cfg80211: Calling CRDA to update world regulatory domain
>>>>> [ 15.794599] lp0: using parport0 (interrupt-driven).
>>>>> [ 15.824809] kvm: disabled by bios
>>>>> [ 15.872017] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5392,
>>>>> rev 0223 detected
>>>>> [ 15.881957] ieee80211 phy0: rt2800_init_eeprom: Error - Invalid RF
>>>>> chipset 0x5362 detected
>>>>> [ 15.881961] ieee80211 phy0: rt2x00lib_probe_dev: Error - Failed to
>>>>> allocate device
>>>>>
>>>>> --
>>>>> :-)~MIKE~(-:
>>>>>
>>>>> ---------------------------------------------------
>>>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> James McPhee
>>>> jmcphe at gmail.com
>>>>
>>>> ---------------------------------------------------
>>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>>
>>>
>>>
>>>
>>> --
>>> :-)~MIKE~(-:
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>
>>
>>
>>
>> --
>> James McPhee
>> jmcphe at gmail.com
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>
>
>
> --
> :-)~MIKE~(-:
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
--
James McPhee
jmcphe at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20171122/8c0ee670/attachment.html>
More information about the PLUG-discuss
mailing list