Jump to content
8 posts in this topic

Recommended Posts

If anyone could help, I would be so grateful!

 

I have an Abit AV8 motherboard with on-board Giga-bit ethernet. This is not recognised and will not work so I have put in an old Network card - Allied Telesyn AT2700TX - and MacOSX sees the card, configures it as a built in Ethernet card and everything seems fine... until I try to access either the network or Internet - then nothing. The network settings have a green light, it says I have an IP address and that everythign is fine.

 

I can't think what to do. Is there something that would make this card work? It seems the operating system thinks it shoudl work!

 

Thanks,

 

Gareth

I've now tried this with a different card, one that the HCL says should work out of the box and I have exactly the same problem :(

 

If I ping my router I get nothing, even though the green light is on and it OSX says I have a connction.

 

It feels so close!

What version of IONetworking Family.kext are you using I was having trouble with the 10.4.4 kext file so copying IONetworking Family.kext from 10.4.3 install seemed to work - had to do this again when instaaled 10.4.5

I'm using 10.4.3 kext and running 10.4.3. I have now tried four different NICs, one on-board, and three PCI cards.

 

The onboard one comes up red and will not work; it is grayed-out in the network config screen. The other three all do the same - they are recognized by the OS, they can be configured manualy and they appear to work - but don't. If I try to configure by DHCP, they come up with a 169. address instead of 10. address and an incorrect subnet too. They only come up with this after restarting System Preferences. If I hit Renew Lease while in the settings I get nothing. I cannot ping my router either.

 

Weird.

When this first happened to me, I tried all that copying and gave up. No matter which version of the IONetworking kext I used it still didn't work. So then, after updating to 10.4.5, I loaded the drive in VMWARE. I checked out the pref pane, it worked in VMWARE! Then I reboot native (no VMWARE) and now it's working in 10.4.5. Strange, but worth a try for you guys...

×
×
  • Create New...