Jump to content

vienna01

Members
  • Content Count

    13
  • Donations

    $0.00 
  • Joined

  • Last visited

About vienna01

  • Rank
    Junior Member

Profile Information

  • Location:
    Silver Spring MD USA
  • Gender
    Male
  • Interests
    Hackintosh, Ceramics[Clay to Object], Drawing

Converted

  • Biography
    Old Dog Trying To Learn New Tricks
  • Location:
    USA
  • Occupation
    RETIRED LONG TIME AGO
  1. If someone could list the steps on how to INJECT kexts. That would be SUPER HELPFUL to those of us from BEFORE CLOVER. Are there any instructions for using CLOVER CONFIGURATOR? Are there explanations of the different FORMS that APPEAR when any one of the subparts of CONFIG>PLIST are highlighted/selected. I get a different FORM on the screen for each section from ACPI to SYSTEM PARAMETERS. Am I CALLING UP A DEFAULT config.plist edit tool then? How to use each form is not obvious. When you inject kexts in a subpart of EFI, where are the different places that KEXTS are INJECTED? ? ?
  2. When the directions say to inject kexts- What is the mechanism to do that? Can I just copy & paste into S/L/E? If ?so do I paste into EFI>Clover>config.plist>kernel & kexts patches or: somewhere else? If I can't just copy & past kexts into the proper location, what tools can I use? Can I use Kext.wizard? Any other old favorite kexts TOOL? Should I use the tool that pops-up when I highlight ?efi>clover>config.plist KERNEL & KEXT PATCHES?? If So, how do I use this tool to add kexts? I tried dragging a kexts to the SECTION FORCE KEXTS TO LOAD even tried after clicking the + sign. That didn't work. Is there a place that describes how to use all the forms that pop up when you select a part of the config.plist such as: ACPI BOOT CPU DEVICES etc. ? When I look at s/l/e using FINDER I see fewer kexts than if I ?use System information.app. What tool should I use to read/see the kexts that are listed in config.plist. ? IF I HAVE ASKED THE WRONG QUESTIONS PLEASE ANSWER THE RIGHT ONES THAT I DID NOT KNOW ENOUGH TO ASK.
  3. Re: "Error encountered...pausing 5 seconds" Solution found in 2012 by makie100 type on terminal sudo systemsetup -setkernelbootarchitecture i386 Hit ENTER Fix permissions [use Disk Utility] REBOOT THAT's ALL Please add this reply where you see the error discussed
  4. I have a Dell 1500 with T5470 CPU, 8400m GS nVidia,Broadcom 440,Dell 1390,HDefAudio. I'm trying to get a dsdt to use. I extracted a base DSDT for my 1500 using DSDTE, I know I need many "hacks/fixes" Don't know which ones. I see your DSDT posts but are these Ok for me because of my different hardware? Should I start with someone's DSDT and try to fix or should I start with my BASE DSDT? If someone's DSDT [Yours? Or another here on osx86.net? ] If I should start from my baseDSDT which patches should I apply? If I understand how to do the LION install, I use a DSDT that is CLOSE. Then I debug from that point. Is that correct? I'll move this to the forum if suggested or if I don't get feedback here.
  5. Do you think it would have been easier to get the video card working installing kexts and bootloader etc via most recent MB{censored} ? Folks seem to have good luck installing Lion that way with Radeon cards. MB{censored} has a separate kext for Radeon. Latest MB{censored}[and Chimera bootloader] was specially configured for Lion. For folks following this thread: Read all about MB{censored},Chimera bootloader with Lion in Blog & forums {censored}86.com. Never-the-less glad you made it.
  6. This is the Summary of the posts in this thread referred to in the initial thread post.. The problem: for my Hackintosh [see signature for details], I was getting error messages stating the NVDANV50HAL kext had been improperly installed. Also I had a problem with one of my 2 ASUS nVidia 8400 GS 512 kb graphics cards [GPUs]. One, “ OLDER 8400 CARD??, of these cards was about 9 months old. Its ID was 06e4. The other card “NEW 8400 CARD’, was purchased a few weeks ago. Its ID was 10c3. The NEW 8400 CARD [iD=10c3]booted with QE/CI and maximum resolution NOT WORKING. The OLDER 8400 CARD booted OK. Seeing the error message and the QE/CI problem, I decided to modify the NVDANV50HAL.kext installed, by adding both 8400 card IDs. Typically you add IDs to the kexts’ info.plist section IOPCIPrimaryMatch to fix video problems. Examining the info.plist of the NVDANV50HAL.kext that was installed, I found that it did not have the section: IOPCIPrimaryMatch. Moreover the section that it did have, IOPCIMatch, only had a single string with one card ID-like entry. The usual info.plists with the IOPCIPrimaryMatch section typically have a list of video card IDs. I downloaded another NVDANV50HAL.kext from kext.com. The info.plist for it had the IOPCIPrimaryMatch section and a list of video card IDs. I attempted to install that kext version using kext helper. I got the kext improperly installed ERROR MESSAGE. As part of installing a kext I also set ownership and other paramerters using the terminal. I rebooted. QE/CI & resolution were STILL NOTworking OK. Moreover, examining the NVDANV50HAL kext’s info.plist, I found it had not changed from the one with IOPCIMatch key. I had failed to replace the kext somehow. With advice from a forum member , I next used KEXT WIZARD plus a series of terminal commands to install the kext I had downloaded from kext.com. I no longer got the previous ERROR MESSAGE. This kext, from the download, included the 10c3 ID among its list of IDs in info.plist. I rebooted. This reboot yielded QE/CI and max resolution still NOT WORKING. I verified I had successfully installed the desired NVDAN50HAL kext, the downloaded one. I no longer saw the NVDANV50HAL kext improperly installed error message. The system.log from this reboot however included several errors associated with NVDANV50HAL kext which I cannot interpret. At this point my OSX 10.6.7 production environment’s video was NOT working correctly. I had a separate OSX 10.6.8 environment on another HDD partition. I built this one to test the upgrade. I used a copy of an earlier 10.6.7 for this upgrade. I used the Apple upgrade download and MB{censored} 3.7.2 to go from 10.6.7 to 10.6.8. Both the NEW 8400 CARD and the OLDER 8400 CARD worked OK in this 10.6.8 environment. I examined the info.plist for the 10.6.8’s NVDANV50HAL kext. It appeared to be the same as the downloaded version[from kext.com] in respect to the list of video card IDs in section IOPCOPrimaryMatch. Next I copied the NVDANV50HAL kext from the 10.6.8 environment and installed it into the 10.6.7 environment using TEXT WIZARD and the Terminal command strings[listed below].No error messages. I rebooted. I was surprised QE/CI & maximum resolution were NOW working. Moreover the system.log, boot log ,did not indicate any NVDANV56HAL kext errors. Problem solved! Why did the copy of the kext from my 10.6.8 environment work, when the downloaded one did not? I don’t know. It remains a puzzle. Their info.plists appear the same looking at them. I have not used an application to compare them. There COULD be a difference in the kexts somewhere. I did not compare the non info.plist parts of the kext. Why was I working with 2 different ASUS 8400GS cards? I was checking out the NEW 8400 CARD to give to a friend building a dual boot [OSX+Windows 7] Hackintosh. He is going to use a G41m-ES2H F2 motherboard with a Core 2 Quad Q8300 CPU. We had tried non-Asus 8400 cards in this PC. They slowed it down so much that the BIOS code took over 5 minutes to complete. We never got to the BIOS setting screens with these video cards. My OLDER 8400 Card seemed to work fine in his PC. That’s why I bought another ASUS 8400 GS 512 kb card for him. I know that cards with the same vendor and model may be very different inside. My 2 cards have different IDs. I hope that I won’t have problems when I upgrade my PC using a more powerful video card. I typically use MultiB{censored} to change my Hackintosh kexts and such. The Chameleon bootloader that is used by MB{censored} [technically via the Chimera branch] has a very extensive list of both nVidia and AMD graphics card’s IDs included. That is for my future. The following are the terminal commands I used after iunstalling a kext using Kext Wizard: sudo -s TYPE YOUR PASSWORD chown -R 0:0 /System/Library/Extensions/* chmod -R 755 /System/Library/Extensions/* kextcache -v 3 -a i386 -a x86_64 -m //System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext -z /System/Library/Extensions
  7. Take a look at recent postings at the blog [and forum] of {censored}86com. There is a article on Lion & integrated graphics support.
  8. SOLVED[thus far]. I copied the NVDANV50HAL kext from my 10.6.8 environment, installed it with Kext Wizard and executed the terminal commands suggested in this thread. I rebooted with verbose parameter. Reboot was OK. 10.6.7 environment now has full resolution with QE/CI. The 10.6.7 environment works OK with both a year-old ASUS nVidia Geforce 8400GS 512 kb [iD=0x06e4] and a newer ASUS 8400 card [iD= 10c3]. The only notable error messages in the boot log[system.log] were associated with lpcidrv kext. I will post a summary of the problem, attempts to fix it and the solution in this thread. I have already added an update message to my first post of this thread indicating that a summary will be posted. That first post will have a pointer to the summary. Notice that my signature describing the environment has been updated. Many Many thanks for most useful suggestions for solving problem.
  9. For the next attempt, I plan to go back to a 10.6.7 environment when QE/CI & Max resolution worked OK and Profiler recognized video card and display [Dell 23" montitor] edit I will report on each new attempt to fix the error message problem [while getting resolution and QE/CI]. Typically I report on all changes & results from previous attempts. Next time I will summarize all the parameters that I think might be associated with my problem. I'll try to make next post include enough IMPORTANT info so folks don't have to read this entire thread. Was there anything SPECIAL that I should include in that feedback Here's some addition background info I may have neglected to post, that could be important to help folks understand the 10.6.7 environment for which I am trying to fix an NVDANV50HAL.KEXT error message problem. I don't know if the error message is important or that error will be important when I add or use applications, upgrade video card or when I eventually[years?] upgrade to Lion. I guess that kext will be important when I upgrade my video card. I have i5 650 CPU OSX 10.6.7 on a GA-P55a-UD3 V 2.0 F11. Not overclocked. This is my "production" installation. This 10.6.7 environment was built using the patched DSDT from {censored}86, and the most recent MB{censored} at the moment. But I only selected a few kexts from MB{censored} for each upgrade. I started with 10.6.3 using Apple retail install disk. Then I upgraded to 10.6.5, then 10.6.6 then 10.6.7. For each upgrade the {censored}86 blog discussed kexts and other optional parts to be selected in MB{censored} to repair things Apple broke with the upgrade. Usually I needed to input new kexts for audio, Ethernet and wanted the latest version of bootloader. Sometimes I had to manually fix com.apple.boot.plist as I recall. My memory isn't great at 74. Unfortunately I didn't keep records of how I achieved each upgrade. Because of the information in {censored}86 and MB{censored}, you might say that I was upgrading blindly, not understanding all the changes associated with making the upgrade work for my Hackintosh. I don't plan on repeating this info about my use of MB{censored}, downloaded DSDTs, etc in subsequent posts. ---------------------------------------------------------------------------------------------------------------- I don't know if you were asking about this. I assume it's off the topic of this thread though because I am not working with this separate install. FYI: I have also experimented using an earlier copy of the production environment, upgrading it from 10.6.7 to 10.6.8. I had to use a HDA Rollback kext for audio because Apple broke my Hackintosh 10.6.7 with their upgrade. I also selected Nvida 256.02.05f1. I selected Chimera 1.4.1 r877 for bootloader. This was under the MB{censored} option that uses the modified DFST for my motherboard that MB{censored} calls "User DSDT install". I have not needed to use autopatcher because I could download DSDT for my motherboard that was already patched from {censored}86.com. I don't know if I get the NVDANV50HAL error message in my 10.6.8 environment. Full resolution & QE/CI does work fine there, but it has that strange NVDANV50HAL.kext that doesn't have IOPCIPrimaryMatch section in info.plist and doesn't have a list of video card ID strings in the info.plist. Remember this was my experimental upgrade to 10.6.8. I haven't done this to my production environment 10.6.7. The production environment[focus of this thread]is the one for which I'm working to eliminate the NVDANV50HAL error message while retaining resolution & QE/CI.
  10. WOW Your suggestions for proceeding are really helpful. I will try them out tomorrow. In response to your questions: I haven't been using Chameleon directly I have been using MB{censored} 3.7.2 and selecting Chimera[v 1.4.0]. I think Chimera uses trunk r833, but in MB{censored} it refers to "r877". Maybe r877 means it is the most recent Chimera branch of Chameleon. From the info at the following URL, I gather Chimera still uses r833 of Chameleon. I am having trouble understanding where in this depository to look for things. I don't know about how Chameleon "releases" are numbered. Haven't searched yet. http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/branches/Chimera/i386 If I use Chimera, I can select [check the box for]"Chameleon 2.0 RC5 Prerelease". It doesn't say which trunk or "r" number. I might be better off checking/selecting Chimera. I haven't ever installed Chameleon directly since I began in late 2010. Always used iB{censored} & MB{censored} etc from {censored}86. I know there are many articles on the net about how to install Chameleon, with and without an installer. For the bootloader, tomorrow I'll try things first checking Chimera. If that doesn't help, I'll try checking Chameleon in MB{censored}. If neither help, I'll invest in learning how to install Chameleon directly. I haven't used any kexts from MB{censored} after an earlier attempt several days ago to eliminate the error message. MB{censored} allows me to select which Mac I want to lo look like. Profiler says I am MacPro 3,1. I will try using your smbios [?] file directly. Have you had a chance to review the system.log from Attempt #2? If so was anything obviously wrong? I'll report on what results from using your most recent suggestions.
  11. Made 2 Attempts with Different Kexts Background Summary: I am beginning with an NVDANV50Hal.kext that DOES yield full resolution and QE/CI. Why change? This kext gives me error messages that it was improperly installed. That existing NVDANV50HAL.kext has a different key IOPCIMatch from all other NVDANV50HAL.kexts that I have seen in threads and from the kext on this kexts.com site available for download. Following up on your suggestions: ATTEMPT #1 Beginning with the downloaded NVDANV50HAL.kext that has a long list of IDs in section IOPCIPrimaryMatch-- I added : 0x000010de&0x0000ffff this was the only ID in IOPCIMatch section of kext's info.plist in original nvdanv50hal.kext I did NOT add the key IOPCIMatch to the downloaded kext. I only added the string that was associated with that key. 0x10c310de&0x0000ffff I added this line to match the format you suggested. 10c3 is the ID for the ASUS 8400GS 512Kb card I have in use now. 0x10c310de&0xfff0ffff this line was in the downloaded kext. It seems to be for the same card ID but the format is different from the one you suggested.I left this string in for attempt #1 0x06e410de&0x0000ffff I added this for an older ASUS 8400GS card which I may use later I left ALL the other strings with IDs that were in the downloaded kext. THEN I installed this modified NVDANV50HAL.kext. I used Kext Wizard & targeted S/L/E of my production OSX install [i have a backup]. The install seemed to complete OK EXCEPT I got a NEW error message: ...NVDAGF100Hal.kext was installed improperly... I executed the terminal commands that you suggested. The terminal session seemed to go OK. No error messages. I captured that terminal session if needed. I rebooted with -v. The boot completed HOWEVER SAW ERROR MESSAGES LOW RESOLUTION, NO QE/CI Attempt #2 I began again using the downloaded version of NVDANV50Hal.kext. For attempt #2 the ONLY string added IOPCIPrimaryMatch key was: "0x10c310de&0x0000ffff" This is string for installed ASUS nvidia 8400 GS ID in format you suggested. I removed "0x10c310de&0xfff0ffff" that was in the downloaded version This string has the IDin a different format from the way you suggested. "0xfff0ffff" versus "0x0000ffff". So for this attempt the kext is almost the same as downloaded. I used kext wizard. Completed OK. NO ERROR MESSAGE. Executed terminal commands OK. Rebooted -v SAW ERROR MESSAGES [extract of system,log included below] Again low resolution & no QE/CI. NEXT STEPS? From the system.log for the boot, it appears that there are STILL problems with my NVDANv50HAL.KEXT There are also other errors, but some may be secondary because of initial kext problem. I am unable to understand these errors. I believe they can suggest fixes. Are you able to help on this? If I could understand what the errors mean, a more appropriate next attempt can be performed. SUGGESTIONS? In the meantime-I might try installing a stripped down kext with only a very few ID strings in the key section IOPCIPrimaryMatch. That would include a string for the 10c3 ID in the format used in the downloaded kext. I might next try adding in the single ID string that was in the original IOPCIMatch section. Recall that was the version of the NVDANV50HAL.kext that booted OK with QE/CI but gave the kext "installed improperly" error message. AGAIN MY THANKS. When this is solved I hope the thread info will be used by others for whom the standard fixes for graphics IDs don't work. ======================================================== Extract of Attempt #2-- System.log Aug 10 18:38:01 MacOSX86-Users-iMac bootlog[61]: BOOT_TIME: 1313015869 0 Aug 10 18:38:03 MacOSX86-Users-iMac com.apple.usbmuxd[44]: usbmuxd-211 built on May 16 2011 at 00:14:56 on May 16 2011 at 00:14:55, running 64 bit Aug 10 18:38:05 MacOSX86-Users-iMac com.apple.kextd[10]: Failed to load /System/Library/Extensions/NVDANV50Hal.kext - (libkern/kext)link error Aug 10 18:38:05 MacOSX86-Users-iMac com.apple.kextd[10]: Load com.apple.nvidia.nv50hal failed;removing personalities. Aug 10 18:38:06 MacOSX86-Users-iMac com.apple.kextd[10]: Can't load/System/Library/Extensions/lspcidrv.kext - no code for running kernel's architecture. Aug 10 18:38:06 MacOSX86-Users-iMac com.apple.kextd[10]: Failed to load /System/Library/Extensions/lspcidrv.kext - (libkern/kext) requested architecture/executable not found Aug 10 18:38:06 MacOSX86-Users-iMac com.apple.kextd[10]: Load com.x86dev.driver.lspcidrv failed; removing personalities. Aug 10 18:38:06 MacOSX86-Users-iMac iStatLocalDaemon[70]: Waiting for connections on port 5204. Aug 10 18:38:06 MacOSX86-Users-iMac com.apple.kextd[10]: Can't load /System/Library/Extensions/lspcidrv.kext - no code for running kernel's architecture. Aug 10 18:38:06 MacOSX86-Users-iMac com.apple.kextd[10]: Failed to load /System/Library/Extensions/lspcidrv.kext - (libkern/kext) requested architecture/executable not found. Aug 10 18:38:06 MacOSX86-Users-iMac com.apple.kextd[10]: Load com.x86dev.driver.lspcidrv failed; removing personalities. Aug 10 18:38:06 MacOSX86-Users-iMac mDNSResponder[16]: SIGHUP: Purge cache Aug 10 18:38:07 MacOSX86-Users-iMac blued[62]: Apple Bluetooth daemon started Aug 10 18:38:07 MacOSX86-Users-iMac /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[50]: Login Window Application Started Aug 10 18:38:07 MacOSX86-Users-iMac com.apple.kextd[10]: Can't load /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext - no code for running kernel's architecture. Aug 10 18:38:07 MacOSX86-Users-iMac com.apple.kextd[10]: Failed to load /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext - (libkern/kext) requested architecture/executable not found. ---------
  12. THANKS YOU FOR YOUR REPLY. Yes , from reading the net, I know it is easy to add a video card Device ID to the list. My issue was: The current version of the kext had 2 problems [which I may not have explained sufficiently]. First was current kext did NOT have the section [and the ID list] IOPCIPrimaryMatch.See my original post. Really don't understand why that kext is different[missing section] from all the ones posted on net.] Second and BIGGEST problem is can't seem to install ACCEPTABLE [to OSX] replacement kext. I download from kexts.com remove old kext.Use kext helper to install the downloaded kext. Clean up permissions, caches etc.using MB{censored}. Reboot. Still get the same error message. keep getting the error message: "The system extension "/System/Library/Extensions/NVDANV50HAL.kext" was installed improperly and cannot be used. Please try reinstalling it, or contact the product's vendor for an update." The replacement kext seems to replace[ I checked it by looking at it with a text editor] but OSX still doesn't like it.
  13. Problem: How to install a correct NVDANV50Hal.kext in OSX86 10.6.7 to fix associated error message.? UPDATE: SOLVED. A summary of the Problem, Attempts to Fix,Solution etc. at POST #13 below I keep getting the error message: "The system extension "/System/Library/Extensions/NVDANV50HAL.kext" was installed improperly and cannot be used. Please try reinstalling it, or contact the product's vendor for an update." So I downloaded NVDANV50HAL.KEXT from this kexts.com website and attempted to install it to system/library/extensions using kext helper. It seems to install OK. I then reboot. I get the same error message again. I performed the various "fixes" posted on the internet for this problem. None eliminated the error message. Then I examined and compared my original NVDANV50HAL.kext, info.plist [the version that gives the error message and the NVDANV50HAL.kext, info.plist I downloaded from this web site. These 2 kext versions are different in an important section. These 2 NVDANV50HAL.KEXT versions also have different CFBundle Version numbers, CFBundleGetInfoString numbers and other different"version" IDs". Original [old] NVDANV50HAL.kext has a section: <key>IOPCIMatch</key> <string>0x000010de&0x0000ffff</string> Downloaded [new] NVDANV50HAL.kext omits that section and replaces it with: <key>IOPCIPrimaryMatch</key> <string> 0x0be310de&0xfff0ffff 0x10c310de&0xfff0ffff 0x00f010de&0xfff0ffff 0x019010de&0xfff0ffff 0x040010de&0xfff0ffff 0x042010de&0xfff0ffff 0x05e010de&0xfff8ffff 0x05f010de&0xfff0ffff 0x060010de&0xffe0ffff 0x062010de&0xffe0ffff 0x064010de&0xffe0ffff 0x06e010de&0xfff0ffff 0x086010de&0xffe0ffff 0x08a010de&0xffe0ffff 0x0a2010de&0xffa0ffff 0x0ca010de&0xffe0ffff </string> The Original [old] NVDANV50HAL kext version doesn't have the section [listing video card IDs]. This is the section where folks say to add IDs for Graphic cards that are not fully recognized by the Hackintosh. Typically when the cards are not fully/correctly recognized QE/CI doesn't work and maximum resolution doesn't work. Can anyone help me successfully install the downloaded NVDANV50HAL kext version and thus eliminate the NVDANV50HAL error? Can anyone explain what is going on with these 2 different kext versions? Note: After I install the downloaded version of NVDANV50HAL.kext [and reboot] the info.plist LOOKS RIGHT. It has the long list of card IDs in IOPCIPrimaryMatch section.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.