Jump to content

problem installing maya, please try this tool


24 posts in this topic

Recommended Posts

hey guys

 

i have a problem, i can't install maya. something is weird with the realtekr1000 driver

i fixed this issue once in 10.5.6 by replacing some kexts with the ones from a friend of mine (like ionetworking, acpiplatform ...). but he still has 10.5.6 and i'm now using a retail 10.5.7 installation

 

anyway i want to find out what is causing this problem.

you can find out if you have the same problem by using the foundry tool. it looks for your system id.

my network card shows up in system preferences and my system works like a charme. all the apps work, except for apps that are licensed with flexlm!

 

please click on the foundry system id app and see if it gives you an id

for me it just says no system id found!

to check if it works for you just download Foundry System ID 5.0v1 (Mac)

http://www.thefoundry.co.uk/useful_dls.aspx

 

does this work for you guys?

Link to comment
Share on other sites

  • 2 weeks later...
to answer my own question!

i got a system id by replacing the vanilla 10.5.7 ionetworkingfamily.kext with the one attached (from 10.5.5)

now it works fine and i can use maya!

 

Just wanna say thanks it worked for me on ipc 10.5.7 You saved my life.

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

This is a common Hackintosh issue, you can find more about it by googling "Time Machine fix" (which will mostly come up with the old, obsolete fixes for it) or "UUID error 35". Like AES decryption, SMBIOS and video card injection, getting this issue fixed is one of the fundamentals of a fully operational Hackintosh.

 

OSX generates the Hardware UUID using part of the MAC address of the first built-in ethernet device. So it follows that for the UUID to be successfully generated, an ethernet device on your system must be "EN0" and recognized as "internal" like on a real Apple computer.

It doesn't matter if it's on-board or a PCI card or whether it's the device you actually use. I don't think it even needs to be able to establish a connection.

 

On Hackintoshes this often doesn't work like it's supposed to, the OS doesn't find any "built-in" ethernet hardware and you get these problems with some apps not working properly, such as Time Machine and Maya. And you will see UUID error 35 all over your system logs.

 

Instead of relying on an older, patched version of IONetworkingFamily.kext, you can fix it permanently by adding ethernet device properties (AKA an EFI-string) to com.apple.Boot.plist, or if you're using Chameleon 2.0 RC2, set EthernetBuiltIn=yes (works perfectly on my P4 hackintosh). It can also be fixed by patching DSDT, but the fix has to be tailored specifically for your hardware and only a few very patient and intelligent people know how to do that. :) Yes, that means don't ask me.

 

You could also use UUID.kext and UUIDGenerator.app to fix it but it's not as elegant a solution.

 

