428 replies to this topic

[Vinnymac]

I checked, and my DSDT is definitely being loaded. Why would LegacyHDA not work altogether? Where as ALC885 works fine. In abhilash's case both at least work in some way. LegacyHDA doesn't throw up any errors for me, but output/input are blank for me.

I think if my DSDT is being loaded it is less likely the problem, since our mobos are similar and I don't have any weird hardware. Regular intel cpu, 2GB of ram, I'm not throwing a wrench in the mix. So what could it be?

[verdant]

I checked, and my DSDT is definitely being loaded. Why would LegacyHDA not work altogether? Where as ALC885 works fine. In abhilash's case both at least work in some way. LegacyHDA doesn't throw up any errors for me, but output/input are blank for me.

I think if my DSDT is being loaded it is less likely the problem, since our mobos are similar and I don't have any weird hardware. Regular intel cpu, 2GB of ram, I'm not throwing a wrench in the mix. So what could it be?

I am presuming that you have reset ownership and permissions for the kexts in /S/L/E/ including the AppleHDA.kext and for the kexts in /E/E/ including the LegacyHDA.kext for good measure even though Chameleon does not bother with kext ownership and permissions......I would then again repair permissions of the system folders and files using Disk Utility......

Note that abhilash reported that "no they are not same... LegacyHDA has BuiltinHDA addition and configdata is different", so the answer would seem to be the differences between the LegacyHDA and ALC885 kexts and the differences between the implementation of the ALC885 codec by your nVidia 680i LT SLI MOBO and abhilash's XFX nForce 680i LT SLI, given that you both use the same DSDT Device (HDEF) sections and the same AppleHDA.kext.......

I suggest that you try the general DSDT Device (HDEF) section by THE KiNG (see post #5), which he says should work with all codecs:

Method (_DSM, 4, NotSerialized)
{
Store (Package (0x04)
{
"layout-id",
Buffer (0x04)
{
0x0C, 0x00, 0x00, 0x00
},

"PinConfigurations",
Buffer (Zero) {}

}, Local0)
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}
}

with both the LegacyHDA and ALC885 kexts but same AppleHDA.kext.......

[Vinnymac]

Okay, so you guys are gonna laugh but I figured it out.

So I have fixed permissions before, and reset em on the specific files, but it never worked. And I did not know why. So I thought well why not go back and reread what they wrote. Nobody ever told me WHERE to put the LegacyHDA.kext file. So then I see verdant here say /E/E/ and I am like, hrmm why not test it out. I have never dealt with LegacyHDA before, so how would I know, I just thought it belonged with AppleHDA. Anyways, it worked!, after placing LegacyHDA in /E/E all of my problems are fixed. LegacyHDA works with both back and front panels, and is completely functional! Verdant you can now add abhilash's information to your guide, thank you abhilash, and I hope when you write the guide you mention specifically where to place the files because my stupid mistakes could as well be anothers

The only problems I can see in my kernel.log are these three:
1.

Kext com.apple.driver.AppleHDAController might not load - kextd is currently unavailable.
Sound assertion "0 == pciVendorProductID" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDAController/AppleHDAController.cpp" at line 2682 goto Exit

2.

kxld[com.yourcompany.driver.AppleACPIPS2Nub]: The Mach-O file is malformed: Invalid magic number: 0xfeedfacf.
 Can't load kext com.yourcompany.driver.AppleACPIPS2Nub - link failed.
 Failed to load executable for kext com.yourcompany.driver.AppleACPIPS2Nub.
 Kext com.yourcompany.driver.AppleACPIPS2Nub failed to load (0xdc008016).
 Failed to load kext com.yourcompany.driver.AppleACPIPS2Nub (error 0xdc008016).
 Couldn't alloc class "AppleACPIPS2Nub"

3.

0		0 AppleUSBCDC: start - initDevice failed
 USBMSC Identifier (non-unique): 0c1401d76b1535 0x1b1c 0xab1 0x100
0		0 AppleUSBCDC: start - initDevice failed

[verdant]

Okay, so you guys are gonna laugh but I figured it out.

