Jump to content


  • Content count

  • Joined

  • Last visited

About jtm297

  • Rank
    InsanelyMac Protégé
  1. I never even seen this! I probably would have not tried it because I didn't know you had a Core i7. When reading through the thread I was looking for people who reported they had it working with their Core i7. Voodoo kernel itself never worked for me, but I am glad you have it working! You are very welcome! I am happy it works for you! Hopefully it works for other people also. NDA means non-disclosure agreement. It means he can't talk about upcoming releases relating to VMWare. Essentially he has a legal agreement with them to keep his mouth shut.
  2. Thank you! Yes, I did notice for Voodoo 2 that busratio wasn't doing anything. I didn't try it with Voodoo 1 though, it might work, who knows.
  3. That would be really awesome. Yes, I tried Voodoo 1, but it did the exact same thing as Voodoo 2 Alpha3. I was shocked AnV worked considering all the Voodoo variants seemed to do the exact same thing. AnV was the first to give me a real kernel panic (actually it was useful!). The setting of the busratio=20 is REQUIRED for me to get to boot into OSX 10.5.8. I still need to add it to do it automatic. But for now, I don't plan on restarting the machine often. I have installed iPhone SDK 3.1 and I can confirm XCode is working perfectly on it. I even downloaded an example and was able to compile it without any issues. I really just recommend people to try different kernels and options. You could make a nice long list of kernels for this with different settings predefined also with appropriate names. I think that would help a lot of people out and end a lot of the troubles people are having here. Also remember the KERNEL must match the OS, or you will get a crash during mounting of a dmg file. So this is pretty crucial. You may need to include every kernel version.
  4. Newest Update!!!!!!! I have AnV XNU Kernel 9.8.0 kernel running on 10.5.8! This kernel is based off Voodoo (I tried other Voodoo variants also). http://www.infinitemac.com/f36/anv-xnu-9-8...3651/page1.html Now I don't really know what makes his kernel any different than Voodoo but it says: "Apart from the improvements in the code that Apple has made it will include all Voodoo features as well as a built-in decrypter and Mac model override + Legacy AppleIntelClock driver for additional RTC support. It is also in general a lot faster, especially in booting, than stock Voodoo kernel." So I installed it in hopes it'll work. I went to boot into it and KERNEL PANIC! But this time a REAL Kernel Panic and it didn't just reboot like it was doing with the Voodoo kernel and the 10.5.8 vanilla kernel. It was actually showing an error. So my first guess was to try passing into busratio=20 (this is a common fix for Core i7 with voodoo), and it booted into OSX! Absolutely no problems so far! And since the 9.8.0 kernel matches for 10.5.8, I have currently experienced no dmg mounting issues! If anyone else with a Core i7 is still having problems even after using Donk's very detailed and great guide. I would definitely recommend trying the following steps if you want 10.5.8: 1) Install OSX 10.5.4 (or anything less than 10.5.7) 2) Boot like normal, backup the kernel /mach_kernel to /mach_kernel.original 3) Update OSX to 10.5.8 using the Apple menu. 4) Reboot and you probably will get some nasty reboot cycle or kernel panic. 5) type in mach_kernel.original at the boot menu prompt (the one from when you press h and F8) 6) Hope it boots to 10.5.8 with this older kernel. 7) Download the AnV XNU kernel from http://www.infinitemac.com/f36/anv-xnu-9-8...3651/page1.html (first post) 8) Download OSX86Tools: http://code.google.com/p/osx86tools/ 9) Install any System.ktex with OSX86Tools and copy the mach_kernel from AnV XNU kernel over /mach_kernel with a sudo cp command. 10) Reboot and pray... (it probably won't work yet, it didn't for me) 11) If it doesn't work spam h and F8 until you get to the boot menu again. Type in busratio=20 (you may need to modify the 20 depending on your setup) and press enter and really start praying. From the Voodoo Guide: busratio= This is used to specify your processor's clock multiplier. This is also known as the bus ratio, and is the ratio of your FSB frequency to your processor's highest frequency. If you need to specify a non-integer bus ratio, simply omit the decimal point. Typical range: 3 to 30. Examples: busratio=13 (multiplier 13) or busratio=105 (multiplier 10.5) I really hope these steps help someone out there! If not, keep trying different kernels and setting until it works! Don't give up! I didn't. EDIT: Attached is my vmx and I am also using the original darwin.iso (not the voodoo.iso). OSX.zip
  5. I think I figured out why I can boot into this OS. It is because my kernel is the one from 10.5.4! It says Darwin Version 9.4.0 when it should be 9.8.0. I found this thread: http://www.insanelymac.com/forum/index.php?showtopic=148566 So I checked my kernel and was shocked to see it was 9.4.0 when this says it should be 9.8.0. Now my choices are to upgrade the kernel to something else, or figure out how to fix the mounting issue with this 9.4.0. It probably has to do with seatbelt.kext to be set for 9.4.0. I am currently using a seatbelt.kext which is made for the 9.8.0 kernel. Now I just need to get the 9.6.0- Kernel and this might work and the seatbelt and it should work...
  6. BREAKING NEWS: For some reason, I decided to try to install OSX 10.5.8 again on the SCSI machine. I am booting with the voodoo.iso, but I am not loading the voodoo kernel at all, and guess what? It is booting into 10.5.8! I don't understand what I changed. I even checked if it had to do with: monitor.virtual_exec = "hardware" monitor.virtual_mmu = "software" But it seems to not matter at all if that is there or not. So I am able to get into OSX 10.5.8, and I am really not sure why. I did the following: 1) Installed 10.5.4 without anything special 2) Booted to it with voodoo.iso without using voodoo kernel. 3) Upgraded the kernel to use Kabyl kernel. Seemed to boot into 10.5.4 fine with this new kernel. It also had a System.kext that I installed. 4) Upgraded to 10.5.8 through Software Update menu 5) Rebooted, and crashed... 6) Decided to boot off mach_kernel.original without any parameters, booted fine. 7) Got into 10.5.8 8) Snapshotted, and moved mach_kernel.original to mach_kernel, and rebooted 9) Got into 10.5.8 again 10) Confused.... 11) Tried to download iPhone SDK 3.1. FAILED So I am stuck at the iPhone SDK 3.1 download (yes the download...) I am getting: "you need to restart your computer. hold down the power button for several seconds..." with a grey background as soon as the download finishes. I am guessing it has to do with hard drive activity... not sure what or why. I need assistance on this one! Why this is working? Only guess is the System.kext did something? Or me changing to not overclock in the BIOS. I am about to try it with the IDE setup. I doubt it will work though... The kernel and System.kext that I used is from http://www.mediafire.com/?voiwzyo0yn3 Remember this kernel did not work for me with 10.5.8, only with 10.5.4. I did keep the System.kext, which I installed with osx86tools. I just tried and couldn't get the IDE one to work. Not sure why this SCSI one is working, except for this error.
  7. Yes, I agree it is definitely the kernel not liking my machine. The same result happens when I try manually installing the voodoo kernel. My guess is that the only options I have are: 1) Find another kernel which supports Core i7 2) Trick XCode and iPhone SDK
  8. Ah, you are right about last test not having: monitor.virtual_exec = "hardware" monitor.virtual_mmu = "software" I am redoing it now... (this is for SCSI with OSX 10.5.4) Didn't seem to fix it. I will disable the SpeedStep stuff now. Disabled SpeedStep in BIOS of host machine, still didn't work. Here is the newest log of OSX 10.5.4 with SCSI issuing command: rd(0,1)/mach_kernel.voodoo.alpha3 -v rd=disk0s2 Still seems to not work on both SCSI and IDE (IDE being 10.5.8) and (SCSI being 10.5.4). I don't understand why I cannot boot to this kernel without it having a kernel panic. Is there anyway I can get more information about this crash? vmware.zip
  9. Nothing seems to work with the SCSI 10.5.4 install and voodoo. I posted the log and the video. The log looked interesting around: Sep 16 10:30:51.871: vcpu-0| MonitorInitNumaUnmapVMM64 Sep 16 10:30:51.902: vcpu-0| Triple fault. Sep 16 10:30:51.902: vcpu-0| Msg_Hint: msg.monitorEvent.cpl0SS (sent) Sep 16 10:30:51.902: vcpu-0| *** Virtual machine kernel stack fault (hardware reset) *** I just find it weird that people with the same CPU and motherboard can get it to work. I wonder if it has to do with my OS being 64bit. I really can't think of why... vmware.zip OSXFinal_Movie002.zip
  10. Update: With 10.5.4 with SCSI using: rd(0,1)/mach_kernel.voodoo.alpha3 -v rd=disk0s2 Instantly reboots the virtual machine (kernel panic) I have also tried earlier manually installing voodoo (on 10.5.4) using the official google code one and I experienced the same problems. It just wouldn't boot to the kernel. Same problem...
  11. This actually should be setup with IDE. Strange for you to say it is SCSI. The settings say Hard Drive (IDE). I am actually doing the update right now, but I can try on the other OSX virtual machine I have which is actually on SCSI and has 10.5.4 on it still. I will check mount with that and adjust accordingly. I currently have both IDE and SCSI (both with snapshots to 10.5.4). The update to 10.5.8 on the IDE finished, but of course it kernel panics at start up. I haven't tried with voodoo yet for that one. I will do the SCSI with 10.5.4 and voodoo right now. I did read that voodoo recommends 10.5.5 to avoid issues.
  12. Well it is still possible to do a reverse VNC connection to get around firewalls. The current progress is this: mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local) fdesc on /dev/ (fdesc, union) map -hosts on /net (autofs, automounted) map auto_home on /home (autofs, automounted) on /Volumes/VMware Shared Folders (vmhgfs) I attached my vmx Please note I did not do: rd(0,1)/mach_kernel.voodoo.alpha3 -v rd=disk1s3 to install this, I had to NOT use this command for it to install. I just booted off the cd, but I am using voodoo.iso, I am just not loading the kernel. I have a snapshot of this virtual machine, so I am going to download the update and do another snapshot. I will proceed to the next step after that. OSX_.zip
  13. For disabling power management I am going into the Energy Saver section and putting sleep to never and put hard drive to sleep unchecked. I am assuming this is what you mean... if there is something I am missing let me know!
  14. If you want I can give you remote access to the machine with the vmware. I have turned off the overclocking. I am going to reinstall the vanilla retail OSX 10.5.4 with IDE etc. I can confirm: guestOS = "darwin-64" ich7m.present = "TRUE" smc.present = "FALSE" monitor.virtual_exec = "hardware" monitor.virtual_mmu = "software" I just copied that directly from the vmx. I would do the rest and post vmx, log, and mount output.
  15. Same here I hope you and your family get better. --------------------------------------------- Just tried without overclocking my CPU, didn't fix it.