Jump to content

SSE2 & 3 Retail Leo and Vanilla installs - Boot 132 on pre-Core !


munky
 Share

614 posts in this topic

Recommended Posts

Voodoo has this up there site:

Anyone having the same problem?

 

"Database Error

 

There appears to be an error with the database. But don't worry, we have a dedicated team of 1000 Monkeys working on the case

You can try to refresh the page by clicking here"

 

This error comes a lot to me also BTW 1000 Monkeys LOL :P

Link to comment
Share on other sites

munky: I took your suggestion and added the Voodoo kernel to my boot-132 iso.

 

Darwin Rainbow 9.4.0 Darwin Kernel Version 9.4.0: Tue Sep 16 19:36:00 IST 2008; Voodoo; based on ToH:xnu-1228.5.20/BUILD/obj/RELEASE_I386 i386

 

As for the results, I don't see much/any difference. The warning messages about sandbox_init are still there. They appear just before the screen clears to display the login window. The other earlier messages about duplicate extensions appear to be the same as with the modbin kernel.

 

I can't tell if there is any operational impact from the sandbox_init warning or not. If there is, I can't identify it. My concern about it is a carryover from a previous life when I was a systems programmer :(

 

I still could use some pointers to where these early boot messages are logged - if in fact that are logged at all.

 

Anything else I should try?

 

--- BladeRunner

Link to comment
Share on other sites

OK, given that I am basically lazy, I would like to quit typing in "rd(0,1)/voodoo rd=diskXsY" every time I boot the system.

 

I have install OS X on 2 different drives - one internal and the other an external USB drive. I have chameleon installed on both drives. I can boot either one using the CD and entering 80 or 81 to select the drive. When the next prompt is given I enter a version of the command I listed.

 

I know that if I copied the "Extra" folder onto the retail OS X partition I could modify com.apple.Boot.plist to correctly boot the system without my needing to enter any more data.

 

What I want is to do this without placing the "Extra" folder on the retail partition. Does anyone know the correct sequence of plist entries to boot the system with the "Extra" folder residing on the CD?

 

Any pointers on how to do this would be greatly appreciated.

 

EDIT: Well, I found the solution. And, if I can ever locate the original post, I will provide attribution because it is not my original work. I just adapted it.

 

Install chameleon on you drive.

 

Edit your com.apple.Boot.plist to look like the following - adjusting the diskXsY parms to match your drive

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Graphics Mode</key>
	<string>"1280x1024x24"</string>
	<key>Kernel</key>
	<string>rd(0,1)voodoo</string>
	<key>Kernel Flags</key>
	<string>-v -f  rd=disk0s3</string>
	<key>Timeout</key>
	<string>7</string>
	<key>device-properties</key>

 

 

Now, with the CD in the reader - at the first prompt press "enter" to get to the drive selection prompt. Enter the NN number that relates to your drive as usual. At the next prompt select the desired partition and press enter.

 

I have tried this on my external USB drive and on the 2 OS X partitions on the internal drive. It does everything I had hoped for. Now if I can just get a faster boot device than the CD :(

 

--- BladeRunner

Link to comment
Share on other sites

hi there....

 

testing currently bladerunners bootdisc....

got a kernel panic ....someting boot nfs blabla....

tested with both kernels modbin and voodoo....no success :)

any suggestions???

 

thanx folk ;-)

 

Dont you get ROOT DEVICE Becouse i have the same pc

Link to comment
Share on other sites

hi there....

 

testing currently bladerunners bootdisc....

got a kernel panic ....someting boot nfs blabla....

tested with both kernels modbin and voodoo....no success :(

any suggestions???

 

thanx folk ;-)

 

I have found that I generally need to use the -f flag to avoid the waiting for root device error and/or a kernel panic. I never was able to learn why.

 

try "rd(0,1)/voodoo -f -v ....." and see if that helps.

Link to comment
Share on other sites

I was having this problem but after I made my HDD primary master it gone ;)

 

i got sata drives installed....thanx bro

 

@shatterhenner try using 3D man`s iso and after install use the voodoo kernel from bladerunner`s iso. It worked for me..

 

i give it a try tonight...already tested balderunners with both kernels...no success

 

Dont you get ROOT DEVICE Becouse i have the same pc

 

 

I have found that I generally need to use the -f flag to avoid the waiting for root device error and/or a kernel panic. I never was able to learn why.

 

try "rd(0,1)/voodoo -f -v ....." and see if that helps.

 

im hanging not at waiting for root device....panics a bit later in boot process

Link to comment
Share on other sites

I got it installed but it failed becouse i couldn't the uuid of the disc anyway to add it

 

You said you got it installed. I assume that meens you installed OS X on your hard drive and booting that failed. Is that correct?

 

I have never used the uuid. I always use rd=diskXsY. That should not be too hard to find. If you don't know the correct x/y then restart the install dvd and select the disk utility from the menu bar. Or, select the terminal and enter the command "diskutil list" That will provide the data you need.

Link to comment
Share on other sites

I booted the disc OK and when in to the install and disk utility and formated then i pressed install and install log to see if anything fails after installing when its at 95´-99% i get the error messege 35. could find UUID or something luckly i wrote down the UUID but rd=diskXsY workes but is it anyway i can write both diskXsY and uuid like rd=disk1s2 boot-uuid=......

 

 

The error _CFGETHOSTuuidstring: unable to determine UUID for host . Error 35

Link to comment
Share on other sites

just one tiny point: the reason I use uuid rather than diskXsY is that I don't want my booting to break if I change the number or arrangement of hard disks on my system. For example, plugging in a USB hard disk makes that disk0. For my money, uuid is a more robust approach, cos it won't change.

Link to comment
Share on other sites

Well the problem is the leo disc cant set my HDD to boot thats why it failes when its 1 min left

 

If that is the problem you are having, it's basically a non problem.

 

Just reboot the system and boot into your hard drive. It will go into the welcome messages and then do the standard setup. Your installation, the part that uses the install dvd, is done when it tries to re-boot.

 

 

As for getting the uuid, you can get that from disk utility. Just open disk utility, select the volume in question and then click the "i" info icon on the task bar. The resulting pannel will display both the diskXsY and uuid information for the selected volume.

Link to comment
Share on other sites

 Share

×
×
  • Create New...