Jump to content

[Guide] Installing Mountain Lion.


  • Please log in to reply
116 replies to this topic

#101
Huckleberry Pie

Huckleberry Pie

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 156 posts
  • Gender:Male
What if I don't have a USB drive, and I want to stuff the installer on a DVD?

#102
abiyyufahmi

abiyyufahmi

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
  • Gender:Male
  • Location:Jakarta
is there anyway to use ps2 keyboard on mountain lion?, i've tried to insert ApplePS2Controller.kext into S/L/E But got no success

#103
PGHammer

PGHammer

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 282 posts

Thanks so much for this great tutorial. 10.8 boots perfect but unfortunately without USB at all.. No mouse or keyboard. Tried different hardware but no result. Only with -f the USB will work but my system doesn't open any program with that boot flag.

Anybody..?? Thanks.


Now I'm curious - is this a desktop?

I have an ASUS P5G41-M LX2/GB that is now running Mountain Lion GM (installed via USB and did a *straight replace* of my Snow Leopard partition, since an upgrade didn't work) and keyboard and mouse (both USB) work swimmingly.

UPDATE - Got my HD5450 working; turned out to be rather simple - editing the Info.plist of the two affected kexts (ATI5000Controller.kext and AMDRadeonAccelerator.kext).

The Walkthrough - The IOPCIMatch strings appear in the Info.plist in reversed order - hence 0x100268F9 (my particular string) appears as 0x68F91002. I used nano to do the editing (via sudo in Terminal) and used Kext Wizard to do permission repair/rebuild post-edit; however, I don't see why TextEdit wouldn't work. You can either add your ID or edit an existing; either will work.

Edited by PGHammer, 26 July 2012 - 09:56 PM.


#104
Joshua60

Joshua60

    InsanelyMac Protégé

  • Members
  • Pip
  • 15 posts

Finally got it working perfectly, by injecting the device ID into NVDANV50Hal.kext!! The 8400GS video card wasn't recognised natively and the existing Chameleon didn't seem to inject the device ID into ML correctly.


Hi monto,

Perfect, excellent!!! ... works for my 9600GT (device ID: 0x0622) too.

Thanks a lot! :thumbsup_anim:

#105
Joshua60

Joshua60

    InsanelyMac Protégé

  • Members
  • Pip
  • 15 posts

Finally got it working perfectly, by injecting the device ID into NVDANV50Hal.kext!! The 8400GS video card wasn't recognised natively and the existing Chameleon didn't seem to inject the device ID into ML correctly.


Hi monto, me again,

I accidentally copied the injected kext to my main system, Lion OS. The screen resolution changed to 1024x768.
I corrected the kext back but the screen resolution did'nt changed.
I would like to bring back the screen resolution to 1920x1080. But how ?

thanks

#106
monto

monto

    InsanelyMac Protégé

  • Members
  • Pip
  • 20 posts
  • Gender:Male
Hi Joshua, Just send me $50 and the answer will be mailed to you in an express post.
Just kidding!
Ok, what did you mean by accidentally copied the file? Did you try to rebuild the cache and fix the permissions using kext wizard? That's what I'd do first.
Was there anything else you also did but may not have noticed, if you changed several things at the same time?
Take a time machine backup if it's working almost perfectly, and later on if anything is stuffed up during the fine tuning, at least the system can be restored.
Hope this helps.

#107
Hackintosh2000

Hackintosh2000

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 171 posts
  • Gender:Male
  • Location:Unites States of America

Just tried Chameleon r2015 you recommended and ran Kext Utility from safe mode of ML to reset permission. I was using Kext Wizard previously as it allowed me to select which drive to install kext where Kext Utility didn't allow it. Unfortunately, both of these actions didn't make a difference. Still stalling at boot unless booting in safe mode.


I meant to say "Kext Wizard" not Utility. I went back and corrected my post.

One thing I have noticed just now, is that the first line in boot.log (assuming the first line is the last entry) under root is as below:

Read HFS+ file: [hd(0,2)/System/Library/Extensions/GeForce.kext/Contents/Info.plist] 2335 bytes.

Where my Lion's boot.log has a different first line. Does it suggest the problem is indeed NVidia 8400GS?


Perhaps. I am not sure. I do not have that card.

#108
Joshua60

Joshua60

    InsanelyMac Protégé

  • Members
  • Pip
  • 15 posts

Hi Joshua, Just send me $50 and the answer will be mailed to you in an express post.
Just kidding!
Ok, what did you mean by accidentally copied the file? Did you try to rebuild the cache and fix the permissions using kext wizard? That's what I'd do first.
Was there anything else you also did but may not have noticed, if you changed several things at the same time?
Take a time machine backup if it's working almost perfectly, and later on if anything is stuffed up during the fine tuning, at least the system can be restored.
Hope this helps.


Hi monto,

I used 'kext utility' to rebuild the cache and fix the permissions (my mistake!).
This is the only change I did to Lion OS prior to notice the screen resolution change to 1024x768.
After that I used 'kext utility' again to restore NVDANV50Hal.kext to the previous condition.

For the ML GM installation i use a HD Partition of the same disk where I have Lion OS installed.

Maybe using 'kext wizard' instead of 'kext utility' helps ?

#109
Hackintosh2000

Hackintosh2000

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 171 posts
  • Gender:Male
  • Location:Unites States of America
If anyone is encountering the following error while installing I've got a solution...

OS X install data is incomplete.
The following required components of OS X were not found on an installation disc:
Essential System Software
OS X cannot be installed.

If you are installing to a MBR volume get your MBR patched files from HERE. If you are using a GUID Partition Table disk you do not need to even mess with patched files. Just leave the originals alone!

#110
C.Frio

C.Frio

    InsanelyMac Legend

  • Pandora Team
  • 1,149 posts
  • Gender:Male
  • Location:Cabo frio - Brasil

Finally got it working perfectly, by injecting the device ID into NVDANV50Hal.kext!! The 8400GS video card wasn't recognised natively and the existing Chameleon didn't seem to inject the device ID into ML correctly.


Booted now with this trick.. 'll try to install

on a GA-z68 of the signature GTS250 ID: 0x1615

c.frio

#111
puercoro

puercoro

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts
  • Gender:Male
  • Location:Hun

Yippee it's working.

( P5QL-CM, HD4670 )

Thx a lot.

#112
Neo_01

Neo_01

    InsanelyMac Protégé

  • Members
  • PipPip
  • 56 posts

I've tried 3 different methods (John Cash, MyHack & Tech Erra Brian) to build ML 10.8 GM, and they all got stuck at around the same place during booting. If I put the Atheros network kext in /E/E, the last line I see at booting (from -v) is related to it being loaded successfully. If I put NVEnabler in /S/L/E via kext wizard, the last thing I would see is about 20 lines of NVEnabler probing. Prior to the logs from these two kexts (or if I removed these two kexts), I was getting the followings:

DSMOS has arrived
[IOBluetoothHCIController]....
[IOBluetoothHCIController][start] -- completed
[IOBluetoothHCIController].... calling registerService

It seemed the booting got stuck here and the hard disk LED light would stop flashing at this point. My same hardware is currently running 10.7.4 fine with vanilla build (ML staging was built on a separate HDD.)

Does anyone know after IOBluetooth and kexts mentioned above, what's the booting doing at this stage? It was failing without giving any further useful logging. The main suspect was probably NVidia 8400GS 256MB card but 1. it has been working fine on 10.7 fully (2 monitors at full res) and 2. someone at OSX86 compatibility list suggested this card should work OOTB. I have tried graphicsenabler=yes and npci=0x2000 & 0x3000 with no avail.

Any suggestion of where to go next to boot to ML? I don't mind buying a new video card if this card is not supported, but I'd hate to spend the money and find out the culprit is something else.


(Tried uploading the system.log but the forum wouldn't let me... I've pasted the last 100 lines or so)


Jul 14 01:36:51 localhost kernel[0]: Pin sense: cad 2 nid=28 res=1
Jul 14 01:36:51 localhost kernel[0]: setDesc change description Line-out (Green Rear) channel 0 assoc 0
Jul 14 01:36:51 localhost kernel[0]: Pin sense: cad 2 nid=29 res=0
Jul 14 01:36:51 localhost kernel[0]: Pin sense: cad 2 nid=30 res=0
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 0 on
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 1 on
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 2 on
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 3 off
Jul 14 01:36:51 localhost kernel[0]: setDesc change description CD (Analog) channel 1 assoc 1
Jul 14 01:36:51 localhost kernel[0]: [BroadcomBluetoothHCIControllerUSBTransport][start] -- completed
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: init : begin
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : probe
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : ROM shadow enable
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : patch PRAMIN
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : patch PROM
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: dcb table at offset 0xbb70
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: dcb numentries 16
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 0: 02000300
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 1: 01000302
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 2: 04011310
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 3: 010223f1
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: 2 not grouped
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: 3 not grouped
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Channel 1: 03
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Channel 2: 0c
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce 8400 GS
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG VRAM: 256
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property hda-gfx
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property vbios
Jul 14 01:36:52 localhost kernel[0]: NVEnabler::probe fails
Jul 14 01:36:52 localhost loginwindow[64]: Login Window Application Started
Jul 14 01:36:52 localhost kernel[0]: DSMOS has arrived
Jul 14 01:36:52 localhost kernel[0]: [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification
Jul 14 01:36:52 localhost kernel[0]: [IOBluetoothHCIController][start] -- completed
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: init : begin
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : probe
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : ROM shadow enable
Jul 14 01:36:52 localhost com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
Jul 14 01:36:52 localhost mds[60]: (Normal) FMW: FMW 0 0
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: probe : patch PRAMIN
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: probe : patch PROM
Jul 14 01:36:53 localhost kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: dcb table at offset 0xbb70
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: dcb numentries 16
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 0: 02000300
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 1: 01000302
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 2: 04011310
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 3: 010223f1
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: 2 not grouped
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: 3 not grouped
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Channel 1: 03
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Channel 2: 0c
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce 8400 GS
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG VRAM: 256
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property hda-gfx
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property vbios
Jul 14 01:36:53 localhost kernel[0]: NVEnabler::probe fails
Jul 14 01:36:53 localhost configd[18]: New network configuration saved
Jul 14 01:36:53 localhost configd[18]: network changed: v4(en0!:192.168.1.142) DNS! Proxy- SMB
Jul 14 01:36:53 localhost configd[18]: network changed: v4(en0-:192.168.1.142) DNS- Proxy SMB
Jul 14 01:36:57 localhost apsd[80]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
Jul 14 01:36:57 localhost configd[18]: network changed: v4(en0+:192.168.1.142) DNS+ Proxy+ SMB
Jul 14 01:36:57 localhost mDNSResponder[61]: mDNS_RegisterInterface: Frequent transitions for interface en0 (192.168.1.142)

Hi I have the same problem, do you solve it??

#113
Joshua60

Joshua60

    InsanelyMac Protégé

  • Members
  • Pip
  • 15 posts

Hi monto,

I used 'kext utility' to rebuild the cache and fix the permissions (my mistake!).
This is the only change I did to Lion OS prior to notice the screen resolution change to 1024x768.
After that I used 'kext utility' again to restore NVDANV50Hal.kext to the previous condition.

For the ML GM installation i use a HD Partition of the same disk where I have Lion OS installed.

Maybe using 'kext wizard' instead of 'kext utility' helps ?


Fixed using Lion GM kext.

#114
The Real Deal

The Real Deal

    InsanelyMac Legend

  • Donators
  • 886 posts
  • Gender:Male
  • Location:France

Finally got it working perfectly, by injecting the device ID into NVDANV50Hal.kext!! The 8400GS video card wasn't recognised natively and the existing Chameleon didn't seem to inject the device ID into ML correctly.


Kudos. It made the trick for my 8400GS too ;)

#115
csowerby

csowerby

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
Hi All

I've tried 3 different install guides, (Tseug, John Cash and Tec Erra) - for the latter two everything works perfectly with the actual install - but in the case of John Cash i couldn't get the installed OS to boot from the HD or by booting from USB and then choosing the HD installed system.
I had much better results with the Tec Erra guide - It requires a bit more "manual" work with the terminal screen but the instructions are clear enough.

I'm installing onto a "clean" system and I noticed there were reported issues with Gigabyte boards and GPT so I formatted the host drive MBR and used the modified OSinstall files as per the kit instructions.
At the Chameleon install to the USB step, I added only the NVidia enabler and chose a SMBIOS from the list that matches my processor.

Install went fine without issue. First boot from the USB then choose the HD ML intsall to run and everything came up fine - was able to set up ML and get running all ok.

Now my problems begin!! :-)

