Jump to content
6 posts in this topic

Recommended Posts

After a good install of LawlessPPC I hang at one of two places:

 

using 10485... ...buffer 4096 cluster

or,

"still %$@#-ing waiting for root device"

 

Which hangup i get depends on my BIOS settings. I can see when i boot with -v that the root device hang is further down the boot process than the "using 10485 buffer 4096 cluster" hang. So should i keep the BIOS settings that get as far as "waiting for root device" and troubleshoot that issue or the revert to the settings that throw the buffer/cluster error and deal with that?

 

I guess what asking is, since i can pick between the two problems, which is the problem that I should be solving, which one is closer to having this thing goin'?

 

-e

A big dilemma indeed!

For "using 10485 buffer 4096 cluster" http://www.insanelymac.com/forum/index.php...=78235&st=0

For "still waiting for root device" i h a c k i n t o s h.com/2009/05/still-waiting-for-root-device/

 

In general both are bad. Nether gets you closer to install.

 

For "using 10485 buffer 4096 cluster" try using ACPI=off flag. But there is no warranty you will not face the "still waiting for root device" error later on.

 

It is hard to tell for certain, then the specs are unknown.

Leopard is already installed from the LawlessPPC disk, even got the "Successful Installation" splash screen at the end.

 

so these errors are coming during the boot into the OS from my HD.

 

When I boot into verbose mode, and i get to the "root device" hang, i can see further up the line that i passed the buffer/cluster thing. So i think ill stick with the BIOS settings that get my that far and troubleshoot the root device/grey screen with a O / hang.

 

sorry for not putting system info:

 

AMD Athlon X2 Black Ed. 2600+

Asus M3A mobo

Nvidia EVGA 8800GT

3 gigs of corsair ram @ 800 (i think. BIOS it isnt seeing all 3 atm, only 2, which ill fix later and i cant for sure remeber the bus speed)

Western Digital HD (3 partions, MacOs on prmary, one empty for windows later on, and on with all my data)

Generic DVD burne

both the DVD and HD are on an IDE cable, no SATA devices. HD is currently jumpered to prim. master, with DVD as prim. slave, though ive tried other settings.

 

 

How is is that the program can see my harddrive when it boots into the instal program, then see my harddrive to format it, then see my HD to write to it and then cant boot from it? Is there a way to boot into the the instal program (which always works) and from there boot into the OS?

 

better stll, what could the DVD be doing to boot that OS isnt? Is it automatically loading some generic IDE drivers or something? could be that simple that i just copy them over? id have no clue where they are

 

 

thanks

 

-e

How is is that the program can see my harddrive when it boots into the instal program, then see my harddrive to format it, then see my HD to write to it and then cant boot from it? Is there a way to boot into the the instal program (which always works) and from there boot into the OS?

 

better stll, what could the DVD be doing to boot that OS isnt? Is it automatically loading some generic IDE drivers or something? could be that simple that i just copy them over? id have no clue where they are

Let me explain how it is possible to install but not possible to boot. :thumbsup_anim:

 

Any patched install disk contains some amount of different drivers. These drivers for sure includes a chipset drivers (or an on-board disk controller drivers). Then you launch an install DVD all the divers included on the disk are loaded, so an installer could use all the (more or less) hardware installed.

 

Then you do installation, NOT ALL THE DRIVERS CONTAINING ON THE DISK ARE INSTALLED BY DEFAULT. You must select the one that are essential, by yourself. Click customize button before proceeding to installation. Be sure to select an appropriate chipset drivers. Check what your MB has and select accordingly.

 

I'd also advise not to install any VGA/LAN/WLAN/Sound drivers in this stage. Install them later, then booted to working system.

 

Be also sure to select a PS/2 driver if you use a PS/2 mouse&keyboard. Select a AppleSMBIOS driver/patch. Other drivers/patches are optional. May be needed, but may be not.

 

There is no need to reinstall the whole system if you have forgot something. Ether you can copy the driver(s) needed from the same install DVD, or download them, place them to a FAT formatted USB pen drive and install from there. In ether approaches one will need to boot to Install DVD and use the Terminal.app to install driver(s).

wow thanks for answering so quickly.

 

im on USB mouse and keyboard

 

I had suspected the DVD was just loading all drivers until one worked. its just a bit goofy that it does not install the working drivers or remember them. neither here nor there though.

 

I went through one of the walkthrus you sent me, the one suggest I run the install DVD so I can use terminal to copy the drivers off of the DVD onto your HD. Command line is no problem for me, although the Apple commands are new, they are right in front of me so you would think i cant blow it.

 

still im getting caught on the dumbest of things. I know the volume name and location of the OS drive (disk0s2, i called it "mac") and it is at /volumes/mac.

 

but i dont know the volume name of the DVD im installing from, or at least, i think I am typing it wrong When i put it into other computers, or when i use system profiler to see the volumes name it is LawlessPPC-Leo-10.5.4-Phen&AMD. but when i punch that in Terminal cant see the it (error "directory does not exist"). In DOS such a long filename would be abbreviated and renamed Lawles~1, and i do not think the "&" is recognized. Is there a similar problem here and that is why Terminal cant find the directory?

 

im going to go google how to to do things like go to a drive and look into it (in DOS C:, dir, cd whatever...etc ive gotta learn these for whatever you call apple command line) with terminal. but if you have any tips posting them up is appreciated. Im positive this is a case of loading the right drivers, ive just gotta learn the commands.

 

-e

About naming. To get the name of the install dvd type

cd /Volumes
ls

or other approach

diskutil list

Both should output some info about volumes mounted. Note that if there are spaces in the name of a disk/folder, there should be a "\" before each space. Like

iAtkos\ OS\ X\ Install\ Disk\ 10.5.1

which corresponds to iAtkos OS X Install Disk 10.5.1

 

Some more info on copying kexts from DVD: i h a c k i n t o s h.com/2009/05/still-waiting-for-root-device/

×
×
  • Create New...