Lastly, some people have managed to get around the issue by injecting a fake ethernet device into the device tree (again, don't ask!)

 

If there are problems after applying any of the fixes, delete /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist and Preferences.plist and reboot. This will set off a reshuffling of the ethernet device(s) on your system and should place the device for which you applied a fix at en0.

Link to comment
Share on other sites

Hey man, thanks for the hint!

I was worried about switching form chameleon RC1 to RC2 because my system runs really well!

But I had to try the Ethernetfix option... and it did the trick! I enabled the fix during installation and Maya runs fine with my vanilla ionetworkingfamily kext now!

Thanks again!!

Link to comment
Share on other sites

I tried to use the ethernet built in and it didn't work. I think it's because I installed RC2 over RC1+PCEfi (i'm running snow leopard).

However the problem was solved with the efi strings - using osx86tools, I created an ethernet efi string, and combined the string with my graphics string, and now maya works !

Link to comment
Share on other sites

Yep, EthernetBuiltIn=y does the same thing as a device properties string.

 

It's possible that EthernetBuiltIn didn't work in Snow because you are running in 64-bit mode.

I didn't test that myself because I could not get Chameleon 2.0 RC2 to work with 10.6, I had to use RC1 plus the 'boot' file from Netkas' PCIEFIv10. Chameleon 2.0 RC1 doesn't have ethernet injection capability.

Link to comment
Share on other sites

I have the same problem. I updated to Chameleon RC2 and tried Ethernetfix....nothing.

Also tried add efi string to com.apple.Boot.plist, using osx86 tools, i get this error message:

/bin/sh: /Applications/iDeneb: No such file or directory (127)

Any other ideas? :(

Link to comment
Share on other sites

That's the kind of trouble you get for using a hacked distro instead of installing retail OSX. Only other iDeneb users can help you now, muHAHAHAhahaha..

 

Generate the Ethernet device properties, copy and add them to com.apple.Boot.plist manually.

Link to comment
Share on other sites

  • 2 weeks later...
Instead of relying on an older, patched version of IONetworkingFamily.kext, you can fix it permanently by adding ethernet device properties (AKA an EFI-string) to com.apple.Boot.plist

 

Hi, can you please show me a screenshot of your boot.plist ?

 

Thank you.

Link to comment
Share on other sites

  • 2 weeks later...

Hi, I'm running vanilla Snow Leopard 10.6.0 with Chameleon RC2, and I can't get Maya to run.  My OS X install originally had the "CFGetHostUUIDString: unable to determine UUID for host. Error: 35", but even after I fixed that, I still can't get Maya to run.  The problem is, it can't see my motherboard's onboard ethernet card, so flexlm can't find a license and it refuses to run.

 

Here's what I've tried:

 

- added EthernetBuiltIn=y to my boot.plist file.  Result: had no effect!  This seems like the answer to the problem, but for whatever reason, it neither fixes Maya nor solves the UUID -35 errors.  Doesn't matter if I boot using the 32-bit or 64-bit kernel.

 

- Tried installing either UUID.kext or PlatformUUID.kext.  This is the only thing I've tried that fixes the UUID -35 errors for me! But it doesn't fix the problem with Maya.  And if there's a way to fix the CFGetHostUUIDString error -35 thing without resorting to a kernel extension, that'd be great. 

 

- Also tried editing /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist to add another ethernet device to it.  Had no effect on anything.

 

I've tried all of these things in both 32-bit and 64-bit kernels.  After each time I erased /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist and preferences.plist as was recommended in another thread.

 

 

 

 

I'm at my wit's end! Does anyone know how I can fix this problem?

Link to comment
Share on other sites

mhhh... did you try the patched leopard network drivers? is your ethernet card en0 at the moment?

Is that a good idea?  I'd be replacing a Snow Leopard driver with a Leopard driver if I did that.

 

My ethernet card is en0, though, and it's working in all respects other than being detectable by Maya.  If I open NetworkInterfaces.plist I can see it's not being detected as built-in, though, even though I'm using EthernetBuiltIn=y. 

Link to comment
Share on other sites

if you backup your sl ionetworkingfamily.kext you can go back to it if it doesn't work. remember that you can only use the leopard kext in 32 bit mode. i heard from a few people with my gfx card that they are using the leopard driver on sl...

 

one more thing that comes to my mind... are you using chameleon rc3?

 

good luck,

chriss

Link to comment
Share on other sites

  • 3 months later...

if someone still has issues with the built in issue, try this:

 

go to either /Extra/com.apple.Boot.plist or System/Preferences/SystemConfiguration/com.apple.Boot.plist (mostly the one in Extra is used for bootup)

 

copy the file to the desktop and edit with textedit

 

replace the code with this one:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>

<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>debug=0x100</string>
<key>EthernetBuiltIn</key>
<string>y</string>
<key>Timeout</key>
<string>3</string>
	<key>device-properties</key>
<string>4b00000001000000010000003f0000000100000002010c00d041030a0100000001010600001e
0101060000017fff0400160000006200750069006c0074002d0069006e0000000500000001</string>

</dict>
</plist>

 

copy back to the original folder, restart

Link to comment
Share on other sites

  • 3 months later...
copy the file to the desktop and edit with textedit

 

replace the code with this one:

		<key>device-properties</key>
<string>4b00000001000000010000003f0000000100000002010c00d041030a0100000001010600001e
0101060000017fff0400160000006200750069006c0074002d0069006e0000000500000001</string>

</dict>
</plist>

 

what is that device-properties string for? hackintosh users can't just copy device properties strings from any other machine and expect it to work with their hardware if they have different parts, graphics card, and/or chipsets then you.

Link to comment
Share on other sites

Exactly. Don't use device-properties strings from other people folks! Always generate your own.

 

You can use EFIStudio, OSX86Tools or gfxutil (which is what EFIStudio and OSX86Tools use in the first place) from Terminal.

 

gfxutil original release thread.. this is hackintosh scene history, respect:

http://forum.netkas.org/index.php/topic,64.0.html

 

EFIStudio v1.1

http://www.mediafire.com/?xz14ytrmddo

Link to comment
Share on other sites

 Share

×
×
  • Create New...