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 Fatshenanigans

  • Rank
    InsanelyMac Protégé
  • Birthday 10/22/1985

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Over the river and thru the woods
  • Interests
    I love anything where I can push all of the buttons to see what it does! My time is spent playing first person shooters (Fallout 3, Halo, and Resident Evil series), modeling, photography, guns, gadgets, blowing stuff up, and anything geek...with finesse and style of course! :)<br /><br />Why my name? Well since I'm typical in that I obsess about being fat is part of it. The second part is due to being asked by my father, "I don't know what kind of shenanigans you are up to now but I don't think I want to know so don't let me find out" LOL if he only knew... :)
  1. Intel DP55SP or DP55KG ... good for SL ?

    Nothing wrong with that choice at all. But I've never had problems with the TI chips and I do consulting work for a pro audio user who uses Firestation and Mark of the Unicorn who never had a problem also. Plus a friend of mine on this forum uses MOTU also with ASUS that (Motu uses) TI and VIA equally well. The kexts for firewire support nearly every imaginable chip and are not like LAN that only support specific chips. When firewire doesn't work it's usually because there is a conflict somewhere in the DSDT or with another kext. So no matter what board you go with, you'll need to look out for pitfalls and gotchas. About the LAN, it's supported natively but there are also at least two kexts that support it also for E/E. This answer was more for people who have the Intel board since they are very good questions EDIT: I just realized that I wrote TIA when I meant to say TI to answer the other question. Bluetooth is supported in the same way as firewire as an array. I've yet to see a bluetooth in a P55 that wasn't plug n play - at least so far anyway. But I cannot find anything about the specific supplier of bluetooth devices.
  2. DFI's Shiny New MI P55 T36 MINI-ITX (!) Board

    I just installed to an EVGA P55 board and I went through my own procedure and I realized that I made a mistake in how I wrote step 6 part 1 It should be: Select option 1 for "System partition" (Extra)! Oh dammit. Sorry about that You may need to enter 17 to change the install target if your drive is not showing up. Now that I think about it I think it can work either way but it depends on whether or not the script sees the external USB when you run the script. I think my version, as written, will work but if you do another installation to the boot USB it may not immediately identify the drive as available. It can be confusing. I'm going to revise the above but I hope it worked!
  3. They are very solid and the DSDT is very clean code...nearly identical to the real iMac11,1. Go to the 10.6 installation forum and look at the P55 Intel post and the DFI lanparty P55 post. The DSDT I edited in the Intel thread will work on your mobo (since all of the DSDT are the same for that Intel brand regardless of the P55 model) and the install technique I outlined for the Lanparty will work on your system also. You can also use the files I attached since they are standard for all P55 systems. Post on the Intel thread if you need anymore help. Good luck!
  4. Intel DP55SP or DP55KG ... good for SL ?

    There are guides here but they are incomplete as far as I've seen. There's plenty of "do this" or "do that" but not nearly enough explanation. I'm grateful that theres SOMETHING but what exists sometimes hurts more than it helps since most people have a hard enough time with the DSDT. If they think that's hard to understand I'm sure 99.9% of people out there would think this is much much worse. At first I almost gave up when I first saw the code but after awhile I started to see the pattern. Now I basically understand it but obviously I need to test my theories on rare boards like yours to see if what I've interpolated matches what the guides are trying to say but don't actually say it. I'm actually doing quite a bit of detective work to reverse engineer what they did. Master Chief started a really good guide but he never finished it and I don't think he intends to do so even though he knows what to do since his P5K Pro has audio working with LegacyHDA. I guess he has his reasons why not. But with yours I'm close since your pin configuration is very similar to the other legacyHDA that I found. If you test these and record what was not working, what was, and what showed up in your system profiler, we can solve this and you will learn exactly what the guides are not able to teach since while they are broad, your mobo and pins are specific. In other words, the best teacher is experience I'm fairly certain that we can get most of your Jacks working. All of your ports are "alive" but they are just confused. It will just take a bit of trial and error.
  5. DFI's Shiny New MI P55 T36 MINI-ITX (!) Board

    Ok let's do that then: What you'll need: The files I attached here, Digital Dreamers install script, a 2 gig USB drive or smaller, an 8 gig USB drive or larger, your retail Snow Leopard disk, a Mac mach_kernel 10.6.2 (I'm not sure where to download this but your current Mac will have one in the root directory when you use the "show/hide" files tool), the Show/Hide files tool, and kext utility. Part I: Boot drive prep - External USB Step 1: Download Digital Dreamers script here: http://www.insanelymac.com/forum/index.php?showtopic=185097 Step 2: Get a USB that can be formatted as a GUID. Some will only allow you to format them as FAT32 but they can still be used in Macs to transfer files. Step 3: Format your USB drive and call it something easy like "Boot" or "George" or whatever is easiest Don't call it EFI since you might overwrite Mac EFI since it has a hidden EFI partition and the script will mount the hidden partition if you declare your target drive as "EFI". I learned this the hard way...twice. Step 4: Go into the pack that I included here and swap out the bootloaders folder inside of Digital Dreamers ~Extras folder with the one I included since it has 1156 support Step 5: Swap out the SMbios.plist and boot.plist in his plists folder with the ones I included. Step 6: Now click the run patch installer script to run the script and it will ask you which type of install to run. Select the EFI option or Option 2 and you'll choose your GUID formatted USB as your target drive. EDIT 3/22/2010: The prepared USB may not always show up as available to install! Should this be the case, choose 17 in the menu to "change install target" and select OPTION 1 or "Extra" to install to the prepared drive. After this has completed there will be a "stored kexts" folder inside the "Extra" folder. It's not critically important to delete it, but it's a good idea to do so as it might be confusing later. Step 7: You then be asked which bootloader to install and you'll select the Chameleon RC4 option. This will write the necessary bootloader files to your drive just like if it was to be done manually but for me this is a much better method since it's airhead-proof (like I tend to be ) Step 8: Select the option to make your USB the "active" or target drive. Step 9: Exit the install script by using the "Exit" (I think it's #20 on the list). Step 10: Open the USB drive and go into the Extra folder. Copy my Extensions folder, the two plist files, the DSDT, and the Extensions.mkext. For good measure, drag and drop the Extensions folder over kext utility. So you should see your two plists, the Extensions folder, your DSDT, and the extensions.mkext. When you enter the USB drive you probably won't see the boot file since it should be hidden. You'll likely only see the Extra file. Step 11: Eject your boot USB and put it aside for later. Part II: Retail disk restored to 8 gig USB with 10.6.2 kernel. 1) Get your retail disk and insert it in your Superdrive. You'll be restoring (not installing) your Snow Leopard disk to a separate USB. You'll need at least 8 gigs of space for this. Be sure to restore it at the slowest speed of 1X write. You can also do this with Toast Titanium. 2) Now you'll need to "Show Hidden Files" using either the Show/Hide tool or any other methods you might know of with the SL USB drive (not the boot drive that you created earlier) still attached and active on your desktop. You'll now delete the 10.6.0 mach_kernel in the USB and replace it with the 10.6.2 kernel. 3) Hide your files again using the Show/Hide tool and you are done with preparation. Part III: Installation to your main hard drive 1) Boot into your bios with only your boot USB connected. 2) Configure your bios to see only the USB as your sole boot drive and also the first hard drive on your list of active drives. My memory is blanking but you should be able to disable your installation drive and show only your USB drive active in the boot drives subdirectory. You should see your other hard drive in the AHCI configuration portion. Since we aren't using it, unplug the DVD burner from both the power supply and the SATA or IDE port. Be sure your target installation drive is plugged into the first SATA port. It's either Port 0 or Port 1. No other drives should be plugged in for now. 3) Plug in your 8 gig USB and then Save and Exit. 4) The system will reboot and you should now see your USB and the Snow Leopard Install disk in the menu. Scroll down to Verbose and then begin the boot process. Keep a note of any error messages that you may encounter along the way. If all goes well you should be able to install with zero installation errors. Keep an eye on the installation log while installing. You should now be in Snow Leopard. Once you inspect your system initially, eject your 8 gig drive, reboot, go into bios and enable your newly installed drive as the #2 hard drive behind the USB that remains first.. But the USB should be listed as the only boot drive. This is important since the installation drive doesn't (or shouldn't) have any boot files and you wouldn't want to boot from it anyway. Now you can enable your LAN and Audio. If LAN works natively cool but if not the kext for that is available. Audio will be the next task and I'll help you with that once you get the system up and running. EDIT: The smbios and boot plists are installed where they are supposed to be by the script - see above that you don't need to manually move those two files. Also once you've booted to desktop, immediately install a 10.6.2 combo update and reboot normally as outlined earlier. Now you can proceed to enabling everything. EDIT 2: I revised step 6 should there be problems identifying the external USB. Fats_DFILanPartyPack.zip
  6. DFI's Shiny New MI P55 T36 MINI-ITX (!) Board

    For me, Boot CD's are much more difficult to handle. I only was able to get one to work once about 6 months ago but I reinstalled as soon as I mastered the USB method. If you just want it to get initially up and running, by all means swap out the DSDT as you said especially if you don't have a Mac or access to one. But if you do let me know and I can outline a much better and cleaner method to let you do a vanilla installation with a USB stick or we can at least create one later and move all of your boot files and extra folder to an external USB. When you modify the Boot CD, make a second copy with the following kexts, assuming he's using the latest bootloaders that don't require a restart kext: fakesmc2.5.kext IOACHIblockstorage nullcpupowermanagement sleepenabler Three of these you can get from netkas.org but these are all you should use when you first get started. You can drop the nullcpu and sleepenabler after you install to 10.6.2 and then later install your audio and LAN kexts. It's better to leave them out at first so there's nothing that can conflict or hang. Be sure to only have one hard drive connected. Make sure you disconnect your LAN cable, audio plugs, and everything else other than your USB mouse and USB keyboard. Set your bios to AHCI for your drives and disable all of your onboard devices like ethernet, eSATA, and HD audio in bios. Oh yea, before I forget, most importantly, be sure that the only boot flag that you have is arch=i386 to ensure that you boot into 32 bit mode since 64 bit causes most of the problems and issues that people are having since we still run dozens of 32 bit apps that are very unstable with the 64 bit kernel. All 64 bit apps can run on the 32 bit kernel with full power. If those guys tell you differently, I'll post my Geekbench scores of 12,000+, xbench of 320, and Cinebench scores of 6+ for the CPU and 32+ for my lowly 8800 GT video card Actually you can see part of those scores here: http://www.insanelymac.com/forum/index.php...155&st=1520 Later you'll be using the 885/889a audio codec and the IOnetworking family kext if the vanilla IOnetworking doesn't find your LAN.
  7. Intel DP55SP or DP55KG ... good for SL ?

    Round 1: With no existing or complete guides out there, reinventing the wheel sure stinks sometimes. But I gotta do what I gotta do. So let's see what happens: First you'll need to delete voodoo from S/L/E. When you reboot type in -f for caches to be ignored/rebuilt. On this first boot use the DSDT I included and see if anything shows up in system profiler or if audio even works (probably not). Then it will be trial and error each time, installing to your E/E folder, using kext utility to rebuild extensions and then reboot. If it works partially, make a note of good and not so good. I only actually expect some sort of results on 2 of the 6 but I'm not sure which two remembering to swap out the kexts from E/E and rebuilt the extensions.mkext cache each time. If one or more works, try manual and auto sleep and see if sound comes back when it wakes up. I know how to fix that should it happen but if it ain't broke... Before I forget, boot with the arch=i386 FatShenanigans_mic_check_intel_p55_beta.zip
  8. Intel DP55SP or DP55KG ... good for SL ?

    So far so good! Ok now I'll work on the graph and see if we can get this sound working To respond to your earlier question, you'd be able to get rid of voodoo and therefore all of the problems it brings like broken sound when your computer wakes up or no sleep at all. This requires the LegacyHDA kexts in the /E/E instead of voodoo in S/L/E. The DSDT binds to it in E/E. This is usually fairly simple for an 889 codec. For my ASUS I nearly melted my brain the other day figuring it out and it's still a beta
  9. Try the Microsoft drivers that came with your mouse for OSX and then see what happens in 32 bit. On the website it's listed to support 10.5 but it installs just fine with 10.6.2. It will give you a Microsoft Mouse icon in your apps folder where you can adjust the settings and set options on the mouse.
  10. I use the DSDT by Bchemist in my P7P55D-E with a few modifications he suggested since my USB and Event Controller are a little different than your motherboard but everything else is the same once the code is optimized. I'm replying here though because I have a Microsoft mouse like the Arc and after installing the drivers on the disk for Mac it didn't update so I guess those are the current drivers. Here's my Extensions output in Profiler: Version: 6.1 Last Modified: 6/15/06 6:00 PM Kind: Universal Architectures: i386, ppc 64-Bit (Intel): No Location: /System/Library/Extensions/MicrosoftMouse.kext Kext Version: 6.1 Load Address: 0x48991000 Valid: Yes Authentic: Yes Dependencies: Satisfied Did you check to see if your drivers are 32 bit or 64 bit? Maybe booting in 64 bit is causing the problem? I was already scolded by Bchemist through PM because I was stubborn to make my system default to 32 bit hehe But it did solve the last bugs I had when I finally booted with the arch=i386 as the default. Hope this helps!
  11. thinking before buy

    I have the HP9000 series from 2007 and it's super easy compared to other laptops I've installed to plus it is almost a carbon copy of the MacBook Pro. So if that's your first choice go with it The second one has the i5M and that's not yet supported by OSX. It might be supported in the future though. So if you want a low stress level avoid this one for now.
  12. Intel DP55SP or DP55KG ... good for SL ?

    Time to do a codec dump. If you want to do the pin configurations yourself that's fine but if you want I can do it pretty quickly since I've done it already. You need the ubuntu Live CD but you can run from the CD so you won't change your existing install. Post the text file of the dump here. But what I'd also need you to do is the map portion. I've found dozens of pre-made LegacyHDA kexts for codec 889 but doing a codec dump and a map will help avoid endless trial and error. I'm supposed to set up this board for somebody next week so if I can work with you guys to figure this out earlier my client will think I'm a wizard...or witch...or whatever hahaha Here's what to do next (this is taken a guide by The King): Chapter I: Collecting codec info/dumps/etc. There are several way to get codec info, my advice use them all. From Linux: Boot any live linux distro(try to use latest avail, and also if possible use latest ALSA drivers) Once you are in GUI start terminal and run this command: cat /proc/asound/card0/codec#1 > ~/Desktop/codec_dump.txt This will yield a file CodecDump.zip containing the codec dumps from all your sound cards. Save it in a safe place, mail it etc. On OS X we must use the dump to get a graphical interface, convert it to decimal(I will explain later why), get the codec verbs from it and fix them for OS X. a. Creating Codec Graph: - Download and install GRAPHVIZ for Mac OS X - Download CodecGraph, unpack it to descktop, copy on it the linux codec_dump.txt then start terminal and type: Edit: QUOTE cd ~/Desktop/codecgraph - then type: ./codecgraph codec_dump.txt *replace "codec_dump.txt" with your codec name file(if you gave it a specific name) -Now you should have in the codecgraph folder a file codec_dump.txt.svg If u like to see it open it with Safari or Firefox Don't worry about his part - This part is my job
  13. If you want to leave HDEF out give the EFI method a try. You'll need to download Mozilla browser since Safari still doesn't support the map you'll need to create.
  14. Some very Technical questions...

    Read this primer - it's everything I ever wanted to put in writing for my own reference and more http://www.insanelymac.com/forum/index.php?showtopic=211705 Plus it's uses a laptop as an example and laptops have painfully difficult DSDT files if you compare to desktop boards so this will help you relate more to what is being written. The first step would be to post your DSDT here. But it does take a long time for most people to learn who take the time and it's usually trial and error to see what happens when you make changes. The best advice I can give is do one change at a time, reboot, and see what happens. If everything is ok, do another fix and see if it breaks anything or conflicts. It can be tempting to do 20 hacks at once but then when something goes wrong, you are facing impossible odds at finding exactly where you went wrong. I've done that plenty of times myself because I get overly excited sometimes
  15. Intel DP55SP or DP55KG ... good for SL ?

    You'll have to experiment with different 889 Legacy HDA's if you want the optical out. For your specific motherboard we'd need to do a codec dump to create a set of pins if that doesn't work. If Voodoo works and you can still autosleep and have no other problems, by all means keep using it But what I've noticed in my case is that the audio quality is usually bad, especially after it wakes from sleep and I have to reboot when using voodoo. In other cases if I used voodoo I'd lose internet or something else.