So I have fixed permissions before, and reset em on the specific files, but it never worked. And I did not know why. So I thought well why not go back and reread what they wrote. Nobody ever told me WHERE to put the LegacyHDA.kext file. So then I see verdant here say /E/E/ and I am like, hrmm why not test it out. I have never dealt with LegacyHDA before, so how would I know, I just thought it belonged with AppleHDA. Anyways, it worked!, after placing LegacyHDA in /E/E all of my problems are fixed. LegacyHDA works with both back and front panels, and is completely functional! Verdant you can now add abhilash's information to your guide, thank you abhilash, and I hope when you write the guide you mention specifically where to place the files because my stupid mistakes could as well be anothers

The only problems I can see in my kernel.log are these three:
1.

Kext com.apple.driver.AppleHDAController might not load - kextd is currently unavailable.
 Sound assertion "0 == pciVendorProductID" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDAController/AppleHDAController.cpp" at line 2682 goto Exit

2.

kxld[com.yourcompany.driver.AppleACPIPS2Nub]: The Mach-O file is malformed: Invalid magic number: 0xfeedfacf.
  Can't load kext com.yourcompany.driver.AppleACPIPS2Nub - link failed.
  Failed to load executable for kext com.yourcompany.driver.AppleACPIPS2Nub.
  Kext com.yourcompany.driver.AppleACPIPS2Nub failed to load (0xdc008016).
  Failed to load kext com.yourcompany.driver.AppleACPIPS2Nub (error 0xdc008016).
  Couldn't alloc class "AppleACPIPS2Nub"

3.

0		0 AppleUSBCDC: start - initDevice failed
  USBMSC Identifier (non-unique): 0c1401d76b1535 0x1b1c 0xab1 0x100
 0		0 AppleUSBCDC: start - initDevice failed

Thanks for your honesty Vinnymac.......every step taken is something new learned hopefully.......

Glad the "problem" is now sorted.....and I will make sure that I put in the Audio section ALC885 codec guide explicitly where each kext should go.......

Problem 3) is seen by just about everyone I think......

Problem 2) is a PS/2 kext..... use a USB keyboard and USB mouse.....no need for PS/2 kexts......

Problem 1) over to iLeopod on this one.....

[iLeopod]

Can be solved by adding subsystem ids to HDEF Device in DSDT:
like:

"subsystem-id", 
Buffer (0x04)
{
0x79, 0xCB, 0x00, 0x00
}, 

"subsystem-vendor-id", 
Buffer (0x04)
{
0xDE, 0x10, 0x00, 0x00
},

or

"subsystem-id",							 
Buffer (0x04)							
{							   
 0xA0, 0x00, 0x00, 0x00						   
 }, 

"subsystem-vendor-id",							 
Buffer (0x04)							
{								
0x6B, 0x10, 0x00, 0x00							
},

would prefer the first entry.
Be carful with:

