DW1830 wifi performance issues #56
Comments
|
Hi, I connected the 2 antennas on pin 1 and 2. Did you remove the tape on the antennas near the hinge? Here is a speedtest on my 5GHz: Possible error (and a joke): Do you use the new LG 5k Montior for Apple products? :) |
|
I resecured the tape on the hinge after connecting the antennas. I plugged
them in the same position as the dw1820 it replaced, black cable plugged
into where black triangle is, white cable plugged to where white triangle
is on the label. I get full throughput of the card when I use win 10. Seems
like you are having performance issues too. I wish I was rich enough for
those 5k monitors to be the problem :) .
If you need any additional command output, feel free to let me know and I
can provide. It's been several years since I did my last hackintosh but I'm
comfortable in Linux environments so not afraid of the terminal.
…On Feb 13, 2017 6:26 AM, "furrybanana" ***@***.***> wrote:
Hi,
I connected the 2 antennas on pin 1 and 2. Did you remove the tape on the
antennas near the hinge?
Here is a speedtest on my 5GHz:
[image: wifi_speeds]
<https://cloud.githubusercontent.com/assets/25349617/22883318/f28a44d8-f1ef-11e6-8f65-5bd07a00e0e2.jpg>
Possible error (and a joke): Do you use the new LG 5k Montior for Apple
products? :)
http://www.techradar.com/news/lgs-5k-monitor-for-macs-
doesnt-like-being-near-routers
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYiKHa4WBvuQ2K6Zm27iokbK9dJVttcKks5rcEvcgaJpZM4L-i57>
.
|
|
Follow. I ordered the same card and I'm interested in this 👍 |
|
@furrybanana @filequit try putting the white antenna on the grey triangle and the black one on either white or black. I get full wifi throughput in macOS like this. I haven't tested in Windows. |
|
@squash- I tried it with grey/white and grey/black and still same results. what is odd is that the 2.4ghz performs better than the 5ghz, when typically its the opposite. Did you just follow latest deploy.sh from syscl or did you modify any other kexts? |
|
@filequit I'm assuming you also checked your router settings, correct? I was not getting very good speed with my DD-WRT configuration so I had to change a few things on that to make it work for this card and MacOS. For example it doesn't like dd-wrt setting of Channel Width = VHT (80+80 MHz). |
|
@R1MnTnA - that did fix the issue. However that means I won't be able to run at full ac bandwidth that my Netgear r7000 offers and some of my other clients (including this card) can take advantage of. Is this just a bug with the fakepciid kext or is it an incompatibility with OS X? Would hooking up the third antenna lead resolve the problem? |
|
I should also note that while I'm getting close to 200mbit speeds on 5ghz now, it's still less than the 300mbit speed I get from my ISP and could obtain with 80mhz wide channels in Windows with the same card |
|
@filequit wow I can't believe I guessed that was the same problem I had and you have the same router I do! Lol :-D cool. |
|
I did try removing the broadcom fakepciid kext and saw it reported as third party wireless card in system profiler, but still same performance degradation once I kick up to 80mhz channels. Im thinking it may be something with the airportbrcm4360 kext and the dw1830 running in 80mhz mode. |
|
And now that I remember, my previous MacBook Pro (a real one) had no problems with the 80mhz. It was very fast. Unfortunately I don't have that MacBook anymore, so unfortunately I can't get any info to maybe help troubleshoot this problem, but maybe if someone else has one and is running on the same router setup, we could possibly get some useful info to fake it or modify a kext or patch the OS so this DW1830 could work. |
|
@filequit I think I may have found the answer to our problem. Although I can't try this now, but maybe you can. - Someone on the forums had the same issue, here is what he did- Changed the country code. - https://www.tonymacx86.com/threads/guide-airport-pcie-half-mini-v2.104850/page-143#post-1127441 |
|
Something like this might work as well. - http://apple.stackexchange.com/questions/9768/change-mac-os-x-wireless-card-country-code/129681#129681 |
|
@R1MnTnA Nice! I will look into it and add the patches if it works. Thank you, |
|
Hi @filequit @furrybanana @ZombieTheBest @squash- @R1MnTnA Please try the latest config.plist under my Clover/ Here's the new patch I add in the config.plist Thanks for @R1MnTnA 's tip, this patch fix my Precision M3800 slow Wi-Fi issue, though I haven't had Wi-Fi issue on XPS 13 9350(maybe I'm in United States?). Wish this help! |
|
@syscl Excellent! Glad I could be of assistance. Obviously the guys that discovered this are truly the ones we need to thank. But Wow, That was fast! Thanks for updating this so quickly. I'll have to try it later today when I get home. I'll let you know how it goes. Thanks again! |
|
Hi, Biggest thing now: Display Brightness with F11 and F12 does not work any longer for me. :( |
|
Didn't fix the slowness for me on 80mhz channel, and f11/f12 brightness broken here as well. My country code before the new config.plist showed as US in system profiler too. What is interesting is that the channel number shows as 161 then -1 which doesnt appear to be a valid wifi channel
|
|
@furrybanana try these patches for the keyboard brightness keys, in your DSDT. You'll have to use MaciASL or other DSDT editors and patch it manually. Go to the following thread and scroll down to Set OSIS to linux (credit ) instructions. After you do that patch then the next patch under that will be the main keyboard patch. - |
|
@filequit see above for keyboard patch. |
|
@R1MnTnA - I am using the stock r7000 firmware so only setting i have is up to 600mbit/ up to 1300mbit for 5ghz (which is equivalent of 40mhz channel to 80mhz channel) |
|
When trying on a different router/ISP I get still slow downloads with 80mhz channel, but upstream i was pulling over 200mbit on a fiber ISP (att gigapower)... so it appears the issue is isolated just to the downstream portion |
|
@furrybanana Re dump all your ACPI tables, remove all your old and patched ACPI tables, re run the deploy.sh That's it. No more fixed need. syscl |
|
@syscl |
|
@furrybanana I don't know what you change, brightness key has been fixed for quiet a long time. Double check which driver you use, and if system has some other touchpad driver that cause the brightness malfunction. syscl |
|
I had to revert to the commit before you switched backlight kext to get it
back for me
…On Sat, Feb 18, 2017 at 10:03 AM Zhou Yating ***@***.***> wrote:
@furrybanana <https://github.com/furrybanana> I don't know what you
change, brightness key has been fixed for quiet a long time.
Double check which driver you use, and if system has some other touchpad
driver that cause the brightness malfunction.
syscl
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYiKHc7zz02J7SVp-UaMQb2nGyUCTa1bks5rdxZBgaJpZM4L-i57>
.
|
|
@furrybanana @filequit do you have 1920x1080p model? If yes, then I need to add id for your panel. Because I don't have 1920x1080p model, I need your help to provide correct information for me. Thank you! Seems I forget to add PNLF id for your models. Please provid information after executing the follwing in terminal uid=10
ioreg -n AppleBacklightDisplay -arxw0>/tmp/syscl.plist
id=`/usr/libexec/PlistBuddy -c "Print :0:DisplayProductID" /tmp/syscl.plist`
id=`printf "F%02dT%04x" $uid $id`
echo $idI will add injector for you! Thank you, |
|
MacBook-Pro:~ clayton$ uid=10 |
|
@R1MnTnA What's the output on your XPS 13 9360? uid=10
ioreg -n AppleBacklightDisplay -arxw0>/tmp/syscl.plist
id=`/usr/libexec/PlistBuddy -c "Print :0:DisplayProductID" /tmp/syscl.plist`
id=`printf "F%02dT%04x" $uid $id`
echo $idThank you, |
|
@syscl id: F10T144a |
|
@furrybanana Do you use rc script? Install latest Clover choose 'RC Script'. syscl |
|
@syscl do you include this patch for Coredisplay for QHD resolution in your script? |
|
@furrybanana The patch for CoreDisplay is discovered by me, why do you think I don't include this patch for non-Iris QHD model(yes, Iris do not require QHD patch)? You should pay attention to the piece of code in my deploy function _unlock_pixel_clock()
{
if [ $gMINOR_VER -ge $gDelimitation_OSVer ];
then
#
# 10.12+
#
gTarget_rhd_Framework="$gMountPoint/System/Library/Frameworks/CoreDisplay.framework/Versions/Current/CoreDisplay"
else
#
# 10.12-
#
gTarget_rhd_Framework="$gMountPoint/System/Library/Frameworks/IOKit.framework/Versions/Current/IOKit"
fi
sudo perl -i.bak -pe 's|\xB8\x01\x00\x00\x00\xF6\xC1\x01\x0F\x85|\x33\xC0\x90\x90\x90\x90\x90\x90\x90\xE9|sg' ${gTarget_rhd_Framework}
_tidy_exec "sudo codesign -f -s - ${gTarget_rhd_Framework}" "Patch and sign framework for Recovery HD"
}and here function _getEDID()
{
#
# dump kext load status
#
local gKextStatus=$(kextstat)
#
# Whether the Intel Graphics kernel extensions are loaded in cache?
#
if [[ ${gKextStatus} == *"AppleIntelSKLGraphicsFramebuffer"* && ${gKextStatus} == *"AppleIntelSKLGraphics"* ]];
then
#
# Yes. Then we can directly assess EDID from ioreg.
#
# Get raw EDID.
#
gEDID=$(ioreg -lw0 | grep -i "IODisplayEDID" | sed -e 's/.*<//' -e 's/>//')
#
# Get native resolution(Rez) from $gEDID.
#
# Get horizontal resolution. Arrays start from 0.
#
# Examples:
#
# 00ffffffffffff004c2d240137314a4d0d1001036c221b782aaaa5a654549926145054bfef808180714f010101010101010101010101302a009851002a4030701300520e1100001e000000fd00384b1e510e000a202020202020000000fc0053796e634d61737465720a20
# ^
# ^^
# ^
# ^^
gHorizontalRez_pr=${gEDID:116:1}
gHorizontalRez_st=${gEDID:112:2}
gHorizontalRez=$((0x$gHorizontalRez_pr$gHorizontalRez_st))
#
# Get vertical resolution. Actually, Vertical rez is no more needed in this scenario, but we just use this to make the
# progress clear.
#
gVerticalRez_pr=${gEDID:122:1}
gVerticalRez_st=${gEDID:118:2}
gVerticalRez=$((0x$gVerticalRez_pr$gVerticalRez_st))
else
#
# No, we cannot assess EDID from ioreg. But now the resolution of current display has been forced to the highest resolution as vendor designed.
#
gSystemRez=$(system_profiler SPDisplaysDataType | grep -i "Resolution" | sed -e 's/.*://')
gSystemHorizontalRez=$(echo $gSystemRez | sed -e 's/x.*//')
gSystemVerticalRez=$(echo $gSystemRez | sed -e 's/.*x//')
fi
#
# Patch IOKit/CoreDisplay?
#
local gIntelGraphicsCardInfo=$(ioreg -lw0 |grep -i "Intel Iris Graphics" |sed -e "/[^<]*<\"/s///" -e "s/\"\>//")
if [[ "${gIntelGraphicsCardInfo}" == *"Iris"* ]];
then
#
# Iris version, no IOKit/CoreDisplay patch require
#
gPatchIOKit=${kBASHReturnFailure}
else
if [[ $gHorizontalRez -gt 1920 || $gSystemHorizontalRez -gt 1920 ]];
then
#
# Yes, We indeed require a patch to unlock the limitation of flash rate of IOKit to power up the QHD+/4K display.
#
# Note: the argument of gPatchIOKit is set to 0 as default if the examination of resolution fail, this argument can ensure all models being powered up.
#
gPatchIOKit=${kBASHReturnSuccess}
else
#
# No, patch IOKit is not required, we won't touch IOKit(for a more intergration/clean system since less is more).
#
gPatchIOKit=${kBASHReturnFailure}
fi
fi
#
# Passing gPatchIOKit to gPatchRecoveryHD.
#
gPatchRecoveryHD=${gPatchIOKit}
}That's it. |
I did nothing special to my clover or xps. Just run your script. Ever since the intel backlight was added I had problems witch backlight buttons, now it is fixed, but not after a reboot always at max 100 brightness. I'll reset the machine and do a reinstall if I find the time for it. I plan to try the latest 1.4.13 bios too.
|
|
@syscl and @furrybanana I think there was some confusion here on who wrote the question about the Coredisplay patch. I'm sorry syscl I had not known you had originally wrote that patch. I was just merely asking the question because it came up in the 9360 guide on the forums that someone recently posted and so I was just curious and too lazy or didn't have time to look through your script. Thanks for clarifying that info and again amazing job with writing and figuring out that patch. How long ago did you write it? |
|
So, Slow WiFi issue has been fixed? I should still buy DW 1830 or 1560 is better? Thank you :) |
|
I just installed DW1830 and wifi connection is seriously bad. ping to router is in tens of seconds with packages often dropped altogether. It seems to settle sometimes and works for a short while with pings in milliseconds. Worth noting is that my other devices at home have speeds close to 1300MBps and ping constantly in milliseconds - and it's no surprise since I use Ubiquity UniFy access point. |
|
@kultigspritzig Using latest Deploy/config.plist? How did u connected the two antenna Wires? |
|
I have resolved the problem! Changed the country to code #a from US, and applied the 94352 fcvo patch, both obtained from @the-darkvoid 's config.plist for the 9530. Getting full 867mbps as expected with two antenna leads in Sierra on my FHD 9350. I'm not sure if the fcvo one is actually needed, as I attempted both patches at once, but it is working now for me! Here are the relevant entries in my config.plist: |
|
@filequit this fixes my issue as well, the connection seems much more stable with pings closer to 1-3ms, although every now and then I get response time in hundreds of ms. So although still not as good as under Windows, it's passable. Thanks! EDIT: Strangely, it seems now to fallback to 2.4GHz connection more eagerly than before. Essentially it connects at 5GHz but then continues to run at 2.4GHz all the time. |
|
@filequit and @ZombieTheBest He actually has the fcvo patch already, but those of us in the US had issues withe #a fix so he changed it to US. Maybe when he has time he can put in an option in the script to ask the user if they are in the US or outside the US to incorporate the correct patch. |
|
My config plist did not have the fcvo patch before from deploy.sh and the country code patch made it set to us, where I am located and it didn't fix anything. Putting the fcvo patch for the 94352 and changing the country code to the global #a allowed my dw1830 to connect beyond 300mbps to 867mbps which is what is max expected with 2 antennas |
|
@filequit Oh ok, I see. And I was using both the US patch and the fcvo and I was only able to connect to 5Ghz in 40mhz channel and around 500Mbps now that I changed it back #a patch, I can connect on the 80mhz channel and now up to 1053Mbps with 3 wires. I thought the US fixed my original problem, but I guess not. EDIT: Now up to full speed 1300Mbps! |
|
@kultigspritzig - I would recommend having separate SSIDs for your 2.4ghz and 5ghz networks so you can manually control which frequency you are connecting to, as performance for 5ghz networks drops pretty steadily at further distances and I've found the OS's frequency switching to never quite act the way I want it to (in Windows or OS X), and there isnt much in the way of tuning you can do. |
|
But then again without these patches it would stay connected to 5GHz and
not resort to 2.4. And two other alreal MacBooks connected to same AP stick
to 5GHz, so it can't be just a generic macOS issue.
…On Sun, Feb 26, 2017 at 1:37 AM filequit ***@***.***> wrote:
@kultigspritzig <https://github.com/kultigspritzig> - I would recommend
having separate SSIDs for your 2.4ghz and 5ghz networks so you can manually
control which frequency you are connecting to, as performance for 5ghz
networks drops pretty steadily at further distances and I've found the OS's
frequency switching to never quite act the way I want it to (in Windows or
OS X), and there isnt much in the way of tuning you can do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYcStF2K1hrsATZVliyk22niSjb_Pi33ks5rgR2qgaJpZM4L-i57>
.
|
|
I'm not sure the patches themselves indicate anything in regards to roaming/frequency hopping, just changing country code and setting fcvo power settings. I'm currently at work which has a wifi network that broadcasts same SSID on 2.4 and 5 ghz, and it is staying connected to the 5ghz network on channel 36 (granted this is only a 20mhz wide network, which may come into play too). I believe that the wireless ap's firmware can also tell clients to connect on either 2.4ghz or 5ghz depending on how they are configured (your AP may not like seeing wifi client that has a "global" country code). |
|
@filequit @furrybanana @ZombieTheBest @squash- @R1MnTnA Nice discovery! Thank you! So how about disable Thank you, |
|
@filequit my AP not liking global country code seems like a reasonable explanation. I will see if I can dig some details from ubiquity logs. @syscl I tested with and without fcvo patch and from my perspective it doesn't do anything. The global country code is enough to have 80211ac running at full speeds in US. |
|
I finally got my DW1830 card! I just closed my laptop back, for now it seems to work very very well here in Europe without any config. |
|
@ZombieTheBest |
|
#a only is all that is needed for the fix - i removed fcvo from my clover.plist with no bad results. going to close this one out. thanks everyone for the assistance |
|
@filequit or anyone who can please help me, |
|
@R1MnTnA I know this is an old thread, but you stated earlier:
Where did you buy the third wire? Where did you run it on the outside of the laptop? When I had my Zenbook Hackintosh I did the same thing, but that was a long time ago. |
|
@ggctseng I purchased the extra wire on eBay. IPEX MHF4 NGFF M.2 wifi antenna cable with a flat piece of sticky copper attached/soldered on the other end, which I just stuck to the inside bottom of the laptop. |
syscl -
I got the DW1830 card as reccomended by you and am having some performance issues with it in sierra 10.12.3. It appears I can only get around 30mbit/s downstream on 5ghz, and 60mbit/s downstream on 2.4ghz . In windows i get full 300mbit download speed from my ISP with this card. Anything I am missing on my set up? I've included a debug output of deploy.sh . Any help would be appreciated
debug.txt
The text was updated successfully, but these errors were encountered: