InfiniteMac OSx86  


Reply
 
Thread tools Display modes
  #11  
Old 01-03-2009, 08:26 AM
nfoav8or's Avatar
nfoav8or nfoav8or is offline
 
Join Date: Jan 2008
Location: WA, USA
Posts: 933
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.

Reply With Quote
  #12  
Old 01-03-2009, 11:29 AM
ron73 ron73 is offline
Puma
 
Join Date: Jan 2009
Location: Netherlands
Posts: 18
Quote:
Originally Posted by nfoav8or View Post
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
Reply With Quote
  #13  
Old 01-03-2009, 11:58 AM
nfoav8or's Avatar
nfoav8or nfoav8or is offline
 
Join Date: Jan 2008
Location: WA, USA
Posts: 933
Quote:
Originally Posted by ron73 View Post
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?

Reply With Quote
  #14  
Old 01-03-2009, 02:59 PM
ron73 ron73 is offline
Puma
 
Join Date: Jan 2009
Location: Netherlands
Posts: 18
Quote:
Originally Posted by nfoav8or View Post
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
Reply With Quote
  #15  
Old 01-04-2009, 04:28 AM
nfoav8or's Avatar
nfoav8or nfoav8or is offline
 
Join Date: Jan 2008
Location: WA, USA
Posts: 933
Quote:
Originally Posted by ron73 View Post
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.

Reply With Quote
  #16  
Old 01-04-2009, 08:28 PM
ron73 ron73 is offline
Puma
 
Join Date: Jan 2009
Location: Netherlands
Posts: 18
Quote:
Originally Posted by nfoav8or View Post
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?

_____________________________________

CPU: AMD Athlon 64 3800+
Asus A8N-E
RAM: 2 x 1 GB
NVIDIA nForce 4 MCP
NIVIDIA GeForce 6600
Realtek AC'87 audio
Windows Vista
USB Harddisk Lacie 250 Gb with MAC OSx86 iPC Leopard 10.5.6
Reply With Quote
  #17  
Old 01-04-2009, 09:35 PM
lanceomni's Avatar
lanceomni lanceomni is offline
 
Join Date: Nov 2008
Location: Florida, US
Posts: 521
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.

MOBO: Z77MX-QUO-AOS CPU: Core i7 3770K GPU: MSI N760 TF 2GD5/OC Case: Modded MacPro2,1
Memory: 32GB Corsair Vengeance (CMY32GX3M4A1600C9) Wifi: Airport Extreme bcm94321MCA BIOS: HermitCrab Labs H3A.816M
Monitor: AOC Q2963Pm 29" WFHD 2560x1080 21:9
Interests: KDE on Apple Darwin, Keeping it real with the command line, Helping those that help themselves

Last edited by lanceomni; 01-04-2009 at 09:43 PM.
Reply With Quote
  #18  
Old 01-04-2009, 09:50 PM
ron73 ron73 is offline
Puma
 
Join Date: Jan 2009
Location: Netherlands
Posts: 18
Quote:
Originally Posted by lanceomni View Post
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)

_____________________________________

CPU: AMD Athlon 64 3800+
Asus A8N-E
RAM: 2 x 1 GB
NVIDIA nForce 4 MCP
NIVIDIA GeForce 6600
Realtek AC'87 audio
Windows Vista
USB Harddisk Lacie 250 Gb with MAC OSx86 iPC Leopard 10.5.6
Reply With Quote
  #19  
Old 01-04-2009, 10:31 PM
lanceomni's Avatar
lanceomni lanceomni is offline
 
Join Date: Nov 2008
Location: Florida, US
Posts: 521
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.

MOBO: Z77MX-QUO-AOS CPU: Core i7 3770K GPU: MSI N760 TF 2GD5/OC Case: Modded MacPro2,1
Memory: 32GB Corsair Vengeance (CMY32GX3M4A1600C9) Wifi: Airport Extreme bcm94321MCA BIOS: HermitCrab Labs H3A.816M
Monitor: AOC Q2963Pm 29" WFHD 2560x1080 21:9
Interests: KDE on Apple Darwin, Keeping it real with the command line, Helping those that help themselves
Reply With Quote
  #20  
Old 01-04-2009, 11:14 PM
ron73 ron73 is offline
Puma
 
Join Date: Jan 2009
Location: Netherlands
Posts: 18
Quote:
Originally Posted by lanceomni View Post
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.



💡 Deploy cloud instances seamlessly on DigitalOcean. Free credits ($100) for InfMac readers.


_____________________________________

CPU: AMD Athlon 64 3800+
Asus A8N-E
RAM: 2 x 1 GB
NVIDIA nForce 4 MCP
NIVIDIA GeForce 6600
Realtek AC'87 audio
Windows Vista
USB Harddisk Lacie 250 Gb with MAC OSx86 iPC Leopard 10.5.6
Reply With Quote
Reply
Thread Tools
Display Modes