"still waiting for root device"

[ARCHIVED] About PearPC, a mostly obsolete PPC Mac emulator for Windows and Linux to run MacOS X 10.1 up to 10.4. Using QEMU is now recommended.

Moderators: Cat_7, Ronald P. Regensburg

Locked
f/a-18
Space Cadet
Posts: 4
Joined: Fri May 16, 2014 12:24 am

"still waiting for root device"

Post by f/a-18 »

hello everybody. this is my first time on the board (and using pearpc) and i'm having problems running mac osx cheetah pear pc. When stsrting in verbose, it says things which i am guessing has to do with startup with osx, but it eventually just say "still waiting for root device". I have tried searching the internet and i tried switching my cheetah iso to master and putting my disk img to secondary, but with no luck. I have also heard disscussion about tring to install tiger on pear pc, and peoplee were talking about the dvd and cd. would that affect my matter? here is my pearpc configuration.

## PearPC Configuration File

##
## Start Resolution
##
## (clients that use video.x can change the resolution at runtime,
## so this would be used only for starting up)
##
## format: "(width)x(height)x(depth)"
## or "(width)x(height)x(depth)@(frequency)"
##
## depth can only be 15 or 32
##
## default: "800x600x15"
##

ppc_start_resolution = "800x600x15"

##
## Set this to non-zero for turning on fullscreen mode on startup.
##

ppc_start_full_screen = 0

##
## Redraw interval (in ms)
## must be between 10 and 500
##
## If you set this higher, PearPC will spend less time doing redraws
## (and so run faster) but feel less responsive. You should adjust
## this to your computer speed and personal preference.
##

redraw_interval_msec = 10

##
## Key codes
##

key_compose_dialog = "F11"
key_change_cd_0 = "none"
key_toggle_mouse_grab = "F12"
key_toggle_full_screen = "Alt+Return"


##
## Loader
##

##
## Boot method
## this can be
## 1. "auto", prom will boot the first bootable partition found (default)
## 2. "select", prom will show you a list of bootable partitions
## 3. "force" [ADVANCED USERS ONLY], prom will load and boot the
## local file prom_loadfile
##

prom_bootmethod = "select"

## Example of how to use "force":

#prom_bootmethod = "force"
#prom_loadfile = "test/yaboot"
#prom_env_bootpath = "disk"

##
## bootargs: don't change unless you know what you are doing
## machargs: set to "-v" to get a verbose startup
##

#prom_env_bootargs = ""
prom_env_machargs = ""

##
## This is needed if you want to boot Mac OS X
##
prom_driver_graphic = "video.x"

## This will adjust the position of the initial page table (don't change)

#page_table_pa = 104857600

##
## CPU Config
##
## Processor Version Register
## Defaults to 0x00088302 (G3)
## Set to 0x000c0000 to enable G4 emulation
## Only change if you know want you are doing
##

#cpu_pvr = 0x00088302
#cpu_pvr = 0x000c0000


##
## Main memory (default 128 MiB)
## must be >= 64 MiB
##

#memory_size=0x8000000

##
## IO Devices
##

##
## PCI IDE Config
##
## Drive type will be set according to file extension:
## .img: Harddisk (filesize must be multiple of 516096)
## .iso: CD-Rom
## Or you can override this by specifying the type via
## pci_ide0_master_type / pci_ide0_slave_type
##
## Valid drive types are:
## hd: A hdd image should be specified
## e.g. "test/imgs/linux.img"
## cdrom: A cdrom image should be specified
## For Linux or BeOS a cdrom device can be specified as well
## e.g. "/dev/cdrom"
## nativecdrom: Platform dependant
## Win (SPTI): drive letter, e.g. "d:\"
## Win (ASPI): SCSI host adapter,target,lun e.g. "2,0,1"
## BeOS (ATAPI): device path, e.g. "/dev/disk/ide/atapi/0/master/0/raw"

pci_ide0_master_installed = 1
pci_ide0_master_image = "b.iso"
#pci_ide0_master_type = "cdrom"

pci_ide0_slave_installed = 1
#pci_ide0_slave_image = "e:\"
#pci_ide0_slave_image = "2,0,0"
pci_ide0_slave_image = "myharddisk.img"
pci_ide0_slave_type = "hd"

##
## Network
##
## Choose one of the cards

pci_3c90x_installed = 0
pci_3c90x_mac = "de:ad:ca:fe:12:34"

pci_rtl8139_installed = 0
pci_rtl8139_mac = "de:ad:ca:fe:12:35"

##
## USB
##
pci_usb_installed = 0

##
## Serial Port (internal use)
##
pci_serial_installed = 0

##
## NVRAM
##
nvram_file = "nvram"
oh, and my operating system is ubuntu, but i am running this with the wine cmd.
in the terminal box it says
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License version 2 as published by
the Free Software Foundation.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111 USA

[PPC/VEC] Vector Address: 004d1a90
GenuineIntel
CMOV MMX SSE SSE2 SSE3
[CPU/MMU] new pagetable: sdr1 = 0x00300003
[CPU/MMU] new pagetable: sdr1 accepted
[CPU/MMU] number of pages: 2^15 pagetable_start: 0x00300000 size: 2^18
start: 368640
Loading XCOFF...
[CPU/CPU] execution started at 01c00510
[CPU/MMU] new pagetable: sdr1 = 0x0100000f
[CPU/MMU] new pagetable: sdr1 accepted
[CPU/MMU] number of pages: 2^17 pagetable_start: 0x01000000 size: 2^20
[IO/IDE] <Error> command 'e1' not impl
User avatar
Cat_7
Expert User
Posts: 6145
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Re: "still waiting for root device"

Post by Cat_7 »

Hi,

This might have something to do with a badly formatted hard disk image file.

Also, please change your config:
prom_env_machargs = "-v"
and set
#pci_ide0_slave_type = "hd" (effectively commenting out this line)
pci_usb_installed = 1

Let us know what happens.

Best,
Cat_7
f/a-18
Space Cadet
Posts: 4
Joined: Fri May 16, 2014 12:24 am

Re: "still waiting for root device"

Post by f/a-18 »

well, i tried what you said (but i didn't get the hd thing, my settings already say "hd") i have download a new hard drive from http://www.emaculation.com/pearpc/macosx_6gb.rar and unziped the rar and put it in my pearpc directory, and i have tried the verbose mode, which at the end said waiting for root device, but also said other errors which it bypassed verif_kmod:Kmod com.app;e.iokit.ioscsimultimedia commands device has no cfbundle property. I will also try another cheetah cd.

ok, puma say "root device is locked or something before crashing pearpc, but mabye i can try mounting the iso, then trying to get pearpc the read from that. Should i try that?
User avatar
Cat_7
Expert User
Posts: 6145
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Re: "still waiting for root device"

Post by Cat_7 »

Hi,

The # in front of the line: pci_ide0_slave_type = "hd" would comment the line out. It was meant to do that.

Master and slave types are not needed when the extensions of the files referred to at
pci_ide0_master_image =
pci_ide0_slave_image =

already end in .img or .iso. img translates to type "hd" and iso translates to type "cdrom".

It is of no use mounting the CD or CD image, it would perhaps prevent pearpc from reading from the file or cd. Also there is no way of telling PearPC where to read.

I'm downloading a Cheetah.iso, I'll see what I can come up with (will take a while ;-) )

Best,
Cat_7
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

I can check my config and setup in another 10 hours or so. I know I've had that problem in the past, but can't recall what caused it. It's always worthwhile deleting your nvram file after making changes, just in case you're booting with a bad nvram.

Just make sure you don't have your HD or ISO files loaded in any other way, the HD file is not locked in any way, your nvram file is deleted, and you select the right image from the boot menu.

If you're switching between OS versions, you'll want to delete the nvram file before you boot the new version. I keep a separate pearpc binary for each major OS revision I use to prevent nvram complications.
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

Doh... I just clued in that you're trying to run Cheetah (AKA 10.0) under PearPC. PearPC only supports 10.1 through 10.4 -- I've never got 10.0 to run reliably under any of the versions. I doubt you'll be able to boot off of a 10.0 CD; you *might* be able to set up 10.1 or later, then add the 10.0 installer to install to an external (secondary) HD, and then tweak EFI a bit to get it to boot, but I haven't had success doing this yet.

