Jump to content
6 posts in this topic

Recommended Posts

So after retrying it again with another distro package, I finally managed to install Leopard on a partition of an IDE drive. While the installation finally pulled through without a hitch, I am now left not knowing how to get any bootloader to work with the new OS. The distro I finally got to work was iAtkos 5i, I believe. Before the install, the partition was previously FAT32, and was reformatted into the Mac Journaled File System (I forget the exact name). It installs fine, and I get to the very end and restart the computer when it says to, at which point I take out the install DVD and let it reboot. Rebooting into the destination drive yields a "boot0: error" message, followed by a complete stop by the computer.

 

I've read up on this issue and it seems that the drive has to be set active, or the boot flag has to be set on the partition. As for doing this, I have already done so. More specifically, I have put in the install DVD again and used the Terminal within the installer to run:

 

fdisk -e /dev/rdisk3

 

which corresponds to the drive I have Leopard installed into, as according to diskutil list.

 

In setting it active, I typed f 2 for the Leopard partition and checked the drives again, and it seemed to have starred the second partition for the boot flag. I then applied the changes with write at which point I get something about not being able to access the drive exclusively and will apply changes upon reboot. I confirm that and then exit the Disk Utility and restart the computer.

 

This time around, I get what I wrote for the topic's subject, that is:

 

boot0: MBR

boot0: done

 

And then my computer just stops doing anything meaningful after that. I'm not quite sure where else to go from here, as the boot flag has already been set on the drive, yet I can't get past this point in booting.

 

Any help would be appreciated.

 

EDIT: Never mind on the top problem, I've found a workaround for it by adding chain0 to the Windows XP bootloader. Now I have a new problem.

 

I can't get it to boot. It seems that the order of the messages in the verbose mode of display occur in different orders sometimes, but it always seems to hang around the time the nForce ethernet is being initialized. It finds a MAC address, an then hangs. I don't see a real issue with it, but above that, I get the following:

 

Jan 19 09:04:17 lus-mac-pro mDNSResponder[21]: WARNING: sandbox_init error Could not set Mach 
lookup policy for service com.apple.bsd.dirhelper err=1100Could not set 
Mach lookup policy for service com.apple.distributed_notifications.2 err=1100Could 
not set Mach lookup policy for service com.apple.ocspd err=1100Could not set 
Mach lookup policy for service com.apple.mDNSResponderHelper err=1100Could 
not set Mach lookup policy for service com.apple.SecurityServer err=1100Could 
not set Mach lookup policy for service com.apple.SystemConfiguration.configd er

 

Quite literally, the log stops there, with the final "err=1100" (I assume) chopped off. Also, there is, again, quite literally, no space between "err=1100" and the following "Could" for each occurrence.

 

What I have tried is the -x switch, which boots into safe mode. This does indeed work, and I can get to the Leopard desktop with this switch. So this issue only applies for normal boot. My guess is that one of the drivers is screwy, though I'm not sure which. My hunch is the ethernet, which has been said to be glitchy (or so I've heard.)

Link to comment
https://www.insanelymac.com/forum/topic/147844-safe-mode-but-not-normal/
Share on other sites

Bumping this to the top of the list since the first issue has been solved and the second issue arises. This is the same as above, but to reiterate:

 

Never mind on the top problem, I've found a workaround for it by adding chain0 to the Windows XP bootloader. Now I have a new problem.

 

I can't get it to boot. It seems that the order of the messages in the verbose mode of display occur in different orders sometimes, but it always seems to hang around the time the nForce ethernet is being initialized. It finds a MAC address, an then hangs. I don't see a real issue with it, but above that, I get the following:

 

Jan 19 09:04:17 lus-mac-pro mDNSResponder[21]: WARNING: sandbox_init error Could not set Mach
lookup policy for service com.apple.bsd.dirhelper err=1100Could not set
Mach lookup policy for service com.apple.distributed_notifications.2 err=1100Could
not set Mach lookup policy for service com.apple.ocspd err=1100Could not set
Mach lookup policy for service com.apple.mDNSResponderHelper err=1100Could
not set Mach lookup policy for service com.apple.SecurityServer err=1100Could
not set Mach lookup policy for service com.apple.SystemConfiguration.configd er

 

Quite literally, the log stops there, with the final "err=1100" (I assume) chopped off. Also, there is, again, quite literally, no space between "err=1100" and the following "Could" for each occurrence.

 

What I have tried is the -x switch, which boots into safe mode. This does indeed work, and I can get to the Leopard desktop with this switch. So this issue only applies for normal boot. My guess is that one of the drivers is screwy, though I'm not sure which. My hunch is the ethernet, which has been said to be glitchy (or so I've heard.)

 

