Asus pce-ac88 not working

Hi!

*
Today, once I was ready to install the OS, rerelocate XFCE and also install Plasma, I uncovered a problem I wasn’t expecting, my netjob-related adapter doesn’t job-related via the October release (I haven’t checked previous releases). I have an ASUS PCE-AC88. Some importat things to include, when I had AntergOS I had a similar difficulty, yet I addressed that by developing a little archive called (if I remember correctly) brcmfmac4366c-pcie.bin that you had to copy inside the /lib/firmware/brcm magazine and also after doing that the adaptor can begin functioning, I thought that probably that was the case through vr-tab-quebec.com, so I determined to examine if Manjaro had those papers currently there (as it functions without having to “insert” that little bit file) and also the file is already tbelow, no have to carry out anypoint else, I then checked if the vr-tab-quebec.com records mechanism had actually it also, and also, surprisingly, it is tbelow, yet it doesn’t job-related anymeans, which is exceptionally stvariety to me. So possibly there’s somepoint else preventing my wiremuch less adapter from functioning via this OS.Has anyone else mounted the OS on a computer system through that very same wireless adapter? Did it work-related without any kind of tweaks? if it didn’t job-related via the live OS, did it job-related when installed? if it didn’t, did you make it work? how?Any help about this issue will certainly be very appreciated.THANKS in advance!
*




You watching: Asus pce-ac88 not working

ricklinux November 21, 2019, 4:43am #2

Have you tried the dkms version? broadcom-wl-dkms Give that a shot and check out.


joekamprad November 21, 2019, 12:22pm #3

without giving any type of logs we just might usage a

*
to aid you…

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && cat log.txt | curl -F "f:1=(https://vr-tab-quebec.com.com/docs/vr-tab-quebec.com/how-to-include-systemlogs-in-your-post/)


I guess I did, for what it seems that’s the one that comes by default on the October EOS release, in fact the dkms and also the brcm files are there, yet, it doesn’t job-related.Also,
joekamprad, I will attempt to get those files this particular day, I haven’t installed the OS yet I guess the live CD have to show the very same log papers, so… I’LL BE BACK!

*




See more: Acpi Smo8800 Windows 7 Driver Download, AcpiSmo8800 Dell

*
dante_igashu:

the live CD need to show the very same log files

yes it will hopecompletely give some error or faientice on the wifi gadget so we can see what is missing…


Okay, the pastebinit isn’t working for the Live CD log file, so I pasted it somewhere else, right here is the connect for the log.txt via the command you gave using the Live CD log.txt, and below is very same command but running Manjaro log.txt (Manjaro), I put this one also bereason I guess it can be beneficial as well, as the adapter is working simply fine in Manjaro.Thanks Once More!

*


It looks prefer it have to be making use of brcmfmac for the driver. If you say the firmware is tright here i wonder if it’s simply not loading on the live ISO? Hmm? As you say i wonder if it works after installation? I don’t understand unmuch less you might test it. I think it is the BCM4366 chipcollection so right here is some details.

https://wiremuch less.wiki.kernel.org/en/users/drivers/brcm80211


live-ISO logs:

Nov 22 03:43:46 archiso kernel: wl: loading out-of-tree module taints kernel.Nov 22 03:43:46 archiso kernel: wl: module license "MIXED/Proprietary" taints kernel.Nov 22 03:43:46 archiso kernel: Disabling lock debugging due to kernel taintNov 22 03:43:46 archiso kernel: wl: module confirmation failed: signature and/or compelled crucial missing - tainting kernelNov 22 03:43:46 archiso kernel: wl 0000:09:00.0: permitting device (0000 -> 0002)Nov 22 03:43:46 archiso kernel: wl driver 6.30.223.271 (r587334) failed through code 1Nov 22 03:43:46 archiso kernel: ERROR
wl_cfg80211_detach : Nov 22 03:43:46 archiso kernel: NULL ndev->ieee80211ptr, unable to deref wlNov 22 03:43:46 archiso kernel: wl driver 6.30.223.271 (r587334) failed through code 1Nov 22 03:43:46 archiso kernel: ERROR


See more: “Outlook Cannot Open This Item Outlook 2007 : Cannot Open This Item

wl_cfg80211_detach :

manjaro:

Nov 21 21:54:36 DANTEXTRMCOMPUTER kernel: brcmfmac: brcmf_fw_alloc_request: utilizing brcm/brcmfmac4366c-pcie for chip BCM4366/4Nov 21 21:54:36 DANTEXTRMPC kernel: brcmfmac 0000:09:00.0: Direct firmware fill for brcm/brcmfmac4366c-pcie.Gigabyte Technology Co., Ltd.-AX370-Gaming K7.txt failed via error -2Nov 21 21:54:36 DANTEXTRMCOMPUTER kernel: brcmfmac 0000:09:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed via error -2***Nov 21 21:54:37 DANTEXTRMCOMPUTER kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4Nov 21 21:54:37 DANTEXTRMPC kernel: brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), tool might have limited networks availableNov 21 21:54:37 DANTEXTRMPC kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4366/4 wl0: Nov 5 2018 03:19:56 variation 10.28.2 (r769115) FWID 01-d2cbb8fd***Nov 21 21:54:39 DANTEXTRMPC wpa_supplicant<797>: Failed to develop interchallenge p2p-dev-wlp9s0: -52 (Invalid exchange)Nov 21 21:54:39 DANTEXTRMCOMPUTER wpa_supplicant<797>: nl80211: Faibrought about create a P2P Device interface p2p-dev-wlp9s0Nov 21 21:54:39 DANTEXTRMPC wpa_supplicant<797>: P2P: Failed to enable P2P Device interfaceNov 21 21:54:39 DANTEXTRMPC kernel: ieee80211 phy0: brcmf_p2p_set_firmware: fairesulted in upday tool resolve ret -52Nov 21 21:54:39 DANTEXTRMCOMPUTER kernel: ieee80211 phy0: brcmf_p2p_create_p2pdev: collection p2p_disc errorNov 21 21:54:39 DANTEXTRMCOMPUTER kernel: ieee80211 phy0: brcmf_cfg80211_add_iface: include ichallenge p2p-dev-wlp9s0 type 10 failed: err=-52Nov 21 21:54:39 DANTEXTRMCOMPUTER wpa_supplicant<797>: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interconfront.P2PDevice dbus_property=P2PDeviceConfig getter failedNov 21 21:54:39 DANTEXTRMCOMPUTER NetworkManager<696>: <1574394879.7558> sup-iface<0x558b76214920,wlp9s0>: supports 5 shave the right to SSIDsNov 21 21:54:39 DANTEXTRMPC NetworkManager<696>: <1574394879.7564> tool (wlp9s0): supplicant interchallenge state: starting -> readyNov 21 21:54:39 DANTEXTRMCOMPUTER NetworkManager<696>: <1574394879.7564> Wi-Fi P2P tool regulated by interconfront wlp9s0 createdNov 21 21:54:39 DANTEXTRMPC NetworkManager<696>: <1574394879.7566> manager: (p2p-dev-wlp9s0): brand-new 802.11 Wi-Fi P2P gadget (/org/freedesktop/NetworkManager/Devices/5)Nov 21 21:54:39 DANTEXTRMCOMPUTER NetworkManager<696>: <1574394879.7569> gadget (p2p-dev-wlp9s0): state change: unregulated -> unavailable (reason "managed", sys-iface-state: "external")Nov 21 21:54:39 DANTEXTRMPC NetworkManager<696>: <1574394879.7573> sup-iface: faicaused cancel p2p connect: P2P cancel failedNov 21 21:54:39 DANTEXTRMCOMPUTER NetworkManager<696>: <1574394879.7575> gadget (p2p-dev-wlp9s0): state change: unaccessible -> dislinked (reason "none", sys-iface-state: "managed")Nov 21 21:54:39 DANTEXTRMCOMPUTER NetworkManager<696>: <1574394879.7577> gadget (wlp9s0): state change: unaccessible -> disconnected (factor "supplicant-available", sys-iface-state: "managed")So on Live-ISO fails to fill the driver may caused by instcapacity of the driver pack only… and at manjaro you have the right to see additionally failing to acquire the firmware and is functioning unsteady at all as it is providing a lot error on the journal also…

I would certainly give LTS Kernel a possibility (if you get/want EnOS set up over wired connection)

superform pacmale -S linux-lts linux-lts-headers broadcom-wl-ltssucarry out mkinitcpio -Psuexecute grub-mkconfig -o /boot/grub/grub.cfgsuexecute systemctl rebootand choose LTS kernel to boot from boot menu!!

From Live-ISO you could try to unload WL module and also loadbrcmfmac instead:

sucarry out rmmod wlsuperform modprobe brcmfmacwhile watching live journal journalctl -fin a second terminal…


Hi!Could it be that those errors in Manjaro are brought about by the driver not being “designed” to job-related through 5Ghz? the details I have checked out about the driver states it will certainly just work through 2.4Ghz, it only finds the 2.4Ghz Wi-Fi signals around in truth, so possibly it is trying to load the driver for 5Ghz however it can’t?

*
I’ll attempt to load the brcfmac tonight.THANKS joekamprad!!!
*