Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About mastershredder

  • Rank
    InsanelyMac Protégé
  1. Lenovo Z560 installation

    Alright all you insanelymac nutters. First attempt at a tutorial. If any of you have Lenovo Z560 or similar then this guide should serve you well. This may be one of the most compatible laptops out there for installing OS X on. The only real dissapointment is the audio chip. unfortunately you have to use voodooHDA to enable full audio support but alas a custom DSDT for this laptop allows system profiler to show correct audio information while using VoodooHDA. I really should not do this guide like this but i really cba to show everyone how to do the various DSDT modifications. lets have a look at compatibility first. CPU: Intel core i3 350m works duh! with speedstep RAM: 2GB sodimm 1066 MHz works again duh! GPU: nVidia 310m works perfect via DSDT or chameleon Audio: Conexant CX20671/20585 works via voodooHDA system profiler show correct info via DSDT LAN: Realtek RTL8103E(L) works with driver from realtek Wifi: Atheros 9285 works via DSDT or legacy extension Trackpad: synaptics v7 two finger scrolling and other gestures work Battery: works via VoodooPower Card Reader: Realtek USB works via AnyCardReader.kext The installation was via [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] however i did not use [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] afterwards personally i like it even more vanilla than [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] however because i3 were not supported natively until 10.6.3 we are stuck unless you have a snow leopard disc that is using 10.6.3 or higher. i believe i had to use -x -v -f as options to get where i needed to install the OS. make sure ahci is enabled in bios or you will not get as far as installation. Once booted into operating system i updated to 10.6.6 combo and recieved a kernel panic at the end of instalation dont worry just reboot again with -x -f and run the installer again. once updated all you will have to do is install latest chameleon to EFI partition and stick the contents of my EFI partition on there and you will be up and running after a reboot:P the only thing that needs to be done manually is install voodooHDA 2.7.2 to /system/library/extensions you can also run voodoohda off the EFI partition but i decided not to as you need a few extra extensions to make it work so defeats the point really. then all you have to do is install the realtek driver for Ethernet. i have my installation as dual boot with windows 7 if you dont know how to do this then ask elsewhere it is fairly easy simple breakdown is boot snow leopard installation format disk as GUID 2 partitions one as Macintosh HD HFS+ filesystem and the other as windows set as fat32. continue install of snow leopard get to desktop reboot install windows 7 to windows fat32 partition. reboot back into snow leopard with boot cd and install latest chameleon to EFI partition then stick the included files on there and everything should be A OK. The only issues that are left with this laptop are system profiler show diagnostics as failed on memory dimm0. this is cosmetic as i bought 2 of these laptop at the same time and both showed it. i beleive this is to do with the bios programming it shows 4 dimm slots but labelled the following way: bank0 dimm0 bank1 dimm1 bank2 dimm1 bank3 dimm3 this is also shown in windows under everest or similar system utilities programs like cpu-z. hoping someone can shed some light on this strange issue. Another issue is occasionally the laptop will wake from sleep immediately after being put to sleep this is caused by the usb specifically the built in webcam however changing dsdt values to remove sleep capabilitys does not rectify the situation as a quick fix if it does wake immediately after sleep you have to press fn + Esc key this disables webcam and should then sleep properly. again any fixes for this would be a welcome addition. Do not use attached DSDT under the following circumstances: A) you are not using core i3 350m // i beleive this laptop can come with core i5 and i7 also you are using more than 2GB or ram i only have 1 stick of ram if you have 4GB the memory addresses in the attached DSDT will be different so be warned TBH it would be advisable to just alter your own DSDT and use diffmerge or something similar to compare your original DSDT to mine and make the necessary alterations. the attached extra folder though contains all of the themes smbios plist Boot.plist and extensions and mkext to make the system plug and play. and a tasty theme it is to boot:P smbios plist is set as macbookpro 6.1 as this is the closest match. Extra.zip RTGMac_v2.0.5_1.zip
  2. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    Hi all good news is chameleon auto generated p states and c states works bad news is they dont work as well Reason only educated guessing here but my q6600 is overclocked to 3GHz which would be the logical answer however thinking deeper it makes no sense as this is the G0 stepping and i can run at 3GHz with less voltage specified manually in bios than if i left it as auto in bios. The VID values i used in the DSDT orginally were made based upon the voltages i manually set in the bios. As these are lower than the default values one would expect temps to go slightly up using auto generated C states and P states in chameleon as this is basically extracting values from SSDT tables from bios and injecting them properly into the operating system. however what is occuring is random instability in the operating system using the new chameleon method so i have returned to just manually using the DSDT method as i have had the most stable system for nearly a year without incident and this was the only recent change i made. second topic i have just bought and started the long process of getting mac stable on a new laptop the lenovo Z560 great laptop very compatible except audio however as this is a new i3 it has way more information in the SSDT tables and i have yet to take the plunge and editing the dsdt to include the c state and p state information and i am currently just using chameleon to do the hard work for me. now for whatever reason once i am booted into the os and at desktop its very stable havent had a single crash but when booting its a different story i recieve mabey 1 out of 3 times when booting a random kernel panic relating to many things . originally i thought i was due to voodoohda as it was always present in the kernel backtrace of dependencies however this is not the case as i have these kernel panics occuring on completely unrelated things. this leads me to believe that again its the chameleon p state and c states at fault. that last statement is a bit harsh i shall try and explain further the SSDT and DSDT state there are 8 CPUS in this machine and this is seen when booting in verbose mode however CPUs 4 to 7 are disabled this obviously occurs as this machine can be configured with a dual core i3 /i5 which would be 4 cores 2 physical and 2 logical hyperthreading and a core i7 4 physical 4 logical now this is why the SSDT tables contain the extra info for these core that dont exist this may be partly responsible for the instablilty of the chameleon method as its scraping this info from the SSDTs and injecting it accordingly. WHat i would like to know is there any way to use voodoopstate or any other tool that will work with the new core i3 processors as the way i got this information for my q6600 does not work for this core i3 350m ie the tools dont support the new architecture. ps sorry for ther long winded rant
  3. How to boost the OS X boot process...

    ntsmkfob I have a X48 based board with Q6600 also overclocked to 3GHz i have looked at your DSDT and added what i changed to make the SpeedStep work on my board a few things to note are that i believe you should have smbios plist set to mac pro 3.1 otherwise the speedstep wont work properly also since we are running different intel based chipsets and also different q6600's the voltages that mine are set to may make yours unstable as i actually have set mine to custom undervolted voltages as my chip turned out to be a good-un so if any instability occurs just substitute the voltages and you should be set i believe the VID for the q6600 G0 revision is set at 1.2875 according to my motherboard however i can overclock it to 3GHz and undervolt it to 1.21675 and it is absolutely stable yours may not be also yours may be the B3 stepping of the Q6600 which ran hotter and probably takes more voltage to reach 3GHz however give this a go and report back there is no harm in trying as the voltages are lower than your board would set at stock to be safe i have the DSDT voltages set to 1.292 which should be very compatible with all but the worst batches of Q6600's DSDTQ66003GHZ.zip
  4. Im sorry to say pwned XFX 4870 1Gb default clocks 8.8 Seconds FTW. BTW GTS 250 in UK are selling for about 100 pounds ATM I bought a 4870 512 MB in november for 89 pounds at ebuyer I bought another 4870 1GB in February for 99.99 from http://www.videocardshop.co.uk/ Anyone who wants a good card for cheap i suggest from here as there was only a few left when i bought them and they wont last long at that price Peace.
  5. DSDT fixes for Gigabyte boards

    Blackosx i cannot seem to get the manual uuid working with this revision of the boot file it hides partition ala chameleon RC4 and also restart works without openhaltrestart or any restart kext with the flag provided but after removing platformuuid.kext and removing SMUUID key from smbios.plist the uuid still remains a random one and the flag <key>SystemID</key> <string>enter uuid</string> in com.apple.Boot.plist doesnt seem to change it to my prefered uuid which is 00000000-0000-1000-8000-MacAddress. Just thought id let you know everything else is working spot on.
  6. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    Hello All I cant figure out why i have AppleLPC loading with or without the injected device id in the DSDT i assume the orginal device ID must be in that extension because it loads clear as day with kextstat | grep AppleLCP also it shows in extensions in system profiler however the power saver option does not show restart after a power outage or whatever it is. speedstep clearly works andi cant understand why i dont have this option in system preferences can anyone help me out with it? attached is current DSDT.dsl dsdt.dsl.zip
  7. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    Did you get it working Smith?
  8. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    @ Smith your code was written quite differently to mine but basically you need to stick the values in here :- Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x65, //Your values were the same as mine so leave as what is here 0x03E9 // and here } }) } also for mine i had a Cst method for CPU1 as well which was actually longer than the one for cpu0 the edit i made looks like this :- Method (_CST, 0, NotSerialized) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, Zero, 0x03E9 // only change this value but yours was the same as mine so leave as 03E9 }, hope that gets yours working also dont forget you might need to remove the IRQ entries for the PIC and TMR devices as well
  9. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    i knew i had Cstates working early on becasue of the massively reduced temps with only pstates working i had temps around 35C with out pstates temps 40C and with pstates and cstates temps 28-30C although at the beginning cstates were causing strange issues like i said in the operating system which then lead to me investigating the values in the FACP table and adjusting what was in the CST method Also as pointed out by macuser2525 the voltage was falling to about 1.1 volts in voodoo monitor which is well below what is stated in my pstates the lowest is around 1.2. regarding the Phase leds they are pretty pointless but there are several different colour leds and they light up depending on CPU load but like i said i was getting harsh BSODS in windows because of it so i would recommend against using the Dynamic energy saver application.
  10. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    hi do you have your pstates currently working? Right try this one also is a copy of my current DSDT.dsl for reference in case this one still doesnt work for you. dsdt.aml.zip my_working_dsdt.dsl.zip
  11. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    BlackOSX what you need to do to get the phase leds working is to install Dynamic Energy Saver Advanced from gigabyte and install it in windows then it should work always even when in mac. i beleive theres a chip on the board thats reponsible for them working however this chip must remain dormant until this application enables it however i advise against installing it as when i had i started to get major BSODS in windows and no explaination as to what caused them suffice to say uninstalling the app corrected this. however again if you do go ahead and install it and start to recieve BSODS and want to uninstall it make sure you run the app first then disable the energy saver as once the app enables the chip it doesnt need the app to be initialized to make it work this explains why the lights work in OSX the wierd thing is i never had any instability in OSX from the lights being enabled it was jsut crazy harsh BSODS in windows which were unacceptable. SO to sum up if u install it and then you change your mind make sure you disable the energy saver with the app before uninstalling it or you will continue to recieve BSODS in windows it is obviously a poorly written application as i have read if you leave it on for an entire year it will only save you about $3 a year on your electric Can you send me your DSDT.dsl and your FACP table as it curently is and i will have a look also post values for your pstates if known and i will help to intergrate them refer to the initial post by FormerlyKnownAs to find out the values for your pstates. MacUser2525 i assume your main machine which needed no altering to the CST method used the same values in ur FACP table and this is why you have had no complication making this work. I am glad to hear that your cstates work on the second machine by replacing the values present in the FACP table. I am no expert in ACPI i have never even looked at the specification on it as i dont have the time or energy from reading this thread i can safely say Chief seems to know what he is doing regarding ACPI and FormelyKnownAs for writing the guide i tried SSDT tables about 6 months ago from the thread that was using the modified chameleon to use up to 30 ssdts and just plain gave up because the people in that thread at the time were way over my head i beleive the confusion in this thread is a combination of different hardware makers especially laptops the way different comapnys write these tables is causes a lot of confusion fortunatley the gigabyte tables are quite easy to understand compared with some manufacturers . for example i extracted all the tables from my brother laptop made by clevo and the way those tables were written was completely different.
  12. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    hey Shaj yes you have got it correct dont forget that you need to input that value a bit lower in the method as well when it looks like this :- One, Zero, 0x03E8 you would need to change it to this :- One, Zero, 0x0384 Also regarding if u need to enter the first value as 005A or 5A it wont matter as when compiled it will be optimized to 5A anyhow. Dont worry about your CST entrie saying 0 either in FACP mine did. i had the cstates working very early on but had strange behaviour when using the default values in the generic scope the combination of entering my values and removing the IRQ values sorted out the strange behaviour. FormerlyKnownAs this is a section from my FACP table and the values say C2 and C3 no mention of C1 so i assume those values correspond to C2 and C3 in the CST method [05Eh 094 1] GPE1 Base Offset : 00 [05Fh 095 1] _CST Support : 00 [060h 096 2] C2 Latency : 0065 [062h 098 2] C3 Latency : 03E9 [064h 100 2] CPU Cache Size : 0000 [066h 102 2] Cache Flush Stride : 0000 Am i right in reading that you do not have your Cstates working FormelyKnownAs ? thats a shame but i think you do not need to worry about not having a CST method in any of your tables as i do not either. it is possible that you mite get these cstates working and not have any reduction in temps i saw a reduction of about 4 C from my dsdt with cstates compared with hte one with just pstates working however i am using water cooling it is possible that your HSF just cant reduce the temps for your processor any further if you have the error messages removed from the kernel.log and are not seeing a reduction in temps that doesnt mean that they are not working.
  13. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    I have just really started to scratch the surface of the importance of these tables and the values they contain tbh i really didnt know what these valeus were only they were very similar to the one listed in my FACP table and they showed they were the C2 and C3 latencies whether this is actually the case doesnt really matter to me as i have it working now by using the values used from my extracted FACP table as before using the values that were in the generic scope was casuing very strange behaviour in Mac
  14. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    Thanks Shaj? I hope this was just a typo
  15. DSDT - Vanilla Speedstep - Generic Scope (_PR)

    hey Shaj lf you go through the last 5 pages or so of this thread i have posted various messages about the status of my speedstepping it took many hours of fiddling about to get just a couple of pstates working correctly however that was all worth it as i now have all 4 pstates for my cpu even windows doesnt use 4. My original DSDT which was extracted using everest ultimate in windows shows only 2 pstates for my cpu one for the highest multiplier and one for the lowest now as far as the cst method goes i was getting very strange results when those methods were included in the dsdt when loading on the apple screen at boot the little grey wheel that spins was lagging and then the desktop felt a little sluggish compared to when they werent in the dsdt. I figured something must be wrong. The CST tables were working as i had an even further reduction in temps and the errors had gone from kernel.log but itunes was laso lagging when playing mp3's which was obviously unacceptable. I did the method mentioned by FormelyKnownAs which is on page 16 which was to delete the IRQ references in the following Devices in DSDT (PIC) and (TMR) this howeveer resulted in even more strange behaviour starting with kernel panic on first boot then susquent boots did strange things like it never got to the desktop but when the blue screen shows it looked as if it was stuck in a loop of continually reloading that section. Again this was unnaceptable so i tried one more time taking specific care to look at my FACP dump from everest is shows the latency timings for the C States one of which was ever so slightlt different from the one written in the generic scope. After doing this and the included IRQ method from above it bootedfine no wierd lagg problem no stability problem no CST errors in kernel.log and temps have had the extra 5 C shaved off compared with just using pStates. Also my motherboard GA-X48-DS4 has never been able to sleep regardless of operating system i have spoken to various gigabyte techs who were unable to resolve and suggested an RMA which i didnt want to do so i lived with it but since doing this DSDT modification sleep works 100% on mac now which is great. Also geekbench now shows 6400 on mac and 5300 on windows 7 which i thought was lol. attached is my current DSDT which for me has everything working. Also a nice pic to show Temps as of this morning its slightly colder than it shud be because im freezing my ass off this morning they are usually about 28C or so which is impressive as before pstates were included they were about 40C with pstates they were about 33 -35 C and now with Cstates 28-30C. Now finally all i have to tackle in my system is the dreaded Alc889a audio which i have working but a few irratating things like front panel doesnt work and stupid sound assertion errors in kernel.log then thats it for me no more errors in my log when booting. One final note for anyone who is still struggling make sure your smbios.plist is using macpro 3.1 i found out last night if i removed all entries relating to model identier board etc system profiler shows as mac pro 2.1 which i though was great because app like geekbench and ibench show up as macpro however pstates then do not work this is dues the the plist entries in the ACPI_SMC_PlatformPlugin.kext if you look at the plists in there the one for macpro 2.1 has a lot less power saving techniques and this was causing all pstates to fail. this is unfortunate as when setting model to macpro 3.1 in smbios.plist ibench and geekbench now show hackintosh as model which is a shame. Attached also is my smbios.plist just remeber to change any settings regarding FSB and memory to your own or it will change your current configuration in about this mac. DSDT.dsl.zip smbios.plist.zip