Jump to content

[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos


4,696 posts in this topic

Recommended Posts

cool update! weird i notice the ionetworking kext has the plugin folder and it chose to use LNX's plugin? is that right?

Correct. I haven't switched them. Sorta forgot about it. :(

 

I got a new one in there with the RealtekR1000SL.kext: RealtekR1000SL__Yukon 88E8056. But, it's in the repository folder.

 

MAJ

Link to comment
Share on other sites

Thanks for the script update DD. Works like a charm on my medion laptop :P

Can anyone tell me the best top notch GPU at the moment that will work OOB with OSX?

Thinking of picking up a new GPU if I dont get the SSD first. Thanks in advance.

 

Cheers

Charles

Link to comment
Share on other sites

The drive I am booting to to get work caught up is continuing to have what I cam calling a memory leak. I don't actually know that it is leaking memory access or what it is doing in actuality, the result is that I am loosing spotlight access and that apps are not responding and that some of the time it boots and I Can use all my apps and I Can search in spotlight. But some of the time after boot it boots into the condition I am describing.

 

But even when it boots normally and I Can use spotlight, after a half hour to an hour of working it seems to stop working anymore, programs get half launched and spin the beach ball. I still cant shut down properly and have to hard switch off.

 

When I do this and reboot single user, APplejack finds volume and directory count is off and repairs it. THen on reboot it works - for a while - then it doesn't work anymore.

 

I have had a healthy hack before and it ran beautifully, It should not be doing this. It should be shutting down normally.

 

What am I not seeing here? Can anyone suggest a strategy to find out what the problem is so that I can correct it? Without the fast spotlight search feature, using the Mac platform is a lot less pleasant an experience. Worse, I use LEap (ironicsoftware) to metadata tag my files so I Cant even keep track off all the projects I am currently trying to keep spinning right now.

 

Thanks all.

Link to comment
Share on other sites

I've a problem with a Graphic Card selector.

After i've selected my graphics card from list there an script error:

 

nVidia GeForce GTS 250 1024MB

Is this card selection correct?: [Y/n]:

2010-12-09 16:38:05.017 defaults[1491:903]

Domain /Volumes/newOsX/Extra/com.apple.boot does not exist :D

 

In effect there is a com.apple.boot.plist on /Extra path.

 

Another problem: anyone has experienced some Geekbench crash ?

I think is Graphic card related, this is the Geekbench log: GeekBenk log

 

Some ideas ? Thank you guys.

Link to comment
Share on other sites

ZoroLives,

I'm thinking you got hard drive issues, which is effecting your virtual memory paging performance. This would explain why it progressively gets worst as time goes on. You are using more memory (natural) and more pages are getting paged to the hard drive. But, hard drive fails to to able to retrieve needed pages as you continue to work.

Is journaling enabled on your boot drive?

Have you run a SMART test on your hard drive?

Can you post your system.log for us?

 

 

AndreaM,

I can't see any issues with the EFI strings on my side, so could you post your Install.log from the script?

It looks to be a volume not mounting issue. Are you using a EFI partition install or RAID install?

 

EDIT: Oh, and when using the bash default read commands, you don't list the ".plist" in the path name, so that's why it's not listed in the error. Nothing unusual here. :)

 

regards,

MAJ

Link to comment
Share on other sites

Thanks for the script update DD. Works like a charm on my medion laptop :D

Can anyone tell me the best top notch GPU at the moment that will work OOB with OSX?

Thinking of picking up a new GPU if I dont get the SSD first. Thanks in advance.

 

Cheers

Charles

Hey Charles,

I saw this in another thread Here lists a few goodies that work with RC5 and GraphicsEnagler=Yes.

Sadly they just came out with the 560 and 570, so its probably only a matter of time till they get worked into the mix.

Link to comment
Share on other sites

AndreaM,

I can't see any issues with the EFI strings on my side, so could you post your Install.log from the script?

It looks to be a volume not mounting issue. Are you using a EFI partition install or RAID install?

 

EDIT: Oh, and when using the bash default read commands, you don't list the ".plist" in the path name, so that's why it's not listed in the error. Nothing unusual here. :wub:

 

regards,

MAJ

 

Hi MAJ,

thanks for your attention. This is my Install.log. In effect seem to to correct.

But in Terminal i see the following message:

...

12) nVidia GeForce 7300 32) nVidia GeForce GTX 460

