zev Posted September 7, 2009 Share Posted September 7, 2009 thanks bcc9, my audio is now working great with your hdaidt patch Link to comment Share on other sites More sharing options...
bcc9 Posted September 8, 2009 Author Share Posted September 8, 2009 I seem to have gone slightly ahead from where I was stuck at earlier..Now Im getting a similar looking but different from the earlier panic..I am attaching a snapshot below..No indications of any kext failed while loading or anything like that.. Even if im using -x32 flag at boot , when I get the panic, the screen says 64bit enabled. Am I doing something wrong? Why do you say you're ahead here when the panic is appearing right away, before any kexts are loaded? Before you said "I can see a whole lot of kexts being loaded"? I'm confused.I believe the "64 bit mode enabled" just means that the kernel supports 64bit applications. You see on the next line that it's booting the I386 kernel, so 32 bit. You can also see that the addresses in the panic are just 32 bit. Time to fire up gdb and figure out where it's crashing for you I think. Link to comment Share on other sites More sharing options...
macooks Posted September 8, 2009 Share Posted September 8, 2009 Hi everyone, Couple of questions: 1. When I run my SL I get the following suspect messages from kernel (32-bit) before going to graphical mode. Can someone point out if they are normal or problem? Sep 6 21:25:12 localhost kernel[0]: Warning - kext com.superhai.driver.VoodooPower has immediate dependencies on both com.apple.kernel* and com.apple.kpi.* components; use only one style. Sep 6 21:25:12 localhost kernel[0]: VoodooPower.kext: [Warning] Unloading Sep 6 21:25:12 localhost kernel[0]: ApplePS2Controller: Timed out on mouse input stream. Sep 6 21:25:12 localhost kernel[0]: Not loading kext com.apple.driver.AppleHDAController - not found and kextd not available in early boot. Sep 6 21:25:13 localhost kernel[0]: systemShutdown false Sep 6 21:25:17 localhost kernel[0]: Sound assertion "0 == requireMaxBusStallArray" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDAController/AppleHDAController.cpp" at line 1212 goto Exit Sep 6 21:25:18 localhost kernel[0]: Sound assertion ""( kRequestStateCORB == fCodecRequest->state ) = CORB engine stuck or response was missing"" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDAController/AppleHDAController.cpp" at line 2013 goto handler Sep 6 21:25:18 localhost kernel[0]: Sound assertion "0 != err" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/IOHDAFamily/IOHDACodecDevice.cpp" at line 128 goto Exit Sep 6 21:25:23 localhost kernel[0]: Sound assertion "0 == pathMap_aDriverInstance" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDA/AppleHDADriver.cpp" at line 1459 goto Exit Sep 6 21:25:23 localhost kernel[0]: Sound assertion "0 != createAudioEngines ( fPathMap_aDriverInstance )" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDA/AppleHDADriver.cpp" at line 172 goto Exit Sep 6 21:25:23 localhost kernel[0]: Sound assertion "0 == pathMap_aDriverInstance" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDA/AppleHDADriver.cpp" at line 1459 goto Exit Sep 6 21:25:23 localhost kernel[0]: Sound assertion "0 != createAudioEngines ( fPathMap_aDriverInstance )" failed in "/SourceCache/AppleHDA/AppleHDA-174.1.1/AppleHDA/AppleHDADriver.cpp" at line 172 goto Exit Sep 6 21:25:26 kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0. 2. Do I have to keep /Extra/com.apple.Boot.plist ?? I deleted it once and fakesmc did not work anymore after that. 3. In post #1 your voodops2controller package bbc9 compiled includes AppleACPIPS2Nub.kext but Voodoo Package says not to use this, otherwise we get KP. What is correct info here?? 4. BTW your bluetooth extensions does not load in 64-bit mode. Any chance of getting a updated version for this?? Thank you. Link to comment Share on other sites More sharing options...
bcc9 Posted September 8, 2009 Author Share Posted September 8, 2009 1. When I run my SL I get the following suspect messages from kernel (32-bit) before going to graphical mode. Can someone point out if they are normal or problem?Those sound assertions are the same ones I linked to a few post back, and so they are common and seem to be cosmetic. Or they may be a symptom of the AppleHDA panic that happens sometimes. Maybe someone can help figure this out?? The voodoopower error would be cosmetic & trivial to fix. 2. Do I have to keep /Extra/com.apple.Boot.plist ?? I deleted it once and fakesmc did not work anymore after that.I don't recommend using /Extra/com.apple.Boot.plist as chameleon can pick that plist file up from a partition other than the one 10.6 is on which is pretty confusing. I suppose it could make sense if you're using EFI partitions. On the other hand with chameleon only supporting 4 MBR partitions per disk I wouldn't want to have an EFI partition, so I still say the chameleon behavior makes little sense.Now, I use fakesmc and I have no such problem. 3. In post #1 your voodops2controller package bbc9 compiled includes AppleACPIPS2Nub.kext but Voodoo Package says not to use this, otherwise we get KP. What is correct info here??Notice I no longer reference the package in post #1 With the 32+64bit version of VoodooPS2 you need to use the supplied AppleACPIPS2Nub. Perhaps that'll change again when a new "release" is built but for now that's what works with the voodoops2keyboard kext.4. BTW your bluetooth extensions does not load in 64-bit mode. Any chance of getting a updated version for this??The new version, 1.1a, that I put out 4 days ago fixes that. It *is* linked correctly from what I see. Link to comment Share on other sites More sharing options...
Traggr Posted September 8, 2009 Share Posted September 8, 2009 Why do you say you're ahead here when the panic is appearing right away, before any kexts are loaded? Before you said "I can see a whole lot of kexts being loaded"? I'm confused. I feel that im ahead here looking at the system uptime in nanosec. Its slightly more than my earlier crash. Also, the screenshot iv posted appears after nearly all the kexts from S/L/E get loaded..I see them zipping rapidly down on the screen & then the screen goes blank for a moment & then the crash screen appears. I believe the "64 bit mode enabled" just means that the kernel supports 64bit applications. You see on the next line that it's booting the I386 kernel, so 32 bit. You can also see that the addresses in the panic are just 32 bit. Time to fire up gdb and figure out where it's crashing for you I think. Ohh.. Thanks for clearing my doubt. Im still a novice,gdb would be way pro for me.. maybe i'll try to reformat & try to see if it works.. Please do suggest any other way if you have come across before.. Thanks & sorry again for the trouble.... Link to comment Share on other sites More sharing options...
pmcnano Posted September 9, 2009 Share Posted September 9, 2009 2 questions: Does anyone has been able to install in a 9500M laptop?? 2nd question... @bcc9: Dude, by anyyy chance, did you injected 9400+9500m info to the dsdt??? I mean, this is weird, is the second time i install, everything is fine...i get no KP's or anything, I just boot perfectly, get grey screen (where welcome video shoudl start) and it doesnt start at all!! Thanks edit: nvm, I deleted dsdt.aml and it stills happen the same. Grey screen! damn.. Link to comment Share on other sites More sharing options...
bcc9 Posted September 9, 2009 Author Share Posted September 9, 2009 the screenshot iv posted appears after nearly all the kexts from S/L/E get loaded..I see them zipping rapidly down on the screen & then the screen goes blank for a moment & then the crash screen appears.Your screenshot shows the panic with no kext loads being printed so either I still don't understand you or you're confusing the messages that the bootloader is printing with kext loading.Ohh.. Thanks for clearing my doubt. Im still a novice,gdb would be way pro for me.. maybe i'll try to reformat & try to see if it works.. Please do suggest any other way if you have come across before.. Thanks & sorry again for the trouble.... A rudimentary look at the function pointers in your stack trace reveals: % gdb -arch i386 mach_kernel GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul 3 01:19:56 UTC 2009) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-apple-darwin"... (gdb) x/i 0x021acfa 0x21acfa <panic+445>: mov 0x8011d0,%eax (gdb) x/i 0x2a6ac2 0x2a6ac2 <panic_trap+273>: jmp 0x2a6ade <kernel_trap+1558> (gdb) x/i 0x29c968 0x29c968 <trap_from_kernel+25>: mov %edi,%esp (gdb) x/i 0x508684 0x508684 <_ZN6OSKext18initWithBooterDataEP8OSStringP6OSData+424>: movb $0x0,-0x1(%eax,%edx,1) (gdb) x/i 0x502548 0x502548 <_ZN6OSKext14withBooterDataEP8OSStringP6OSData+58>: test %al,%al (gdb) x/i 0x88b91b 0x88b91b <_ZN12KLDBootstrap20readBooterExtensionsEv+621>: mov %eax,%edx (gdb) x/i 0x88bfc7 0x88bfc7 <_ZN12KLDBootstrap21readStartupExtensionsEv+87>: mov %ebx,(%esp) (gdb) x/i 0x88bffa 0x88bffa <_ZL32bootstrapRecordStartupExtensionsv+18>: leave (gdb) x/i 0x52bc22 0x52bc22 <StartIOKit+200>: mov (%ebx),%eax (gdb) x/i 0x57349c 0x57349c <PE_init_iokit+437>: add $0x2c,%esp (gdb) x/i 0x22847d 0x22847d <kernel_bootstrap_thread+87>: movl $0x1,(%esp) (gdb) x/i 0x29c68c 0x29c68c <call_continuation+28>: add $0x10,%esp (gdb) quit So without looking very far, I'd say you didn't get your kext cache built right. Maybe you can describe how you used the kextcache command & compare it to what I recommended. You could also try using mkextunpack to unpack the system kext cache and verify whether it's right. PS: Exact same screen shot posted by another user over here: http://www.insanelymac.com/forum/index.php...t&p=1255113 Edit: I think you should try to boot with -f Link to comment Share on other sites More sharing options...
bcc9 Posted September 9, 2009 Author Share Posted September 9, 2009 @bcc9: Dude, by anyyy chance, did you injected 9400+9500m info to the dsdt??? I mean, this is weird, is the second time i install, everything is fine...i get no KP's or anything, I just boot perfectly, get grey screen (where welcome video shoudl start) and it doesnt start at all!! Thanks edit: nvm, I deleted dsdt.aml and it stills happen the same. Grey screen! damn.. The injection patch I made to the dsdt was under Scope IXVE.IGPU, for the 9400m part. The 9200m part is scope XVR0.Z01I I believe. Did you test graphics injection via dsdt under 10.5.x? That'd be the obvious way to narrow things down. Or test with my natit solution (making sure to set the IOPCIMatch clause to only match the 9400m part). Edit: as for grey screen, sounds like you're not booting with the recommended -v Link to comment Share on other sites More sharing options...
pmcnano Posted September 9, 2009 Share Posted September 9, 2009 Im booting with -v, It is actualing opening loginwindow.app. I see the gray screen I can move the cursor!! Its just, the welcome video / welcome setup assistance doesnt come up at all.......... And, its not the video injection since I deleted dsdt.aml file and it didnt worked at all. Meh, this is so weird, Im still, curious if its the 9500m Link to comment Share on other sites More sharing options...
Traggr Posted September 9, 2009 Share Posted September 9, 2009 Your screenshot shows the panic with no kext loads being printed so either I still don't understand you or you're confusing the messages that the bootloader is printing with kext loading. Yes.. you are right. I realise now that I was mistaking the messages printed by the bootloader as kext loading... So without looking very far, I'd say you didn't get your kext cache built right. Maybe you can describe how you used the kextcache command & compare it to what I recommended. You could also try using mkextunpack to unpack the system kext cache and verify whether it's right. These are exactly the commands I used in Terminal after doing sudo -s . ( Note : /dev/disk1s3 is the Hdd partition for Snow) mount -u -o suid /dev/disk1s3 cd /Volumes/Snow chown -R root:wheel Extra/Extensions chmod -R 755 Extra/Extensions kextcache -a i386 -K /Volumes/Snow/mach_kernel -m /Volumes/Snow/Extra/Extensions.mkext /Volumes/Snow/Extra/Extensions After hitting enter here, I get a message saying that the kexts(both Voodoops2 & fakesmc) have some dependency issues but have been included in cache anyways. Edit: I think you should try to boot with -f I tried again with -f.... no luck,below is the screenshot of the crash.. Link to comment Share on other sites More sharing options...
pmcnano Posted September 9, 2009 Share Posted September 9, 2009 Well I can actually tell you, dont remember where, but I read that using -f in snow leopard gets all things {censored}ed up! Ill just zip you my Extra/Extensions folder and atach it for you! Link to comment Share on other sites More sharing options...
n00bmanEXE Posted September 9, 2009 Share Posted September 9, 2009 Whenever I try to execute the command mount -u -o suid /dev/disk0s3, I get the error mount: unknown special file or file system /dev/disk0s3 . However diskutil shows: #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *298.1 Gi disk0 1: Apple_HFS Leopard 15.1 Gi disk0s1 2: Windows_NTFS 224.1 Gi disk0s2 3: Apple_HFS Mac OS X 58.9 Gi disk0s3 Link to comment Share on other sites More sharing options...
bcc9 Posted September 10, 2009 Author Share Posted September 10, 2009 These are exactly the commands I used in Terminal after doing sudo -s . ( Note : /dev/disk1s3 is the Hdd partition for Snow)Those look OK to me. You can just use the mount point name, like /Volumes/Snow, instead of the device in that remount command.Um, I'm assuming you didn't have /Volumes/Snow mounted with nosuid access before the install. If you did, all your system files probably have the wrong ownerships. Check the ownerships of your system files in /Volumes/snow. If they are owned by 'unknown' then there's your problem. After hitting enter here, I get a message saying that the kexts(both Voodoops2 & fakesmc) have some dependency issues but have been included in cache anyways.That's normal for /Extra extensions I tried again with -f.... no luck,below is the screenshot of the crash..Same addresses on the stack, so same problem. Whenever I try to execute the command mount -u -o suid /dev/disk0s3, I get the error mount: unknown special file or file system /dev/disk0s3 Probably you partitioned it, but the partition hasn't been formatted yet. Well I can actually tell you, dont remember where, but I read that using -f in snow leopard gets all things {censored}ed up!Would be good if you could dig up the reference, and just as important *why*. I'm finding it hard to believe. Link to comment Share on other sites More sharing options...
pmcnano Posted September 10, 2009 Share Posted September 10, 2009 I read it in several Snow Leo guides, no clue. Mh, still asking, anyone with a 9500m has been able to install Snow Leo????????? Thanks! @bcc9, I will ask but im sure you already tried, does your legacy kexts work with 10.5.8 applehda? or, will they work with modified 10.5.3 applehda, just for the headphone sense... Link to comment Share on other sites More sharing options...
bcc9 Posted September 10, 2009 Author Share Posted September 10, 2009 @bcc9, I will ask but im sure you already tried, does your legacy kexts work with 10.5.8 applehda?Yes, it does. Link to comment Share on other sites More sharing options...
Traggr Posted September 10, 2009 Share Posted September 10, 2009 Hello Guys... Finally it worked..Snow is up & running on the 1340 & I guess it would probably have worked fine right from the first boot without any of those nasty KPs had I not been stupidly booting from the Leopard OS(the laptop HDD). The booting is to be done from the Snow partition on the external HDD. I suppose in many guides(atleast the ones I referred) out there, its not explicitly highlighted & many who are new may misunderstand.. as I did :censored2: This is for just for those who might be novices at OS X. After you have done all the processes & steps as recommended by bcc9 .. viz- the OS install,the bootloader install,DSDT,plists, kext cache compilation etc & when u head for your first boot - Hit F12,change the boot sequence to boot from external HDD,(eSATA/USB) & then Chameleon should take over. hopefully booting you without any panics to the Snow Leopard welcome screen.. A ton of thanks to bcc9 firstly for the awesome guide,kexts,plists & more which made this process specific & monumentally useful for all of us with the 1340..& secondly for all his patience in helping me with the KPs.. you simply rock dude !!!! .. jus cant thank u enuf.... @pmcnano - Ur insights have helped me like a zillion times.. thanks again this time as well ..!!! Hope the video card issue u hv gets figured out quickly & ur booting Snow toooo... .. now im off to install the rest of the kexts.... Link to comment Share on other sites More sharing options...
pmcnano Posted September 10, 2009 Share Posted September 10, 2009 @bcc9, By yes, You mean that Vanilla AppleHDA.kext (10.5.8) plus HDAIDT.kext plus dsdt.aml work for you? lol, I tried it and it paniced D:................... referencing applehda of course.. Thanks for your help Link to comment Share on other sites More sharing options...
bcc9 Posted September 10, 2009 Author Share Posted September 10, 2009 By yes, You mean that Vanilla AppleHDA.kext (10.5.8) plus HDAIDT.kext plus dsdt.aml work for you? Exactly. lol, I tried it and it paniced D:................... referencing applehda of course..Yes, it does that about 15-20% of the time, as posted over&over. Never twice in a row for me however. Hello Guys...Finally it worked..Snow is up & running on the 1340 & I guess it would probably have worked fine right from the first boot without any of those nasty KPs had I not been stupidly booting from the Leopard OS(the laptop HDD). Glad you finally got it working. Not sure I get your explanation of what you were doing wrong until now. Sounds like you were previously booting using an old chameleon 1 boot loader (which wouldn't pick up the dsdt.aml, etc)? Link to comment Share on other sites More sharing options...
pmcnano Posted September 10, 2009 Share Posted September 10, 2009 Lol, no fix atm right? XD....I dont know what is better, headphones+shutdown+KP vs stable-headphones-shutdown lol Link to comment Share on other sites More sharing options...
bcc9 Posted September 10, 2009 Author Share Posted September 10, 2009 Lol, no fix atm right? XD....I dont know what is better, headphones+shutdown+KP vs stable-headphones-shutdown lolIt's not like anyone has offered me any help on the panic issue... That comparision is not valid for 10.6 as you can't use 10.5.3 applehda under 10.6. Your choice is no audio or voodhda with hopelessly distorted audio or applehda with occasional panic at boot time. As for shutdown, 10.5.3 applehda+shutdown works fine with OpenHaltRestart, no? Link to comment Share on other sites More sharing options...
pmcnano Posted September 10, 2009 Share Posted September 10, 2009 Well as you said, it will boot eventually, did 3 boots in a row, and now im in, as you said Microphone works, and headphone mutes speakers =P. You get assertions if you use the other headphone jack, just informing if you didnt noticed. As for the shutdown, not sure, I mean, atm i dont use openhaltrestart but Im pretty sure I used it once and it didnt make a difference in our system. Anyway, I have so few time lately (or maybe since like.....6 months ago).....so it makes things difficult for me helping anyone. But if you ask for something specifically to help you, shoot and I will give it a try if I can. Nano Link to comment Share on other sites More sharing options...
bcc9 Posted September 10, 2009 Author Share Posted September 10, 2009 Also if you're not interested in staying current, and are only interested in headphone detection, you could probably just back-port my pathmap change found in my hdaidt.kext into the 10.5.3 Applehda. As for the shutdown, not sure, I mean, atm i dont use openhaltrestart but Im pretty sure I used it once and it didnt make a difference in our system. AWell gambit posted a reference to a fix at one point called "shutdown fix v3". I never tried it myself as managing an extra kext just for such a minor detail seemed like a waste of time to me. Feel free... Anyways these are 10.5.x specific issues for the older thread. Link to comment Share on other sites More sharing options...
Traggr Posted September 10, 2009 Share Posted September 10, 2009 Glad you finally got it working. Not sure I get your explanation of what you were doing wrong until now. Sounds like you were previously booting using an old chameleon 1 boot loader (which wouldn't pick up the dsdt.aml, etc)? Well,what I was doing wrongly was booting off the ChameleonRC1 431 installed on leopard laptop hdd drive which was why Snow was KP'ing..When I booted off the External drive changing Boot preference to (external)USB,the latest Chameleon RC3 worked & booted me into Snow.. Well, after putting in all the other kexts in E/E & compiling cache & rebooting , Im only able to get sound working. Im not sure if VoodooPower is working(any way I can check?). I cant see battery,bluetooth & when I ran the patch-acpi , I got the foll error . . Patching AppleACPIPlatform for OS version 10a432 Original version saved as /System/Library/Extensions/AppleACPIPlatform.kext/Contents/MacOS/AppleACPIPlatform.orig cp: /System/Library/Extensions/AppleACPIPlatform.kext/Contents/MacOS/AppleACPIPlatform.orig: Permission denied touch: /System/Library/Extensions: Permission denied logout . . Anything I did incorrectly here.. I had done sudo -s before. Also, when I booted in 64bit mode, i think it was HDA that caused a panic..Im attaching a screenshot below..I think you had mentioned about this in an earlier post ... Link to comment Share on other sites More sharing options...
pmcnano Posted September 11, 2009 Share Posted September 11, 2009 did you ran the script with root privileges? @bcc9: I will stick with your new kext, after the first successfully boot It hadnt paniced again, so its all good. And about not staying current, well I WANT to jump to snow leopard but lol at the moment it isnt working for me..so I have to stick with Leo. Not sure yet whats my problem with Snow thanks anyway Link to comment Share on other sites More sharing options...
bcc9 Posted September 11, 2009 Author Share Posted September 11, 2009 Patching AppleACPIPlatform for OS version 10a432Original version saved as /System/Library/Extensions/AppleACPIPlatform.kext/Contents/MacOS/AppleACPIPlatform.orig cp: /System/Library/Extensions/AppleACPIPlatform.kext/Contents/MacOS/AppleACPIPlatform.orig: Permission denied touch: /System/Library/Extensions: Permission denied As pmcnano wrote, you need to run my script as root. Otherwise it doesn't do anything. Also, when I booted in 64bit mode, i think it was HDA that caused a panic..Im attaching a screenshot below..I think you had mentioned about this in an earlier post ...Looks like the same old AppleHDA crash to me. PS: That's a 32 bit crash not 64 bit. Well,what I was doing wrongly was booting off the ChameleonRC1 431 installed on leopard laptop hdd drive which was why Snow was KP'ing..I still don't get you then because for me chameleon 431 doesn't cause a panic. Link to comment Share on other sites More sharing options...
Recommended Posts