render^ Posted March 17, 2010 Share Posted March 17, 2010 I tried both dsdt.aml. The one Ashmodai posted and the one you provided. I opted to use Ashmodai's because it correctly identifies my processor as a dual xeon, and the boot time is so much shorter (about 4 secs), whereas yours doesn't correctly identifies the processor, showing Unknown instead, and booting time is much longer. I do not use the SleepEnabler because it kernel panics. Thankfully i had a bootable USB installation, so I was able to take care of that by deleting the problematic kext and rebuilding the kext cache (permissions and kextcache) Also, after the 10.6.2 update from apple using software updater, networking no longer works. It seems apple updates install a new IOnetworkingfamily.kext. I tried fixing it by doing the same thing i did before. It didnt work. I tried by restoring the original 10.6.2 IOnetworking kext and modifying the Info.plist with vi as su. I rebuilt the /S/L/ kextcache. I redid this on boot -s mode. Nothing works. I don't know what else to try. My networking worked in 10.6, but it doesn't work anymore on 10.6.2 Any help? Link to comment Share on other sites More sharing options...
peach-os Posted March 17, 2010 Share Posted March 17, 2010 the files I provided are from my 10.6.2 and working flawless. you might be doing something wrong - give kextutility a chance it shows the right informations on my machine because they are in the smbiosplist in extra - the same thing Ashmodai is doing have a look on the device id´s of the network. it´s possible that they are patched in the dsdt (not in mine) Link to comment Share on other sites More sharing options...
render^ Posted March 17, 2010 Share Posted March 17, 2010 I see. The processor issue might have been an smbios.plist thing. It's working fine for me, so I'll stick with it for now. Also, do you know why my kernel panics when I install the Sleepenabler.kext? Netkas's sleepneabler kext KP's with chameleon RC4 boot file. Many people are having trouble with Sleepenabler kexts because there are in fact, two or more versions of Sleepenabler. Version 10.6.2 works only in Netkas's while the 10.6 Sleepenabler kext works only in chameleon and it is compatible with 10.6.2 using chameleon's RC4. There is a third option by meklort which is backwards and forward (10.6.3) compatible, also using chameleon. I won't touch Sleepenabler for now since I don't know how to find the correct version of SE.kext. There is no easy way to track versions and documentation/readmes with the files are practically non-existent, and this throws off many unlucky people. I found no discernible differences on your smbios.plist and Ashmodai's but I'll look more closely, after I get done with Graphics (high priority). I'm taking the next step with graphics now, but solutions like http://www.insanelymac.com/forum/index.php?showtopic=206137 and this http://www.insanelymac.com/forum/index.php...t=?do=findComment&comment=1380825 look weak, and often come with incomplete support (not full res. no dual monitors, etc.) AND various problems with sleep/screensaver. The Sapphire ATI 512 (vga/dvi/hdmi outputs) graphics card shows up in System profiler as: DeviceID 0x9442 and Vendor: 0x1002, so that's 0x10029442, if I'm thinking correctly. Booting the computer atm is only possible through -x. How do I fix this? Will I need to put bootflags every time I restart the computer? Idk what to do... In response to myself: http://tonymacx86.blogspot.com/2009/12/ena...celeration.html It shows at least 3 different ways to enable graphics. Documentation is also poor, and it confuses many people, but tonymacx86 makes it easier for newcomers (like me) to get a quick and dirty understanding of the options and what they do, kinda. http://tonymacx86.blogspot.com/2009/12/ena...eleration.html[/url'>']Chameleon's GraphicsEnabler=YesThis is the simplest method to enable your graphics card. It was introduced in Chameleon 2.0, and is probably the most widely used method right now. Edit your com.apple.Boot.plist- located in /Extra/Extensions, to add the below text. Sometimes it doesn't identify all of the ports on the card, but if you're looking for full acceleration for 1 monitor only, this could be the way to go. It's automatically enabled in the tonymacx86-snowleopard.zip and tonymacx86-P55BootCD. DSDT The cleanest and newest method favored by many OSx86 enthusiasts for it's 'vanilla' approach. You add some code to your DSDT, and it auto-identifies your graphics card. You need to view your system's information to edit NVCap values using IORegistry Editor. This tool comes with XCode and should be on your Snow Leopard Retail DVD. If you selected XCode at install, it will be in /Devloper/Applications/Utilities. For an example of the edited code, download this .dsl file, taken from an MSI GD65 motherboard. EFI String You can use OSx86 Tools or EFIStudio applications to extract your specific card information, or EFI String. Then place that information into your com.apple.Boot.plist. It is also a very clean method involving no edited or additional kexts. Enabler Kexts Enabler kexts, like ethernet or audio kexts, are installed either in /Extra/Extensions or /System/Library/Extensions are the oldest used method of identifying graphics cards. Older methods for Leopard included NVInject, NVKush. Lately the most widely used kexts for Snow Leopard is NVEnabler and EVOenabler which both feature 32/64 bit support. NVEnabler injects 2nd display and TV-OUT information better than any method I've used.The downside of this method is that many times Apple's updates break functionality, necessitating users to find a new solution. Modified Kexts For troublesome and newer cards, some users must inject device IDs directly into stock system kexts in addition to providing enablers. Specifically the ATI 48xx series and nVidia GTX 2xx cards have proved more difficult to enable. For many solutions, check out netkas' blog. There are various ways to enable full graphics card acceleration for your Hackintosh. You can probably do 2 or 3 different methods to get to the same place. Some users will tout DSDT modifications over kexts for the sake of keeping the installation more like a real Mac. Others will argue that whatever is functional will suffice. Part of the fun is testing them all out and coming up with your own favorite solution. If you have any solutions for specific cards, feel free to post them in the comments section. Good luck with your graphics card! Time to fix graphics card. Soft RAID and Sleep next. ===== First post from *working!* Dual Xeon 8-core 2.27 GHz, 12 GB ECC, Asus Z8NA-D6, OSX 10.6 Retail+10.6.2 with Software Update. Thanks to peach-os, Ashmodai, uman, and kernel from #osx86@irc.moofspeak.net Link to comment Share on other sites More sharing options...
peach-os Posted March 17, 2010 Share Posted March 17, 2010 your posts are more like blogs - I like that. a newbie who is not afraid of trying things, sharing his progress and experiences - cool my first choice for the gfx solution would be also dsdt - because of lack of time I´m using the GraphicsEnabler in Chameleon. Works really good, but could also be one of the reasons that sleep is not working. does the shutdown work for you ? here only once in 20 times - restart works flawless. yes, the sleepenabler versions are really confusing - will try the one you posted. Link to comment Share on other sites More sharing options...
render^ Posted March 17, 2010 Share Posted March 17, 2010 Shutting down and Restarting have worked fine. I haven't touched on their functionality. I've set up the Graphics with the kexts that Apple includes in their 10.6.2. I downloaded and looked inside the LegacyATI4800family kext and found out all it does is add the key id string to the supported ATI4800family kext that apple already has in its 10.6.2 so apple detects it. I have not tested whether the 10.6 ati drivers work out of the box, but I sure believe they would. I added the kext in /Extra/Extensions, then did a boot -s and fixed permissions, and ran kextcache for /e/extensions.mkext /e/e. This installed the problematic kext, as it would not be recognized as a "legitimate" kext doing kextcache. I have to boot with the argument "GraphicsEnabler=Yes". Booting with "graphicsenabler=yes" doesn't work, it's case sensitive. I still need to fix the fact that I have to boot with this every time. I think I have to put the com.apple.Boot.plist in /E but I'm not sure. The Radeon 4850 Sapphire DVI/VGA/HDMI: (Fails in my hands, I don't have the patience or technical knowledge to try harder with this. I'm returning this, getting the 4890 XFX dual DVI. These seem to work better on dual monitors with the exotic package, according to several forums. I plan to use one monitor for 3D display, another for 2D) Works without patches, with an unintrusive /e/e/legacyati.kext no address/key/id modding or anything on the system's atifamily kexts, so this prevents any breakage when doing Software Upgrade. Working with single monitor at native resolution, correctly recognized EDID Dell S2409 1920x1080p60. QE/CI has full functionality. QE/CI seems to work only on Frontrow (smooth fadeouts, functionality seems ok), but not in Dashboard (choppy,blocky animations, low fps). Not sure why this is happening. However, this card has problems displaying two monitors. I tried connecting DVI and VGA, but no signal, and even the DVI has problems displaying to some larger monitors (samsung 24", used single D-DVI link). The monitor's EDID doesn't seem to go through. This issue might could be because I don't have a dual D-DVI cable. (Both monitors work fine with single D-DVI on MBs.) I also tried a DVI Splitter, with single dvi cables through both ends; neither monitor works. HDMI not tested. The Samsung Monitor is an isolated issue. Some Monitors are correctly recognized by apple through EDID, some aren't. the T260HD doesn't like apple (has EDID issues on my pc as well). TL;DR: Don't get the 4850 without dual dvi if you need 2 monitors. qe/ci working. Single VGA: Works with 3:4 aspect ratios Single DVI-d: works with some EDID monitors. DVI+VGA: doesn't work. HDMI: not tested. Might test tomorrow for the sake of thoroughness. Not that I really want to. Link to comment Share on other sites More sharing options...
peach-os Posted March 17, 2010 Share Posted March 17, 2010 1. this kext has to be in S/L/E because of dependencies - it cant´t work from extra 2. afaik you can´t use the modified kext and GraphicsEnabler a the same time Link to comment Share on other sites More sharing options...
render^ Posted March 18, 2010 Share Posted March 18, 2010 This kext has no dependencies, I'm using the vanilla approach. No kexts are modified. The purpose of Legacy kext is to allow apple to recognize the card on address 0x10029442, and many other cards that share the same address. Please open and read the kext itself. The kext is working because chameleon loads this kext and addresses before the actual legacy drivers, ie. ATI4800family.kext, fooling apple to think that my ATI kext driver is modified, when it fact it is not. Thus it doesn't need to be installed on /s/l/e; chameleon loads it from /e/extensions.mkext fine. This is the "vanilla" approach that allows apple to update ATI's drivers without breaking functionality (This means that if it gets updated, apple software will overwrite your modded ATI, which contains your custom hardware key, and you lose your mod; your graphics driver won't load, and you will cry). Lol I thought I was supposed to be the newbie, and here I am explaining what the kext does. Graphics Enabler only enables the OS to load the available graphics drivers/kexts. It won't tell the OS the custom addresses (ie. 0x10029442 for the sapphire 4850). This is why many people who enable GraphicsEnabler get a garbled screen (I also forgot to rebuild the kext cache, so I saw the same garbled screen. No issues after rebuilding). Remember graphicsenabler is only a chameleon command, and it works in the interface between the bios and the OS; it doesn't know anything about graphics cards ids or drivers. Graphics are disabled by default because it would likely mean most computers without apple's hardware ids would make the computer not display much. After enabling this, you must either add your hardware id/address on to the actual kext (ATIFamily kexts), or use LegacyATI kext. You can mod your LegacyATI kext and add your own address if it's not included in there! (If you think your card will work with apple's 4800 drivers.) That concludes my lecture about LegacyATI kext. I think I need to get a modded com.apple.Boot.plist so I don't have to type GraphicsEnabler=y every time. Do you know anything about this? In reply to myself. I'm thinking the Boot.plist file does just what I'm assuming. It loads boot arguments. So if I were to do something like <key>SingleUser</key> <string>Yes</string> or TRUE, or something like that, I'd get boot -s. I might test this later, if I'm not too lazy. Link to comment Share on other sites More sharing options...
peach-os Posted March 18, 2010 Share Posted March 18, 2010 that´s my lack of knowledge about ATI cards - never used them on hacmacs. with nvidia cards i never had such issues. I didn´t know that it is only a kext faking the id´s - of course this doesn´t have dependencies. about the GraphicsEnabler: my intention was to express that it usually doesn´t make sense. thanks for the explanations (although I knew the functionality of kexts and chameleon already) I´m a two finger typer - that might be the reason that my answers are shorter than yours and my last one misunderstandable Link to comment Share on other sites More sharing options...
render^ Posted March 18, 2010 Share Posted March 18, 2010 Yea I discovered something new. The problems many people have with unrecognized screens are most likely hardware/EDID monitor issues, not an improper graphics install. This explains why so many people have recurrent problems. Apple doesn't like some monitors, and they are not recognized (http://discussions.apple.com/thread.jspa?threadID=1986829&tstart=1). This is the reason for the high failure rate on some graphics threads. So now, monitors should also be added to the list of "supported" hardware. I would say any EDID compliant monitor should work. But most people will have to simply test it. Sometimes the monitor's the problem so there's this VNC test mentioned here. Link to comment Share on other sites More sharing options...
render^ Posted April 5, 2010 Share Posted April 5, 2010 Everything's been working great since 10.6.3 update. Everything works. Have not yet tried installing or enabling Sleep. Here's the latest: http://www.insanelymac.com/forum/index.php?showtopic=214226 2x Xeon E5520 w/ generic fans with spring loaded screws. XFX ATI 4890 12GB ECC ram 3x 1TB (Apple softRAID1+TM) (2xSamsung F1R, 1xWD Caviar Black) 64GB SSD with OSX 10.6.3 LiteOn DVD burner iHAS124-04 steelseries Siberia 51001SS USB Interface Soundcard Asio USB Bluetooth (for the apple kbd) Apple wireless keyboard 2x22" monitors Original Snow Leopard DVD 10.6 with Xcode full install. Updated with Software Updater. Complete install from vanilla with retail DVD. Thanks to the Chameleon team, netkas, and osx86.es Link to comment Share on other sites More sharing options...
render^ Posted November 9, 2011 Share Posted November 9, 2011 Hey Peach! Long time no post. I saw your thread on DSDT with CPU states and sleep, so I thought I'd revive this old thread. I have some issues regarding the possibility of a problematic DSDT and/or hardware issues. I was using Ashmodai's old DSDT.aml (from this thread) and it recognized both quad core Xeons E5520 (even the model was correctly recognized). I since ran a parallelized CPU-intensive program which crashed the machine. After rebooting, I had problems booting with Chameleon not loading at all. I've updated to the latest Chameleon svn (build 1668, I believe) and could still not load the bootloader, so I removed a hard drive (non-boot drive) that was singled out as the source of Chameleon not booting. After the booting issue was resolved, (and the problematic drive formatted and put into a different computer) I re-ran the CPU-intensive program again, but realized only 4 cores were being detected (logical cores). System Profiler shows 2 single core Xeons. I've tried using your DSDT.aml on this machine, but it doesn't boot, as it hangs on the gray screen (small 'no apple' sign). Reverting back to Ashmodai's old DSDT allows it to boot. Then I updated from 10.6.3 to 10.6.8 by Software update and fixed the appropriate kexts (netkas' Radeon HD 4890 exotic for 10.6.8, Intel networking, and Evoreboot, Fakesmc, and Blockinjector (last 3 on E/E). Again in 10.6.8, using your DSDT gives the the boot error, while Ashmodai's OLD DSDT gives me two single core Xeons. I have not changed any bios settings after using your DSDT or Ashmodai's old DSDT (Nov 20 2009, 12:59 PM). Could you help me with any ideas? I have E5520's on the Hac. Link to comment Share on other sites More sharing options...
peach-os Posted November 9, 2011 Share Posted November 9, 2011 did you try to boot your machine without DSDT with disabler.kext ? please generate a DSDT file when booted with disabler.kext and upload it - I will check it. add also the one that's causing the trouble. I have my machine running with 10.6.8 without any issues and sleep Link to comment Share on other sites More sharing options...
render^ Posted November 10, 2011 Share Posted November 10, 2011 Here it is. Could not load the dsdt with DSDTSE 1.4.3 at first, due to NilObjectException. (Why is it that I always run into these problems?) Figured that making a new Account with a default home folder in /Users/ fixed the issue, since I have a non-standard home location in the Raid drive, separate from the boot SSD. The DSDT that is causing trouble is the one you posted in your thread. Booting with Disabler.kext and without DSDT also shows only two single core Xeons. dsdt.zip Link to comment Share on other sites More sharing options...
peach-os Posted November 11, 2011 Share Posted November 11, 2011 you messed up something - your "virgin" dsdt file is 100% identical with mine from the first post, which includes (only) the cmos reset fix and the HPET fix, so that you can boot without disabler. I posted a few better versions later. It looks like you still have a DSDT file loading - check it with bdmesg in chameleon utils. comparing your file with my actual DSDT there are many differences, which may be based on the fact that we are using different bios versions. also you hyperthreading seems to be deactivated on your machine - mine shows 32 cpu cores entries in DSDT - yours 16 for using the attached DSDT you should update bios to version 902 and activate hyperthreading. dsdt.aml.zip Link to comment Share on other sites More sharing options...
render^ Posted November 11, 2011 Share Posted November 11, 2011 How would I load the virgin DSDT? What I did was move the DSDT to another drive, add Disabler.kext to /e/e and reboot. I have no idea how DSDT is handled by the EFI/chameleon. Is it also cached as the kexts? Should I kextcache rebuild? I found out the processor had only one core enabled from the BIOS (DUH!). Once fixing that setting in the bios, I can see all 4 cores per processor. About HT... I thought you only double your physical cores into two logical cores. That would make 8*2=16, not 32. Unless you are using two 8-core processors, you can't have 32 logical cores. Link to comment Share on other sites More sharing options...
peach-os Posted November 12, 2011 Share Posted November 12, 2011 that's the reason I told you to check it with bdmesg. it will tell you if a dsdt file is loaded and where it's located. it's not cached. chameleon bootloader loads it from root or from Extra. actually you're right - it has only 8 + 8 virtual cores, but in the cpu part of the DSDT you will find 2 entries for each core=32 - sorry for the confusion. Link to comment Share on other sites More sharing options...
render^ Posted November 14, 2011 Share Posted November 14, 2011 I have deleted this post, as it contained a lot of useless text (dmesg output). Link to comment Share on other sites More sharing options...
peach-os Posted November 15, 2011 Share Posted November 15, 2011 dmesg is helpful, but we need bdmesg - in Extra - Utilities Link to comment Share on other sites More sharing options...
render^ Posted November 15, 2011 Share Posted November 15, 2011 I was able to run bdmesg. Enabled root user in System Preferences>Account>Login Options>Network Account Server>Open Directory Utility>Edit>Enable root user... By the way, I could not find bdmesg in /Extra/Utilities. It's not clear why I cannot sudo bdmesg when I log in to a regular Administrator account. If I log in as root, however, I can run bdmesg. I could not run bdmesg because it wasn't installed. This was solved by copying the binary from the Chimera 1.6 package or installing Chimera 1.6. It's interesting that it's seeing two different filesizes and files with same names for the kexts. Could this be from the GPT's EFI partition? Also, bdmesg says it's loading Darwin 10.6, (I have updated to 10.6.8) but uname -v tells me Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 Here's the diskutil output: # diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk0 1: EFI 209.7 MB disk0s1 2: Microsoft Basic Data 1000.0 GB disk0s2 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI 209.7 MB disk1s1 2: Apple_RAID 999.9 GB disk1s2 3: Apple_Boot Boot OSX 134.2 MB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk2 1: EFI 209.7 MB disk2s1 2: Apple_RAID 999.9 GB disk2s2 3: Apple_Boot Boot OSX 134.2 MB disk2s3 /dev/disk3 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS RAID1 *999.9 GB disk3 /dev/disk4 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *64.0 GB disk4 1: EFI 209.7 MB disk4s1 2: Apple_HFS Solid State 63.7 GB disk4s2 Link to comment Share on other sites More sharing options...
render^ Posted November 17, 2011 Share Posted November 17, 2011 I checked the .pkg of Chimera 1.6 and found that bdmesg was installed by it. I have switched bootloaders to chimera and manually set to boot from EFI (see also this). I have installed /Extra on the EFI as well. My OSX installation is now completely "vanilla", except for netkas' ATI HD exotic package 10.6.8. Disabler.kext (10.6 from Chameleon RC4) is being used, since I have no DSDT.aml here is bdmesg output. Chameleon 1.6.0 (svn-r1394) [2011-10-28 20:34:09] msr(301): platform_info 04011101 msr(305): flex_ratio 00000000 Sticking with [BCLK: 133Mhz, Bus-Ratio: 170] CPU: Brand String: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz CPU: Vendor/Family/ExtFamily: 0x756e6547/0x6/0x0 CPU: Model/ExtModel/Stepping: 0x1a/0x1/0x5 CPU: MaxCoef/CurrCoef: 0x0/0x11 CPU: MaxDiv/CurrDiv: 0x0/0x0 CPU: TSCFreq: 2266MHz CPU: FSBFreq: 133MHz CPU: CPUFreq: 2266MHz CPU: NoCores/NoThreads: 4/8 CPU: Features: 0x000002ff Attempting to read GPT Read GPT Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B Reading GPT partition 2, type 48465300-0000-11AA-AA11-00306543ECAC Read HFS+ file: [hd(0,1)/Extra/org.chameleon.Boot.plist] 238 bytes. Attempting to read GPT Read GPT Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B Reading GPT partition 2, type 52414944-0000-11AA-AA11-00306543ECAC Reading GPT partition 3, type 426F6F74-0000-11AA-AA11-00306543ECAC Attempting to read GPT Read GPT Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B Reading GPT partition 2, type EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 Attempting to read GPT Read GPT Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B Reading GPT partition 2, type 52414944-0000-11AA-AA11-00306543ECAC Reading GPT partition 3, type 426F6F74-0000-11AA-AA11-00306543ECAC Module 'Symbols.dylib' by 'Chameleon' Loaded. Description: Chameleon symbols for linking Version: 0 Compat: 0 Read HFS+ file: [hd(0,1)/Extra/Themes/Default/theme.plist] 2797 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/background.png] 2938 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/logo.png] 3016 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_generic.png] 16789 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_hfsplus.png] 16789 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_ext3.png] 16789 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_fat16.png] 24504 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_fat32.png] 16789 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_ntfs.png] 16789 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_cdrom.png] 24504 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_selection.png] 6075 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_scroll_prev.png] 2816 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/device_scroll_next.png] 2813 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_boot.png] 621 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_verbose.png] 2817 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_ignore_caches.png] 2817 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_single_user.png] 2817 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_memory_info.png] 621 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_video_info.png] 621 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_help.png] 621 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_verbose_disabled.png] 2817 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_ignore_caches_disabled.png] 2817 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_single_user_disabled.png] 2817 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/menu_selection.png] 3220 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/progress_bar.png] 2806 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/progress_bar_background.png] 2801 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/text_scroll_prev.png] 2935 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/text_scroll_next.png] 2940 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/font_console.png] 13715 bytes. Read HFS+ file: [hd(0,1)/Extra/Themes/Default/font_small.png] 8303 bytes. Read HFS+ file: [hd(0,2)/Library/Preferences/SystemConfiguration/com.apple.Boot.plist] 290 bytes. Read HFS+ file: [hd(0,1)/Extra/org.chameleon.Boot.plist] 238 bytes. Read HFS+ file: [hd(0,2)/System/Library/CoreServices/SystemVersion.plist] 479 bytes. Loading Darwin 10.6 Loading kernel mach_kernel Read HFS+ file: [hd(0,2)/mach_kernel] 4096 bytes. Read HFS+ file: [hd(0,2)/mach_kernel] 7690788 bytes. ACPI table not found: DSDT.aml No DSDT found, using 0 as uid value. Using PCI-Root-UID value: 0 ATI Framebuffer Addr: @0xD0000000 MMIO Addr: @0xFBEE0000 I/O Port Addr: @0x0000E000 ROM Addr: @0xFBEC0000 ATI card POSTed, reading Video BIOS from legacy space Card reported ports: 2 Framebuffer set to: Motmot using device's default. Number of ports set to: 2 using framebuffer's default. ATI Radeon HD 4800 Series 1024MB [1002:9460] (subsys [1682:2702]) (RV770:Motmot) :: PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0) Read HFS+ file: [hd(0,1)/Extra/smbios.plist] 735 bytes. Intel NHM IMC DRAM Controller [8086:3403] at 00:00.0 Frequency detected: 533 MHz (1066) Triple Channel CAS:7 tRC:7 tRP:7 RAS:20 (7-7-7-20) SMBus CmdReg: 0x103 Scanning SMBus [8086:3a30], mmio: 0xfaeff004, ioport: 0x400, hostc: 0x1 SPD[0] (size): 255 @0x50 SPD[0] (size): 255 @0x51 SPD[0] (size): 255 @0x52 SPD[0] (size): 255 @0x53 SPD[0] (size): 255 @0x54 SPD[0] (size): 255 @0x55 SPD[0] (size): 255 @0x56 SPD[0] (size): 255 @0x57 CPU is Intel(R) Xeon(R) CPU E5520 @ 2.27GHz, family 0x6, model 0x1a Type: 0, Length: 24, Handle: 0x0 BIOSInformation: vendor: Apple Computer, Inc. version: MP31.88Z.00C1.B00.080209154 releaseDate: 11/06/2009 Type: 1, Length: 27, Handle: 0x1 SystemInformation: manufacturer: Apple Inc. productName: MacPro3,1 version: 1.0 serialNumber: XB927BJ320G uuid: 405EDBC7-74FE-D511-AAD0-E841494777AD wakeupReason: 0x6 skuNumber: To Be Filled By O.E.M. family: MacPro Type: 2, Length: 15, Handle: 0x2 BaseBoard: manufacturer: Apple Inc. product: Mac-F4208DC8 version: Rev 1.xxG serialNumber: 103169680000135 assetTagNumber: To Be Filled By O.E.M. locationInChassis: To Be Filled By O.E.M. boardType: 0xA Type: 3, Length: 21, Handle: 0x3 SystemEnclosure: manufacturer: Chassis Manufacture type: 3 version: Chassis Version serialNumber: Chassis Serial Number assetTagNumber: Asset-1234567890 Type: 4, Length: 40, Handle: 0x4 ProcessorInformation: socketDesignation: CPU 1 processorType: 3 processorFamily: 0xB3 manufacturer: Intel processorID: 0x106A5 processorVersion: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz externalClock: 133MHz maximumClock: 2266MHz currentClock: 2266MHz serialNumber: To Be Filled By O.E.M. assetTag: To Be Filled By O.E.M. partNumber: To Be Filled By O.E.M. Type: 7, Length: 19, Handle: 0x5 Type: 7, Length: 19, Handle: 0x6 Type: 7, Length: 19, Handle: 0x7 Type: 4, Length: 40, Handle: 0x8 ProcessorInformation: socketDesignation: CPU 2 processorType: 3 processorFamily: 0xB3 manufacturer: Intel processorID: 0x106A5 processorVersion: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz externalClock: 133MHz maximumClock: 2266MHz currentClock: 2266MHz serialNumber: To Be Filled By O.E.M. assetTag: To Be Filled By O.E.M. partNumber: To Be Filled By O.E.M. Type: 7, Length: 19, Handle: 0x9 Type: 7, Length: 19, Handle: 0xa Type: 7, Length: 19, Handle: 0xb Type: 8, Length: 9, Handle: 0xc Type: 8, Length: 9, Handle: 0xd Type: 8, Length: 9, Handle: 0xe Type: 8, Length: 9, Handle: 0xf Type: 8, Length: 9, Handle: 0x10 Type: 8, Length: 9, Handle: 0x11 Type: 8, Length: 9, Handle: 0x12 Type: 8, Length: 9, Handle: 0x13 Type: 8, Length: 9, Handle: 0x14 Type: 8, Length: 9, Handle: 0x15 Type: 8, Length: 9, Handle: 0x16 Type: 8, Length: 9, Handle: 0x17 Type: 8, Length: 9, Handle: 0x18 Type: 8, Length: 9, Handle: 0x19 Type: 8, Length: 9, Handle: 0x1a Type: 8, Length: 9, Handle: 0x1b Type: 8, Length: 9, Handle: 0x1c Type: 8, Length: 9, Handle: 0x1d Type: 8, Length: 9, Handle: 0x1e Type: 8, Length: 9, Handle: 0x1f Type: 8, Length: 9, Handle: 0x20 Type: 8, Length: 9, Handle: 0x21 Type: 8, Length: 9, Handle: 0x22 Type: 8, Length: 9, Handle: 0x23 Type: 8, Length: 9, Handle: 0x24 Type: 8, Length: 9, Handle: 0x25 Type: 8, Length: 9, Handle: 0x26 Type: 8, Length: 9, Handle: 0x27 Type: 8, Length: 9, Handle: 0x28 Type: 9, Length: 13, Handle: 0x29 Type: 9, Length: 13, Handle: 0x2a Type: 9, Length: 13, Handle: 0x2b Type: 9, Length: 13, Handle: 0x2c Type: 9, Length: 13, Handle: 0x2d Type: 9, Length: 13, Handle: 0x2e Type: 10, Length: 6, Handle: 0x2f Type: 11, Length: 5, Handle: 0x30 Type: 13, Length: 22, Handle: 0x31 Type: 15, Length: 55, Handle: 0x32 Type: 16, Length: 15, Handle: 0x33 Type: 19, Length: 15, Handle: 0x34 Type: 17, Length: 27, Handle: 0x35 MemoryDevice: deviceLocator: DIMM_A1 bankLocator: BANK0 memoryType: DDR3 memorySpeed: 1333MHz manufacturer: N/A serialNumber: N/A assetTag: AssetTagNum1 partNumber: N/A Type: 20, Length: 19, Handle: 0x36 Type: 17, Length: 27, Handle: 0x37 MemoryDevice: deviceLocator: DIMM_B1 bankLocator: BANK1 memoryType: DDR3 memorySpeed: 1333MHz manufacturer: N/A serialNumber: N/A assetTag: AssetTagNum2 partNumber: N/A Type: 20, Length: 19, Handle: 0x38 Type: 17, Length: 27, Handle: 0x39 MemoryDevice: deviceLocator: DIMM_C1 bankLocator: BANK2 memoryType: DDR3 memorySpeed: 1333MHz manufacturer: N/A serialNumber: N/A assetTag: AssetTagNum3 partNumber: N/A Type: 20, Length: 19, Handle: 0x3a Type: 17, Length: 27, Handle: 0x3b MemoryDevice: deviceLocator: DIMM_D1 bankLocator: BANK3 memoryType: DDR3 memorySpeed: 1333MHz manufacturer: N/A serialNumber: N/A assetTag: AssetTagNum4 partNumber: N/A Type: 20, Length: 19, Handle: 0x3c Type: 17, Length: 27, Handle: 0x3d MemoryDevice: deviceLocator: DIMM_E1 bankLocator: BANK4 memoryType: DDR3 memorySpeed: 1333MHz manufacturer: N/A serialNumber: N/A assetTag: AssetTagNum5 partNumber: N/A Type: 20, Length: 19, Handle: 0x3e Type: 17, Length: 27, Handle: 0x3f MemoryDevice: deviceLocator: DIMM_F1 bankLocator: BANK5 memoryType: DDR3 memorySpeed: 1333MHz manufacturer: N/A serialNumber: N/A assetTag: AssetTagNum6 partNumber: N/A Type: 20, Length: 19, Handle: 0x40 Type: 32, Length: 20, Handle: 0x41 Type: 38, Length: 18, Handle: 0x42 Type: 131, Length: 6, Handle: 0x42 AppleProcessorType: ProcessorType: 0x501 Type: 132, Length: 6, Handle: 0x43 AppleProcessorBusSpeed: ProcessorBusSpeed (QPI): 5.9GT/s Type: 127, Length: 4, Handle: 0x44 Customizing SystemID with : 405edbc7-74fe-d511-aad0-e841494777ad ACPI table not found: DSDT.aml ACPI table not found: SSDT.aml FADT: Restart Fix applied! FADT: Restart Fix applied! Read HFS+ file: [hd(0,1)/Extra/Extensions/Disabler.kext/Contents/Info.plist] 1430 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/EvOreboot.kext/Contents/Info.plist] 1358 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/fakesmc.kext/Contents/Info.plist] 1486 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/IOAHCIBlockStorageInjector.kext/Contents/Info.plist] 1271 bytes. LoadDrivers: Loading from [/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext] Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext] 4096 bytes. Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext] 4592090 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/Disabler.kext/Contents/MacOS/Disabler] 4096 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/Disabler.kext/Contents/MacOS/Disabler] 28976 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/EvOreboot.kext/Contents/MacOS/EvOreboot] 4096 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/EvOreboot.kext/Contents/MacOS/EvOreboot] 33328 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/fakesmc.kext/Contents/MacOS/fakesmc] 4096 bytes. Read HFS+ file: [hd(0,1)/Extra/Extensions/fakesmc.kext/Contents/MacOS/fakesmc] 56208 bytes. Starting Darwin x86_64 Read HFS+ file: [hd(0,1)/Extra/Themes/Default/boot.png] 2888 bytes. Link to comment Share on other sites More sharing options...
Recommended Posts