MB5,1 Ethernet Not working with LION - False Alarm

Discussion in 'MacBook' started by hekokimushi, Jul 28, 2011.

  1. hekokimushi, Jul 28, 2011
    Last edited: Jul 28, 2011

    hekokimushi macrumors regular


    Oct 27, 2008
    I googled, searched, no one has yet reported this.

    i normally just use my Wifi. everything seems transparent.
    cleaned installed Lion on me SSD.

    I thought my MB5,1 was a very successful running Lion 10.7.1, working flawlessly, until this morning.
    My Hackintosh's Mainboard's CR2032 battery is dead/flat, which caused boot problems. including LAN. i troubleshoot by putting the LAN cable to my macbook, instead of picking up an assigned IP from the router of 192.... it stays at 169... as an IP address wouldn't update thought it must be the cable or the router port, i tried another cable that i took off from another online computer to the same router that was working, hooked up with the MB, same 169.... same IP, rebooted the router, same.

    put the same cable back to another computer, picks up the normal IP 192... tried one last time with the MB. nope 169...

    Anyone's MB5,1 have their Ethernet working? with ability to pick up an IP from DHCP or router?

    any chance to have your kext please?

    P.s. yes, i restarted my macbook. same same.



    apologise. had the router's external MAC address mirrored. didn't think that would cause a problem in my LAN. but it did... changed the external MAC address, working fine. Recommend a CLEAN install on all Units for Lion. flawless thus far
  2. Detrius macrumors 68000

    Sep 10, 2008
    Asheville, NC
    So, you had manually broken your network settings, and as a result, you're recommending people format their machines when they install Lion? Why?
  3. hekokimushi thread starter macrumors regular


    Oct 27, 2008
    i recommend a clean install as i have not had any problems that many are reporting. i did a clean install.

    my screw up with my network setting made me believed the setup wasn't flawless. but proven it wasn't Lion's problem.

Share This Page