Contribute
Register

[solved] Wi-Fi Issue DELL Inspiron 3000

Status
Not open for further replies.
You should probably update... IMHO, no reason to run old code.



Did you patch ACPI correctly yet?
no I haven't tried yet, should I patch it first and then update or update and then patch it?
 
no I haven't tried yet, should I patch it first and then update or update and then patch it?

You should do both (and remove the unneeded patches from your config.plist).

You ioreg shows the device is working, so I assume you mean you can't turn it on (you didn't really provide any details on what you mean by "not working", so that is my guess). That problem is typically due to no "OS Check Fix" ACPI patch.
 
You should do both (and remove the unneeded patches from your config.plist).

You ioreg shows the device is working, so I assume you mean you can't turn it on (you didn't really provide any details on what you mean by "not working", so that is my guess). That problem is typically due to no "OS Check Fix" ACPI patch.
yes, sorry, I will edit the first post try to patch my ACPI and then update, Thank You!
one last question, when patching my ACPI should I work on the DSDT.dsl generated with or without "refs.txt" ?
both the files show the same error when compiled with MaciASL
 
yes, sorry, I will edit the first post try to patch my ACPI and then update, Thank You!
one last question, when patching my ACPI should I work on the DSDT.dsl generated with or without "refs.txt" ?
both the files show the same error when compiled with MaciASL

Your files do not need refs.txt.
The error you have is a very common one and is covered in the guide.
Please read the guide carefully.
 
Your files do not need refs.txt.
The error you have is a very common one and is covered in the guide.
Please read the guide carefully.

Ok tried to apply the patch as you said but I still am not able to turn on WiFi. Here is the new debug folder
 

Attachments

  • debug.zip
    1.8 MB · Views: 53
You have unpatched _OSI calls. Look at the OSID method in your DSDT and you'll see.
Better to use hotpatch for this: OSID->XSID, _OSI->XOSI, SSDT-XOSI.aml.
Details in hotpatch guide:
http://www.tonymacx86.com/threads/guide-using-clover-to-hotpatch-acpi.200137/

Also, as per guide, ForceKextsToLoad is only for pre-install. You forgot to remove it.

I though hotpatch was for Advanced users only, I don't really feel that comfortable with this stuff yet, I will start reading the guide you sent me right now but could you help me to set it up?
also by
ForceKextsToLoad is only for pre-install. You forgot to remove it.
you mean I should remove the only line I have in Kernel and Kext patches under the ForceKextsToLoad section? or do I also need to disable it somewhere else?
 
I though hotpatch was for Advanced users only, I don't really feel that comfortable with this stuff yet, I will start reading the guide you sent me right now but could you help me to set it up?
also by

Fortunately, hotpatch for SSDT-XOSI.aml is one of the easiest hotpatches to implement.

you mean I should remove the only line I have in Kernel and Kext patches under the ForceKextsToLoad section? or do I also need to disable it somewhere else?

Use a plist editor (Xcode or PlistEdit Pro). Delete ForceKextsToLoad section.
 
Fortunately, hotpatch for SSDT-XOSI.aml is one of the easiest hotpatches to implement.
Ok, for what I have understood I only need to:
uncheck the disabled option for both OSID->XSID and _OSI->XOSI in my config.plist
save SSDT-XOSI.dsl as SSDT-XOSI.aml with MaciASL
move SSDT-XOSI.aml in EFI/CLOVER/ACPI/patched
then reboot, am I right?
 
Ok, for what I have understood I only need to:
uncheck the disabled option for both OSID->XSID and _OSI->XOSI in my config.plist
save SSDT-XOSI.dsl as SSDT-XOSI.aml with MaciASL
move SSDT-XOSI.aml in EFI/CLOVER/ACPI/patched
then reboot, am I right?

Correct. And of course, you may need to experiment with specifically which version of Windows you're spoofing.
 
Status
Not open for further replies.
Back
Top