Jump to content

HOW TO: Installing 10.4.3 in VMWare


DeathChill
 Share

216 posts in this topic

Recommended Posts

Thats the long way around, but hey, whatever works!!

 

Jep :lol: Aaand - finally I'm done. Hoo-ray. *lol

 

It really smells like the boot-failure could come from inside the kernel. I tried every bootflag, and even -x -s does not work. I also moved out 50% of the kextfiles, including most of the IO Stuff, all USBs, FiWis, Ati related, and some plugins inside the storage device. I cleaned the cache, but it still hangs before it gets to the command prompt.

 

One thing I do not understand: Is the flashrom.c file some kind of VMWare stuff, or does it belong to the actual install?

Link to comment
Share on other sites

I just finished installing 10.4.3 in Vmware 5.5.

 

However, I realized that the installation from within 10.4.1 should not be done using the 10.4.2_exec kernel. I observed several crashdumps during the installation and 100% load. Everything went fine when I restored my 10.4.1 vmware installtion to v0.5c kernel.

 

I read on IRC and here that some observed reboots and panics. As I found no screenshot, I would like to know if anybody can boot to these pictures:

 

1043try16uu.th.png

 

(-v verbose mode set)

1043try1verbose6ai.th.png

 

If not, I could post an explanation what I done different to DeathChill's instructions (2 more steps).

Link to comment
Share on other sites

The problem with installing 10.4.3 from within 10.4.1, you will end up with the boot loader of 10.4.1 on your 10.4.3 image/parition. The boot loader ("boot" binary) of 10.4.1 does, however, not work with the 10.4.3 kernel. The reason is that the boot argument structure, which is passed from the loader to the kernel, has changed.

 

