Jump to content

[How To] Install Leopard Retail DVD on ASUS P6T Deluxe LGA 1366 (core i7)


M J
 Share

925 posts in this topic

Recommended Posts

What version of retail DVD's are you guys having success with?

 

I've tried "images" of retail 10.5.4 dvd and 10.5.6 dvd to no avail. both 10.5.4 and 10.5.6 images install perfectly on my P5E/Q9450 machine

 

I've followed MJ's latest instructions (as of 5/5/09) to the tee, and no luck.

 

I did however get iDeneb 1.3 fully working with HT and all 4 cores, I just couldn't upgrade it to 10.5.6 with DSDT.aml patch nor with IntelCPUMdisabler.kext :unsure:

 

The farthest I've gotten is with my 10.5.4 "retail" dvd. It gets all the way to the end of the installation and then this error (see pic) :) . I selected that boot drive with the Startup Disk Utility just after this error and it still won't get to the installation setup pages after rebooting with boot 132 iso...

 

 

 

IMG_2621.jpg

 

 

I'm running a P6T Deluxe V2

i7-920

Corsair Dominator 1600 6gb

9800GT 512mb

 

Was also wondering why we can't use a boot 132 iso that has the extensions and kernel already implemented so we don't have to type rd(0,1)/mach_kernel.voodoo busratio=20 -v -f rd=disk1s3

etc... I mean I've memorized that line by now after trying to install 92029391483048340 times already, but it's still a pain in the butt.

 

with my P5E/Q9450 system,

I just boot up with my boot 132 iso CD

install 10.5.4 or 10.5.6 dvd

reboot with 132, finish install

restore extensions from boot 132 image

install chameleon

and voila...

 

with my P6T, should I be trying 10.5.0 or 10.5.1 dvd's instead of 10.5.4 or 10.5.6?

any help would be greatly appreciated! keep up the good work guys

Link to comment
Share on other sites

Hi.

 

The such an error message is completely ok if it is displayed after the installation (all the files are copied and it trying to finalize the installation) - I got that too.

 

I think the trouble with many leopard images is that some are not the generic ones but are modified to specific hardware such as a mac book or mac book air. I have not had luck with those either. I think the version does not make much difference, except that there have been problems reported with 10.5.6.

If you can just get the 10.5.0 and make sure its a generic original release not tailored to a specific mac hardware.

 

After the error you got just continue with point D. [reboot into your system]

Try that and report if you get further problems.

 

If the error displayed already happens as it starts the real installation (that is, comping the files to disk), then this is another problem. I solved this by installing to a seperate disk only for mac where I create partitons with the disk tool that is available with the installer.

I'm sure it's possible on just a new partition on an existing disk with other (windows) partitions, but I can't help with that.

 

Cheers, Morke

 

What version of retail DVD's are you guys having success with?

 

I've tried "images" of retail 10.5.4 dvd and 10.5.6 dvd to no avail. both 10.5.4 and 10.5.6 images install perfectly on my P5E/Q9450 machine

 

I've followed MJ's latest instructions (as of 5/5/09) to the tee, and no luck.

 

I did however get iDeneb 1.3 fully working with HT and all 4 cores, I just couldn't upgrade it to 10.5.6 with DSDT.aml patch nor with IntelCPUMdisabler.kext :unsure:

 

The farthest I've gotten is with my 10.5.4 "retail" dvd. It gets all the way to the end of the installation and then this error (see pic) :) . I selected that boot drive with the Startup Disk Utility just after this error and it still won't get to the installation setup pages after rebooting with boot 132 iso...

 

 

 

IMG_2621.jpg

 

 

I'm running a P6T Deluxe V2

i7-920

Corsair Dominator 1600 6gb

9800GT 512mb

 

Was also wondering why we can't use a boot 132 iso that has the extensions and kernel already implemented so we don't have to type rd(0,1)/mach_kernel.voodoo busratio=20 -v -f rd=disk1s3

etc... I mean I've memorized that line by now after trying to install 92029391483048340 times already, but it's still a pain in the butt.

 

with my P5E/Q9450 system,

