Jump to content

Hervé

Administrators
  • Posts

    10013
  • Joined

  • Last visited

  • Days Won

    560

Everything posted by Hervé

  1. Hervé

    E5540

    If this is Haswell CPU, you need the patched kernel. Do a search for it on the forum, it's been posted several times.
  2. Place attached kext in /E/E then re-run myFix (quick) and reboot. You can update Chameleon to latest available version. AppleBCM5751Ethernet.kext.zip
  3. Mmm, this is basic OS X operation. I bet you just click on the little red button at top left corner of an app to close it, don't you? That does not close the app, just the window and the app usually still runs in background (with active icon in Dock usually unless you chose to keep the icon on the Dock of course). To properly close an app, you have to click on the 1st menu item and select Quit or do a Command-Q. It's not meant for that, but another way to check which apps are running is to select the Force Quit facility available via the Apple menu. That lists all active apps so that you can manually kill an app that has run into trouble. Since you never actually close any app, your RAM naturally fills up to the point where it may run out. Your issue is a simple matter of lack of knowledge on how to operate OS X. I'm tempted to say: RTFM... the purpose of this site and forum is not to replace it!
  4. Mmm, nothing has failed per sé. Your card is simply not able to support these latest OpenGL versions, that's all. OpenGL versions evolve over time, each newer version bringing newer graphics specs. Your card was built at a given time and with support for OpenGL up to a certain level beyond which the hardware had no capabilities. I suggest that you familiarise yourself with OpenGL before you run those kind of tests so that you know what they're about.
  5. It's a command you type in Terminal app. From the Finder's bar, you'll find the app in Go->Utilities. The command lists all detected PCI devices (hence lspci) and the -nn argument is to specify a particular output format of the resulting data (with PCI ids).
  6. Since you're not booting with a DSDT file, use Chameleon Wizard to extract it, then post it here. I can patch it so that PCI root level is set to 0 and you won't have to boot with PciRoot=4 anymore. Can you post the output of Terminal command lspci -nn?
  7. You'd find a substantial list of PS2 kext packs in EDP when doing a system build.
  8. Wifi light does not work on any Hackintoshes, it's not just something affecting the D830. For trackstick, you'd have to look for the right set of PS2 kexts; however, I could not tell you which one supports the stick unfortunately... Mavericks 10.9.2 only on D830 models with nVidia graphics; Intel GMA X3100 graphics chip is unsupported so, whilst you would still be able to install Mavericks on a D830 with the old Intel graphics controller, it would run pretty bad with severe graphics degradation and overall reduced performance.
  9. Point 10 is where you go go wrong: you cannot just replace the existing /Extra by the /Extra folder of my pack. You have to run myHack and select "create Extra", then "my own" and point to my pack. In addition, doing this will render your stop 9 unecessary, the process will overwrite/replace any existing /Extra and even create a backup of it. Unless you do that, the contents of the pack, more specifically the kexts, are never installed. Only by running the myHack/myFix tool can you ensure that the kexts placed in /Extra/Extensions are properly propagated to /System/Library/Extensions (in the form of PlugIns of myHack.kext) and the kext cache updated (a vanilla OS X installation only loads kexts from /S/L/E). You also mention a Mavericks 10.9.2 "ISO"... Where is that coming from?
  10. As indicated in the guide, I found that on-board AC97 audio is not supported in 64bit mode (it's either buggy or silent or causes KP). As such, no other choice but to opt for a supported add-on card to get audio in ML and Mav (64bit kernel only). The BIOS reset happens if you do not use my patched DSDT. This because I chose to patch the DSDT rather than use the RTC kext that fixes the old but well-known CMOS reset problem. If you start using the kext, the problem will go away. I got a little further last night with 10.9.2/10.9.3: I can boot the Precision 670 with Bronya's 10.9.2 RC5 or RC6 kernels and obtain would-be graphics acceleration if I use the nVidia Web drivers. I installed those drivers in 10.9.3 after having booted Mav in safe mode. After rebooting using option nvda_drv=1, I was able to reach desktop and noticed the translucid Finder's bar. However, system's responsiveness is atrocious, everything lags terribly. I suspect graphics acceleration is not complete. I opened the nVidia app off the Finder's bar icon and did notice that one of the tab mentions the Web driver is not applicable to GeForce 9800GT, so that could explain things. Returning to OS X default drivers got me back to either black screen (no NVEnabler64 kext used) or white/light gray screen with moving mouse (NVEnabler64 kext used) but no desktop. I'm going to start all over again with my GT610 as that card is normally natively supported in Mav, as is the G210. I really need to suss out what the graphics initialisation issue is and why something that worked up to 10.9.1 no longer does from 10.9.2. I will probably try to revert to 10.9.1 graphics kexts during my tests. To summarise status of things on my machine (XC837 mobo with GeForce 9800GT graphics card): SL 10.6.8, Nawcom 10.6.8 v2 kernel, full QE/CI with DSDT patch, AC97 audio in 32bit mode, Ethernet in 32bit mode Li 10.7.5, Bronya 10.7 RC13 kernel, full QE/CI with NVEnabler64, AC97 audio in 32bit mode, Ethernet in 32bit mode ML 10.8.5, Bronya 10.8 RC5 kernel, full QE/CI with NVEnabler64, buggy/no 64bit audio, no 64bit Ethernet Mav 10.9/.1, Bronya 10.9 RC7 kernel, full QE/CI with NVEnabler64 buggy/no 64bit audio, no 64bit Ethernet Mav 10.9.2/3, Bronya 10.9.2 RC5/6, black screen with default graphics Mav 10.9.2/3, Bronya 10.9.2 RC5/6, white screen + moving mouse pointer with NVEnabler64 Mav 10.9.2/3, Bronya 10.9.2 RC5/6, desktop only in safe mode with NVenabler64 (no QE/CI) Mav 10.9.2/3, Bronya 10.9.2 RC5/6, desktop with partial QE/CI with nVidia Web drivers, very sluggish performance
  11. Welcome to the mad house. I hope you'll enjoy it. Remember to use the search facility before you post for help as your questions may have already been answered and it's highly likely to be the case with a D620, the model having been supported for many many years.
  12. Yes, it's a problem solely with graphics initialisation. I need to suss out the problem. You should be Ok with 10.9.1 though.
  13. Try safe mode (-x boot flag). I can boot 10.9.2/10.9.3 with Bronya's latest 10.9.2 RC5/RC6 kernel but end up with black screen or white screen as graphics fail to fully initialise. However, I can boot 10.9.2/10.9.3 to desktop in safe mode. 'need to nail that graphics bastard!
  14. Use a proper SMBIOS.plist with a proper serial number... Is this a myHack installation ? Mind you, you're kind of wasting your time installing Mavericks on GMA X3100-based laptop. That graphics chip is not supported since ML so you will never have graphics acceleration and I expect you should soon realise this D830 is not suitable for 10.9. A quick use of Safari on a site with lots of graphics & animations should suffice to demonstrate the point. At best, ML 10.8 with MLPF hack.
  15. This issue has been discussed many many times before, even very recently. You need to adjust/reset your network settings, making sure your LAN interface is 1st in the list. Please do a search on the forum and you'll find all details in several recent guides or threads on that same matter.
  16. No, you'd have more or less the same problem. I'm only getting there through the NVEnabler at the moment. So, I still need to work on that one... Trying to work out a solution with nVidia's own drivers, not Apple's.
  17. Do as per all other GMA 950-based D Series: apply the brightness fix that is found in EDP or place attached kext in /E/E, apply myFix (quick) and reboot. AppleIntelIntegratedFramebuffer.kext.zip
  18. You could use the D430 pack I've posted not that long ago. Well I think I did...
  19. Did you remove the NVEnabler64 kext from /E/E as recommended? Run myFix (quick) afterwards and reboot. I never mentioned it but do check that GraphicsEnabler is enabled too (boot option GraphicsEnabler=Yes). Mind you, if it is and still giving you black screen, I suppose you could boot with additional option GraphicsEnabler=No...
  20. I actually meant those Chameleon boot modes that are listed in the Wizard Install tab where you can opt for the boot file that suits disk with OS X + Windows or OS X only or multiple OS X partitions, etc.
  21. Bear in mind that you really should avoid myHack v3.3.1 for a Snow Leopard installation and stick to v3.1.2. There's a bug in myHack v3.3.1 but what happens is that it can screw up the SL installation you run it from for an SL USB installer... What you can do re: Chameleon bootloader is use the Chameleon Wizard and, in the install tab, install the latest version having selected the appropriate boot mode listed in the tab.
  22. Mavericks 10.9.2/10.9.3 is work in progress at the moment. Following release of the 10.9.2 source code by Apple, Bronya published an initial version of a 10.9.2 RC5 kernel which allows 10.9.2/10.9.3 to be installed in the Precision 670 using our traditional myHack method. However, some issues remain as far as I'm concerned, most notably an apparent problem to fully initialize nVidia graphics cards on switching to desktop: at present, all I get is the white/light gray screen + mouse pointer on the display. I can move the mouse but cannot get the OS X desktop on screen.
  23. I guess you meant nVidia GeForce G210, not GT210. Bear in mind that the DSDT I posted has been patched to inject nVidia GeForce 9800GT details. As such, I'd recommend you remove that particular patch since you have a G210, a card that normally works OOB in SL, L, ML and Mav (well, it was when I tested one). The patch is fully documented in the guide, so it is very easy to remove. Copy the DSDT to your OS X desktop, decompile it with Chameleon Wizard (or DSDTEditor or other), open the .dsl source file in TextEditor (or any other text or DSDT editor), remove the Device (GFX0) section, save the .dsl file and recompile it with Chameleon Wizard (or DSDTEditor or other). You can verify this likely graphics card injection issue by booting with Chameleon options & flags DSDT=Null -f -v PciRoot=4 and check which nVidia card is detected and which nVidia kexts are loaded, then see if OS X properly switches to desktop. Expect to experience CMOS reset/BIOS settings reset on subsequent reboot (the DSDT was patched to take care of that so that the RTC kext is avoided). Please note that you would not normally require the NVEnabler64 kext either, so remove it if you kept it in /Extra/Extensions. If you want to try and patch the DSDT for the G210, please follow the process outlined in post #6 of the guide. For Mavericks, I assume you've noticed the limitations mentioned in the guide too (i.e. 10.9.1 at the moment). Note that 10.9.2/10.9.3 is work in progress at the moment.
  24. Please post a copy of your /Extra so that we can add your model to EDP. You can also write a guide as many people have done in recent past. Regarding FaceTime, it seems to be a well-known issue. Look it up on the web; seems camera settings related.
×
×
  • Create New...