Hervé
-
Posts
10038 -
Joined
-
Last visited
-
Days Won
562
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
It would be useful to specify the OS X versions you ran this on as it may affect things. For instance, it probably has no official support under Mavericks.
-
I guess that'll be Win8 then, it's Ok with Win7.
-
Which PlugIn kext did you patch? I'm asking because I did a quick search on the Net for the DW370 module and I get pictures of a Broadcom-based card. As such, it looks like it's not the CSR kext that needs patching (unlike for DW350 or DW360), but the Broadcom one... On looking at your attached file, I could not find any reference to product id 33110 (=0x8156 in decimal) in any Info.plist... -
Can you post the Bluetooth adapter's PCI IDs as they appear in System Report? Tuto was here and took CSR chip-based models as examples.
-
Asus N56VV Mavericks 10.9 with any problem but work.
Hervé replied to photoin's topic in The Archive
No links, no, but you can post the list of kexts you have in /E/E if that's available... -
You can install Windows on GUID partitions, so no need for the MBR patch... It's a simple matter of formatting the Win partition as FAT in Mac OS Disk Utility before you proceed with Windows installation and reformatting NTFS.
-
Dell D630C Crash after language selection 10.9 Mavericks
Hervé replied to marlawre's topic in The Archive
Try redoing your USB installer without the MBR patch. D630C is nVidia Quadro NVS 135M-only model, right? -
BCM5722D will not work on the D620, it's for a different model fitted to D630 for instance.
-
DW1395 works for me in Mavericks, albeit on an open network (i.e. no encryption) with MAC address filtering. Basically, it's the same issue as with ML from 10.8.4, but the airportd replacement does not work with Mavericks. -> Replace with a fully supported wireless card model.
-
You should avoid installing kexts in /S/L/E as much as possible. In the case of Voodoo audio, install the VoodooHDA kext in /E/E and do not forget to add the AppleHDADisabler or audio won't work. The kexts go together. Run myFix (quick) afterwards. Remember that your model is integrated in EDP and EDP system build provides more recent VoodooHDA kexts up to v2.8.4.
-
The ANV/Slice kexts option should work just fine on the D830 with ML and Mav.
-
Looks like there could be an issue with the default EDP options. We'll look at it and make some recommendations if things cannot be fixed rapidly. In all likelyhood, it'll be a simple matter of a missing kext and you would be able to boot off your USB installer and copy the lissing item from the USB key to the /Extra/Extensions of your HDD, then run myFix (quick) to recover. In a nutshell, same as what was detailed yesterday for the D630...
-
Provided you have an nVidia D830 (the only D830 models that can properly run Mavericks), you should be able to simply proceed with a fresh install over your ML installation. That would normally preserve all apps and files that you currently have. Needless to say, make a full backup of your ML partition (a full partition image ideally) before you do anything.
- 1 reply
-
- 1
-
-
Ok, that's what I was expecting. If you get full QE/CI in ML with the GeForce 8300GS, I would have thought it would be the same in Mav, but maybe the nVidia kext needs patching for the 8300GS. Failing that, I would recommend you opt for a known supported card; there are some very cheap models like the one I use.
-
Configure your BIOS setup as per recommended settings listed in the pinned thread. It looks like you have IDA enabled when your D830 is fitted with a Merom CPU.
-
Thanks for this contribution. Could you provide the PCI IDs so that I add it to the list of supported USB devices? Is it 0x2001:0x3308 as indicated on Wikidevi: http://wikidevi.com/wiki/D-Link_DWA-121_rev_A1 ? This Lion driver you linked to, is it from the RealTek web site as I don't see a Mac OS driver on Dlink's site? Realtek on the other hand list drivers from Tiger 10.4 to ML 10.8: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true How about trying the ML driver?
-
IOATAFamily has been ON for ages, but it's not required on our D630/D830/... Anyway, we'll fix this in the next few days & weeks.
-
You cannot use the default installation guide since that ML is not normally supported on the D620... You must have noticed there is no ML bootpack for the D620 and therefore no way to proceed with the myHack & standard OSXL booptack. You need to use our special guide with a special hack called MLPF. Look for our specific guides for those unsupported systems in the EDP->Supported Models with Guides section of the forum.
-
It's because the "ACPI fix" is now OFF in D630 System Build Fixes tab, when it used to be ON by default. So guys, make sure you turn it to ON when you do your EDP system builds. Folks, please note that we're working on a set of revised boot packs and revised EDP System Builds kexts and default settings. This will be gradually deployed over the next weeks.
-
I've just made a brand new ML build on my D630n and the system would not boot after EDP. EDP is no longer applying the AppleACPIPlatform kext at System Build with default options and that causes it to hang at reboot... To recover, boot with USB installer, then use Terminal to copy the above kext from USB key to /Extra/Extensions on HDD. Then run myFix (quick). D630n will then boot ML properly.
-
If you use our myHack + special ML bootpack, Ethernet works and you can install EDP to proceed with the D620 system build. EDP will not work unless you actually used myHack as an installer because it relies on myFix. So, provided you did use myHack, did you do the "Install Extra", pointing to the specific ML bootpack previously downloaded?
-
Isn't it that the OS actually shuts down but the computer does not physically switch off?
-
I understood nVidia 7300 card to be unsupported in 64bit-only versions of OS X (ML & Mav)... If you boot the OS Ok, do you actually have graphics acceleration?
-
Can you check your boot plist contains the EFI string?
-
Oh, so it was the bluetooth issue; yes, that's well known and published all over this forum...