I just boot up with my boot 132 iso CD

install 10.5.4 or 10.5.6 dvd

reboot with 132, finish install

restore extensions from boot 132 image

install chameleon

and voila...

 

with my P6T, should I be trying 10.5.0 or 10.5.1 dvd's instead of 10.5.4 or 10.5.6?

any help would be greatly appreciated! keep up the good work guys

Link to comment
Share on other sites

I don't really know how to fix your EFI parition. You might be able to do it in single user mode, using fdisk that comes with the chameleon or EFI_boot installations, but I'm no expert.

 

About the vista bootloader - I did nothing. I actually tried some stuff with EasyBCD, but eventually undid everything. My main bootloader is chameleon 2 RC1 on the Leopard drive's EFI partition - that's where I can choose to boot from the Vista partition which only has the single Vista entry in its boot loader.

The only guide I followed is the one for installing Chameleon on the EFI partition.

Link to comment
Share on other sites

Ok, thanx for the info.

 

I'll try chameleon. Does it provide the fuctionality to easily add boot option for vista? If it is not apparent and easy how to do that, can you tell me how?

 

With single user mode do you mean the startup with the -s option which does not boot into gui but provides command prompt?

Link to comment
Share on other sites

Hi all!

 

Not posted really anywhere on here before, and I have been struggling to get a friends ASUS-P6T Deluxe up and running smoothly using a vanilla cd install.

 

I use an already running Mac to install OSX 10.5.6 to a hard drive, then install Chameleon into the EFI partition and have several kexts in there to do their 'magic' as it were. I've been at this a while and am now looking at a near perfect Mac desktop. (Thanks to lots of guys on here, in this topic and in the Gigabyte X58 topic also)

 

Couple of things puzzle me - in the boot.plist in the EFI partition I have had to add the -f flag in. If I don't put it in, my ethernet will show on next reboot but say no cable is plugged in. Also, I'll get orange hard drive icons. If I then reboot with the flag -f intact, icons revert back to normal metal ones, and ethernet comes back as normal.

 

Sound seems to stay unaffected luckily. Other things of interest are that my e-sata port works initially (Chameleon sees it and gives it me as a boot drive option) but when Mac OS has started it doesn't seem to get picked up. USB can be flaky too - sometimes if a USB drive is plugged in at boot it will work fine, if no USB devices are plugged in at boot if you then plug one in nothing gets picked up. Any ideas?

 

I could probably revert to moving certain kexts over to the S/L/E location, and have everything working but I am aiming at having an untouched OS X system - is this even possible really?

 

Over my experimenting, I have had different results - swapping out kexts and so forth. I've had USB behaving at one point, e-sata working but I don't really know enough about which kext deals with what.

 

Heck, I only just learnt that to get the kexts on the EFI drive to 'override' the kexts on the S/L/E I had to change version numbers! (Thats how I got sound working, spent ages and was happy once I had that up and running...lol)

 

It's all fun though, and I've certainly learnt a lot. Oh one last thing, for shutdown to work properly am I right in thinking I need the OpenHaltRestart.kext on the EFI partition too? Restart works fine, but shutdown I just get the computer screen going off, and some tower lights but the fans stay on. - I then have to reboot to turn off properly with the switch.

 

Cheers anyway, and apologies for going on but I've been at this a while now and would appreciate further insights.

 

If you need to know what kexts I am using on the EFI partition they are as follows:

AD2000b.kext <= audio patcher

AppleACPIPlatform.kext <= was getting 'using 16384 buffer' error before using this

AppleDecrypt.kext <= magic :rolleyes:

AppleSMBIOS.kext <= sorts out some system info stuff

Disabler.kext <= magic ^_^

HDAEnabler.kext <= sound patcher

LegacyAppleAHCIPort.kext <= not sure on this

LegacyAppleIntelPIIXATA.kext <= not sure on this either

LegacyAppleYukon.kext <= network patcher

LegacyHDAPlatformDriver.kext <= audio patcher

LegacyIOAHCIBlockStorage.kext <= not entirely sure about this - fixes drive icons?

