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.

poof86

Members
  • Content count

    7
  • Joined

  • Last visited

About poof86

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  1. Ozmosis

    Hi all I'm using Ozmosis for a little while now and experiencing random reboots. Without kernel panic reports to locate the cause I'm not sure what the problem could be. It might be because I'm using a newer version of HWSensors/FakeSMC, or that my Nvidia driver that I can't use with my iMac15,1 setup is acting up, or that with Ozmosis my X.M.P. memory profile is not detected correctly. My memory frequency should be at 1333 MHz but it's showing 1600 MHz. Is there a DSDT patch I need to apply for this to work correctly? In Clover I could set which profile I'm using in the configurator. Any help would be appreciated, Thanks!
  2. This almost worked for me, Was able to start MemTest86 with the Clover bootloader, but my screen turned black when I started te test. I don't have this problem when I use a bootable USB. Does it have something to do with environment variables that Clover sets to boot things? Can I disable this for certain boot entries? A good partition tool would be a nice application to add to the list
  3. Working X-fi Titanium

    Because it's probably best to update the latest VoodooHDA with the pin settings in the plist for the best result.
  4. Working X-fi Titanium

    I'm back! So here's what I did to get my Creative X-fi Titanium Pci-e working in Yosemite Step 1 Installation I installed VoodooHDA (2.8.7), this got my rear green audio working without any editing the VoodooHDA.kext Goto S/L/E and drag a copy of the VoodooHDA.kext to the desktop for editing. Step 2 Setting Device id Open the contents of the VoodooHDA.kext and open the Info.plist inside. Replace the key IOPCIClassMatch by IOPCIPrimaryMatch and put the PNPID of your audio card in string (link) PNPID = DeviceID+VendorID (PCIID is VenderID+DeviceID, don't use this) Instead of getting this info from the getDump (get it in VoodooHDA official thread, we will need it later) I got it from the Device Manager in Windows where it was slightly different. You can find the Device id in Windows Device Manager (Control Panel > System > Hardware > Device Manager) Right Click the device > Properties > Details > Device instance path. It will be in the form "PCI\VEN_[here is the Vendor ID]&DEV_[here is the Device ID]&..." For my X-fi Titanium the value was : 0x000b1102 instead of 0x000d1102 Step 3 Patching nodes PookyMacMan posted a very nice guide on how to patch your nodes Part1 Part2 Using the voodooHDA getDump in the terminal you'll get a nice view of all the nodes You could also get all the verbs from the Windows Register and take the long route to getting your nodes (info), then parsing them with an PinConfigurator.app (info). But I noticed the getDump was actually the same... Mine looked like this: nid 13 0x01014010 as 1 seq 0 Line-out Jack 1/8 Rear External Green misc 0 nid 14 0x01016011 as 1 seq 1 Line-out Jack 1/8 Rear External Orange misc 0 nid 15 0x01011012 as 1 seq 2 Line-out Jack 1/8 Rear External Black misc 0 nid 16 0x01012014 as 1 seq 4 Line-out Jack 1/8 Rear External Grey misc 0 nid 17 0x0221401f as 1 seq 15 Headphones Jack 1/8 Front External Green misc 0 nid 18 0x01452130 as 3 seq 0 SPDIF-out Jack Optic Rear External Grey misc 0 NoPresenceDetect nid 19 0x01813040 as 4 seq 0 Line-in Jack 1/8 Rear External Blue misc 0 nid 20 0x02a19050 as 5 seq 0 Microphone Jack 1/8 Front External Pink misc 0 nid 21 0x41811060 as 6 seq 0 Line-in None 1/8 Rear External Black misc 0 nid 22 0x41911070 as 7 seq 0 AUX None 1/8 Rear External Black misc 0 nid 23 0x01c51180 as 8 seq 0 SPDIF-in Jack Optic Rear External Black misc 0 NoPresenceDetect To get your other Line-out to show up you will have to give the nodes a unique Default Association 0x01014010. Because Apple doesn't use multichannel analog output, the Line-out nodes can't be grouped (associated). And the Sequence 0x01016011 of the nodes need to be set to zero. To patch a node you will need to add an entry to the key NodesToPatch <key>NodesToPatch</key> <array> <dict> <key>Codec</key> <integer>1</integer> <key>Config</key> <string>0x01014010</string> <key>Node</key> <integer>13</integer> </dict> <dict> <key>Codec</key> <integer>1</integer> <key>Config</key> <string>0x01016020</string> <key>Node</key> <integer>14</integer> </dict> ... </array> </key> The Codec Key refers to the value codec id of your sound card which is shown in the dump here: Probing codec #1... HDA Codec #1: Creative SB0880 X-Fi HDA Codec ID: 0x1102000d Vendor: 0x1102 Device: 0x000d ... and the Node key refers to the node id you want to patch (nid) Step 4 Kext installation Use something like Kext Wizard to install the edited kext on your desktop. (be sure to check the option to backup your old kext) and reboot! Step 5 Creating a Surround aggregated device To regroup all the Line-out nodes you just unassociated you will have to create an aggregated device in Audio Midi Setup and set every node to the correct speaker. I followed this guide (link) but all I got was terrible crackling in my center speaker. After removing the aggregated device and reselecting my green rear output, all my speakers started playing nicely with my music. I'm afraid it's not possible to create a working aggregated device for Creative X-fi sound cards, and I think that the surround sound I'm experiencing is from the CMSS-3D settings I use in Windows. Have a try with my Info.plist and tell me how it's working for you. Are you able to get surround working properly? Greets! Info.plist.zip PS: I forget to say that for some reason my left/right channels are flipped So I had to switch the channels in the Audio Midi Setup for every Line-out. And for surround to pick up you will have to reselect Green Rear Sound output in System Preferences.
  5. Working X-fi Titanium

    Hi all, I've had allot of problems trying to get my X-fi Titanium PCI-e sound card working with Leopard and Lion. Finally It seems I found the correct plist settings for everything to work properly. I'm using the latest VoodooHDA from here (v.2.7.3) Installed the driver and moved the kext from the Extensions directory to the contents of the voodooHDA loader which can be found here Don't forget to replace the Info.plist file inside the kext contents for the correct pin configuration etc. I removed the loader from my login/startup items, but it will probably work without having to start the loader manually. You can still use the VoodooHDA preference panel to switch to SSE2 after the voodoohdaloader has finished. This helps when you have to play multiple sound sources and you hear the sound crackle and pop To get surround working you need to create an Aggregated Device. Guide can be found here On every boot switch between the Aggregated Device and back to Line-out (Green Rear) while you're playing something (yes very strange) It's a kind of a hassle but you'll get great sound every time And probably important to mention, I disabled my onboard sound card in the BIOS and checked if the HDEF device was missing in my DSDT Hope you can finally enjoy using your X-fi Titanium on the mac just like me!
  6. Fix: VoodooHDA KP (10.6.8 + 10.7.x)

    Seems to be working with my custom voodooHDA.kext and X-fi Titanium soundcard! I normally have to cross my fingers to see if I don't get a kernel panic or even get sound working (sometimes have to boot several times to get it to work). after I patched the voodooLoader I get this terminal vd_startup windows popping up. This is part of the loader right? Is there a way to hide this at startup? Thank you so much! -- Edit -- I don't have KP's anymore but using the VoodooLoader still gives me a random chance of VoodooHDA loading properly. Sometimes everything loads quickly and works perfectly, other times I get the loading spinning wheel when I move my mouse over the volume menubar icon until it turns grey. Any Idea what could be the cause of this?
  7. Ralink menubar icon

    I didn't like the new ralink menu bar icon for my RT2870 USB Wireless Driver... so I replaced it with something else Replace WirelessUtility>Contents>Resources>ralink2.gif With the new icon. If you can't be sure to close the program with the ActivityMonitor first and after you replaced the icon start the program up again to see the change. Greets, Niels
×