See:
http://www.emaculation.com/forum/viewtopic.php?t=2663
http://www.emaculation.com/forum/viewtopic.php?t=2562
http://sourceforge.net/p/pearpc/discuss ... #b08c/1f5c
http://sourceforge.net/p/pearpc/bugs/217/

And the penultimate thread:
http://www.emaculation.com/forum/viewtopic.php?t=6362
f/a-18
Space Cadet
Posts: 4
Joined: Fri May 16, 2014 12:24 am

Re: "still waiting for root device"

Post by f/a-18 »

even puma didn't work. it said there was no preheat.sh file, but there clearly was in the file when i mounted it. and sorry i forgot to mention i use pearpc 0.5
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

Puma (10.1) only works on 0.4 for me; can't remember if it's the redscorp release or not. I''ve seen some posts from way back that seemed to imply 10.0 ran on 0.2, but haven't seen that verified anywhere. Plus, it was extremely buggy and didn't do much after booting up.
f/a-18
Space Cadet
Posts: 4
Joined: Fri May 16, 2014 12:24 am

Re: "still waiting for root device"

Post by f/a-18 »

WOOOO thanks adespoton and cat_4 for all the help! it seems puma works fine on 0.4. Now it says there were prblems installing, but that was probably the iso. once again, thanks for the help!
User avatar
Cat_7
Expert User
Posts: 6145
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Re: "still waiting for root device"

Post by Cat_7 »

Hi,

I tried from 0.5 downwards to boot Cheetah. 0.31 and below don't even recognise the cd image as bootable.

I also tried starting the installer from within Panther. It seems the Cheetah installer tries to run the classic environment, and that is something no OS X emulator has been able to do yet.

Best,
Cat_(4+3)
Last edited by Cat_7 on Sat May 17, 2014 6:08 am, edited 1 time in total.
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

Thanks for that! With that information, maybe I could cobble together some instructions for how to hack the installer to run without classic. I'll see if I can get some time to poke at it in the next few weeks.
User avatar
Cat_7
Expert User
Posts: 6145
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Re: "still waiting for root device"

Post by Cat_7 »

I guess the "still waiting for the root device" means that Cheetah can't read the hard image partitioning. And as we can't get to the disk utility, we can't partition the disk image.

I assume that if it were the case that PearPC doesn't provide the necessary hardware support (ide controller), we would not be able to boot the CD image. So I'm hoping it has to with the hard disk partitioning.

I remember providing two different pre-partitioned disk images when there was change in PearPC in how it handled partitions (from 0.2 to 0.3). Partitions 2 and 3 on the disk image had to be reversed. So I tried both disk image, but the both ended up in "waiting for....".

Now that I think of it, could it be possible that Cheetah still has problems with partitions bigger than 2 gb?

Best,
Cat_7
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

Hmm... Cheetah is one of the only Mac OSes I didn't use at the time; the public beta convinced me to wait for 10.1. But I think the 2GB limit was already gone by 10.0. However, IIRC it DID have a memory ceiling, and still used old Apple partitions with driver partition. I think we can fix this one if we isolate each bit of the boot process.
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

Well, I figured I'd start out by checking the 10.0 CD partition format.

MD5 sum: 29fc6cad8f21d10df4c5aa0bd188ad18

Disk Description : Apple read/write
Total Capacity : 590.1 MB (590,135,296 Bytes)
Connection Bus : Disk Image
Disk Write Status : Read Only
Partition Map Scheme : Apple Partition Map

diskXs1:
Capacity : 32 KB (32,256 Bytes)
Partition Type : Apple Partition Map

diskXs2:
Capacity : 29 KB (28,672 Bytes)
Partition Type : Apple_Driver43

diskXs3:
Capacity : 61 KB (61,440 Bytes)
Partition Type : Apple_Driver43_CD

diskXs4:
N/A

diskXs5:
Capacity : 29 KB (28,672 Bytes)
Partition Type : Apple_Driver_ATAPI

diskXs6:
Capacity : 61 KB (61,440 Bytes)
Partition Type : Apple_Driver_ATAPI

diskXs7:
Capacity : 262 KB (262,144 Bytes)
Partition Type : Apple_Patches