LegacyJMicronJMB36xSATA.kext <= just realised i shouldn't be using this! could be my issue with esata?

System.kext <= matches running kernel (9.7.0)

seatbelt.kext <= stops kernel panic on DMG files

 

Addition:

Took out the LegacyJMicron kext above, and added OpenHaltRestart, but no change - still have sleep/shutdown issues. E-sata port no change either - I think it maybe using a Marvell chipset for the e-sata so I will hunt around for a kext for it. Random DMG files are causing Kernel Panics (examples: Firefox, Transmission) but other DMGs work fine (and yes, I have replaced seatbelt.kext with 10.5.5 version in both EFI partition and S/L/E and ensured my mach_kernel & system.kexts match).

 

More Additions:

Edited the plist in LegacyAppleAHCIPort, and copied an existing entry in there and pasted it towards the bottom. Changed the hardware id to match the Marvell controller, and the device descriptions, and then updated the kext in my EFI. Repaired permissions, rebooted and I now have e-Sata working and the Marvell controller showing in the system profiler.

 

USB still plays up, but I can live with that for now. Still getting kernel panics with some DMG files, so going to start experimenting with seatbelt/system kexts and different kernels to see if can stop it altogether - just need to find a 10.5.5 seatbelt.kext. The one I had downloaded when I looked at it didn't seem to have right information, so have binned that for now. I might even try booting without System.kext and seatbelt.kext present in EFI and see what that does.

 

Further Additions:

Seems I had a mismatch of System.kext, mach_kernel & seatbelt.kext. As long as all three match (ie are for the correct kernel you are running) you shouldn't get dmg file kernel panics. Mine is now resolved, and im now using the 10.5.7 kernel updated system & kernel. Not tested sleep yet, but I don't hold out much hope. Also noticed a post regarding the DSDT patch, apparently I may have done that wrong...looks like I need to do a force compile on it. Maybe thats why the ASUS-P6T system doesn't run as quick as it should? I'll try and give it a whirl.

 

Hey I'm doing well. answering most of my own questions. Great isn't it? I'd still be waiting at root device if I was looking for answers elsewhere. :D

Link to comment
Share on other sites

I have got a new hopefully not unique problem:

 

running the DSDT patch exactly as described on page 1, placing the resulting dsdt.aml into the root directory as /DSDT.aml and

 

enabling all cores or disabling all cores again booting gets stuck with the last message:

 

"using 10485 buffer headers and 4096 cluster IO buffer headers"

 

erasing /dsdt.aml resolves it, but of course there is only on core without HT

 

 

Thanks in advance

Link to comment
Share on other sites

So...

I've gotten to Section D-Note 3.

I got the "do you own a mac" loop.

Rebooted with -s append

 

did this:

 

/sbin/mount -uw /

 

passwd root

 

type a password you choose here

 

touch /var/db/.AppleSetupDone

 

reboot

 

After reboot enter with the root account and setup your user account. Don't use the root account!

 

rebooted with this

rd(0,1)/mach_kernel.voodoo busratio=20 -legacy -v -f disk0s2

and I'm stuck here...

 

IMG_2624.jpg

 

I'm not really sure what this means... "After reboot enter with the root account and setup your user account. Don't use the root account!"

 

did I mess up by trying to reboot with this "rd(0,1)/mach_kernel.voodoo busratio=20 -legacy -v -f disk0s2"?

 

Any ideas?

Link to comment
Share on other sites

Chamaleon works.

However:

- how can i modify the icons presented for booting as many of them do not make sense, and how to set a default?

- Networking is not working, and it did with the old boot loader? I modified the Info.plist for Yukon as described in the initial post. I copied all the .kext files, but maybe this is not enough?

 

Pleas help

 

are they on the same drive?

 

I got vista and leopard to dual boot on two different drives by installing Chameleon 2 RC1 on the EFI partition of the OS-X drive. works like a charm.

I followed this guide:

http://www.insanelymac.com/2009/04/how-to-...ameleon-20-rc1/

 

I tried EasyBCD but got nowhere.

Link to comment
Share on other sites

I have got a new hopefully not unique problem:

 