Store (Package (0x08)

just remove the numbers and let the compiler care about this.
like this:

Store (Package ()

[abhilash]

@Vinnymac

I dont know what to say.. Anyways congratulations for getting sound with LegacyHDA kext..

@Verdant, @iLeopod, @Vinnymac

sound not working with AppleHDA 10.6.7 (1.9.9f12) + LegacyHDA or ALC885. Though, upto 10.6.7 AppleHDA is same.

@iLeopod

Do you have any idea of patching AppleHDA >2.0 to work with nforce boards.
As per VCH888 post ALC889A/885 doesnt require to be patched only add Platform.xml and Layout885.xml with ALC885_889a.kext (replacing LegacyHDA/ALC885). But, that method is not working on nforce boards.

[Kilopopo]

I have this problem for quite a while

After the console prints the Nforce HDD drivers and stuff i get stuck on USBMSC Identifier non-unique it just stops there and then nothing happens i waited for 20 minutes but still nothing

can you guys please help me out?

[silentsaint]

Verdant, I've decided to switch to a USB interface for audio. Seems slightly more stable than firewire, but i'm still getting random freezes. This baffles me, because I use USB keyboard, mouse, and flash drives without any issue at all. The apogee lion driver is still a beta.

To recap, the problem with a firewire interface is that if it's connected at bootup, I get the spinning ball before the desktop loads. If connected after, it will freeze at a random time with the spinning ball.
With USB interface, I can boot into lion just fine. Nothing freezes, everything is great. But at a random time, the OS will freeze with the spinning ball. This only happens when the audio interface is connected. Product is an Apogee Duet 2 USB.

Now like I said, the driver is still beta. Maybe this is the problem. I'm not sure. But also, it seems that google chrome browser freezes the system randomly too. But nothing ever freezes if I boot with cpus=1.

[verdant]

Verdant, I've decided to switch to a USB interface for audio. Seems slightly more stable than firewire, but i'm still getting random freezes. This baffles me, because I use USB keyboard, mouse, and flash drives without any issue at all. The apogee lion driver is still a beta.

To recap, the problem with a firewire interface is that if it's connected at bootup, I get the spinning ball before the desktop loads. If connected after, it will freeze at a random time with the spinning ball.
With USB interface, I can boot into lion just fine. Nothing freezes, everything is great. But at a random time, the OS will freeze with the spinning ball. This only happens when the audio interface is connected. Product is an Apogee Duet 2 USB.

Now like I said, the driver is still beta. Maybe this is the problem. I'm not sure. But also, it seems that google chrome browser freezes the system randomly too. But nothing ever freezes if I boot with cpus=1.

I do all my heavy data transfers over Firewire and USB by temporarily booting with cpus=1 maxmem=2048, then when the transfer is complete I reboot as normal........

If you temporarily boot manually with -v cpus=1 maxmem=2048 when installing the app, or for doing large data file transfers e.g. video/audio files......and then afterwards, you reboot as normal.......everything is generally OK again, including making full use of all CPU cores by running applications now using the transferred data......

It is not as bad as you think.....data transfers do not need all 4 cores running at 100%, since it is the MCP (Southbridge chipset) that is controlling the data transfer rate from USB/Firewire/eSATA/SATA/IDE to SATA/IDE and vice versa....see chipset architectures in my two nForce chipset threads.......

Even using an AppleNForceATA kext that enables the use of >3GB RAM without any problems for 99% of the time, there still seem to be some apps that cause memory addressing kernel panics either during installation or during large data file transfers e.g. video/audio files......

I have this problem for quite a while

After the console prints the Nforce HDD drivers and stuff i get stuck on USBMSC Identifier non-unique it just stops there and then nothing happens i waited for 20 minutes but still nothing

can you guys please help me out?

Is this occurring when trying to install OS X Lion using a USB flash driver installer or some other method, or when booting OS X Lion already installed on your HDD......? Please elaborate on how and when this issue is occuring.......

[silentsaint]

I do all my heavy data transfers over Firewire and USB by temporarily booting with cpus=1 maxmem=2048, then when the transfer is complete I reboot as normal........

If you temporarily boot manually with -v cpus=1 maxmem=2048 when installing the app, or for doing large data file transfers e.g. video/audio files......and then afterwards, you reboot as normal.......everything is generally OK again, including making full use of all CPU cores by running applications now using the transferred data......

It is not as bad as you think.....data transfers do not need all 4 cores running at 100%, since it is the MCP (Southbridge chipset) that is controlling the data transfer rate from USB/Firewire/eSATA/SATA/IDE to SATA/IDE and vice versa....see chipset architectures in my two nForce chipset threads.......

Even using an AppleNForceATA kext that enables the use of >3GB RAM without any problems for 99% of the time, there still seem to be some apps that cause memory addressing kernel panics either during installation or during large data file transfers e.g. video/audio files......



Is this occurring when trying to install OS X Lion using a USB flash driver installer or some other method, or when booting OS X Lion already installed on your HDD......? Please elaborate on how and when this issue is occuring.......

yes but the interface also enables audio output which would mean that if I wanted to listen to anything through the unit, I'd have to always be in single CPU mode.

Can you possibly look at my DSDT to see if you think there are any issues? I honestly feel that it's fine but I would appreciate it. I also appreciate everything you've already done to help me. You've been a huge help. Perhaps a PCIe USB 3.0 card would help?  dsdt.aml.zip   7.39KB   2 downloads

[Kilopopo]

Is this occurring when trying to install OS X Lion using a USB flash driver installer or some other method, or when booting OS X Lion already installed on your HDD......? Please elaborate on how and when this issue is occuring.......

This happens when try to install lion on an nforce 650i chipset using a usb flash drive.

[verdant]

yes but the interface also enables audio output which would mean that if I wanted to listen to anything through the unit, I'd have to always be in single CPU mode.

Can you possibly look at my DSDT to see if you think there are any issues? I honestly feel that it's fine but I would appreciate it. I also appreciate everything you've already done to help me. You've been a huge help. Perhaps a PCIe USB 3.0 card would help?  dsdt.aml.zip   7.39KB   2 downloads

Thanks for your appreciation of my help........

I will check your DSDT.........in this particular case, it could just be because the Lion driver is still only in beta stage......what happens when you increase / decrease the Apogee Duet 2's buffer size.......?

Are you powering the Apogee Duet 2 USB via its AC adapter? If not, I suggest you try the AC adapter, so that the USB port you connect to is only lightly "loaded"......

Some USB ports while not indicating 'current limit exceeded' will be pushed to their "limit".......are you connecting to a front or back panel USB port? Generally for powered USB devices, I find that my back USB ports function better.....

This happens when try to install lion on an nforce 650i chipset using a usb flash drive.

OK.........firstly, can you confirm that you have done the following (as per post#1 Part B.):

In Terminal type:

sudo chown -R root:wheel /Volumes/Mac\ OS\ X\ Base\ System/System/Library/Extensions
	sudo chmod -R 755 /Volumes/Mac\ OS\ X\ Base\ System/System/Library/Extensions 
	sudo touch /Volumes/Mac\ OS\ X\ Base\ System/System/Library/Extensions

followed by

sudo chflags nouchg /Volumes/Mac\ OS\ X\ Base\ System/System/Library/CoreServices/boot.efi
	exit

[10] Close all open folders within the Mac OS X Base System folder and in the Terminal type:

sudo chown -R 0:0 /Volumes/Mac\ OS\ X\ Base\ System

[11] Close Terminal and then go to /System/Library/Caches/com.apple.kext.caches/Startup and delete the files within Startup….

IOKitPersonalities_i386.ioplist.gz
IOKitPersonalities_x86_64.ioplist.gz
kernelcache
KextPropertyValues_OSBundleHelper_i386.plist.gz
KextPropertyValues_OSBundleHelper_x86_64.plist.gz

@silentsaint

Here is your 'cleaned up' DSDT.aml with _WAK fix and RTC fix:  SilentSaint_Fixed_DSDT.zip   21.23KB   3 downloads

I have not done any other mods until we see how you get on with this version......also I do not have the time to do further mods at present as I have to go offline for a period.......

Here is your patched DSDT.aml which may or may not help with your USB and/or Firewire issues......

Let me know how you get on with it , or not.........  SilentSaint_Patched_DSDT.zip   21.84KB   3 downloads

Edited by verdant, 26 August 2011 - 02:09 AM.

[Krishna21]

Verdant,

Wish me luck I'm going to attempt Mac OS X Lion on my X1700 tomorrow.
According to the HCL someone already has achieved it but was barely elaborated, I'll be first to elaborate on it!

[verdant]

Verdant,

Wish me luck I'm going to attempt Mac OS X Lion on my X1700 tomorrow.
According to the HCL someone already has achieved it but was barely elaborated, I'll be first to elaborate on it!

Hope it all goes well.........

[silentsaint]

Thank you for the fixed and patched DSDT. Unfortunately, neither fixed the issue. Also, connecting the unit with the power adapter makes no difference. I'm starting to believe that the problem lies with apogee's mixing software, so maybe once the driver is out of beta it will work with all four cores.

I just really don't understand how it can work with one processing core absolutely perfectly, but not with all four. I mean, the hardware doesn't change at all. Do you think that maybe it has something to do with the fact that I have GTLREF lane voltages set?

Would you suggest a USB 3.0 PCIe card? Or do you not think that would help any?

I also read in another thread a long time ago that someone had random freezes with a dual core cpu and both cores active and the problem was with the onboard LAN? Do you think that could be the problem here? The LAN works 100% though as long as I don't have my interface plugged in. Everything works perfectly with 4 cores when my interface isn't plugged in. And that was my whole purpose for installing OSX, was to make music and be able to buy Apple-only hardware.

If you can't think of any solution, i may just try to buy a board with an intel chipset. maybe a p45. But i will of course still donate to the nforce cause, because of all of your excellent help.

[verdant]

Thank you for the fixed and patched DSDT. Unfortunately, neither fixed the issue. Also, connecting the unit with the power adapter makes no difference. I'm starting to believe that the problem lies with apogee's mixing software, so maybe once the driver is out of beta it will work with all four cores.

I just really don't understand how it can work with one processing core absolutely perfectly, but not with all four. I mean, the hardware doesn't change at all. Do you think that maybe it has something to do with the fact that I have GTLREF lane voltages set?

Would you suggest a USB 3.0 PCIe card? Or do you not think that would help any?

I also read in another thread a long time ago that someone had random freezes with a dual core cpu and both cores active and the problem was with the onboard LAN? Do you think that could be the problem here? The LAN works 100% though as long as I don't have my interface plugged in. Everything works perfectly with 4 cores when my interface isn't plugged in. And that was my whole purpose for installing OSX, was to make music and be able to buy Apple-only hardware.

Could you try without having GTLREF lane voltages set.....?

I am not sure USB 3.0 would be of any help as it uses a non-Apple driver I believe.....

You could [1] try disabling onboard Firewire and LAN........then use a OS X Lion compatible PCI or PCIe NIC.....or [2] try a OS X Lion compatible USB 2.0 PCI or PCIe I/O card......

[silentsaint]

Yes, I will try without the voltages set.
I know it's probably not your area of expertise, but if I did switch to an intel mobo with new ram, would I have to reinstall lion completely? Or could I just swap it out and generate a new DSDT? I'm honestly intrigued because I want DDR3 ram anyway, and I could get a new board and new ram for around $160 USD. From what I understand, the intel bridges are far more compatible than the nvidia ones.

I'll let you know about the GTLREF lanes.

about an hour in with GTLREF lanes set to 0.

four terminal windows running yes > /dev/null

two 1080p youtube videos playing simultaneously

itunes, VLC, and apogee mixing software open


so far, no freeze. keep your fingers crossed for me!

[verdant]

Yes, I will try without the voltages set.
I know it's probably not your area of expertise, but if I did switch to an intel mobo with new ram, would I have to reinstall lion completely? Or could I just swap it out and generate a new DSDT? I'm honestly intrigued because I want DDR3 ram anyway, and I could get a new board and new ram for around $160 USD. From what I understand, the intel bridges are far more compatible than the nvidia ones.

I'll let you know about the GTLREF lanes.

5 minutes in with GTLREF lanes set to 0.

four terminal windows running yes > /dev/null

two 1080p youtube videos playing simultaneously

itunes, VLC, and apogee mixing software open


so far, no freeze. keep your fingers crossed for me!

Re switch to Intel MOBO......you could do it as follows.........

[1] Install target OS X HDD for new Intel MOBO in your nForce PC and format it as GPT/HFS+ using Disk Utility

[2] Clone current OS X Lion system on to it using Carbon Copy Cloner, or Disk Utility

[3] On the cloned GPT/HFS+ volume, remove kexts from /E/E/ for nForce MOBOs and add any your research indicates that your new Intel MOBO will need, e.g., Legacy kext for audio, SleepEnabler.kext or whatever, etc......do likewise for /S/L/E......

[4] Check if your new Intel MOBO is listed in MaLd0n's DSDT Auto Patcher and download the patched DSDT......then replace nForce DSDT.aml on cloned volume with the Intel DSDT.aml file....

[5] Run RC5 Chameleon Installer and install boot files on the target OS X HDD for new Intel MOBO

[6] Replace nForce MOBO with Intel MOBO in PC and connect up to the newly prepared HDD and boot into OS X........

Update on GTLREF lanes set to 0.....?

[silentsaint]

about an hour in now, and everything is still stable. I'm almost afraid to update you, because everything is working perfectly. If it was going to crash, I feel like it would've by now (because in the past, it was always within 10 minutes)

[verdant]

about an hour in now, and everything is still stable. I'm almost afraid to update you, because everything is working perfectly. If it was going to crash, I feel like it would've by now (because in the past, it was always within 10 minutes)

Update me when you have no doubts about it crashing just as you type "no crash yet".......LOL