So it seems the above error shows up on the safe mode boot too, yet in safe mode, it just continues and eventually loads successfully. I did notice that safe mode does not load the ethernet drivers, so I'm going to try a re-install and not load ethernet drivers to see if that fixes the issue.

No dice. Same thing happens. I'm not sure what else there is to change...maybe the Kernel?

 

The only drivers I'm installing are the EFI strings for the graphics card, the nForce SATA drivers, and the nForce Ethernet drivers. I've removed the Ethernet drivers in the second install, and the same thing happens, it just hangs somewhere else during normal boot (in both cases, safe mode boots fine.)

Hello, according to that nobody answers on my question there, I'm just joining this thread cause your problems sound quite similar to mine and I wasn't able to find help, anywhere - google always points on this forum. I have to say that I'm a OSX n00blet and not really able to follow all your explanations in detail, but what I can say is:

 

1. tried Leo4All, didn't match in any way, also after 5th install ("still waiting for root device")

 

2. tried this tutorial and was able to boot; had cruel graphic bugs everytime sth. was animated (spaces etc.). Ethernet & sound went well. Sadly at about 40 seconds up to 4 minutes, the whole system freezes and says nothing, only way is reseting the machine. SAFEMODE: Runs, over hours.

 

3. tried install Kalyway 10.5.2 again without natit for ATI. Only installed the very neccessary things.

 

4. No more graphic bugs, damn fast animations etc., but f**** freeze again. Sometimes it feels like the freeze only arives if I use ethernet/ connect to my PPPOE. SAFEMODE: As usual, runs, over hours.

 

5. Tried the Apple graphic update and this forcedeth.kext, but no changes

 

 

I don't know if this is the same problem, but maybe man could exclude that is my AMD, so it just could be the Nforce (which might lead to a solution, I hope so ... )

 

 

Sys:

CPU : AMD 64 X2 4400+

Mobo: Asus A8N-SLI SE Nforce4

RAM: 2GB DDR1-400 Kingston HyperX

VGA: Sapphire ATI X1900XT 512 MB

HDD: 400 GB SEAGATE IDE

 

 

P.S.: Might there be an Web 2.0 online tool for getting usefull Systeminfos for putting em into signature?

  • 3 months later...
Bumping this to the top of the list since the first issue has been solved and the second issue arises. This is the same as above, but to reiterate:

 

Never mind on the top problem, I've found a workaround for it by adding chain0 to the Windows XP bootloader. Now I have a new problem.

 

I can't get it to boot. It seems that the order of the messages in the verbose mode of display occur in different orders sometimes, but it always seems to hang around the time the nForce ethernet is being initialized. It finds a MAC address, an then hangs. I don't see a real issue with it, but above that, I get the following:

 

Jan 19 09:04:17 lus-mac-pro mDNSResponder[21]: WARNING: sandbox_init error Could not set Mach
lookup policy for service com.apple.bsd.dirhelper err=1100Could not set
Mach lookup policy for service com.apple.distributed_notifications.2 err=1100Could
not set Mach lookup policy for service com.apple.ocspd err=1100Could not set
Mach lookup policy for service com.apple.mDNSResponderHelper err=1100Could
not set Mach lookup policy for service com.apple.SecurityServer err=1100Could
not set Mach lookup policy for service com.apple.SystemConfiguration.configd er

 

Quite literally, the log stops there, with the final "err=1100" (I assume) chopped off. Also, there is, again, quite literally, no space between "err=1100" and the following "Could" for each occurrence.

 

What I have tried is the -x switch, which boots into safe mode. This does indeed work, and I can get to the Leopard desktop with this switch. So this issue only applies for normal boot. My guess is that one of the drivers is screwy, though I'm not sure which. My hunch is the ethernet, which has been said to be glitchy (or so I've heard.)

 

So it seems the above error shows up on the safe mode boot too, yet in safe mode, it just continues and eventually loads successfully. I did notice that safe mode does not load the ethernet drivers, so I'm going to try a re-install and not load ethernet drivers to see if that fixes the issue.

 

 

 

hi . i have the same problem the system boots on safemode but not normally,, hangs with this error message.. please let me know if u find a workaround..

i will if i come to know

  • 2 months later...
hi . i have the same problem the system boots on safemode but not normally,, hangs with this error message.. please let me know if u find a workaround..

i will if i come to know

 

i was able to do it....

 

installed efi strings for my graphics card using osxtools and now my resolutions fine and able to boot in normal mode

×
×
  • Create New...