iPC OSx86 10.5.6 Intel AMD SSE2 SSE3: Public beta in 2 days - Page 2

nfoav8or · #11 01-03-2009, 07:26 AM

Depending on where the restart happens, this sounds like a kernel incompatibility restart (normally happens when using a "vanilla" kernel on an unsupported processor) that shouldn't be happening since the default kernel installed is the voodoo kernel (which works with your processor). Check the customization of your install and/or report your selections from customizing.

ron73 · #12 01-03-2009, 10:29 AM

Quote:

Originally Posted by nfoav8or

Depending on where the restart happens, this sounds like a kernel incompatibility restart (normally happens when using a "vanilla" kernel on an unsupported processor) that shouldn't be happening since the default kernel installed is the voodoo kernel (which works with your processor). Check the customization of your install and/or report your selections from customizing.

Is used GUIDE instead of MBR. Can this be part of the problem. Mac is located at my USB HD (Lacie) from wich I can boot.

__________________________

CPU: AMD Athlon 64 3800+
RAM: 2 x 1 GB
NVIDIA nForce 4 MCO
NIVIDIA GeForce 6600
Realtek AC'87 audio

nfoav8or · #13 01-03-2009, 10:58 AM

Quote:

Originally Posted by ron73

Is used GUIDE instead of MBR. Can this be part of the problem. Mac is located at my USB HD (Lacie) from wich I can boot.

__________________________

CPU: AMD Athlon 64 3800+
RAM: 2 x 1 GB
NVIDIA nForce 4 MCO
NIVIDIA GeForce 6600
Realtek AC'87 audio

GUID or MBR really doesn't matter when you installed this... different reasons to install to each of the partition schemes. If your hardware allows you to boot from an external HD then the installation should work. How far are you getting before it restarts? are you able to enter boot flags?

ron73 · #14 01-03-2009, 01:59 PM

Quote:

Originally Posted by nfoav8or

GUID or MBR really doesn't matter when you installed this... different reasons to install to each of the partition schemes. If your hardware allows you to boot from an external HD then the installation should work. How far are you getting before it restarts? are you able to enter boot flags?

The system reboots at: Loading HFS+file: (mach-kernell) (system/library/extensions.mkext) from 4234670

Any idea?

__________________________

CPU: AMD Athlon 64 3800+
RAM: 2 x 1 GB
NVIDIA nForce 4 MCO
NIVIDIA GeForce 6600
Realtek AC'87 audio

nfoav8or · #15 01-04-2009, 03:28 AM

Quote:

Originally Posted by ron73

The system reboots at: Loading HFS+file: (mach-kernell) (system/library/extensions.mkext) from 4234670

Any idea?

first, put your specs into your signature instead of your posts, that way you don't have to keep retyping them or have them show up in quoted text.

It looks like you are getting past where the boot flags would be inputted. interrupt the boot timeout countdown by pressing any key then type the -f boot flag in and press enter.

ron73 · #16 01-04-2009, 07:28 PM

Quote:

Originally Posted by nfoav8or

first, put your specs into your signature instead of your posts, that way you don't have to keep retyping them or have them show up in quoted text.

It looks like you are getting past where the boot flags would be inputted. interrupt the boot timeout countdown by pressing any key then type the -f boot flag in and press enter.

Yes. I can start Mac OS X from external HD. Only thing that doesn't work is my internet. The system can't find my ethernetcard. Can this be solved?

lanceomni · #17 01-04-2009, 08:35 PM

What option did you choose for your network drivers when you installed?

Do you have the model of the computer or the model of the motherboard you have?

There are a handful of nForce lan drivers out there. Look in /System/Library/Extensions for anything that says forcedeth, forcedeth-v or and anything like nForceLAN. There might be issues with having more than one installed. If you have any of these delete them from the folder. You may want to back them up someplace like the desktop. You can try the nForceLAN.kext in my signature first. http://rapidshare.com/files/17110232...ceLAN.kext.zip

After you have removed the files listed above:

1. Copy nForceLAN.kext to /System/Library/Extensions
2. In Terminal write:

Code:

chmod -R 755 /System/Library/Extensions && chown -R root:wheel /System/Library/Extensions
sudo rm -R /System/Library/Extensions.mkext
diskutil repairPermissions /

3. Restart using the boot flags:

Code:

-v -f

You can use the same method for installing other kexts.

ron73 · #18 01-04-2009, 08:50 PM

Quote:

Originally Posted by lanceomni

What option did you choose for your network drivers when you installed?

Do you have the model of the computer or the model of the motherboard you have?

There are a handful of nForce lan drivers out there. Look in /System/Library/Extensions for anything that says forcedeth, forcedeth-v or and anything like nForceLAN. There might be issues with having more than one installed. If you have any of these delete them from the folder. You may want to back them up someplace like the desktop. You can try the nForceLAN.kext in my signature first. http://rapidshare.com/files/17110232...ceLAN.kext.zip

After you have removed the files listed above:

1. Copy nForceLAN.kext to /System/Library/Extensions
2. In Terminal write:

Code:

chmod -R 755 /System/Library/Extensions && chown -R root:wheel /System/Library/Extensions
sudo rm -R /System/Library/Extensions.mkext
diskutil repairPermissions /

3. Restart using the boot flags:

Code:

-v -f

You can use the same method for installing other kexts.

Must I press Enter between these two lines?

Motherboard is Asus A8N-E (NVIDIA nForce networkcontroller)

lanceomni · #19 01-04-2009, 09:31 PM

Yes each of the three line you press enter.
The first line sets permissions in the extensions folder.
The second line removes the extensions.mkext
The third line repairs permissions to the entire drive.

Drivers "kexts" are stored in the extensions folder. OSX creates a cache file called Extensions.mkext of all the appropriate drivers. What we are doing is adding a new driver, repairing permissions and deleting the cache file so that OSX is forced to create a new one with the new driver.
The reason that we have to use line 1 and line 3 is that repairing permissions only works with Apple kexts. OSX does not know what permissions to set thirdparty/homemade kexts to so we use the 1st line.

ron73 · #20 01-04-2009, 10:14 PM

Quote:

Originally Posted by lanceomni

Yes each of the three line you press enter.
The first line sets permissions in the extensions folder.
The second line removes the extensions.mkext
The third line repairs permissions to the entire drive.

Drivers "kexts" are stored in the extensions folder. OSX creates a cache file called Extensions.mkext of all the appropriate drivers. What we are doing is adding a new driver, repairing permissions and deleting the cache file so that OSX is forced to create a new one with the new driver.
The reason that we have to use line 1 and line 3 is that repairing permissions only works with Apple kexts. OSX does not know what permissions to set thirdparty/homemade kexts to so we use the 1st line.

Thanks. I'll try this tomorrow.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode