Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Possible fix for Appletalk startup problem Network
If you're having problems with your network initializing upon startup, this tip might help. This stemmed from my system not initializing my Ethernet on boot and hence not having AppleTalk working. I couldn't print to my Personal Laser Writer 320, so I was fairly motivated to solve this one.

As a test to see if this fix will work for you, log in as root, cd to /System/Library/ and delete or move the "Extensions.mkext" file. Reboot. If your system takes about 6-8 minutes to reboot, and the NetInfo application in /Utilities/ which had never worked before will now come up and give you network information, this fix might work for you.

Read the rest of the article for the steps to take to implement this fix...

The problem is that the Extensions.mkext file that lives in /System/Library/ does not contain the necessary information to initialize the network on boot. This file is created by the rc script (/etc/rc) at this point:
if [ ! -f /System/Library/Extensions.mkext -o \
/System/Library/Extensions.mkext -ot /System/Library/Extensions ]; then

if [ "${SafeBoot}" != "-x" ]; then
ConsoleMessage "Updating kernel extensions cache"
rm -f /System/Library/Extensions.mkext
/usr/sbin/mkextcache -l -t `arch` -o /System/Library/Extensions.mkext \
-d /System/Library/Extensions
fi
fi
If you do a man on kmextcache, you'll see that there is a "-n" option to load the system extensions that have the OSBundleRequired key set to "Network-Root". So, to force mkextcache to do this, edit the rc file in root mode and add the "-n? option. Mine looks like this:
 /usr/sbin/mkextcache -l –n -t `arch` -o 
/System/Library/Extensions.mkext \
-d /System/Library/Extensions
Save the rc script and again remove or rename the Extensions.mkext file in /System/Library/. Reboot.

Your system will take about 6-8 minutes to reboot as it rebuilds the .mkext file. Check the NetInfo application in /Utilities/ to see if networking is running. If it is, reboot again. This is the real test. The system should boot much faster this time because it's using the .mkext file to load the necessary extensions instead of looking through each one to check the OSBundleRequired key. Check the NetInfo application. If it's working and you have access to your ethernet, you're problem is solved (until something overwrites the rc script, which system updates might do – I'm not sure).

Also, make sure that in NetInfo Manager under Config - AppleFileServer - use_appletalk is set to '1'.

[Editor's note: I'll admit ignorance on this one, but if you're having AppleTalk problems, this could be a worthy troubleshooting step.]
    •    
  • Currently 3.25 / 5
  You rated: 5 / 5 (4 votes cast)
 
[9,777 views]  

Possible fix for Appletalk startup problem | 7 comments | Create New Account
Click here to return to the 'Possible fix for Appletalk startup problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
AppleTalk fiasco
Authored by: mkzsteve on Mar 19, '02 04:17:22PM

I have noticed completely contradictory AT behavior, although this only seems to occur on a Ti PB running OS X 10.1.3 (and previous versions). I use location settings to go between home and office. Generally AT is unavailable, in spite of the checkbox on the AT tab in Network System Prefs. Toggling it repeatedly (and saving between toggles) eventually gets it operational. Usually AT becomes alive with the AT check in the UNCHECKED state. I looked at NetInfo, per this suggestion, on two OS X machines and can see nothing listing the network config that would suggest AT is on or off. This brings up another point. there is no simple way I found to determine if AT is working. I have to use the GO... feature to determine if I am seeing AT-networked devices. This is heinous. I have posted this on other lists and never gotten a response.



[ Reply to This | # ]
AppleTalk fiasco
Authored by: CBROSE on Mar 21, '02 04:01:52PM

Hi:

You can query the status of AppleTalk via the Terminal command line. Do a man on appletalk or go here: http://www.osxfaq.com/man/8/appletalk.ws and see if this helps. This is an easy way to see if it's up or not.

cbrose



[ Reply to This | # ]
AppleTalk fiasco
Authored by: machelp on Apr 21, '02 05:21:24PM

Hi,
I have been suffering also from no AT.
I solved mine today by SAVING which means clicking on the lock in the NETWORK window, selecting Built-in Ethernet and Appletalk. The message
kept saying Save, so I found save in the lock in the bottom left. Worked like a
charm.

I can now print!!!!!!!!!!

Pat



[ Reply to This | # ]
Appletalk and Ethernet fixed!
Authored by: Greg on Apr 03, '02 09:33:41AM

I had the following symptoms on a G4 powerbook: removal from the network killed appletalk and ethernet, unless Internet explorer was the first app started. Then ethernet came back but not appletalk. Adding the -n flag as stated above, then restarting has fixed this problem. One note, I deleted the old config file, then added the -n flag, then restarted. Restart only took about 3 minutes.

Thanks for the tip!



[ Reply to This | # ]
Network Initialization
Authored by: jayk6 on Apr 21, '02 05:33:35PM

I have the same problem on my two G4s, but it seems to be caused by starting the computer from a CD. After installing software from a CD or running Norton System works or running Drive 10 from a CD, my network reverts to "internal modem" instead of Ethernet. This occurs regardless fo the fact that I have the network preference "locked." I don't know enough about OS X and UNIX to attempt the fix described, but I'll file it for when I understand more.



[ Reply to This | # ]
Apple's answers
Authored by: joekewe on Apr 22, '02 08:25:20PM

I assume you have seen Apple's TIL docs on AppleTalk problems:
http://docs.info.apple.com/article.html?artnum=106608

and on AppleTalk multi-homing problems:
http://www.info.apple.com/kbnum/n106614

They helped.
Joe



[ Reply to This | # ]
update still relatively valid for 10.2.2
Authored by: smkolins on Nov 21, '02 08:54:18PM

This in 10.1.x:
if [ ! -f /System/Library/Extensions.mkext -o
/System/Library/Extensions.mkext -ot /System/Library/Extensions ]; then

if [ "${SafeBoot}" != "-x" ]; then
ConsoleMessage "Updating kernel extensions cache"
rm -f /System/Library/Extensions.mkext
/usr/sbin/mkextcache -l -t `arch` -o /System/Library/Extensions.mkext
-d /System/Library/Extensions
fi
fi

becomes this in 10.2.2:

if [ ! "${netboot}" = "1" ] ; then
if [ ! -f /System/Library/Extensions.mkext -o
/System/Library/Extensions.mkext -ot /System/Library/Extensions ]; then

if [ "${SafeBoot}" != "-x" ]; then
ConsoleMessage "Updating kernel extensions cache"
rm -f /System/Library/Extensions.mkext
/usr/sbin/kextcache -elF -a `arch`
fi
fi
fi

With some modest changes to the original instructions similar correction to the behavior of appletalk returns! Specifically amend to include "n" as such
/usr/sbin/kextcache -elFn -a `arch`
and delete the Extensions.mkext file in /System/Library/
and reboot (btw, it seemed to me that this file was rebuilt after finishing a normal boot but form then on was available and taken advantage of.) Note "mkextcache" has become "kextcache" but the file it creates is still "Extensions.mkext".

Previous to doing this I could access my 10.2.2 box from appletalk (appletalk enabled in network pref pane and use appletalk set in via SharePoints) it would seem to lockup during some transfers and favor appletalk to the exclusion of IP connections. Now it can use appletalk and work consistently and it doesn't always only use appletalk (though I'm not sure I've nailed all the variables affecting this.)



[ Reply to This | # ]