So, you have to make sure, that the 10.4.3 boot loader is set up. This is not as easy as just you think. The file under /usr/standalone/i386 is actually not loaded during boot time, but serves as the source when the disk is prepared. Unluckily, you would prepare your 10.4.3 image under 10.4.1, and thus the /usr/standalone/i386/* files of your 10.4.1 system are copied. (Note: Do not confuse this with the /usr/standalone/i386/* on the 10.4.3 installation, which indeed are 10.4.3 boot files; however they are not used during boot time, as explained above).

 

Now, the solution to this dilemma is quite easy. You would follow DeathChill's installation procedure (or your own variation), but with the following changes:

 

--

 

Before you initialize/erase the 10.4.3 target image, do this:

- (All following shell commands assume you are root or using "sudo")

- cd /usr/standalone/i386 on your 10.4.1 installation

- mkdir 10.4.1

- mv B* b* c* 10.4.1

- Unpack the files from the ZIP archive

[DMCA Violation Edited by Hagar]

and move them to /usr/standalone/i386. These are the 10.4.3 boot loader files (already patched to skip the SSE3 check).

 

DO NOT REBOOT NOW AS THIS STATE RENDERS YOUR 10.4.1 installation UNBOOTABLE.

 

Initialize/erase the 10.4.3 target image.

 

Install the 10.4.3 system on the the target image (OSInstall.mpkg)

 

After this is done, do this:

- (All following shell commands assume you are root or using "sudo")

- cd /usr/standalone/i386 on your 10.4.1 installation

- mkdir 10.4.3

- mv B* b* c* 10.4.3

- mv 10.4.1/* .

 

Copy the missing kext files (ApplePS2Controller, IOATAFamily) as described by DeathChill. (IOATAFamily is already here; I moved the 10.4.3 one to Extensions_orig and used the one from 10.4.1)

 

Optionally edit and copy the com.apple.Boot.plist from the ZIP-Archive boot-10.4.3.zip to /Volumes/XXXX/Library/Preferences/SystemConfiguration/ (XXX is the name of your 10.4.3 parition).

 

Repair your 10.4.3 image

 

In the terminal, do a

sudo bless -mount /Volumes/XXXX -setBoot

where XXX is the name of your 10.4.3 parition.

Link to comment
Share on other sites

One question about the fallowing comment on the first page:

 

Step 3: Create an ISO containing the DMG (Create an ISO that contains the DMG file! Do not convert the DMG to ISO!). I just use the Image Recorder feature in Nero and make a Data DVD.

 

How is that possible in Linux? I can use dmg2iso to convert, but according to the first post, I shouldn't do that. I do have a copy of NeroLinux installed and working if that helps. I also have wine beta installed and working in case I need to run some type of win32 app but I doubt that it will run the whole Nero Suite.

Link to comment
Share on other sites

maxxuss, tis a really cool guide! :)

 

as soon as my DL of 10.4.3 DVD completes I shall surely try this.

 

One question - do you think it is possible to work around some kinda "upgrade" of existing 10.4.1 system with that 10.4.3 DVD instead of setting a separate partition or HD (or whatever) for it?..

It would be just great!

Link to comment
Share on other sites

- Unpack the files from the ZIP archive

[DMCA Violation Edited by Hagar]

and move them to /usr/standalone/i386. These are the 10.4.3 boot loader files (already patched to skip the SSE3 check).

Does this mean...we're getting towards working 10.4.3 under VMware?

:)

Link to comment
Share on other sites

One question about the fallowing comment on the first page: How is that possible in Linux? I can use dmg2iso to convert, but according to the first post, I shouldn't do that. I do have a copy of NeroLinux installed and working if that helps. I also have wine beta installed and working in case I need to run some type of win32 app but I doubt that it will run the whole Nero Suite.

Here's the not-the-easiest-but-100%-working way, which would take about 4 minutes to complete.

 

Create another vmware drive IDE image, say with 4 gig, connect it to your 10.4.1 installation, and initialize/erase it properly. Name it "DMG 10.4.3" or whatever.

 

You would have now 3 IDE hd drives connected: your 10.4.1 system, the empty target for 10.4.3, e.g. "tiger-x86-10.4.3" (6 gb or more), and the empty drive you just created (e.g. 4 gig).

 

Then, on your 10.4.1. vmware image install the Maxxuss networking driver. Once this is done, connect to your host and download the .dmg file to this new drive "DMG 10.4.3" (under Mac OS X 10.4.1). For Windows as your vmware host, simply make your windows partitions shareable and use via Finder's "Go to Server" to connect via smb, e.g. "smb://yourhostname". For Linux use e.g. Secure Copy, scp, or enable samba.

 

Now you can use the dmg on the IDE drive. Simply double click on the dmg file. Open a new Finder window and navigate to "System/...." on the now mounted virtual 10.4.3 installer volume (the one with the eject symbol) to launch OSInstall.mpkg there (see DeathChill's instructions on this...)

 

Here's also three tips:

 

1. [EDITED] When creating a new IDE image as the target for your 10.4.3 system (the tiger-x86-10.4.3 drive), make the image pre-allocated, i.e. expand to its full size, e.g. 6gb. VMware gives you this option when you add and create a new hd image. The advantage here is, that the img file is a direct map of the drive, and you can hex edit it and transfer files via a 3rd party tool, e.g. TransMac on Windows.

 

2. Do not run 10.4.1 with the 10.4.2_exec kernel. (see my note on this in my former message.)

 

3. When you install, look for a button "Customize" (i think the 3rd or 4th page in the installer). It allows you to deselect unneeded packaged, e.g. exotic fonts, unneeded printers etc. You could save about 1 Gig of space here and accelerate installation.

 

One question - do you think it is possible to work around some kinda "upgrade" of existing 10.4.1 system with that 10.4.3 DVD instead of setting a separate partition or HD (or whatever) for it?..

It would be just great!

I don't know. For now, it's safer to use a new installation as the 10.4.3 system does not boot up correctly, and you would loose your working 10.4.1 system.

 

Does this mean...we're getting towards working 10.4.3 under VMware?

Yes. VMWare is my way to go, as I am far more productive here hacking-wise.

 

------

 

Some other notes:

 

- The screenshot above shows the exact same situation when you boot from DVD/ISO image directly under vmware.

 

- To skip the SSE3 check in the boot phase when you directly boot from DVD/ISO, you can patch the DVD directly. For this, you need to convert it to a ISO file. You can then hexedit/patch the ISO (DMG converted to ISO with e.g. UltraISO). Replace all occurrences of 68fcbe0200e8ca560000 with 68fcbe02009090909090. I found 3 hits (1 for the DVD boot loader, and two for the /usr/standalone/i386/boot, cdboot on the DVD). The locations for me were 0x14a30f3, 0x3aae48f3, 0x3aaf68f3.

Link to comment
Share on other sites

great progress maxxuss! as i haven't got vmware installed, how about installing .3 as a native installation on sse3 cpus?

 

i assume the people that have vmware installed can just create the image and 'dd it to a primary partition?

 

edit; those who booted .3 - what changed? which kexts are new, any progress on the ati/nvidia section? what about wlan drivers?

Link to comment
Share on other sites

great progress maxxuss! as i haven't got vmware installed, how about installing .3 as a native installation on sse3 cpus?

 

i assume the people that have vmware installed can just create the image and 'dd it to a primary partition?

 

edit; those who booted .3 - what changed? which kexts are new, any progress on the ati/nvidia section? what about wlan drivers?

Yes, in the long run a patch set for the DVD/ISO is the goal.

I have setup my test system to support both methods. The forthcoming patches will hopefully be applyable to the DVD/ISO and to your installed 10.4.3 vmware image.

Link to comment
Share on other sites

@ maxxus et al:

 

is it a bad idea to install the 10.4.3 boot-files you zipped onto a 10.4.1 system (no update to 10.4.3) and reboot?

 

i am asking this, since my 10.4.1 boot on an asus m2400n notebook always brings up only 7 MB of video ram, which obviously is too little for QE to run. even though the asus-hotline did swear it does bring up more video-ram for e.g. a linux boot.

 

any clues?

 

thanks and keep up the great work guys!

Link to comment
Share on other sites

Yes, in the long run a patch set for the DVD/ISO is the goal.

I have setup my test system to support both methods. The forthcoming patches will hopefully be applyable to the DVD/ISO and to your installed 10.4.3 vmware image.

 

 

this is prolly a stupid question but this is just to install 10.4.3 but it would still hang as soon as the kernel is initialized without any further patch ? i'm asking this because i've 10.4.3 already installed on a pearpc imagedisk and i've ditto it on a vmware filedisk

Link to comment
Share on other sites

by the way, i haven't modified the dvd image, but i can boot to the "please turn your device off" screen. how can i enable debug output? i would like to know why it panics... turion64/sse3 enabled

I always used

debug=0x100

 

is it a bad idea to install the 10.4.3 boot-files you zipped onto a 10.4.1 system (no update to 10.4.3) and reboot?

This would not work. The 10.4.3 "boot" binary is incompatible to the 10.4.1 kernel. Be careful here.

 

this is prolly a stupid question but this is just to install 10.4.3 but it would still hang as soon as the kernel is initialized without any further patch ? i'm asking this because i've 10.4.3 already installed on a pearpc imagedisk and i've ditto it on a vmware filedisk

Yes, currently only for the installation procedure, to get up to the situation you're in :-; However, now we are on common ground and future patches will improve the situation you're in.

Link to comment
Share on other sites

Yes, currently only for the installation procedure, to get up to the situation you're in :-; However, now we are on common ground and future patches will improve the situation you're in.

 

i see , keep up the good work i'm sure you'll be able to patch the 10.4.3 kernel and after the new oah

Link to comment
Share on other sites

well, i dont know whats different now but it won't kernel panic know..

the boot process loads a whole lot of hardware like ethernet, touchpad etc. and then hangs at this(not a 100% accurate quote):

 

-AppleIOUSBHub: Detected an awful high number of usb-hosts (8).

0x003ce322 Detected USB port 1

0x003ce342 Detected USB port 2

0x003ce362 Detected USB port 3

0x003ce382 Detected USB port 4

Still waiting for root device.

Still waiting for root device.

Still waiting for root device.

Still waiting for root device.

Still waiting for root device.

 

i've broke the loop, maybe it will recieve a timeout someday but i didn't want to wait, maybe someone could take a look into the sources and check if it gets a timeout or it's stuck in the loop..

if i don't boot with -v it will display the apple logo, spinning pie and everything fine and gets stuck at the beachball mouse ( i guess when its looking for the usb root)

 

booting with -x recieves an instant kernel panic and "debugger not available"

 

sadly i cannot disable the usb host since my laptop bios is very limited

Link to comment
Share on other sites

Here's the not-the-easiest-but-100%-working way, which would take about 4 minutes to complete.

 

I may have misread the original post. I was assuming that we extract the content of the dmg file and copy the extracted files to the new ISO created by the burning software. At the end, I did manage to understand the what DC was getting at. NeroLINUX will only burn with .nrg and I didn't want to take the chance in renaming the the extention to ISO. So I did some research and found that K3b does a wonderfull job in creating DVD ISO.

 

- To skip the SSE3 check in the boot phase when you directly boot from DVD/ISO, you can patch the DVD directly.....

I am dangerously running out of room. But I think this part is vital to SSE2 chips. Thanks for the tip!

 

Lastly, I am trying to mount the 10.4.1 DVD ISO using the mount command, yet have yielded no luck. Are there any other mount options to add other than:

 

sudo mkdir /media/iso

sudo modprobe loop

sudo mount osx1043.iso /media/iso/ -t iso9660 -o loop

 

I have not been able to successfully mount the ISO in Linux VMware. Burning the ISO is out of the question because... Well, I don't have a DVD burner.

Link to comment
Share on other sites

Does that mean, that to install it native, we could also 1. install the new Darwin, 2. then mount the dev/cdrom from there, and... hmm, 3. i did not managed to get the .mpkg to run in the command line. Does it require an OSX shell? I read the instructins from the 10.4.1, at googlecache, that bender0 gave to deathchill (I do not mean the hex stuff), but I dont know if this would be possible here, too... :(

Link to comment
Share on other sites

maxxuss, on my motherboard an asrock P775-915gl, with the 10.4.3 dev dvd I was getting an instant reboot at the Starting Darwin/x86 message. I was poking around the bios and found the No-Execute Memory Protection was disabled, I enabled it.

When I booted from the dev dvd again, I could now get all the way to the blue screen with spinning beachball.

I don't know if this helps you at all, but this is what I saw.

Link to comment
Share on other sites

Maxxuss I followed your instructions and also reinstalled twice in vmware to be sure.I get the same panic with or without your patched bootloader and files.I have a P4 3.0E pinset 478.I have to guess its because my cpu does not support DX.here is the usual vmware crash

_________________________________________________________

 

Nov 05 16:13:52: vcpu-0| NOT_IMPLEMENTED C:/ob/bora-16958/bora/devices/misc/flashram.c:502

Nov 05 16:13:52: vcpu-0| Backtrace:

Nov 05 16:13:52: vcpu-0| ----Backtrace using dbghelp.dll----

Nov 05 16:13:52: vcpu-0| Module path: C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe

Nov 05 16:13:52: vcpu-0| Module directory: C:\Program Files\VMware\VMware Workstation\bin\

Nov 05 16:13:53: vcpu-0| backtrace[00] ebp 0x0b25fae0 eip 0x00435cca params 0x00439db0 0000000000 0x0b25ff04 0x00413dad [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x00034cca] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[01] ebp 0x0b25faf0 eip 0x0043a4e6 params 0000000000 0x0b25fb04 0x08f66d94 0x5f544f4e [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x000394e6] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[02] ebp 0x0b25ff04 eip 0x00413dad params 0x005cb8ac 0x006be9a0 0x000001f6 0x0b25ff34 [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x00012dad] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[03] ebp 0x0b25ff18 eip 0x004e246e params 0x08f56240 0x00000001 0x003fd808 0000000000 [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x000e146e] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[04] ebp 0x0b25ff34 eip 0x005acdeb params 0000000000 0x003fd800 0000000000 0x0000015a [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x001abdeb] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[05] ebp 0x0b25ff50 eip 0x005ac2f3 params 0x08f27228 0x003fd800 0x0000015a 0x00000001 [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x001ab2f3] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[06] ebp 0x0b25ff7c eip 0x005b491b params 0x02000000 0x0b25ffb4 0x0043aa17 0000000000 [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x001b391b] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[07] ebp 0x0b25ff88 eip 0x005ac32c params 0000000000 0x00000038 0x00000020 0x0012fc8c [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x001ab32c] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[08] ebp 0x0b25ffb4 eip 0x0043aa17 params 0x0012fc8c 0x00000038 0x00000020 0x0012fc8c [C:\Program Files\VMware\VMware Workstation\bin\vmware-vmx.exe base 0x00400000 0x0001:0x00039a17] (no symbol information)

Nov 05 16:13:53: vcpu-0| backtrace[09] ebp 0x0b25ffec eip 0x7c80b50b params 0x0043a9c0 0x0012fc8c 0000000000 0xffffffff [C:\WINDOWS\system32\kernel32.dll base 0x7c800000 0x0001:0x0000a50b] (GetModuleFileNameA + 0x01b4)

Nov 05 16:13:53: vcpu-0| ----End of backtrace----

 

full log attached

Link to comment
Share on other sites

Maxxuss I followed your instructions and also reinstalled twice in vmware to be sure.I get the same panic with or without your patched bootloader and files.I have a P4 3.0E pinset 478.I have to guess its because my cpu does not support DX.here is the usual vmware crash

Could you explain what you see in -v mode (or make a screen shot). Also, what's your exact CPU spec?

Also, can you boot with -v and look for a message "CPU extended features:" on the Darwin screen. (Alternatively, look what is written to 10.4.3 system.log). What does it say?

 

----------

 

Here's an update of the current state. VMWare boots into the blue screen and then hangs:

1043try2a3zh.th.png

 

A problem however is that the ApplePS2Controller kext is missing in 10.4.3. So in single user mode you could not use your keyboard. from The 10.4.1 version (originally from Darwin 8.0.1) does not work as this picture shows:

1043try2b8bp.th.png

 

Has anyone a idea? We would need the 10.4.3 (Darwin 8.3) kext, compiled on a 10.4.3 or maybe Darwin 8.3 system. Can anybody provide this?

 

BTW: Here's the current 10.4.3 maxxuss kernel (10.4.3-test2). It contains SSE3->SSE2 patches (both the old and some new ones): Removed content violating DMCA

Edited by Metrogirl
Link to comment
Share on other sites

If one of the problems is booting up, as the 10.4.1 gets mixed up with 10.4.3 causing .3 not to work, would formatting the master boot record(Using a dos boot disk, or something of that nature - similar to removing lilo or grub after uninstalling *nix) and installing darwin 8.3 then trying to install 10.4.3 via VMWare and dd it from windows work?

Link to comment
Share on other sites

If one of the problems is booting up, as the 10.4.1 gets mixed up with 10.4.3 causing .3 not to work, would formatting the master boot record(Using a dos boot disk, or something of that nature - similar to removing lilo or grub after uninstalling *nix) and installing darwin 8.3 then trying to install 10.4.3 via VMWare and dd it from windows work?

Do you have a Darwin 8.3 install CD? (see my former posting with the question concerning the ApplePS2Controller kext).

Link to comment
Share on other sites

 Share

×
×
  • Create New...