Switch to full style
This folder is where all the crap like spam and warez requests go.
Post a reply

Linux Install of OS 10.3

Wed May 19, 2004 8:38 pm

Currently have a windows setup almost fully installed, and I figured that I would try installing it on my dual proc (MP 1800+) system with a gig of ram for better speed. Its a linux box, so I knew the install was going to be slightly different.

I built from the 0.1.1 source tarball on the PearPC site, complied fine. (Yes I did use the ./configure --enable-gui=qt --enable-cpu=jtic_x86 flags)

Boots up, using the exact same config file (except I changed the location of the iso and hdd img file) for the install, and it just times out with:

Code:
Still Wating for root device


Its been going for about 30mins now, and still hasnt picked anything up.

What gives?

Wed May 19, 2004 9:05 pm

do you have your hd image set as master and OS X image as slave?

Perhaps an answer

Wed May 19, 2004 9:11 pm

I have your situation running, so it is possible

Justa few fast checks

- Did you correctly mount the device on which your disk image can be found?
- Be sure, that partition is read/write

my file looks something like

/mnt/d/disk.img

and /mnt/d is a FAT32 filesystem.

Some comparative results

I also found that there is a big performance issue in the Linux version, so Now I only run it in Windows. Too many linux processes stealing to many cycles. X windows also isn't a fast graphical system, the windows graphic engine until now is fast.

Good luck

Wed May 19, 2004 9:14 pm

I didnt mount the image on any fs or device, I guess that could be my problem.

I'll just leave it be, let my windows install continue...

Thanks for the quick help :D

Wed May 19, 2004 10:59 pm

lol hod do u forget something that importent

Thu May 20, 2004 9:22 pm

grayfox wrote:lol hod do u forget something that importent


I get the same problem on windows, I doubt that he forgot to mount the volume his image is on, that means he would have not have been able to see the image an would have realized it the problem. this is a problem with the install and I have seen this issue with osx 10.2 and above when the partion is corrupted...

I am reinstalling so I will not be able to tell you if i am sure but this time i will check the partition tables be for i kick of the install (during startup)
Post a reply