I ran the chameleon installer again and duplicated the previous install exactly but this time to the ML HD.

When I restart and attempt to boot from the HD I get the following:

Boot0:test
Boot0:failed

Thats it - nothing else.
Bios is seeing the HD - if i hit F12 during boot its there in the list along with the USB.
I can boot from the USB and run the installed ML everytime.

I'm not sure if this is an error with the chameleon install or something to do with the recognition of the HD by the MB.

The reason I say this is that with the John Cash method I ended up with almost exactly the same problem - ie install went ok but the HD would not boot. In that case the HD was formatted GPT and the boot error was:

Boot0:GPT
Boot0:test
Boot0:test
Boot0:error
Boot0:GPT
Boot0:test
Boot0:test
Boot0:failed

I feel I'm 90% there with this install. ML will run everytime provided i boot from the USB - So far I've never managed to boot from the HD either GPT or MBR

My equipment is:

GA-Z77X-UD5H-WB
GTX 550 1024 ti
2 x 4Gb Twinmos 1300 Mhz
WD green 1Tb D

Anyone else having similar issues?

#116
C.Frio

C.Frio

    InsanelyMac Legend

  • Pandora Team
  • 1,149 posts
  • Gender:Male
  • Location:Cabo frio - Brasil
Hi

Installed on a ASRock mini itx H77M,on external seagate 320gb,4gb,force 210

