Changing System Identifier Causes Hang at Boot

[E-Chris]

I currently have Lion 10.7.2 running fine, though I'm having a few CUDA related issues, and it was suggested to check and possibly change my System Identifier. My System Identifier is currently 3,1 and so I changed it to 4,1 (and also tried 5,1) as well as changing the SMBoardID.

 

When I change that the system no longer boots.

Would this have something to do with AppleGraphicsPowerManagement.kext?

 

This is what I see when it hangs:

 

NVDAGF100HAL loaded and registered

No interval found for . Using 8000000

panic(then a bunch of backtrace info)

 

 

Any thoughts on what might be causing the problem or how I could fix it?

[Foxic]

Hi, it could be to do with AGPM.kext.

 

Can you restore back to your 3,1 definition to get a working install?

 

If you copy AGPM.kext to your desktop, right click and show package contents.

 

Open Contents/info.plist with a text editor

 

Scroll down to the macpro section you wish to use and copy your device id into the device key.

E.g. My Device id for my 480 GTX is 06c0 (look in system information) and I use a macpro 5,1 system definition. So I edited the macpro 5,1 section like so:

<key>MacPro5,1</key>
	<dict>
			<key>Vendor10deDevice06c0</key>
			<dict>
				<key>Heuristic</key>
				<dict>
					<key>ID</key>
					<integer>0</integer>
					<key>IdleInterval</key>
					<integer>250</integer>
					<key>SensorOption</key>
					<integer>1</integer>
					<key>SensorSampleRate</key>
					<integer>4</integer>
					<key>TargetCount</key>
					<integer>5</integer>
					<key>Threshold_High</key>
					<array>
						<integer>87</integer>
						<integer>87</integer>
						<integer>87</integer>
						<integer>100</integer>
					</array>
					<key>Threshold_Low</key>
					<array>
						<integer>0</integer>
						<integer>87</integer>
						<integer>87</integer>
						<integer>87</integer>
					</array>
				</dict>
				<key>LogControl</key>
				<integer>0</integer>
				<key>control-id</key>
				<integer>18</integer>
			</dict>

[E-Chris]

Yeah going back to 3,1 gets the system to boot fine.

 

Thanks for that info on AGPM.kext, I'll give that a try and see if that helps.

[E-Chris]

Okay, I tried modifying my AGPM.kext and that didn't work. I also tried removing it as a whole but that didn't work either... so I don't think it's that.

 

This is the error I get when I change to 4,1 or 5,1:

 

NVDAGF100HAL loaded and registered

No interval found for . Using 8000000

Transcript Offline - Bugger Pool Allocate [181000] failed

 

(**kernel trap and backtrace info**)

 

Kernel Extensions in backtrace:

com.apple.driver.AppleTyMCEDriver(1.0.2d2)[**LONG NUMBER**

dependency: com.apple.iokit.IOACPIFamily(1.4)[**LONG NUMBER**

dependency: com.apple.iokit.IOPCIFamily(2.6.7)[**LONG NUMBER**

dependency: com.apple.iokit.driver.IOPlatformPluginFamily(4.7.5d4)[**LONG NUMBER**

 

Okay, figured it out.

 

I had to remove: AppleTyMCEDriver.kext

 

I guess that gets loaded when you use 4,1 or 5,1, and is only for i7 CPU's... whereas I have a i5. So removing it booted the system perfectly from that point on.

[Foxic]

Ok, you might want to look into using a disabler next rather than just removing AppleTyMCEDriver. The reason being that come the 10.7.3 update that kext will probably be restored.

 

If you can't find a disabler just remember to delete that kext after installing the update (when it comes) (use combo update, not the software update facility) and before rebooting.