-
Posts
10027 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
Try the attached revised DSDT. I suggest you save it alongside your existing one under a name like "DSDT2" and that you manually call it at bootloader level. It's been patched with a new device SDXC added under RP08 at address 0x01 as per IOReg info, i.e. it applies to O2 Micro device 1217,8320. Test this with VoodooSDHC kext removed but no guarantee it'll work of course... Revised_DSDT.aml.zip I wouldn't mind a zipped copy of your saved SysProfiler output. I'm wondering if your SD card reader wouldn't be USB-internal. Do you have a copy of your raw BIOS tables too (DSDT + SSDTs)?
-
1st thing 1st. Which model is it in term of graphics? Intel HD or nVidia? You cannot get full graphics acceleration on this model with 1st gen Intel HD due to unsupported eDP LCD connector type. As such, it's not worth wasting time installing OS X on those models. If you have the nVidia model, great; just make sure to use a patched DSDT where all references to EHCx USB controllers are renamed to EH0x and you install the USB injector kext.
-
Is wireless enabled/activated on the computer (BIOS, side on/off switch, keyboard soft switch)?
-
I invite you to browse the the numerous threads about the E6x20 before you post.
-
Ok, can you remove the VoodooSDHC kext, rebuild your cache then post a new IOReg output?
-
You'll find what you need in the guide section.
-
1st gen Intel HD based laptops need to follow this procedure to ascertain graphics support. You audio is based on codec IDT 92HD87B1/3.
-
Please refer to existing E6x20 guides. From El Capitan 10.11.4, please use Dr Hurt's PS2 controller kext.
-
DW1550: trouble getting Bluetooth to work in my D630
Hervé replied to hackie1056's topic in The Archive
I've reproduced the behaviour in my D630 by trying my Novatel WWAN module and my Apple BRCM94360CD in the WLAN slot. No WWAN module and no BT controller detected when cards fitted there! Unlike the D430's, the D630's WLAN slot is indeed only PCIe, not combo PCIe/USB like its WWAN counterpart. -
Dell mobile Precision 7510 Intel hd530, black screen
Hervé replied to ss2sameer's topic in The Archive
Hmm, MacBook9,1 SMBIOS... -
You'll find out if it works once you've tried it and you can do no harm in trying. If your device is directly attached to a device called IOPP, then patch that. Do not focus on any device called PXSX, that was just what the OP's DSDT device was called and, as it happens, it's a device name under which SD card readers are often defined in the DSDT of many Dell laptops. However, it's not systematic. If in doubt, please post zipped copies of your saved IORegistry output and of your DSDT.
-
Dell mobile Precision 7510 Intel hd530, black screen
Hervé replied to ss2sameer's topic in The Archive
Can't say whether it has adverse effect or not but why do you "Inject ATI" in the Graphics section of your Clover configuration file when you're clearly trying to run off the HD530 ? -
There's a chance it could be listed in the BIOS settings; check it out. You may also try to update your local PCI ids database. Try the Update IDs button in DPCIManager app. Should it fail, install the lspci package as detailed here and make sure to update your local database through Terminal command sudo update-pciids. You may then re-run DPCIManager.
-
In the DSDT, make sure: 1) that your USB3.0 device @00140000 is named/renamed to XHC (rename all instances as necessary) 2) that you set OSYS to 0x07D6 for Darwin or Win2006: Scope (_SB.PCI0) { Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (0x07D0, OSYS) If (CondRefOf (\_OSI, Local0)) { If (_OSI ("Windows 2001")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP1")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP2")) { Store (0x07D2, OSYS) } If (_OSI ("Windows 2001.1")) { Store (0x07D3, OSYS) } If (LOr (_OSI ("Darwin"), _OSI ("Windows 2006"))) { Store (0x07D6, OSYS) } If (_OSI ("Windows 2009")) { Store (0x07D9, OSYS) }
-
Nothing to worry about,everything is perfectly normal. The messages you see refer to add-on kexts which are not signed (meaning approved/validated) by Apple. Most add-on Hackintosh kexts are like that. The messages indicate that the kexts load nevertheless so all is well.
-
That's nothing to do with USB3.0 ports. Don't confuse things. Afaik, you can keep your boot mode as it is.
-
You do not have proper CPU SpeedStep without SSDT-based adequate power management SSDT. Instead, what you see is LFM and HFM, i.e. only the lowest and highest nominal frequencies with no intermediate speeds and no Turbo boost at all. You need to generate and use the CPU-specific SSDT in order to enjoy native CPU SpeedStep, i.e. intermediate speeds between LFM and HFM + Turbo boost between HFM and max Turbo speed.
-
USB3.0 ports are XHCI type whilst USB2.0 ports are EHCI type. Apply the DSDT adjustment to XHCx device as/if necessary and USB ports should work OOB. They do on my E6230. All details here. You may also follow JakeLo's guide for this model family.
-
Erm... you would have had to specify it somewhere in your bootloader configuration to get macOs running. If you did not, it's highly unlikely that you have proper graphics support.
-
Best CPU for your mobo is probably Core2Duo E8600 3.33GHz FSB1333 unless there is support for Core2Quad. It'll depend on the chipset and BIOS. I'll let you do you own homework on that one... http://www.cpu-upgrade.com/mb-Intel_(chipsets)/G43_Express.html
-
Install Display Menu app (available for free on AppStore) to check if you can switch from mirrored displays to separate/independent displays. Your IOReg shows: FB@0: ​no attached display FB@1: connector-type = 00 04 00 00 (DP) port = 0x5 boot display = true FB@2​: ​connector-type = 00 04 00 00 (DP) port = 0x6 FB@3: ​no attached display Which framebuffer layout-id are you using? Once you've identified it, you can try to identify the framebuffer table in the Skylake framebuffer kext and investigate a potential binary patch.
-
Systems specs please? You may need to binary mod/patch your FrameBuffer to get all your output ports supported. You can refer to our existing literature meantime.
-
Download a fresh copy of Sierra installation app and start all over with USB installer creation. If you boot with -f flag, kexts placed in /L/E will be ignored. You therefore need to load add-on kexts from /E/E with boot option KernelBooter_kexts=Yes. It's mentioned in the guide.
-
Please pay attention...
-
Finally tried the kext on the D630 (ALPS V2 ?)... With R4, all seems Ok but one has to hardly touch the TrackPad to control the mouse; a little difficult to use. With R5, no such requirement for an extremely light finger touch but UP and DOWN mouse movements are inverted. LEFT and RIGHT Ok. Trackstick not functional. ALPS version could not be identified as shown in the log: Dec 20 22:41:47 localhost kernel[0]: VoodooPS2Trackpad: Identify TouchPad command returned incorrect byte 2 (of 3): 0x00 Dec 20 22:41:47 localhost kernel[0]: ApplePS2Controller: Timed out on mouse input stream. Dec 20 22:41:47 --- last message repeated 1 time --- Dec 20 22:41:47 localhost kernel[0]: VoodooPS2TouchPad Version 2.8.15 loaded... Dec 20 22:41:47 localhost kernel[0]: VoodooPS2Mouse Version 2.8.15 loaded... Dec 20 22:41:47 localhost kernel[0]: No interval found for . Using 8000000 Dec 20 22:41:47 localhost kernel[0]: ApplePS2Controller: Timed out on mouse input stream. Dec 20 22:41:47 --- last message repeated 1 time --- Dec 20 22:41:47 localhost kernel[0]: ALPS: Touchpad driver started Versions R6Bx do not work at all on that model.