just followed the "recipe of the cake", GE=yes,smbios.list 3,1,boot with chameleon 2009

c.frio

Hi All

I've tried 3 different install guides, (Tseug, John Cash and Tec Erra) - for the latter two everything works perfectly with the actual install - but in the case of John Cash i couldn't get the installed OS to boot from the HD or by booting from USB and then choosing the HD installed system.
I had much better results with the Tec Erra guide - It requires a bit more "manual" work with the terminal screen but the instructions are clear enough.

I'm installing onto a "clean" system and I noticed there were reported issues with Gigabyte boards and GPT so I formatted the host drive MBR and used the modified OSinstall files as per the kit instructions.
At the Chameleon install to the USB step, I added only the NVidia enabler and chose a SMBIOS from the list that matches my processor.

Install went fine without issue. First boot from the USB then choose the HD ML intsall to run and everything came up fine - was able to set up ML and get running all ok.

Now my problems begin!! :-)

I ran the chameleon installer again and duplicated the previous install exactly but this time to the ML HD.

When I restart and attempt to boot from the HD I get the following:

Boot0:test
Boot0:failed

Thats it - nothing else.
Bios is seeing the HD - if i hit F12 during boot its there in the list along with the USB.
I can boot from the USB and run the installed ML everytime.

I'm not sure if this is an error with the chameleon install or something to do with the recognition of the HD by the MB.

