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@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/1ZkeLVAytkRQW1q57YktgOh4lL8Vbf
> Dwa?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@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
--
James McPhee
jmcphe@gmail.com
---------------------------------------------------
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
(text/plain)