running the DSDT patch exactly as described on page 1, placing the resulting dsdt.aml into the root directory as /DSDT.aml and

 

enabling all cores or disabling all cores again booting gets stuck with the last message:

 

"using 10485 buffer headers and 4096 cluster IO buffer headers"

 

erasing /dsdt.aml resolves it, but of course there is only on core without HT

 

 

Thanks in advance

 

Are you sure you are booting with the bootloader of the mac partition? I think the DSDT fix is only applied in this case, and not when you boot in from a CD.

 

Meaning: you have to apply the DSDT and the EFI bootloader and actually boot from that one for the DSDT fix to be used - at least this is my understanding.

 

So...

I've gotten to Section D-Note 3.

I got the "do you own a mac" loop.

Rebooted with -s append

 

did this:

 

/sbin/mount -uw /

 

passwd root

 

type a password you choose here

 

touch /var/db/.AppleSetupDone

 

reboot

 

After reboot enter with the root account and setup your user account. Don't use the root account!

 

rebooted with this

rd(0,1)/mach_kernel.voodoo busratio=20 -legacy -v -f disk0s2

and I'm stuck here...

 

IMG_2624.jpg

 

I'm not really sure what this means... "After reboot enter with the root account and setup your user account. Don't use the root account!"

 

did I mess up by trying to reboot with this "rd(0,1)/mach_kernel.voodoo busratio=20 -legacy -v -f disk0s2"?

 

Any ideas?

 

Have you tried booting with the -x or -legacy option appended to the existing ones?

 

Also make sure that you really specified the right rd=diskXs2 option - if you have multiple harddrives this X number may be different on every boot up depending on the order each harddisk is detected when you start up your pc. I provided the wrong option (of a windows partiotion) once or twice which caused such a panic.

 

I was also unclear about "After reboot enter with the root account and setup your user account. Don't use the root account!" at first.

It means that after you reboot (and it works) you will go into graphic mode again and will be presendted with a login window. Enter root as username, and as password the password you entered on the command line before.

 

Then go in to the system setting and click on users. There click on the + button to add a new user which you will commonly use (for instance, enter your own name as the user name).

After you created the user log out (restart is not required). In my case I got to the console again where it mentioned it is starting login again, which takes a bit. Then the graphic screen is started up again and you will see the user you just created which you can click (and enter your password if you have set one) to log in with that user.

Link to comment
Share on other sites

P6T Deluxe V2, running Bios 0302.

Bios configured as noted

SATA DVD (tried multiple ports, except 0)

SATA 250GB HD (tried multiple ports)

Retail 10.5.6

 

Able to see the DVD during the 'F8, ESC, Return', but...

Dreaded 'waiting for root' issue. Tried every diskXs3 combo, each multiple times (with and without -legacy).

 

Also note: in the bios you can control the order of your disks in the Boot -> Boot Hard Disk menu, which is different then a previous post about the order being 'random due to device ready time'.

 

