Hervé
-
Posts
10026 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
That's because Snow Leopard 10.6.3 does not support your CPU. SandyBridge & Ivy Bridge CPUs are only supported in 10.6.8 as far as I can remember, not in earlier SL versions.
-
Screen resolution only works automatically if the graphics framebuffer loads Ok. With a totally unsupported GPU such as the GMA4500, you won't get very far though. The only way for you to get what you seek is to manually force screen resolution through the Chameleon boot plist. Use the Chameleon Wizard for that, you'll see what to do straight away. Hint: Graphics Mode...
-
'seems safe enough on my old D630...
-
Not far actually, not far. There's just no support for those cards at present. I'm interested myself: my Dell E6440 has a discrete AMD Radeon HD 8690M too.
-
If it's for Xcode programming, maybe you can live without graphics acceleration...
-
There are different ways to fake a device id. Clover can do it through on the fly patching. Otherwise, a DSDT patch will do: you simply describe your device using the PCI device id of another. That can work for similar component of a same or very close family (e.g.: Mobile HD 4600 (dev id 0x416) vs. Desktop HD 4600 (dev id 0x0412)) but less likely to succeed for components that differ a lot. Here is an example: Device (IGPU) { Name (_ADR, 0x00020000) Method (_DSM, 4, NotSerialized) { Store (Package (0x06) { "device-id", Buffer (0x04) { 0x16, 0x04, 0x00, 0x00 // This is where you can fake a device id }, "AAPL,ig-platform-id", Buffer (0x04) { 0x06, 0x00, 0x26, 0x0A }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } ...
-
Good; I've no explanation about Chameleon. Version issue maybe? I see you kept the 800MHz speed...
-
Who knows? Could be something to do with the way you installed OS X...
-
Did you follow my guide and used my boot pack? If so, I trust you won't have missed the important statement about CPU and SSDT table at the end/bottom.
-
I'm using MBP11,1 on the Dell E6440. You can retrieve the SMBIOS plist from the pack posted in my guide. From memory, I generated it through Champlist and it works perfectly with Chameleon whether in Mavericks or Yosemite. Use the Random buttons for Week of Manufacture + Unique number to generate your own serial number. Make sure to remove those incorrect speed entries you had added, I don't know if they could interfere. I'm also using fairly recent versions of Chameleon such as r2377 or above (r2395, r2401, ...).
-
Yes, it started yesterday. Could be that Crew have to contact Google to lift the security status. Unless the site was hacked somehow...
-
Yes, well, you may have added your card id to the device list of the AMD8000 controller Info.plist, but that's clearly insufficient and you still do not have graphics support (VRAM=4MB)... You could have to patch the binary files too and that's more complicated. It's probably worth checking the specs of the currently supported cards of the AMD8000Controller and your own integrated GPU. Maybe you can also fake one of the supported cards. Supported in Yosemite 10.10.2: 0x45001002 -> ? 0x46001002 -> ? 0x66401002 -> FirePro M6100 0x66411002 -> Radeon HD 4930M 0x66461002 -> Radeon HD M280X 0x66501002 -> ? 0x66511002 -> ? 0x665C1002 -> Radeon HD 7790/8770, R9 260 0x665D1002 -> Radeon R7 200 0x67B01002 -> Radeon R9 290X
-
I'm out!
-
As I wrote in the article, I invite people to make their own experiment and opt for what works best according to factual results. What worked well for the Core2Duo based Latitude D Series does not systematically apply to other and more recent system. In particular, power management is very different with Core "i" CPUs and is not configured the same way: no selection of P + C States and systematic tuned FakeSMC for Sandy/Ivy/Haswell CPUs for instance but generated SSDT, that seems to suffice... For EDP, sorry, I pass! Contact a crew member. EDP has been too problematic to my liking for several months now; I stopped using and recommending it. Publish your own guide and full pack, that's my suggestion for what it's worth...
-
CPU speed really is not a valid criteria at all; it's much better to choose by CPU family closeness and/or GPU closeness. In your case, you have an AMD CPU with an unsupported GPU... I'm not familiar at all with recent AMD CPUs but assuming your APU is say a direct competitor of an Intel Haswell, choose MacBookAir6,2 to begin with but you may also opt MacBookPro11,1 (that's what I use on my Dell E6440 as it gives me an extra intermediary CPU multiplier). If your APU is more comparable to Sandy or Ivy Bridge, choose a corresponding model in the list offered by the Cham Wizard.
-
Select everything so as not to miss anything!
-
Technically, you are absolutely correct in the sense that PC3-12800 does indeed operate at a clock rate/bandwidth of 800MHz just like PC2-6400 (DDR2-800) operates at 400MHz or PC2-5300 (DDR2-667) operates at 333MHz. However, that is not how DDR RAM is dubbed in "marketing" terms. PC3-12800 = DDR3-1600 and in the SMBIOS context this is meant to be reflected as 1600 "MT/s", even though OS X uses the term "MHz". You may consider this artificial/incorrect doubling of memory speed but DDR means Double Data Rate and a confusion between MT/s and MHz (you may call it an abuse of language) has just generally settled in... http://en.wikipedia.org/wiki/DDR2_SDRAM http://en.wikipedia.org/wiki/DDR3_SDRAM Even respectable distributors like Crucial refer to speed in MHz rather than MT/s most of the time... http://www.crucial.com/usa/en/latitude-d630/CT2344599 http://www.crucial.com/usa/en/latitude-e6440/CT4972439 Anyway, any Apple Mac or Hackintosh with XX Go of DDRz-YYY RAM will/should report "XX GB YYY MHz DDRz" in "About This Mac". YYY is what the SMBIOS memory speed field will address. For instance, my Dell E6440 has 8Go of DDR3-1600 RAM in the form of 2 x PC3L-12800S SODIMMs. OS X reports RAM as follows:
-
Dell Latitude E5520 - installing Mavericks - graphics problems
Hervé replied to j00z3k's topic in The Archive
See if there wouldn't be many common features with E6320 as described here. From a CPU and GPU point of view, you'd be in same situation... There's a good chance the E5520 bootpack contains a DSDT for a different LCD size than 1366x768. You can therefore compare with the graphics section of the E6320 DSDT available in my pack. -
Look in the R&D->Other Research section. If need be, use the D630n config.plist.
-
I can also confirm that adapter v3.0 works perfectly and does not require any optional connection to the side connector for BCM94360CD wireless/BT 4.0 card to operate properly. NB: card + adapter need to be fitted to a combo PCIe/USB slot (like a WWAN slot) to support Bluetooth since that part of the card is USB based.
-
Unless there's a specific reason to need Yosemite (other than have the latest OS X version), the XPS M1710 will run Lion absolutely fine in 32bit kernel mode.
-
You must zip files to attach them... Coming back to your SMBios, you should not have to specify those CPU/clock speeds in the plist, nor the RAM speed (is it really DDR3@800MHz by the way, not 1600MHz?), all being incorrectly specified as far as I can see... Those values should be entered as numbers expressed in MHz, not text with "GHz" inside, i.e. "2500" for max/nominal CPU speed, "3500" for external clock (this is the bus speed (like old FSB) not CPU max/turbo speed like you seem to believe) or "800" ("1600"?) for RAM speed. Please note this information is purely cosmetic and has no incidence on system behaviour or operation. If I take the example of a computer with a good old Intel Core2Duo T9300 2.5GHz CPU (LFM/HFM/IDA speed 1.2/2.5/2.7GHz, FSB 800MHz) and PC2-5300 RAM modules (DDR2-667), the SMBIOS data could be manually entered as follows: max CPU speed: 2500 external clock: 800 memory type: DDR2 memory speed: 667 Where is your plist located and under which name (full extension included)? You sent me a file called SMBios.plist.txt and that won't work, it must be called SMBios.plist (or smbios.plist) and placed in /Extra. Try the attached file. SMBios.plist.zip What's the reason for choosing the MacBookPro Retina (MBP10,1) profile by the way?
-
All is provided in the bootpack from this guide.
-
Post it.
-
You forgot to specify your new target OS... A Hapertown quad-core Xeon E5450 does not require any patched kernel afaik. I've not had any problems with a (stickered) LGA771 dual-core Xeon X5270 in a modified LGA775 socket as a replacement of a C2D E8600. SL, Lion, ML or Mavericks still booted and ran properly.