13) nVidia GeForce 7500 33) nVidia GeForce GTX 465

14) nVidia GeForce 7600 34) nVidia GeForce GTX 470

15) nVidia GeForce 7800 35) nVidia GeForce GTX 480

16) nVidia GeForce 7900 36) nVidia Quadro FX 1700

17) nVidia GeForce 8200 37) nVidia Quadro FX 3700

18) nVidia GeForce 8300 38) nVidia Quadro FX 4500

19) nVidia GeForce 8400 39) nVidia Quadro FX 4600

20) nVidia GeForce 8500

-----------------------------

1) nVidia GeForce GTS 250

-----------------------------

1) nVidia GeForce GTS 250 512MB

2) nVidia GeForce GTS 250 1024MB

 

nVidia GeForce GTS 250 1024MB

Is this card selection correct?: [Y/n]: y2010-12-10 15:36:10.659 defaults[1349:903]

Domain /Volumes/newOsX/Extra/com.apple.boot does not exist

...

I'm using a EFI partition. I've made a Clone of my 10.6.1 disk, rebooted and verifyed with the script some kext and plist.

The old 10.6.1 disk is always mounted on my new system, could be make some trouble ?

 

regards,

Andrea

Link to comment
Share on other sites

ZoroLives,

I'm thinking you got hard drive issues, which is effecting your virtual memory paging performance. This would explain why it progressively gets worst as time goes on. You are using more memory (natural) and more pages are getting paged to the hard drive. But, hard drive fails to to able to retrieve needed pages as you continue to work.

Is journaling enabled on your boot drive?

Have you run a SMART test on your hard drive?

Can you post your system.log for us?

.........

regards,

MAJ

I can post my system log, please tell me more specifically what you want (where to get it, what to get)? I assume you want me to copy some of the Console log files? Better if I could clear it, restart, and have that data for you? Forgive my paranoia but I don't yet understand how online banking which I have just been doing is absolutely not going to show up in any logs that I will soon post publicly.

 

I don't think it is the hard drive. It has been working for quite a while almost since my last post and what I did was to disable the power-saver/sleep mode. I also used Leap, the metadata finder program that has a preference setting to rebuild the spotlight index. I dragged in and out of the "do not index" folder as suggested earlier, but I think it remained hosed until Leap touched it. I think part of it was a corrupt index that just wouldn't die.

 

I still do not have this all set up the way it should be set up. I am still hit and miss when it comes to figuring what is needed and what is not. I would love to go to the more recent 10.6.5 but I am still trying to make 10.6.2 stable. I am still only booting to this drive and not the old main drive.

 

I think what is wrong is pretty much my fault all around, operator error, garbage in-garbage out, etc. There is so much information scattered over this very long thread, I find it a challenge to just see what I should, and should not have for this install. I remember at one point (I think) someone offered a DSDT patch that really helped my install?

 

Please let me know (exactly) what you need from me to help you, help me.

 

Much thanks.

Link to comment
Share on other sites

AndreaM,

I don't see any evidence in the log that you are installing on the EFI partition. Are you sure you don't have a Extra folder on your main system partition? According to your log, the Plist Selector is only listing boot.plists found in Extra on both "newOsX" and "OsX".

However, there are definitely some issues here. It looks like the script is attempting to access a non-existent (or empty) boot.plist in /Extra, as there are no keys/arguments being displayed.

 

Did you start with a EFI partition setup and then start using this new script version?

I'm looking to see if the script is incorrectly identifying your setup and thinks it's a Extra setup when it's really EFI. It may be a issue with creating the new preferences on an existing setup.

 