So, forget rd, lets try boot-uuid. Yanked the UUID from the retail DVD and tried boot-uuid instead of rd, bummer, no luck. (FYI: if you want to know how I got the UUID without a running Mac, let me know, I'll post the details)

 

Ok, how about installing from a hard drive? So, booted up via trk (linux USB distro) and copied the install DVD to the HD via 'dd if=/dev/sr0 of=/dev/sda'. Copied 8.1 GB to the disk.

 

Then, Slimboot to F8, ESC, 80 (which is the first hard drive), it found the 'Install DVD' (yeah!) and with a rd=disk0s3 we got to the installer!!

 

Note: during the boot to the installer, it stalled after printing something about 'AppleIntelCPUPowerManagement'. It continued to hit the disk randomly, and continued after about 7 mins.

 

Once in the installer, opened up DiskUtil. It took several minutes to 'Gather' the disk information.

 

And of course, could't modify the partitions on the HD (maybe because it was the boot device, maybe because of copying the CD that way). No biggie, figured it wouldn't work anyway but was secretly hoping to be able to extend/add a partition to install to.. oh well, at least we go to the installer, one more step futher.

 

So, shutdown, added a new HD (port 1), booted into trk, copied the DVD again. I also wiped the start of the orig HD just to make sure I didn't confuse things later with a 'dd if=/dev/zero of=/dev/sda'.

 

Checked the Bios for disk port setup, rebooted with the Slimboot, F8, ESC, 81 (hard drive 2), says 'Install DVD', then used rd=disk1s3 and, whoa, got the 'waiting for root' again?? Hmm..... it said it found the DVD on the HD... Lets try disk0s3.. nope...

 

Interesting... between not finding the real DVD, and not finding the DVD on the second part I'm starting to wonder if there is something broken here.... I didn't check using the DVD on port 0, but I would bet money it would have worked.

 

Ok, fine, lets switch ports putting the HD with the DVD copy on port 0, and the dest HD on port 2. Yeah, it found it!

 

Oops, not so fast... It stalled out at AppleIntelCPUPowerManagement, but after waiting the 7 mins as previously, then 30, then 60, then 2 hours it's obviously not going to recover. Hmmm... the new HD with the DVD copy is quite larger-- 1.5 TB. Maybe that has something to do with it? Lets check. Yanked the 1.5TB, and put a 40GB in it's place. Copy the DVD again with dd, and Slimboot.... interesting-- took 3 mins this time... 3 mins for a 40GB HD, 7 mins for a 250GB, and who knows how long for a 1.5TB... something weird here...

 

Ok, back to the install. Got to the DiskUtil, shows the 40 GB, shows my 250 GB where I'm going to put OSX. Selected the 250, setup 1 partition, full disk, Journaled, and waited. And waited. And waited. Wonder if it hung? Try again, reboot, back to here, and waited. Hmmm.. something weird. Ok, boot was slow due to size of disk, maybe this is slow too so lets wait. Come back 12 hours later... same place. Forget this.

 

Yanked the 250GB, attached an external USB drive (internally is an IDE), and Slimboott...etc, and am now running OSX.

 

Haven't switch to the EFI partition yet, but did apply the net and HDA fixes. The HDA fix causes OSX to complain. Backing out the fix and it stops complaining. Haven't researched yet..

 

AND, still want this running on the internall 250GB... that will be the subject of a future post....

Link to comment
Share on other sites

Chamaleon works.

However:

- how can i modify the icons presented for booting as many of them do not make sense, and how to set a default?

- Networking is not working, and it did with the old boot loader? I modified the Info.plist for Yukon as described in the initial post. I copied all the .kext files, but maybe this is not enough?

 

Pleas help

 

How did you get Chameleon to work? I've been able to boot -x and just went through the EFI partition guide here

 

http://www.insanelymac.com/forum/index.php?showtopic=127330

 

problem is my machine/terminal lock up, so I can't do all of the commands at once :/

 

Is there an easier way to install with Chameleon? I know there's some options in the Chameleon 2.0 setup that I've never messed with

 

Update: Ugh, my terminal work didn't work and can't even get in with -x now :lol:

 

I'm looking at the Custom Install settings on Chameleon 2.0 There's this option available

"Chameleon EFI HFS - Install Chameleon to EFI System partition HFS (reformatted)" I'm assuming this would work somehow? Would I just do Phase 1 on the EFI tutorial, or not even need to do that, and pick this setting....?

Link to comment
Share on other sites

How did you get Chameleon to work? I've been able to boot -x and just went through the EFI partition guide here

 

http://www.insanelymac.com/forum/index.php?showtopic=127330

 

problem is my machine/terminal lock up, so I can't do all of the commands at once :/

 

Is there an easier way to install with Chameleon? I know there's some options in the Chameleon 2.0 setup that I've never messed with

 

Update: Ugh, my terminal work didn't work and can't even get in with -x now :(

 

I'm looking at the Custom Install settings on Chameleon 2.0 There's this option available

"Chameleon EFI HFS - Install Chameleon to EFI System partition HFS (reformatted)" I'm assuming this would work somehow? Would I just do Phase 1 on the EFI tutorial, or not even need to do that, and pick this setting....?

 

The link you posted describes the installation of another boot loader, not the Chameleon one.

So please be sure what you talk about.

 

For instructions on the Chameleon boot loader check here:

http://www.insanelymac.com/2009/04/how-to-...ameleon-20-rc1/

 

However there is an installer for Chameleon 2.0 RC1 now, just search for it.

I have not tested it however.

 

I don't know what your problems are however.

I just followed instruction and never had problems with the bood loader itself.

 

I just urge you to stay away from EasyBCD (if you have Vista, it destroyed many of my paritions and currently I can neither boot into Vista nor Mac).

 

If you want more help I advise the following:

Stick to the instructions on the first post of this thread and try to get that running.

 

Afterwards you can switch to the Chameleon boot loader if you want.

 

If you have problems then tell me after which step the problems begin and how they look exactly.

Link to comment
Share on other sites

Hi everyone...

Today I tried to get into macOSX but... after some wins, I eventually get stuck at a really earlier point:

 

During installation, after the "print y to continue" I get this panic... [see the attachment]

 

I tried appending -x

 

Obviously I've a P6T Deluxe, a i7 920, 3x2gb DDR3 Corsair Dominator @1866 (running @1066mhz) and a Asus GTX260... but the problem is that I made some errors, but I don't understand what I've done wrong!

 

Help me!

 

PS: Sorry for my non-perfect english, is quite acceptable, but I'm Italian. ! Byez and thanks in advance.

 

PPS: M J are you italian too?

post-423470-1241912930_thumb.jpg

Link to comment
Share on other sites

So... I got my retail 10.5.6 dvd installed. Got through step F in the tutorial, tried to reboot and get a blinking cursor like there's no boot loader and I'm 99% sure I followed the tutorial correctly. I don't know what else to do besides performing Seppuku on myself :rolleyes:

 

I started chat rooms in irc.insanelymac.com #LGA1366 and irc.osx86.hu #LGA1366 if anybody wants to go in there and help out... I'm 'taq' in there.

Link to comment
Share on other sites

Chamaleon works.

 

how did you get chameleon to work with the insanelymac tutorial? I followed the same tutorial for the efi partition guide and it would hang when loading mac osx (it worked fine with the tutorial in this how to). or did you follow the first set of instructions? what do you mean by installed into the efi partition? Perhaps mine was broken because I used their packaged installer first and it messed something up? did you do anything special with the com.boot.plist file?

thanks for any help.

 

these are the instructions I followed:

 

1. Extract the Chameleon archive and open a Terminal window there.

 

 

 

2. Use sudo -s to own root privileges.

 

 

 

3. Mount the EFI partition:

 

mkdir /Volumes/EFI && mount_hfs /dev/disk0s1 /Volumes/EFI

4. Install boot0 to the MBR:

 

fdisk -f boot0 -u -y /dev/rdisk0

 

5. Install boot1h to the bootsector of your EFI partition:

 

dd if=boot1h of=/dev/rdisk0s1

6. Copy the ‘boot’ file to your root partition:

 

cp boot /Volumes/EFI

7. Make sure your EFI partition is flagged as active.

 

 

 

8. Copy Themes and smbios.plist to your Extra folder:

 

cp -R smbios.plist Themes /Volumes/EFI/Extra

9. Copy any kexts to /Volumes/EFI/Extra/Extensions and your com.apple. Boot.plist to /Volumes/EFI/Extra and DSDT.aml to /Volumes/EFI/DSDT.aml

Link to comment
Share on other sites

If anybody got a Rampage or P6T6 Work Station (like me) Patch your DSDT this WAY

 

cd Desktop/DSDT_Patcher1 change directory to wherever you unzipped the patcher

 

nano Debug/dsdt.dsl open and modify the patched dsdt

 

delete the lines that start with Alias

 

Press Ctrl+O (that's the letter "o") and [ENTER] to save the file, then press Ctrl+X to close nano.

 

./DSDT\ Patcher Debug/dsdt.dsl -f (add -f or it won't wok !!!!!!!!!!!!! )

run the patcher again (you will get 3 errors about files not existing or already existing, that's fine, don't worry about it)

 

cp dsdt.aml /DSDT.aml copy the DSDT to the root directory

 

You'll have 4 core and hyper threading !!! my boot time was 7 to 10mn, now it's about 12sec and computer fast as hellllllll

 

thanks to jimmydigital00

Link to comment
Share on other sites

I have now spent upwards of 2 weeks with the P6T V2 and the 132 method and can't Consistently get over the "still waiting for root device" - the os trying to recognize its bsd root. Installing/booting to a given volume may work once or twice, then only again every (unknown) tries which might be dozens. The issue is not finding the right disk[partition] target, rather something which is not well understood.

 

I have tried everything conceivable including the hints at these pages dedicated to the problem:

http://wiki.osx86project.org/wiki/index.ph...for_root_device

http://www.iclarified.com/entry/index.php?enid=1119

 

- switching sata ports

- different hds, partitions

- different hd order

- boot flags including cpus=1, single user mode

- boot via ideneb dvd

- boot via chameleon

- 132 disks (various)

- turning off all cpus features/cores

- switch to ide in bios

- different intall media

- new 10.5.7 kernel

- reducing number of drives to dvd+hd

- add/delete various extensions

- delete/create kernel etc. caches

- disk check

- fdisk setting boot partition

- removing ram

- UUID of root hd in boot plist file (appended)

- IDE drive connected, Marvell controller enabled (appended)

 

the only repeatable way for me to boot into an install/maintenance system is from the ideneb dvd

 

pt6 v2 latest bios, 12gb, 1,5tb seagate sata, 250 gb seagate, sata dvd, 920 d0, 9800gt

 

 

It can't be that this can not be resolved. If you have any hints please edit

http://wiki.osx86project.org/wiki/index.ph...for_root_device

 

and post it to the forum (not only the forum). I will next try to attach an ide hd.

 

 

*** Possible Resolution ***

Use of patched ICH10 SATA Kext and IDE Mode . It worked, but other items were changed also in this iteration, so it could be something else also.

http://www.insanelymac.com/forum/lofiversi...hp/t129222.html

Link to comment
Share on other sites

I have now spent upwards of 2 weeks with the P6T V2 and the 132 method and can't Consistently get over the "still waiting for root device" ....

 

Did you read my recent post? Did you try your DVD drive on SATA port 0? Have you tried two hard drives, one with a copy of the DVD on port 0, the second for the installation on port 1?

Link to comment
Share on other sites

I have now spent upwards of 2 weeks with the P6T V2 and the 132 method and can't Consistently get over the "still waiting for root device"

 

The only way I've found to reliably boot on any given volume (either the installation DVD, or the partition I eventually managed to install on) was if I used the "boot-uuid={your UUID}" instead of the "rd=diskXsY" method.

 

You'll need a running mac to get the UUID for the install DVD you're using (get info from disk utility), but after you get it to work once, you can get the new UUID of your new installation, and put that in your boot.plist in the kernel flags.

 

My BSD drive names still change pretty randomly, but it doesn't affect my booting.

Link to comment
Share on other sites

Did you read my recent post? Did you try your DVD drive on SATA port 0? Have you tried two hard drives, one with a copy of the DVD on port 0, the second for the installation on port 1?

 

yes - my summary post is now updated with it

 

The only way I've found to reliably boot on any given volume (either the installation DVD, or the partition I eventually managed to install on) was if I used the "boot-uuid={your UUID}" instead of the "rd=diskXsY" method.

 

You'll need a running mac to get the UUID for the install DVD you're using (get info from disk utility), but after you get it to work once, you can get the new UUID of your new installation, and put that in your boot.plist in the kernel flags.

 

My BSD drive names still change pretty randomly, but it doesn't affect my booting.

 

done that with the UUID of the root partition, still "still waiting for root device"

Link to comment
Share on other sites

Has anyone got the "boot1: startupfile" error message when trying to boot from hard drive?

 

I am running leopard retail 10.5 on a Asus P6T deluxe. 1 Sata HD, 1 Sata DVD Drive. 6gb ram, 920. One core active, HT off.

 

I copied all of the kext files from this thread to my EFI Extensions folder and the voodoo kernel, dsdt.aml, and the plist file to my EFI partition as well.

 

I can boot with the boot CD still, but for some reason I can't get it to boot from the hard drive. I have reinstalled Leopard (steps A - E) more than six times in attempt to complete step F. I have at least become familiar with Terminal now, but still can't boot from EFI.

 

Here is exactly what I see?

 

 

 

boot0: 6PT

 

boot0: HFS+

 

boot0: booting

 

boot0: done

 

boot1: startupfile_

 

 

 

I did install the new Chameleon 2.0, so maybe that caused some issues - I've tried without it though, so I don't think it is part of the issue.

 

Any help would be grately appreciated. I've been at this for weeks now!

 

FYI - Encore b/g/n Wireless PCI card working & my old EVGA 7800gt working!

Link to comment
Share on other sites

You'll need a running mac to get the UUID for the install DVD you're using (get info from disk utility),...

 

There is another way....if you have a linux install (and if you don't, you can probably find a decent live CD to boot up with)

 

Going from memory, so the commands may not be exactly right:

 

Booted up into Linux with the Retail DVD in your drive, and as root:

 

(mount the DVD to a loopback device)

losetup /dev/loop0 /dev/sr0

(if need be, replace /dev/sr0 with your DVD device)

(now map the partition table found on the loopback device to actual device nodes)

kpartx -av /dev/loop0

(not, some live CDs don't always include kpartx, but depending on the live CD you might be able to install it)

(it should now list the partitions it found)

(to verify all is good so far, file one of those new device notes:)

file -s /dev/mapper/loop0p2

(this tries to identify the third partition on the DVD-- which is 'hidden'. Partitions are 0 based. 0 should be the partition you see if you put the DVD in when booted under windows. The output should be something about HFS or HFS+)

(you can even mount it if you have HFS in your kernel:)

mount /dev/mapper/loop0p2

 

(but what you really want is:)

vol_id /dev/mapper/loop0p2

 

 

 

done that with the UUID of the root partition, still "still waiting for root device"

 

 

Hmmm.. I'm not quite clear on your issue here.. Are you trying to install or boot to an already installed OS?

 

If your trying to install, the root device being waited for is the installation DVD, slice 3. That is the UUID you need.

 

 

 

 

M J (or anyone else for that matter):

 

Question for you:

 

1) The voodoo kernel on the ISO (and in the EFI pack)-- where is that from? Is that a copy of the xnu-dev kernel from here http://code.google.com/p/xnu-dev/downloads/list ? Has it been patched or can we take it from it's source?

 

AND, still want this running on the internal 250GB... that will be the subject of a future post....

 

This was a no brainer:

 

Boot up via linux (either Live CD, USB distro, or one you already have installed)

 

dd if=/dev/<ext_drive> of=/dev/<int_drive>

 

and let it run-- took a while for me-- but it was a 250GB drive running over USB!

 

Then shutdown, removed external, reconfig'ed the bios so that drive was on port 0, and golden.

 

Obviously the drives have to be either identical in size, or the internal has to be larger. If the internal is larger, you can then boot up Disk Util and resize your partition to use the rest of the disk.

 

If you were thinking when you did the install (I wasn't, alas), you would have created your initial OSX install partition much smaller, say 20 GB, thereby allowing you to mirror this elsewhere much easier, and heck even use the rest of the external drive for something else (which is currently 240GB of wasted space for me). You could always attempt to fix that after the fact with a partition resize, but that is for the reader to experiment with as that space isn't really needed for me (got a couple of terabytes laying around here)

 

And since I did this before I messed with the EFI partition or boot loaders, I now have a virgin install as my backup. Mess up my current one (which I thought I did the other day after a couple of kernel panics) and all I have to do is the same to copy back to my internal.

Link to comment
Share on other sites

Since 10.5.7 is out now, has anyone dared an update yet?

I have the combo installer on my disk now but don’t feel like potentially breaking working system. :P

I'll be running it as soon as I wake up -_- got to get some (needed) sleep first... But in a few hours.. :D
Link to comment
Share on other sites

 Share

×
×
  • Create New...