Jump to content
6 posts in this topic

Recommended Posts

So at the title says, I got kalyway 10.5.2 working on a Gigabyte P35-DS3L with a Allendale Core 2 Duo 1.8 and a Nvidia 8400GT. To make it simple, I was working on my computer then shut it down for the night, and the next day I turned it on to print some stuff off, networked printer, and it boots past the gray apple logo, the screen then for about 1 second shows there is no signal, then the all great black screen comes up. I've searched the forums for this problem and have found a few that have the same problems, but there were no replies and no fixes to the problem. Please help me out, because I'd love to share the fix with the other fellow members who are having the same problem. Thank you for your time.

Link to comment
https://www.insanelymac.com/forum/topic/144480-black-screen/
Share on other sites

So at the title says, I got kalyway 10.5.2 working on a Gigabyte P35-DS3L with a Allendale Core 2 Duo 1.8 and a Nvidia 8400GT. To make it simple, I was working on my computer then shut it down for the night, and the next day I turned it on to print some stuff off, networked printer, and it boots past the gray apple logo, the screen then for about 1 second shows there is no signal, then the all great black screen comes up. I've searched the forums for this problem and have found a few that have the same problems, but there were no replies and no fixes to the problem. Please help me out, because I'd love to share the fix with the other fellow members who are having the same problem. Thank you for your time.

 

boot using -v and see if it stops anywhere in particular right before the black screen. Then try -v -f and then -v -x

boot using -v and see if it stops anywhere in particular right before the black screen. Then try -v -f and then -v -x

 

So I booted using the -v and I saw IONetworkController :: Enabled right before it when black. The -v -f went way to fast for me to see what the last line of code was. When I did the -v -x I was able to boot up in "Safe Mode". I haven't yet rebooted or anything because I'm saving all my important data on another hard drive while I can. Sorry this probably isn't much help.

So I booted using the -v and I saw IONetworkController :: Enabled right before it when black. The -v -f went way to fast for me to see what the last line of code was. When I did the -v -x I was able to boot up in "Safe Mode". I haven't yet rebooted or anything because I'm saving all my important data on another hard drive while I can. Sorry this probably isn't much help.

 

Thats a great idea.

 

Basically when all of the drivers that OSX uses are located in System/Library/Extentions OSX will take all of the appropriate drivers and build a cache file called Extensions.mkext located in System/Library/ Using -f will bypass this and and pull from the extentions folder. Its obvious a kext is causing your problems. What I would do, once you have everything backed up, is to run the following command in Terminal (located in Applications/Utilities)

 

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

 

Pressing enter after each line.

The first line deletes Extensions.mkext so that OSX is forced to rebuild it on startup.

The second line sets proper permissions to the extensions folder just in case something is off.

The third line repairs permissions for your entire drive. The reason why we don't just use this line and not the second is that if you have a kext that inst from apple, OSX will not know the proper permissions to apply.

 

Reboot using -v -f

 

If this does not work then boot using -x into safe mode and open up Console (located in Applications/Utilities) Clear all of your logs. You may need to select Show Log List but go through all the logs and clear them. Now reboot normally let you system hang. Wait a minute or two and boot up using -x and check the logs. We may find out where it is really hanging. My guess is that it is not IONetworkController as it is listed as enabled.

 

You don't necessarily need to clear the log but you will have less stuff to sort through. Post both your Console Messages and System.log

THANKS, I was in a similar situation and these flags saved my bacon. Will I only need to do them once?

 

You should only need to use -f once. If you continue to have problems run this command in Terminal:

sudo rm -R /System/Library/Extensions.mkext

As I mentioned in the previous post, OSX creates a cache of the necessary drivers in the Extensions folder. Using the -f command will force OSX to pull from the Extensions folder and not from the cache. It should also rebuilt the cache file. By running the command above we are deleting the cache file, forcing OSX to rebuild it.

 

Verbose (-v) is pretty usefully and I recommend using it untill your manchine is 100% up and running. You don't need to add it every time you boot. You can add this and many other preferences to com.apple.Boot.plist located in: /Library/Preferences/SystemConfiguration/

 

The syntax goes something like this:

<key>Kernel Flags</key>

<string>boot-flags go here</string>

For example if you only want to use -v then:

<key>Kernel Flags</key>

<string>-v</string>

You can add additional boot-flags using a single space between them and no boot-flags should look like this:

<key>Kernel Flags</key>

<string></string>

×
×
  • Create New...