Ummmm. I can't make it fault on my side. It correctly identifies my Extra, EFI, and RAID setups when started as new. I also changed the names of my drives to the ones you have, just in case the name similarity is a issue. No issues here.

 

When you install kexts, does everything work okay for you? Can you post a log of that install? I need to see where these files are really going.

 

 

ZoroLives,

There won't be any personal info in that log - it'll be all low-level, system-related stuff. Post it as a PM, if you wish. Might be simpler to just select System.log in Console, select all text and drag it to desktop. Or, copy-paste to a TextEdit doc.

 

best regards,

MAJ

Link to comment
Share on other sites

That list doesn't look correct. It looks like a RAID helper partition is listed, but I don't believe it should be there.

Make sure you have no RAID helper partitions mounted before you enter "Modify Plist". This is a bug I have fixed in the next release.

If you want, you can send me your Install.log and I'll look into what may be happening. This will help me get it fixed up.

 

 

Hey,

 

now it seems to work. I can modify my plist - for example booting in 32 bit mode or in 64 bit mode.

I wanted to use my two Graphic cards. i followed the howto provided in your ~extra folder. The Problem is: it simply doesn't work :D.

 

i updated my boot.plist:

<?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>EthernetBuiltIn</key>

<string>Yes</string>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>arch=x64_86 -v boot-uuid=C6B90EA4-4695-4B70-9C48-44E3CCB7A07D</string>

<key>Theme</key>

<string>NebulOSX</string>

<key>Timeout</key>

<string>1</string>

<key>PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>

<dict>

<key>@0,AAPL,boot-display</key>

<data></data>

<key>@0,can-hot-plug</key>

<data></data>

<key>@0,compatible</key>

<string>NVDA,NVMac</string>

<key>@0,connector-type</key>

<data>AAAABA==</data>

<key>@0,device_type</key>

<string>display</string>

<key>@0,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@0,name</key>

<string>NVDA,Display-A</string>

<key>@1,AAPL,boot-display</key>

<data></data>

<key>@1,can-hot-plug</key>

<data></data>

<key>@1,compatible</key>

<string>NVDA,NVMac</string>

<key>@1,connector-type</key>

<data>AAAABA==</data>

<key>@1,device_type</key>

<string>display</string>

<key>@1,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@1,name</key>

<string>NVDA,Display-B</string>

<key>NVCAP</key>

<data>BAAAAAAAAwAMAAAAAAAABwAA</data>

<key>NVPM</key>

<data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data>

<key>built-in</key>

<data>AA==</data>

<key>VRAM,totalsize</key>

<string>0x38000000</string>

<key>device_type</key>

<string>NVDA,GeForce</string>

<key>model</key>

<string>NVIDIA GeForce GTX 260</string>

<key>name</key>

<string>NVDA,Parent</string>

<key>rm_multiboard_capable</key>

<data>AAAAAQ==</data>

<key>rom-revision</key>

<string>NVIDIA GeForce GTX 260 OpenGL Engine</string>

</dict>

<key>PciRoot(0x1)/Pci(0x7,0x0)/Pci(0x0,0x0)</key>

<dict>

<key>@0,AAPL,boot-display</key>

<data></data>

<key>@0,can-hot-plug</key>

<data></data>

<key>@0,compatible</key>

<string>NVDA,NVMac</string>

<key>@0,connector-type</key>

<data>AAAABA==</data>

<key>@0,device_type</key>

<string>display</string>

<key>@0,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@0,name</key>

<string>NVDA,Display-A</string>

<key>@1,AAPL,boot-display</key>

<data></data>

<key>@1,can-hot-plug</key>

<data></data>

<key>@1,compatible</key>

<string>NVDA,NVMac</string>

<key>@1,connector-type</key>

<data>AAAABA==</data>

<key>@1,device_type</key>

<string>display</string>

<key>@1,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@1,name</key>

<string>NVDA,Display-B</string>

<key>NVCAP</key>

<data>BAAAAAAAAwAMAAAAAAAABwAA</data>

<key>NVPM</key>

<data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data>

<key>built-in</key>

<data>AA==</data>

<key>VRAM,totalsize</key>

<string>0x20000000</string>

<key>device_type</key>

<string>NVDA,GeForce</string>

<key>model</key>

<string>NVIDIA GeForce 9800 GT</string>

<key>name</key>

<string>NVDA,Parent</string>

<key>rm_multiboard_capable</key>

<data>AAAAAQ==</data>

<key>rom-revision</key>

<string>NVIDIA GeForce 9800 GT OpenGL Engine</string>

</dict>

</dict>

</plist>

 

i Think this is right till there?!

 

then i updated my DSDT.aml --> this is how my uncompiled DSDT.dsl looks like:

........

Device (PCI0)

{

 

 

 

 

Device (PEGP)

{

Name (_ADR, 0x00030000)

Device (GFX0)

{

}

}

 

Device (GFX1)

{

Name (_ADR, 0x00070000)

}

 

 

 

 

 

 

 

Name (_HID, EisaId ("PNP0A03"))

Name (_ADR, Zero)

Name (_UID, One)

Name (_BBN, Zero)

Method (_S3D, 0, NotSerialized)

{

If (LEqual (OSFL, 0x02))

{

Return (0x02)

}

Else

{

Return (0x03)

}

..........

 

The full version is here: http://paste.ubuntu.com/542317/

 

 

i Boot my Mac in 64 bit mode. That works but i just can use one display, with a crapy resulution 1024x768.

Maybe the Boot.log is interesting too: http://paste.ubuntu.com/542319/

and the kernel.log: http://paste.ubuntu.com/542322/

 

Has anyone an idea what i can do there? in 2 Weeks i need 3 Displays for a presentation...

 

Please Help!

 

Thanks.

 

Pcace

Link to comment
Share on other sites

pcace,

There are two things wrong with your boot.plist setup for EFI strings:

 

1. The EFI string needs to be inside a "device-properties" key or tag. The boot.plist does not/should not contain the EFI string plist.

2. The entire EFI string itself needs to be in hex format before including it in the boot.plist.

 

Take the EFI string you have created and strip out the boot.plist keys/arguments (EthernetBuiltIn, Kernel, etc.). Convert to a hex string, then import into your boot.plist.

 

Here's an example of your boot.plist containing a example EFI string:

 

<?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>EthernetBuiltIn</key>
<string>Yes</string>
<key>GraphicsEnabler</key>
<string>Yes</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
<key>device-properties</key>
<string>cd0300000100000001000000c1030_EFI_STRING_IS_LONG_STRING_OF HEX_NUMBERS</string>
</dict>
</plist>

 

MAJ

Link to comment
Share on other sites

Hey,

 

 

thanks for your answer, but i not realy get it! i have 2 questions:

do i need gfraphics enabler in my boot plist, when i use efi strings? (i think not?!)

and second, im not able to convert these strings to a hex string!

 

i tried the following: i extracted everything that has to do with my graphics cards to an other plist file:

<?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">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

 

<key>PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>

<dict>

<key>@0,AAPL,boot-display</key>

<data></data>

<key>@0,can-hot-plug</key>

<data></data>

<key>@0,compatible</key>

<string>NVDA,NVMac</string>

<key>@0,connector-type</key>

<data>AAAABA==</data>

<key>@0,device_type</key>

<string>display</string>

<key>@0,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@0,name</key>

<string>NVDA,Display-A</string>

<key>@1,AAPL,boot-display</key>

<data></data>

<key>@1,can-hot-plug</key>

<data></data>

<key>@1,compatible</key>

<string>NVDA,NVMac</string>

<key>@1,connector-type</key>

<data>AAAABA==</data>

<key>@1,device_type</key>

<string>display</string>

<key>@1,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@1,name</key>

<string>NVDA,Display-B</string>

<key>NVCAP</key>

<data>BAAAAAAAAwAMAAAAAAAABwAAAAA</data>

<key>NVPM</key>

<data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data>

<key>built-in</key>

<data>AA==</data>

<key>VRAM,totalsize</key>

<string>0x38000000</string>

<key>device_type</key>

<string>NVDA,GeForce</string>

<key>model</key>

<string>NVIDIA GeForce GTX 260</string>

<key>name</key>

<string>NVDA,Parent</string>

<key>rm_multiboard_capable</key>

<data>AAAAAQ==</data>

<key>rom-revision</key>

<string>NVIDIA GeForce GTX 260 OpenGL Engine</string>

</dict>

 

<key>PciRoot(0x1)/Pci(0x7,0x0)/Pci(0x0,0x0)</key>

<dict>

<key>@0,AAPL,boot-display</key>

<data></data>

<key>@0,can-hot-plug</key>

<data></data>

<key>@0,compatible</key>

<string>NVDA,NVMac</string>

<key>@0,connector-type</key>

<data>AAAABA==</data>

<key>@0,device_type</key>

<string>display</string>

<key>@0,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@0,name</key>

<string>NVDA,Display-A</string>

<key>@1,AAPL,boot-display</key>

<data></data>

<key>@1,can-hot-plug</key>

<data></data>

<key>@1,compatible</key>

<string>NVDA,NVMac</string>

<key>@1,connector-type</key>

<data>AAAABA==</data>

<key>@1,device_type</key>

<string>display</string>

<key>@1,display-connect-flags</key>

<data>AAAAAA==</data>

<key>@1,name</key>

<string>NVDA,Display-B</string>

<key>NVCAP</key>

<data>BAAAAAAAAwAMAAAAAAAABwAAAAA</data>

<key>NVPM</key>

<data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data>

<key>built-in</key>

<data>AA==</data>

<key>VRAM,totalsize</key>

<string>0x20000000</string>

<key>device_type</key>

<string>NVDA,GeForce</string>

<key>model</key>

<string>NVIDIA GeForce 9800 GT</string>

<key>name</key>

<string>NVDA,Parent</string>

<key>rm_multiboard_capable</key>

<data>AAAAAQ==</data>

<key>rom-revision</key>

<string>NVIDIA GeForce 9800 GT OpenGL Engine</string>

</dict>

</plist>

 

Than i wanted to use gfxutil to convert this to a hex:

 

/Applications/HackInstaller/\~extra/Resources/gfxutil -i xml -o hex /Users/me/Desktop/Graphic.plist /Users/me/Desktop/Graphic.hex

/Applications/HackInstaller/~extra/Resources/gfxutil: invalid property list xml inputfile '/Users/me/Desktop/Graphic.plist'!

 

 

what am i doing wrong?

 

Please help me out!

 

 

Thanks,

 

Pcace

 

pcace,

There are two things wrong with your boot.plist setup for EFI strings:

 

1. The EFI string needs to be inside a "device-properties" key or tag. The boot.plist does not/should not contain the EFI string plist.

2. The entire EFI string itself needs to be in hex format before including it in the boot.plist.

 

Take the EFI string you have created and strip out the boot.plist keys/arguments (EthernetBuiltIn, Kernel, etc.). Convert to a hex string, then import into your boot.plist.

 

Here's an example of your boot.plist containing a example EFI string:

 

<?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>EthernetBuiltIn</key>
<string>Yes</string>
<key>GraphicsEnabler</key>
<string>Yes</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
<key>device-properties</key>
<string>cd0300000100000001000000c1030_EFI_STRING_IS_LONG_STRING_OF HEX_NUMBERS</string>
</dict>
</plist>

 

MAJ

 

 

Sorry,

 

i got it now...

 

 

does that look right?

 

<?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>EthernetBuiltIn</key>

<string>Yes</string>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>arch=x64_86 -v boot-uuid=C6B90EA4-4695-4B70-9C48-44E3CCB7A07D</string>

<key>Theme</key>

<string>NebulOSX</string>

<key>Timeout</key>

<string>1</string>

 

<key>device-properties</key>

<string>4c0400000100000001000000400400001700000002010c00d041030a010000000101060000030101060000007fff04002e000000400030002c004100410050004c002c0062006f006f0074002d0064006900730070006c00610079000000040000000e0000004e00560050004d00000020000000010000000000000000000000000000000000000000000000000000001e00000072006f006d002d007200650076006900730069006f006e000000280000004e5649444941204765466f7263652047545820323630204f70656e474c20456e67696e652e000000400031002c004100410050004c002c0062006f006f0074002d0064006900730070006c0061007900000004000000100000004e00560043004100500000001600000004000000000003000c00000000000007000022000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001a0000004e5649444941204765466f726365204754582032363036000000400030002c0064006900730070006c00610079002d0063006f006e006e006500630074002d0066006c006100670073000000080000000000000014000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d4124000000400030002c00630061006e002d0068006f0074002d0070006c00750067000000040000003000000072006d005f006d0075006c007400690062006f006100720064005f00630061007000610062006c0065000000080000000000000114000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4224000000400031002c00630061006e002d0068006f0074002d0070006c00750067000000040000001c0000006400650076006900630065005f0074007900700065000000100000004e5644412c4765466f72636536000000400031002c0064006900730070006c00610079002d0063006f006e006e006500630074002d0066006c006100670073000000080000000000000020000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61630e0000006e0061006d00650000000f0000004e5644412c506172656e7422000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c617920000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616328000000400031002c0063006f006e006e006500630074006f0072002d00740079007000650000000800000000000004220000005600520041004d002c0074006f00740061006c00730069007a00650000000800000000000038160000006200750069006c0074002d0069006e000000050000000028000000400030002c0063006f006e006e006500630074006f0072002d00740079007000650000000800000000000004</string>

 

<key>device-properties</key>

<string>4c0400000100000001000000400400001700000002010c00d041030a010000000101060000070101060000007fff04002e000000400030002c004100410050004c002c0062006f006f0074002d0064006900730070006c00610079000000040000000e0000004e00560050004d00000020000000010000000000000000000000000000000000000000000000000000001e00000072006f006d002d007200650076006900730069006f006e000000280000004e5649444941204765466f7263652039383030204754204f70656e474c20456e67696e652e000000400031002c004100410050004c002c0062006f006f0074002d0064006900730070006c0061007900000004000000100000004e00560043004100500000001600000004000000000003000c00000000000007000022000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001a0000004e5649444941204765466f726365203938303020475436000000400030002c0064006900730070006c00610079002d0063006f006e006e006500630074002d0066006c006100670073000000080000000000000014000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d4124000000400030002c00630061006e002d0068006f0074002d0070006c00750067000000040000003000000072006d005f006d0075006c007400690062006f006100720064005f00630061007000610062006c0065000000080000000000000114000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4224000000400031002c00630061006e002d0068006f0074002d0070006c00750067000000040000001c0000006400650076006900630065005f0074007900700065000000100000004e5644412c4765466f72636536000000400031002c0064006900730070006c00610079002d0063006f006e006e006500630074002d0066006c006100670073000000080000000000000020000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61630e0000006e0061006d00650000000f0000004e5644412c506172656e7422000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c617920000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616328000000400031002c0063006f006e006e006500630074006f0072002d00740079007000650000000800000000000004220000005600520041004d002c0074006f00740061006c00730069007a00650000000800000000000020160000006200750069006c0074002d0069006e000000050000000028000000400030002c0063006f006e006e006500630074006f0072002d00740079007000650000000800000000000004</string>

 

 

</dict>

 

</plist>

 

 

Thanks,

 

 

Pcace

Link to comment
Share on other sites

I appreciate this is a shot in the dark but I was wondering if anyone could help me diagnose a kernel panic problem I'm getting very often.

 

My osx86 is stable most of the time, but as soon as I connect to my work VPN using the Juniper Network connect client, I get a KP within a few minutes.

 

This only seems to have happened since I upgraded to 10.6.5. I know it isn't the software because if I run it on my macbook or even an osx86 netbook it's fine.

 

I'm using the realtek driver for OSX86 on their website if that makes a difference.

 

Thanks for any help.

Link to comment
Share on other sites

I am on 10.6.2 and am ready to upgrade once i get some new hardware.

 

I would like a 1GB video card. is this the best for hackintosh using Digital Dreamers script:

 

nVidia GeForce GTS 250 1024MB

 

what are some other options? Links to newegg. I want a good one that will last a while.

 

Also are there limits to the RAM i can install in a hackintosh?

Link to comment
Share on other sites

fruitbat04,

If I were you, I'd try a different LAN driver and see if your situation improves.

There are two others you can try: The RealtekR1000SL.kext and RealtekRTL81xx_Lnx2Mac.kext

 

 

taylorutah,

The GTS 250 is considered a "low-end" card by today's standards, although it is basically a reworked 9800 GTS+, which is not a weak card. I've been in the market looking for an inexpensive nVidia card as a backup to my ailing ATI 4870X2 (yes, it'd be a downgrade on the Windows side) and this is one I have my eye on. I think it's great for the casual gamer on a budget. Still won't run Crysis respectably. ;)

 

RAM limits are set by the motherboard and I know many have 12GB installed without any issues. The Gigabyte UD5 board supports 24GB, but I haven't heard of any reports of any having that much installed and how overclockable it is in that configuration.

 

MAJ

Link to comment
Share on other sites

Hi,

 

i just got my 2 Graphic cards working.

But again i have some Questions:

 

oclinfo sais, that my GTX260 has no Doubleprecision. That is NOT true. How can i make that card recogniced with Double-Precision Processor?

 

And second:

 

is there an git or svn repository to stay up to date with your script dd?

 

 

Thanks,

 

 

Pcace

 

 

PS.: the Output of oclinfo-0.2:

macpro:~ me$ /Users/me/Downloads/oclinfo-0.2/oclinfo ; exit;

1 OpenCL platform found!

 

[Platform 0]

Name: Apple

Vendor: Apple

Version: OpenCL 1.0 (Aug 22 2010 18:08:16)

Profile: FULL_PROFILE

 

 

[OpenCL-only Context]

3 OpenCL devices found!

 

[Device 0]

Name: GeForce GTX 260

Vendor: NVIDIA

Type: GPU

Device Version: OpenCL 1.0

Driver Version: CLH 1.0

Compute Units: 24

Work Group Size: 512

Clock: 1242 MHz

Global Memory: 896 MB

Local Memory: 16 KB

Cache Size: 0 KB

Cache Line Size: 0 Bytes

Available: Yes

Double-Precision: No

Extensions:

cl_khr_byte_addressable_store

cl_khr_global_int32_base_atomics

cl_khr_global_int32_extended_atomics

cl_APPLE_gl_sharing

cl_APPLE_SetMemObjectDestructor

cl_APPLE_ContextLoggingFunctions

cl_khr_local_int32_base_atomics

cl_khr_local_int32_extended_atomics

 

[Device 1]

Name: GeForce 9800 GT

Vendor: NVIDIA

Type: GPU

Device Version: OpenCL 1.0

Driver Version: CLH 1.0

Compute Units: 14

Work Group Size: 512

Clock: 1500 MHz

Global Memory: 512 MB

Local Memory: 16 KB

Cache Size: 0 KB

Cache Line Size: 0 Bytes

Available: Yes

Double-Precision: No

Extensions:

cl_khr_byte_addressable_store

cl_khr_global_int32_base_atomics

cl_khr_global_int32_extended_atomics

cl_APPLE_gl_sharing

cl_APPLE_SetMemObjectDestructor

cl_APPLE_ContextLoggingFunctions

 

[Device 2]

Name: Intel® Core i7 CPU 920 @ 2.67GHz

Vendor: Intel

Type: CPU

Device Version: OpenCL 1.0

Driver Version: 1.0

Compute Units: 8

Work Group Size: 1

Clock: 3800 MHz

Global Memory (Total): 9216 MB

Global Memory (Host): 6912 MB

Global Memory (PCIe): 2304 MB

Local Memory: 16 KB

Cache Size: 8192 KB

Cache Line Size: 64 Bytes

Available: Yes

Double-Precision: Yes

Extensions:

cl_khr_fp64

cl_khr_global_int32_base_atomics

cl_khr_global_int32_extended_atomics

cl_khr_local_int32_base_atomics

cl_khr_local_int32_extended_atomics

cl_khr_byte_addressable_store

cl_APPLE_gl_sharing

cl_APPLE_SetMemObjectDestructor

cl_APPLE_ContextLoggingFunctions

 

[shared OpenCL+OpenGL Context]

2 OpenCL devices found!

 

[Device 0]

Name: GeForce GTX 260

Vendor: NVIDIA

Type: GPU

Device Version: OpenCL 1.0

Driver Version: CLH 1.0

Compute Units: 24

Work Group Size: 512

Clock: 1242 MHz

Global Memory: 896 MB

Local Memory: 16 KB

Cache Size: 0 KB

Cache Line Size: 0 Bytes

Available: Yes

Double-Precision: No

Extensions:

cl_khr_byte_addressable_store

cl_khr_global_int32_base_atomics

cl_khr_global_int32_extended_atomics

cl_APPLE_gl_sharing

cl_APPLE_SetMemObjectDestructor

cl_APPLE_ContextLoggingFunctions

cl_khr_local_int32_base_atomics

cl_khr_local_int32_extended_atomics

 

[Device 1]

Name: Intel® Core i7 CPU 920 @ 2.67GHz

Vendor: Intel

Type: CPU

Device Version: OpenCL 1.0

Driver Version: 1.0

Compute Units: 8

Work Group Size: 1

Clock: 3800 MHz

Global Memory (Total): 9216 MB

Global Memory (Host): 6912 MB

Global Memory (PCIe): 2304 MB

Local Memory: 16 KB

Cache Size: 8192 KB

Cache Line Size: 64 Bytes

Available: Yes

Double-Precision: Yes

Extensions:

cl_khr_fp64

cl_khr_global_int32_base_atomics

cl_khr_global_int32_extended_atomics

cl_khr_local_int32_base_atomics

cl_khr_local_int32_extended_atomics

cl_khr_byte_addressable_store

cl_APPLE_gl_sharing

cl_APPLE_SetMemObjectDestructor

cl_APPLE_ContextLoggingFunctions

 

logout

 

[Prozess beendet]

Link to comment
Share on other sites

is there an git or svn repository to stay up to date with your script dd?

LOL. No.

I release updates when I think they are ready for public use. The front page will announce the updates with version number.

 

Would this card work out of the box?

 

MSI N460GTX CYCLONE 1GB

http://www.newegg.com/Product/Product.aspx...N82E16814127510

From my research: It'll work, but may need a bit more work. See the following:

nVidia GTX460, Anyone Installed and Working?

fermi/gtx 480/gtx 470, it's working!

New fermi drivers for osx

 

MAJ

Link to comment
Share on other sites

I CANNOT GET GEEKBENCH TO RUN...any ideas? IT only works as Rosetta and Im trying to confirm if my machine is running at full spec!

 

I have the following

 

Core i7 930

12 gb of 1600mhz ram

GB-X58-UD7

128gb SSD

BFG GeForce 285 OXC

 

thanks for any help!

 

Kevlar

Link to comment
Share on other sites

fruitbat04,

If I were you, I'd try a different LAN driver and see if your situation improves.

There are two others you can try: The RealtekR1000SL.kext and RealtekRTL81xx_Lnx2Mac.kext

 

Hey DD.

 

Cheers, I tried the one in this package http://lnx2mac.blogspot.com/p/realtekrtl81xx-osx-driver.html and it's seems to have done the job so far :thumbsdown_anim:

 

Good to see the unofficial ones are much more stable than the official ones :dev:

Link to comment
Share on other sites

 Share

×
×
  • Create New...