mercurysquad Posted September 19, 2008 Author Share Posted September 19, 2008 I just tried the Voodoo kernel as part of my boot-132 iso. My system specs are in the sig. It is an Intel P4 with SSE3 and hyperthreading (2 threads). The system is a retail dvd install + chameleon and Extra/Extensions on the boot cd. As far as I can tell at the moment, everything is running correctly. The SystemProfiler shows: L2 Cache: 512 KB I have never tried speed step or sleep. Hmm cache info is incorrect. Fix is in progress. LOL... Yeah, works fine here. Almost native speeds too. So does Parallels. Darwin Kernel Version 9.4.0 ToH & StageXNU:xnu-1228.5.20/BUILD/obj/RELEASE_I386 OK. A bit more context is helpful - if you want to give it a try again, please boot into the beta kernel, start VMWare, and when it panics and reboots, start stagexnu kernel and look in /var/log/System.log --> Please file a bug report on the google code page (link on first post) and attach the System.log file. is there any specific kexts I need to use for sleep and speedstep to work? For sleep you just need to do > Sleep (or shut laptop lid). For speedstep, install kext in my sig. Link to comment Share on other sites More sharing options...
PeteRock Posted September 19, 2008 Share Posted September 19, 2008 Thanks for the fast response mercurysquad, I am getting closer to solving the problem. I disabled bluetooth, wireless and usb legacy support in the dell bios and tried sleep again and this time it did not hang immediately, i got the mouse cursor back and it hung when i tried to click on finder! Link to comment Share on other sites More sharing options...
Nick14 Posted September 19, 2008 Share Posted September 19, 2008 Hmm cache info is incorrect. Fix is in progress. cache has always been wrong in OS X on every kernel Link to comment Share on other sites More sharing options...
dies Posted September 20, 2008 Share Posted September 20, 2008 OK. A bit more context is helpful - if you want to give it a try again, please boot into the beta kernel, start VMWare, and when it panics and reboots, start stagexnu kernel and look in /var/log/System.log --> Please file a bug report on the google code page (link on first post) and attach the System.log file. Well I kind of suspected this, gave that a try but unfortunately the lockup is instant, nothing in the system log, jumps right from the last thing I did ( disk utility ) before starting VMware into the next boot. In any case, if there's another way to get the info you guys need let me know. Link to comment Share on other sites More sharing options...
BladeRunner Posted September 20, 2008 Share Posted September 20, 2008 Well I kind of suspected this, gave that a try but unfortunately the lockup is instant, nothing in the system log, jumps right from the last thing I did ( disk utility ) before starting VMware into the next boot. In any case, if there's another way to get the info you guys need let me know. You might try to boot into single user mode - using the -s kernel flag at the F8 boot prompt. Then try: tail -n 25 /var/log/System.log That should give you the last 25 lines of the system log. e.g., Rainbow:~ lrh$ tail -n 5 /var/log/System.log Sep 19 20:27:36 Rainbow mDNSResponder[22]: Unknown DNS packet type 5450 from 192.168.1.15 :1900 to 192.168.1.5 :63867 on 0080CC00 (ignored) Sep 19 20:42:36 Rainbow mDNSResponder[22]: Unknown DNS packet type 5450 from 192.168.1.15 :1900 to 192.168.1.5 :63867 on 0080CC00 (ignored) Sep 19 20:57:36 Rainbow mDNSResponder[22]: Unknown DNS packet type 5450 from 192.168.1.15 :1900 to 192.168.1.5 :63867 on 0080CC00 (ignored) Sep 19 21:12:36 Rainbow mDNSResponder[22]: Unknown DNS packet type 5450 from 192.168.1.15 :1900 to 192.168.1.5 :63867 on 0080CC00 (ignored) Sep 19 21:26:45 Rainbow login[391]: USER_PROCESS: 391 ttys000 I did the command in terminal mode but it should be the same in single user mode. Link to comment Share on other sites More sharing options...
Recommended Posts