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.

rxmd

Members
  • Content count

    23
  • Joined

  • Last visited

About rxmd

  • Rank
    InsanelyMac Protégé
  1. I am currently experimenting with this install method and am getting a slew of mDNS-related errors when booting the newly-installed, clean, virgin retail Leopard partition for the first time (see the attached image). Basically it seems that there is a networking issue won't go away. Has anyone ever seen these mDNS-related errors? My first idea was that this is an extension-related problem, but I get it even when booting without any extensions in the boot/"EFI" partition, so by now I'm doubting it a little bit. Currently the Extensions folder on the boot partition contains the following: AppleAHCIPort (for ICH7 AHCI); AppleIntelGMA950, AppleIntelIntegratedFramebuffer (modified to fit the PCI IDs) Natit IOGraphicsFamily, IONDRVSupport (original Leopard, only with OSBundleRequired set to Root to satisfy dependencies) dsmos, IntelCPUPMDisabler The system is a Thinkpad X60s, which has a 945 chipset, 950 graphics, a Core Duo processor and an 82577 LAN chipset; the latter is supported by OS X's 8254x driver (I'm currently posting through it on an iDeneb installation).
  2. My plists for boot-132 method :)

    Would this work for graphics drivers, too? I'm specifically thinking of the GMA950 driver. It would be convenient just to add the PCI IDs and use the vanilla driver.
  3. Hi, I've been successively nailing down some of the installation errors I kept getting that I was posting about earlier, but this one is a tough one. I've got a working iDeneb, from which I installed Leopard from a retail DVD image, and I am currently trying to get this fresh Leopard to boot using BOOT-132. I've been juggling extensions a lot but I keep getting mDNS responder errors like the ones in the attached image. This is on the first boot, so there is no host name, user name etc. set - this is what Leopard asks for on the first boot, but we don't ever get there, it just sits there and shows me mDNSResponder initalisation errors all day. The machine is an IBM Thinkpad X60s, whose hardware is practically identical with the original MacBook. The Leopard partition is completely vanilla, the BOOT-132 extensions are AppleAHCIPort (for the ICH7 chipset), AppleIntelGMA650, AppleIntegratedFramebuffer, ApplePS2Controller, AppleSMBIOS, Disabler, dsmos, IntelCPUPMDisabler, Natit, SMBiosEnabler and some IOFamily kexts (IOACPIFamily, IOGraphicsFamily, IONDRVSupport, IOPCIFamily). Anyone got any idea how to get rid of the annoying mDNSResponder messages? I think as soon as I get those nailed down, Leopard should work fine. As soon as I get it to work, I'll post a detailed install guide, but for that I need to get this mDNS stuff out of the way.
  4. Hi, I'm trying to get a fresh install of Leopard (from a Retail DVD) booted using BOOT-132. This is the first boot, so I should get the user registration boxes etc., but all I get is a grey screen with a mouse cursor and no Apple logo. Upon booting with -v, I'm seeing lots of network-related error messages, especially mDNS failing, sandbox initialisation failing and CoreServicesD being a wrong version etc. You can get an idea from the attached screenshot (it's difficult to photograph because they zoom by so fast). I have to switch off the hard way all the time, which is why fseventsd finds all sorts of cruft from the last boot, but I don't think this is the problem. The machine is a Thinkpad X60s, i945 chipset, GMA-950 graphics, with BOOT-132 in a small HFS+ partition called EFI (more or less following Munky's guide) and a completely unmodified vanilla Leopard install in a larger partition. (I've also got another partition with iDeneb from which I'm doing all the modifications, but the Leopard partition itself is untouched.) Extensions are currently the ones for GMA950, integrated framebuffer and AppleAHCI from iDeneb, then IOPCIFamily, IOAHCIFamily, IONDRV, IOGraphicsFamily and IONetworking from Leopard, and Disable.kext, dsnos.kext and some ACPI-related stuff also from iDeneb. Anything I can do? Does anyone else see similar error messages with BOOT-132?
  5. Hi, I'm struggling to get a vanilla Leopard to boot on my Thinkpad X60s. The machine has a Core Duo processor and an Intel 945 chipset with GMA950 graphics. The lspci output is attached below. I've got iDeneb 10.5.5 working fine in another partition, with everything supported fine (including sleep, excluding wireless which is no surprise and doesn't concern me at this point), so I know that OSX86 can run fine on my machine. It's about the vanilla Leopard and what I need to get it to boot. I have the problem that I can't seem to get the proper set of extensions together so that vanilla Leopard will boot from the BOOT-132 loader. Currently when booting with -v -x, I get multiple messages saying "VID: family specific matching fails" and "display: family specific matching fails", and the GUI won't come up. The laptop has a GMA950. I've copied the GMA950 driver over from iDeneb, and the Info.plist in AppleIntelGMA950.kext and AppleIntegratedFramebuffer.kext contain the necessary PCI IDs (0x27A28086 for the VGA controller, 0x27A68086 for the framebuffer driver), but it still won't boot. Other than that, my Extensions package currently contains AppleIntelPIIXATA.kext (for the ICH7 chipset), AppleSMBIOS.kext for MacBooks from iDeneb, Disabler.kext (to get rid of HPET problems), IntelEnhancedSpeedStep.kext (for SpeedStep), AppleACPIPlatform.kext (for power management) and Natit.kext (of which I'm not sure whether I need it at all). Any ideas what I can do extension-wise to get vanilla Leopard to boot? I have good general computer knowledge and knowledge of Unix, but I'm somewhat of a newbie with the specifics of OSX86. I'm ready to do some reading and listening to the experts though When I get vanilla Leopard running on the machine, I intend to post a detailed guide here. Here's some more information. My hard drive looks like this (MBR partitioning): hd(0,1): 80GB NTFS (Windows XP) hd(0,2): 700 MB HFS+ (EFI-esque, for extensions etc.) hd(0,3): 50GB Leopard target disk (contains a completely unmodified vanilla Leopard install hd(0,4) : 30GB iDeneb 10.5.5, working. I'm dual-booting using GRUB. My extensions are on hd(0,2). In setting up Leopard, I've followed this guide for EFI installation, with the only differences that I've used MBR partitions like this poster, and that I installed Leopard not by booting from the DVD, but by calling OSInstaller.mpkg from an image of the Leopard retail disk. I'm booting using the following com.apple.Boot.plist on hd(0,2): <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <string>hd(0,3)/mach_kernel</string> <key>Kernel Flags</key> <string> -v -x boot-uuid=(the UUID string for my Leopard partition, this works)</string> <key>Timeout</key> <string>3</string> </dict> </plist> I've also tried adding an EFI string for the GMA950 controller, but it made no difference (<key>Graphics Mode</key> <string>1024x768x32@50</string> <key>device-properties</key> <string>6d0000000100000001000000610000000200000002010c00d041030a000000000101060000027 ff0400100000006d006f00640065006c0000000b000000474d412039353020000000410041005000 c002c00480061007300500061006e0065006c0000000800000001000000</string>, which was what OSx86Tools gave me on my iDeneb install) Here's the output from lspci showing the machine's hardware, PCI IDs and the like: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 02) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 [8086:27d2] (rev 02) 00:1c.2 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 [8086:27d4] (rev 02) 00:1c.3 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 [8086:27d6] (rev 02) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 02) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 02) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 02) 00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] (rev 02) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02) 00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller [8086:27c4] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 02) 02:00.0 Ethernet controller [0200]: Intel Corporation 82573L Gigabit Ethernet Controller [8086:109a] 03:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG Network Connection [8086:4227] (rev 02) 15:00.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b4) 15:00.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 09) 15:00.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 18) Finally, here's the menu.lst I'm using for GRUB and double-booting. Note that GRUB has different semantics for partitions - what is hd(0,1) for the Darwin loader is (hd0,0) for GRUB, so all the numbers seem off by one: color light-gray/red yellow/light-gray timeout 1800 default /default title Windows XP on (hd0,0), find NTLDR and boot it fallback 1 find --set-root /ntldr chainloader /ntldr savedefault --wait=2 title MacOS X 10.5 "vanilla Leopard" on (hd0,2), boot from via auxiliary partition (hd0,1) fallback 2 rootnoverify (hd0,1) makeactive chainloader +1 savedefault --wait=2 title MacOS X 10.5 "iDeneb" on (hd0,3), direct boot fallback 3 rootnoverify (hd0,3) makeactive chainloader +1 savedefault --wait=2 Any ideas what I can do extension-wise to get vanilla Leopard to boot? I'd be extremely grateful.
  6. What's the last version of Apple's XCode developer tools that can be installed on 10.4.3 8f1099 with the Maxxuss patches under VMWare? I tried the version 2.2 that I was using on the institute Macs, but it won't install under VMWare, saying that the volume doesn't contain a suitable version of OS X.
  7. Would it be possible to hack up an equivalent of X.Org's vmmouse driver for better, less laggy mouse support in OS X under VMWare? It could be on the basis of the existing PS/2 driver - even as a drop-in replacement, since nobody is using a physical PS/2 mouse with VMWare. And the logic for communicating with VMWare can be taken from the X.Org driver, which is open source.
  8. No, you can't. Why would you want to?
  9. I got it working with VMWare 5.0 on a Thinkpad where 5.5 and VMWare Server would produce exactly the error you describe,
  10. What version of VMWare? I had the problem with 5.5 and VMWare Server, and it went away once I went back to 5.0.
  11. There were some threads over the last months about how it was impossible to get OS X working in VMWare on recent Thinkpads (such as this thread and this thread). I just got OS X working in VMWare on my Thinkpad X60s, and I guess it would work on most other Thinkpads, too. (It does work natively, too, but that was not what I was interested in.) The advantage of using VMWare is that a VMWare setup is easier to use productively. OS X on Intel still has some severe shortcomings, e.g. hardware support for sleep mode, power management or wireless networking, and these can be avoided in VMWare because OS X can use VMWare's virtual network adapter. Also, it's easier to switch between the Mac and Windows sides because you don't have to reboot. The disadvantage is that it is a little slower, but at least for me (and my Dual Core CPU) MacOS X in VMWare runs at acceptable speeds alongside Windows, and I don't notice much of a slowdown. The problem on the Thinkpad appears to be the way in which newer VMWare versions (since 5.5) initialise the CPU. (This is why paevm=true no longer works on Thinkpads, too.) So the trick to get it working in VMWare is actually not a trick at all but just using an older version of VMWare. I use 5.0 at the moment, for which I had an old license sitting around. On the Thinkpad, 5.0 boots OS X just finde, while 5.5 and the newer, free Server versions apparently crash on loading the gray Apple screen. You don't lose a lot by choosing the older version, either. There is no support for Intel's Vanderpool virtualisation instructions, but they aren't that much of an advantage if you only run one VM at a time. Otherwise 5.0 does the job nicely and is compatible and mature. Note that it does matter what OS X version you choose. Maxxuss suggested that there was a significant change at Apple during the 10.4.3 lifecycle (between versions 8f1099 and 8f1111) in the way memory was organised (it's all in his 8f1111 tuning guide for you to read). Hence, versions since 10.4.3-8f1111 are significantly slower under VMWare, in fact, slower by several orders of magnitude, so it looks like Apple changed this on purpose. So the version I would suggest is 10.4.3-8f1099 from the dtk-userdvd image. You don't lose that much either by choosing the older version if you're not a version junkie. I haven't tried 10.4.6 or so in VMWare yet (it runs natively, but without wireless and power management, it locks up when trying to go to sleep mode, and sound is a hassle to get working, so 10.4.3 in VMWare is actually a lot more usable in the end than 10.4.6 natively) Note also that I am in no way endorsing the usage of OS X on non-Apple Intel machines. It's illegal.
  12. Mac OSX x86 On Microsoft Virtual PC

    Yes, I have, with 10.4.3 and 10.4.6. With both versions it crashes at the gray Apple screen.
  13. Well, if the Thinkpad is the problem, then I'm out of luck, too, I guess. I'll try to reproduce the problem with a piece of slightly less illegal software and ask around on the VMWare forums, there haven't been any conclusive answers there so far. If there's anything new, I'll post here. Native 10.4.6 is working perfectly on the X60s - if I could only get VMWare to work!!
  14. The IBM Thinkpads have an embedded TPM chip for performing various security functions such as local hard disk encryption and fingerprint scanning. It could be that the Apple bootloader chokes on this TPM chip. Another option could be that the boot loader on the installation CDs is still checking or relying on some Apple hardware. Could this be the case?
  15. I'm assigning a physical partition. However, I just tried using a fixed size disk image and it makes no difference, still getting a stack fault. The choice of guest OS in the machine configuration makes no difference either. Any other suggestions? I'm suspecting that there's an incompatibility with VMWare under OS X and the Core Duo CPU. I'm definitely out of ideas now. I'll try booting the Deadmoo image once it's finished downloading, maybe that one works as it has lower CPU requirements. It would be kind of absurd, though, to be forced to run a SSE2 kernel on a SSE3 CPU. Could someone who has OS X running under VMWare post their virtual machine configuration files here (not the disk file, obviously, but the rest)? That way I could go on looking systematically where the problem is, it would be very much appreciated.
×