Jump to content
2 posts in this topic

Recommended Posts

 

 

there is a motherboard Asus H81T in it the adapter bcm94331cd is installed through an adapter,

781069876_2020-03-2623_36_46.png.2c3fbb8b9ce3396528848600c31f7678.png

wifi does not work without clover settings and kext (although this adapter was used for a long time in the Sierra system and everything worked),
Kext AirportBrcmFixup allowed to determine WIFI and it works beautifully in 2.4 GHz, but the card does not work in 5GHz mode, although there is a connection to the router and the router gives an IP address (albeit longer than 2.4)

I tried to set different countries through the argument brcmfx-country= did not help, either it did not work at all or the same way.
I tried to use the brcmfx-driver= parameter, it works only when brcmfx-driver=1, and then only 2.4GHz works in this mode, WIFI 5GHz does not even look.

In windows 10 everything works fine on this hardware

 

screen shots when connected to a 5g network

1236508627_2020-03-2621_54_08.png.73807c8687235e0a240137df1d3d3fcb.png904666926_2020-03-2621_36_15.png.74df13e7603e289543bef59fa16f2e04.png

 

 

test in console 5GHz

>:curl google.com -m 10
curl: (7) Failed to connect to google.com port 80: Operation timed out

>:ping google.com -c 20
PING google.com (64.233.163.113): 56 data bytes
64 bytes from 64.233.163.113: icmp_seq=0 ttl=41 time=128.415 ms
64 bytes from 64.233.163.113: icmp_seq=1 ttl=41 time=41.624 ms
64 bytes from 64.233.163.113: icmp_seq=2 ttl=41 time=759.356 ms
64 bytes from 64.233.163.113: icmp_seq=3 ttl=41 time=393.776 ms
64 bytes from 64.233.163.113: icmp_seq=4 ttl=41 time=69.126 ms
64 bytes from 64.233.163.113: icmp_seq=5 ttl=41 time=57.535 ms
64 bytes from 64.233.163.113: icmp_seq=6 ttl=41 time=40.581 ms
64 bytes from 64.233.163.113: icmp_seq=7 ttl=41 time=147.680 ms
64 bytes from 64.233.163.113: icmp_seq=8 ttl=41 time=37.702 ms
64 bytes from 64.233.163.113: icmp_seq=9 ttl=41 time=42.357 ms
64 bytes from 64.233.163.113: icmp_seq=10 ttl=41 time=91.294 ms
64 bytes from 64.233.163.113: icmp_seq=11 ttl=41 time=32.100 ms
64 bytes from 64.233.163.113: icmp_seq=12 ttl=41 time=56.324 ms
64 bytes from 64.233.163.113: icmp_seq=13 ttl=41 time=28.981 ms
64 bytes from 64.233.163.113: icmp_seq=14 ttl=41 time=114.478 ms
64 bytes from 64.233.163.113: icmp_seq=15 ttl=41 time=406.602 ms
64 bytes from 64.233.163.113: icmp_seq=16 ttl=41 time=247.047 ms
64 bytes from 64.233.163.113: icmp_seq=17 ttl=41 time=37.130 ms
64 bytes from 64.233.163.113: icmp_seq=18 ttl=41 time=52.197 ms
64 bytes from 64.233.163.113: icmp_seq=19 ttl=41 time=360.568 ms

--- google.com ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 28.981/157.244/759.356/183.998 ms

 

test in console 2.4GHz

>:ping google.com -c 20
PING google.com (64.233.163.102): 56 data bytes
64 bytes from 64.233.163.102: icmp_seq=0 ttl=40 time=29.244 ms
64 bytes from 64.233.163.102: icmp_seq=1 ttl=40 time=34.057 ms
64 bytes from 64.233.163.102: icmp_seq=2 ttl=40 time=30.471 ms
64 bytes from 64.233.163.102: icmp_seq=3 ttl=40 time=31.533 ms
64 bytes from 64.233.163.102: icmp_seq=4 ttl=40 time=30.793 ms
64 bytes from 64.233.163.102: icmp_seq=5 ttl=40 time=27.310 ms
64 bytes from 64.233.163.102: icmp_seq=6 ttl=40 time=34.731 ms
64 bytes from 64.233.163.102: icmp_seq=7 ttl=40 time=37.340 ms
64 bytes from 64.233.163.102: icmp_seq=8 ttl=40 time=34.127 ms
64 bytes from 64.233.163.102: icmp_seq=9 ttl=40 time=31.942 ms
64 bytes from 64.233.163.102: icmp_seq=10 ttl=40 time=30.383 ms
64 bytes from 64.233.163.102: icmp_seq=11 ttl=40 time=35.625 ms
64 bytes from 64.233.163.102: icmp_seq=12 ttl=40 time=30.906 ms
64 bytes from 64.233.163.102: icmp_seq=13 ttl=40 time=29.679 ms
64 bytes from 64.233.163.102: icmp_seq=14 ttl=40 time=59.688 ms
64 bytes from 64.233.163.102: icmp_seq=15 ttl=40 time=31.159 ms
64 bytes from 64.233.163.102: icmp_seq=16 ttl=40 time=28.696 ms
64 bytes from 64.233.163.102: icmp_seq=17 ttl=40 time=32.336 ms
64 bytes from 64.233.163.102: icmp_seq=18 ttl=40 time=28.234 ms
64 bytes from 64.233.163.102: icmp_seq=19 ttl=40 time=31.067 ms

--- google.com ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 27.310/32.966/59.688/6.616 ms

>:curl google.com -m 10
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="http://www.google.com/sorry/index?continue=http://google.com/&amp;q=EgRfGaEsGLTr8_MFIhkA8aeDS5TZXndxZ2y8F0M3SyQlTEZprHXgMgFy">here</A>.
</BODY></HTML>

when ping for some reason ttl changes from 40 to 41

 

I also tried FakePCIID_Broadcom_WiFi.kext, it did not help

 

As it turned out, there is everything connected to the Internet through 5GHz but it is very slow

>:speedtest-cli --timeout 100
Retrieving speedtest.net configuration...
Testing from Beeline Home (95.25.120.170)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by DOM.RU (Saint Petersburg) [5.58 km]: 244.885 ms
Testing download speed................................................................................
Download: 0.05 Mbit/s
Testing upload speed................................................................................................
Upload: 0.08 Mbit/s

in windows 10 Wifi 5GHz - Download/Upload: ~90 Mbit/s

mac os wifi 2.4Ghz  - Download/Upload: ~90 Mbit/s

 

How to fix the speed at 5GHz?

×
×
  • Create New...