On Sep 10, 2008, at 10:25 AM, insightinmind wrote:
> That's what I've been trying to do ... Delete ("Delete" under Panther,
> "-" under Leopard) the en0 port aka "Built-in Ethernet", but, under
> Network > Network Port Configurations, it just doesn't go away.
>
> I was curious then, if I could find an Extension that I could Trash
> and
> have the en0 port go away, that way ...
> Yes ... confession: I'm on an XPostfacto'd PowerPC 8500 w/ Sonnet
> G4/450 ... but I don't think that matters ... pardon the intrusion, if
> I have done so ...
The 8500 being an "unsupported OS X" Mac does explain the "en0" vs.
"Built-in Ethernet" port name discrepancy. This 8500 built-in ethernet
will be 10 Mbps whereas your Asanté card is likely 100 Mbps, so you
should always prefer the Asanté. In Panther, the hardware is
determined by explicit device ID#s in the info.plist file of the
ethernet .kext. In Leopard this should be changed to some type of
implicit score built upon a polling of the hardware, but obviously
you're not using Leopard on an 8500.
I don't know why the port won't allow you to delete it properly. As an
alternative, in Panther you could possibly identify the Vendor ID #
and Product ID # of this built-in ethernet (look in System Profiler,
or use IORegistryExplorer), and then identify the associated ethernet
kext (could be a plugin kext within a larger kext), open the
info.plist (can use Text Edit) and delete the line(s) containing the
associated VID# & PID#. You'd also need to delete the kextcache file
so that it's rebuilt. Also, the will be permissions issues with
editing the .plist file, you'll need to restore the correct
permissions and ownership for the edited kext to load correctly. Seems
like too much work to me unless this is a big problem.
I think it's unlikely you could delete an entire Apple ethernet kext
and still retain functionality of the Asanté card, but perhaps I'm
wrong if the Asanté has it's own dedicated kext.
Again, I don't understand "what" or "how" an unused, disconnected port
is "connecting" to? If there is no cat5 cable attached, even if the
port is shown as active in Network System Preferences, it shouldn't be
doing anything, unless the "fried" thing you've mentioned is somehow
causing a spurious false activation? Certainly it should be
independent of the Asanté card's port, meaning it shouldn't interfere
with the ability of the Asanté card to be recognized or connect if
properly configured.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed Low End Mac's G3-5 List, a
group for those using G3, G4, and G5 desktop Macs - with a particular focus on
Power Macs.
The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette
guide is at http://www.lowendmac.com/lists/netiquette.shtml
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/g3-5-list?hl=en
Low End Mac RSS feed at feed://lowendmac.com/feed.xml
-~----------~----~----~----~------~----~------~--~---
