Contribute
Register

[SOLVED] Dell DW1560 & DW1830 WiFi+BT Issue on XPS9350

Status
Not open for further replies.
Swapped with DW1560, no more problems with BT. It probably was something related to my system, but it's good I've fixed this way. My laptop has 2 antenna connectors anyway, so DW1830 wasn't so useful!
Regarding the wrong name in Geekbench I think it's just a bug of the app. I will try hot patching later, now I have exams, but laptop is working pretty good now! :)

Thank you for everything RehabMan, I think we can close the thread and mark it as solved! :D
 
Swapped with DW1560, no more problems with BT. It probably was something related to my system, but it's good I've fixed this way. My laptop has 2 antenna connectors anyway, so DW1830 wasn't so useful!
Regarding the wrong name in Geekbench I think it's just a bug of the app. I will try hot patching later, now I have exams, but laptop is working pretty good now! :)

Thank you for everything RehabMan, I think we can close the thread and mark it as solved! :D

Marked solved.
 
Well, with BCM94352Z bluetooth sometimes is not available after sleep and it happens frequently, after 2 or more sleep/wake circles, don´t matter if I am on El Capitan or Sierra. I tried to fix that a long time ago with your help, but we could no solve my problem. After the error, ioreg shows like there are two connected BT devices on HS08 and BRCMPatchram2 is there hocked. You said that it could be a timing issue on my system and that I would need to fix it for myself looking into the code of BRCMPatchRam2.
I don´t have this problem with BCM94360baed.
On Sierra BCM94360baed is the problem, with high ping after sleep, don´t matter if I am connecting on AC or N PHY mode.
For both cards I use FakePCIID.kext + FakePCIID_Broadcom_WiFi.kext + BrcmPatchRAM2.kext + BrcmFirmwareRepo.kext + Clover handoff patch and #a country code. And only for BCM94352Z, the fcvo patch on Sierra.

No ideas without problem reporting files.

Also make sure wake for network is disabled us sysprefs->energy saver.

As you can see, before sleep my wifi card is just fine:
Sem Título.jpeg

Code:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.217 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.680 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.743 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.406 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.722 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=21.010 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2.652 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.198 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=2.589 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=3.100 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2.660 ms

But after sleep ping is very bad:

Code:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=106.395 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=318.805 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=235.180 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=155.920 ms
Request timeout for icmp_seq 4
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1403.224 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=399.770 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1441.218 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=436.815 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=352.481 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=473.648 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=390.035 ms

and I have Wake For Network Access disabled:
wake for network.jpeg

I will upload problem report files.
 

Attachments

  • My Files.zip
    2.2 MB · Views: 108
As you can see, before sleep my wifi card is just fine:
View attachment 277714

Code:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.217 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.680 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.743 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.406 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.722 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=21.010 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2.652 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.198 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=2.589 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=3.100 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2.660 ms

But after sleep ping is very bad:

Code:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=106.395 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=318.805 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=235.180 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=155.920 ms
Request timeout for icmp_seq 4
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1403.224 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=399.770 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1441.218 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=436.815 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=352.481 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=473.648 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=390.035 ms

and I have Wake For Network Access disabled:
View attachment 277715

I will upload problem report files.

Might be related to that country code patch. Try without.
 
Might be related to that country code patch. Try without.
It didn´t solve my problem and now I have bluetooth not available after sleep with BCM94360baed.
I will post ioreg with problem.
 

Attachments

  • ioreg.zip
    664.2 KB · Views: 96
How often does it happen?
It doesn't´t happen before when I used to work on El Capitan with BCM94360baed.
Now, it is very frequently. Two or three sleep/wake cycles.
 
It doesn't´t happen before when I used to work on El Capitan with BCM94360baed.
Now, it is very frequently. Two or three sleep/wake cycles.

Did you try a fresh install?
 
image.jpeg
Did you try a fresh install?
I think I found what made the problem with BT. Trying to reproduce the success in this thread with wifi speed after sleep I made some changes here. I swapped 2013 to 2012 on OSI and disabled on BIOS the option to permit Wake Machine from USB and, maybe this was the really culprit, I enabled darkwake=0 on bootflags.

EDIT1: Actually, reverting those changes made BT available most of the time, but if I insist on sleeping/waking, I will get the same error again.
EDIT2: After a fresh new install, Wifi was fast after sleep, with ping values equal before sleep times.
EDIT3: After setting up my appleid account, I got the wifi problem again, with high ping, so I starting to disable some functions on iCloud, just to know what was going on.
First I disabled Find My Mac and rebooted. Nothing changes.
Then I disabled Keychain, and set it to erase my keychain, and it "fixed" the Wifi speed after Sleep.
Now I am far from home and, here there is only one detectable wifi.
After creating a new Appleid, everything is fine with all iCloud functions enabled, including Keychain and Find My Mac.
I need to do some more testing when I get home, because I live in an Apartment Building and every apartment has its own wifi, with unique channels, frequency and country codes (some are wrong, because I live in Brazil and some of them show as US).
I suspect that this heterogeneous environment may cause the error and this error can be transmitted by keychain somehow.
 
Last edited:
My tests with wifi at home revealed that a fresh install with fresh new Appleid have no issues with wifi after sleep.
But I want to use my old Appleid.
Is there any way to clear keychain on iCloud base?
 
Status
Not open for further replies.
Back
Top