I Just installed a fresh copy of Kodi to my HTPC and the WIFI card I have worked great! I was able join my network then place the most current build into the UPDATE folder.
After I rebooted Kodi WIFI connections were no longer available.
Will I be forced to use older builds, or is there somthing I can do to get my WIFI card working?
Rosewill RNX-AC1900PCE
LibreELEC-Generic.x86_64-9.0-Milhouse-20181018210245-#1018-g86e23ee
Help with WIFI
-
theboy181 -
October 19, 2018 at 3:52 AM -
Thread is Unresolved
-
-
- Official Post
I would try the stable LibreELEC-9.0 update channel. Post the log file, if the stable release doesn't work. See here how to post kodi.log.
-
- Official Post
The first question for all "my wireless doesn't work" questions is .. what chipset is in the wireless device?
-
https://wikidevi.com/wiki/rosewill_rnx-ac1900pce
Is there a way to tell from within kodi? -
Da Flex. I did roll it back to stable LibreELEC-9.0 and its working. That said should I be doing something to report that its not in the latest build?
-
- Official Post
BCM4360 should be supported by the "wl" driver in Generic images. Provide "dmesg" output from a clean boot using the 006 alpha release.
-
I will after I get my new HW all installed. What do I need to do, exactly to get the output?
-
- Official Post
-
Should it work with LibreELEC-Generic.x86_64-9.0-Milhouse-20181020002309-#1019-g86e23ee.tar
I really want to be able to use netflix.
Update:
I tired to update so that I could use Netflix, but my Wifi card stopped working after the update. Should I upload the log, or is it pointless? -
- Official Post
If you share the log we can see if there's an obvious problem. If you don't share the log .. we are not clairvoyant. It's entirely your choice.
-
-
- Official Post
Code
Display MoreOct 19 23:54:25 kernel: bcma: bus0: Found chip with id 0x4360, rev 0x03 and package 0x01 Oct 19 23:54:25 kernel: bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x2B, class 0x0) Oct 19 23:54:25 kernel: bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x2A, class 0x0) Oct 19 23:54:25 kernel: bcma: bus0: Core 2 found: ARM CR4 (manuf 0x4BF, id 0x83E, rev 0x02, class 0x0) Oct 19 23:54:25 kernel: bcma: bus0: Core 3 found: PCIe Gen2 (manuf 0x4BF, id 0x83C, rev 0x01, class 0x0) Oct 19 23:54:25 kernel: bcma: bus0: Core 4 found: USB 2.0 Device (manuf 0x4BF, id 0x81A, rev 0x11, class 0x0) Oct 19 23:54:25 kernel: bcma: Unsupported SPROM revision: 11 Oct 19 23:54:25 kernel: bcma: bus0: Invalid SPROM read from the PCIe card, trying to use fallback SPROM Oct 19 23:54:25 kernel: bcma: bus0: Using fallback SPROM failed (err -2) Oct 19 23:54:25 kernel: bcma: bus0: No SPROM available Oct 19 23:54:25 kernel: bcma: bus0: Bus registered
^ looks like the card is trying to use the in-kernel brcmfmac driver instead of the vendor wl driver, so perhaps blacklist it and reboot:
sorted?
-
I SSH'd into my HTCP and ran the echo you mentioned above using my NIC over the LAN.
There was no change to the WIFI, and I saw now wireless connection settings in kodi's settings.
I used root to send the echo, is there something else missing?
-
reinstalled the latest Nightly .20
blacklisted the WIFI as instructed above
Still cant see the wifi connections.I have 3 different wifi devices (2 of them USB) and they all dont work. I would love to get my ac1900 working. Any other ideas?
All my wifi devices plugged in.
-
- Official Post
what does "lsmod" show?
-
Module Size Used by
8021q 24576 0
nvidia_modeset 1024000 4
wl 6381568 0
mt7601u 94208 0
mac80211 569344 1 mt7601u
snd_hda_codec_hdmi 49152 1
nvidia 16482304 166 nvidia_modeset
intel_powerclamp 16384 0
intel_rapl 20480 0
cfg80211 552960 3 wl,mt7601u,mac80211
rfkill 20480 2 cfg80211
bcma 49152 0
snd_hda_intel 36864 3
snd_hda_codec 106496 2 snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 16384 1 snd_hda_codec
snd_hda_core 65536 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
pcc_cpufreq 16384 0
uvesafb 28672 1
-
echo "blacklist bcma" > /storage/.config/modprobe.d/brcmfmac.conf
rebootThis worked! ! I guess you meant that from the beginning.
-
- Official Post
Looks like the device ID exists in both drivers (bcma and wl) so whichever one happens to be loaded by the kernel first (roll dice) tries to claim the device. We should probably patch out the device ID to prevent that.
-