The reason I say this is that with the John Cash method I ended up with almost exactly the same problem - ie install went ok but the HD would not boot. In that case the HD was formatted GPT and the boot error was:

Boot0:GPT
Boot0:test
Boot0:test
Boot0:error
Boot0:GPT
Boot0:test
Boot0:test
Boot0:failed

I feel I'm 90% there with this install. ML will run everytime provided i boot from the USB - So far I've never managed to boot from the HD either GPT or MBR

My equipment is:

GA-Z77X-UD5H-WB
GTX 550 1024 ti
2 x 4Gb Twinmos 1300 Mhz
WD green 1Tb D

Anyone else having similar issues?


Hi...

try to use "chameleon wizard" and reinstall the boot at boot0 ,choosing the option ...

c.frio

#117
Stormed

Stormed

    InsanelyMac Protégé

  • Members
  • Pip
  • 24 posts
  • Location:US
Hi all,
I have been trying to get my GTS 250 1GB (id 0x0615) to work but no luck so far. I have tried to inject the device ID into both NVDAGF100Hal and NVDANV50Hal. Anyone got this to work? Below are the info.plist files.

Thanks!


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>NVDAGF100Hal</string>
<key>CFBundleGetInfoString</key>
<string>NVDAGF100Hal 7.4.9 270.05.05f01</string>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nvGF100hal</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>NVIDIA gf100 Resman Kernel Extension</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>7.4.9</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>7.0.4</string>
<key>IOKitPersonalities</key>
<dict>
<key>NVidiaRM</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nvGF100hal</string>
<key>IOClass</key>
<string>NVDAGF100HAL</string>
<key>IOMatchCategory</key>
<string>IOService</string>
<key>IOPCIPrimaryMatch</key>
<string>
0x06c010de&amp;0xffe0ffff
0x061510de&amp;0xffe0ffff
0x0dc010de&amp;0xffc0ffff
0x0e2010de&amp;0xffe0ffff
0x0ee010de&amp;0xffe0ffff
0x0f0010de&amp;0xffc0ffff
0x104010de&amp;0xffc0ffff
0x124010de&amp;0xffc0ffff
</string>
<key>IOProbeScore</key>
<integer>60000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
</dict>
</dict>
<key>OSBundleCompatibleVersion</key>
<string>1.2.0</string>
<key>OSBundleLibraries</key>
<dict>
<key>com.apple.NVDAResman</key>
<string>1.2.0</string>
<key>com.apple.kpi.iokit</key>
<string>9.0.0</string>
<key>com.apple.kpi.libkern</key>
<string>9.0.0</string>
</dict>
<key>OSBundleRequired</key>
<string>Safe Boot</string>
</dict>
</plist>


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>NVDANV50Hal</string>
<key>CFBundleGetInfoString</key>
<string>NVDANV50Hal 7.4.9 270.05.05f01</string>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nv50hal</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>NVIDIA NV50 Resman Kernel Extension</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>7.4.9</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>7.0.4</string>
<key>IOKitPersonalities</key>
<dict>
<key>NVidiaRM</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nv50hal</string>
<key>IOClass</key>
<string>NVDANV50HAL</string>
<key>IOMatchCategory</key>
<string>IOService</string>
<key>IOPCIPrimaryMatch</key>
<string>
0x00f010de&amp;0xfff0ffff
0x019010de&amp;0xfff0ffff
0x040010de&amp;0xfff0ffff
0x042010de&amp;0xfff0ffff
0x05e010de&amp;0xfff8ffff
0x05f010de&amp;0xfff0ffff
0x060010de&amp;0xffe0ffff
0x061510de&amp;0xffe0ffff
0x062010de&amp;0xffe0ffff
0x064010de&amp;0xffe0ffff
0x06e010de&amp;0xfff0ffff
0x086010de&amp;0xffe0ffff
0x08a010de&amp;0xffe0ffff
0x0a2010de&amp;0xffa0ffff
0x0ca010de&amp;0xffe0ffff
</string>
<key>IOProbeScore</key>
<integer>60000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
</dict>
</dict>
<key>OSBundleCompatibleVersion</key>
<string>1.2.0</string>
<key>OSBundleLibraries</key>
<dict>
<key>com.apple.NVDAResman</key>
<string>1.2.0</string>
<key>com.apple.kpi.iokit</key>
<string>9.0.0</string>
<key>com.apple.kpi.libkern</key>
<string>9.0.0</string>
</dict>
<key>OSBundleRequired</key>
<string>Safe Boot</string>
</dict>
</plist>





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy