Hi,
I'm pretty newbie to OSX on PC. After reading posts for like a week, I started my first installation on my Lenovo T60 laptop. Everything went fine, and I could even get both audio and network working when I first boot into Mac OS X (I know it worked cuz it correctly pulled out my apple account information). The wierd thing began since I rebooted the machine, and all of a sudden, I can never get my box on line any more. The System preference keeps telling me that the cable is unpluged (which of course is not, cuz I can get online once I reboot into Linux), and I get the following information if I dmesg in console:

===============================================
Intel8254x -- Link Down -- 00:15:41:ae:36:8f -- called by interruptOccurred() --
-- Auto-Negotiation Advertisement Register (04d) = 0xde1
-- Auto-Negotiation Link Partner Ability Register (05d) = 0x21
-- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
-- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x4000
-- PHY Specific Status Register (17d) = 0xd00

and the T60 uses Intel 82573 Ethernet chip (0x8086:109a), and I installed using iATKOS 1.0 and EFI. Any suggestions or instructions are welcome...


Thanks in advance.

Any chance on this problem? Did you get it resolved. I also have a T60, and I have exactly the same issue (and the same controller, same vendor and part IDs, 8086:109a).

It turns out that even though it says "Cable unplugged", I can get the LAN to connect by selecting BootP (you may have to switch back and forth between DHCP and BOOTP a couple of time, and it doesn't work 100% of the time).

But of course this is very annoying, so I am trying to solve the problem. Btw, I am using kalyway 10.5.2.

In my case, I switch (at startup) between DHCP with manual addressing and DHCP, selecting (as a manual address) any IP in the range my router supports (but not in use) prior to swapping back to DHCP (where the router gives out the (correct) IP address. Amusingly, the Network information *still* says that the Ethernet cable is unplugged (I call this the *false red light*).

The method itself I call the *DHCP jumpstart* method, and I've had this issue with *every* build of Leopard from 10.5.2 up (including iDeneb 10.5.5, which I'm posting from). This particular kext is old (it is, in fact, one of the few kexts still in Leopard from the Darwin Days); however, it's not as bad as the problem that the Linux crowd is having with the driver for a related (coincidence?) Intel gigabit Ethernet adapter/controller series, the PRO/1000e, where the kernel driver actually has been known to kill adapters entirely.