Mac OS X Install CD:
Capacity : 589.7 MB (589,656,064 Bytes)
Format : Mac OS Extended
Available : 3.9 MB (3,887,104 Bytes)
Owners Enabled : No
Used : 585.3 MB (585,347,072 Bytes)
Number of Folders : 1,755
Number of Files : 4,315
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

Well, after trying various mounting options, I eventually copied /System/Installation off of the install CD, and then ran the packages to install on a 3GB image, right from Mavericks. This seemed to work, and the boot process started -- however, it hung right after the GUI was supposed to come up and instead I got the white bar down the left side with garbled text in it. It's possible if I change the memory this might work, but that's pretty much the same hang I get attempting to boot with the install CD "inserted".

Anyone else want to try and get it past this point?
User avatar
Cat_7
Expert User
Posts: 6145
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Re: "still waiting for root device"

Post by Cat_7 »

I installed from inside PearPC for Windows (Tiger) onto a newly partitioned disk (2 and 1 Gb).
After installing from the OSInstall.mpkg, I tried to boot with the new disk. PearPC showed 2 bootable partitions, but immediately crashed on attempts to boot them.

Best,
Cat_7
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

PearPC 0.1.1
Submitted by Seppel on May 14, 2004 - 15:06, GMT +0200.

Here comes the first small update for PearPC. Changes include:

(Win32) fixed: '=' key wasn't mapped
fixed: "JITC Error: cannot read page-table"
fixes for older BootX (for Mac OS X 10.0 and 10.1)
FPU: fixed fmaddx and friends (That means your Finder will no longer crash-loop)
gcard: 1024x768x32 mode wasn't useable
io registers weren't zero extended on byte or half accesses (aka "[IO/IDE] <Error> command 'ffffffa1' not impl")
compiles now also with gcc 2.95
boots debian for PowerPC


According to this, as of PearPC 0.1.1, it appears 10.0 worked with JITC in 1024x768x32. So it SHOULD be possible to get it working somehow.
User avatar
adespoton
Forum All-Star
Posts: 4227
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: "still waiting for root device"

Post by adespoton »

Just tried running the OS X build so I could watch the generic emulation at work.

Unfortunately, it wasn't much more clear:

[CPU/CPU] <Warning> You are using the generic CPU!
[CPU/CPU] <Warning> This is much slower than the just-in-time compiler and
[CPU/CPU] <Warning> should only be used for debugging purposes or if there's
[CPU/CPU] <Warning> no just-in-time compiler for your platform.
[CPU/MMU] new pagetable: sdr1 = 0x06400003
[CPU/MMU] new pagetable: sdr1 accepted
[CPU/MMU] number of pages: 2^15 pagetable_start: 0x06400000 size: 2^18
start: 512
start: 32768
getStartBlock: 0 Apple_Free
getStartBlock: 1 Apple_Free
getStartBlock: 2 Apple_Free
getStartBlock: 3 Apple_Free
start: 134619136
getStartBlock: 0 Apple_HFS
getStartBlock: 1 Apple_HFS
getStartBlock: 2 Apple_HFS
getStartBlock: 3 Apple_HFS
start: 3220946944
getStartBlock: 0 Apple_Free
getStartBlock: 1 Apple_Free
getStartBlock: 2 Apple_Free
getStartBlock: 3 Apple_Free
getStartBlock: 0 Apple_HFS
getStartBlock: 1 Apple_HFS
getStartBlock: 2 Apple_HFS
getStartBlock: 3 Apple_HFS
Loading XCOFF...
[CPU/CPU] execution started at 01c00510
[CPU/OPC] <Warning> read from spr 25:31 (L2CR) not supported! (from 00089334)
[CPU/MMU] new pagetable: sdr1 = 0x0100000fr: 00000000
[CPU/MMU] new pagetable: sdr1 accepted
[CPU/MMU] number of pages: 2^17 pagetable_start: 0x01000000 size: 2^20
[CPU/OPC] <Warning> read from spr 25:31 (L2CR) not supported! (from 002704dc)
[IO/CUDA] <Warning> reset! pdec: 00002cc5 lr: 00000000
XIO: fatal IO error 9 (Bad file descriptor) on X server "/tmp/launch-nLhtot/org.macosforge.xquartz:0"
after 997 requests (997 known processed) with 0 events remaining.

Possibly I need to adjust the pagetable start location?
Locked