Jump to content

flyingtinopener

Members
  • Content count

    3
  • Joined

  • Last visited

About flyingtinopener

  • Rank
    InsanelyMac Protégé
  1. [SOLVED] Really weird Realtek 8168 problem

    Yeah it occurred to me that might fix it. I'm in the process of doing a CMOS reset and reconfiguring the BiOS right now. Will post an update afterwards whether it worked or not. Yeah, confirming that CMOS reset did in fact solve this issue. Awesome.
  2. Hello, Having a super unusual (possibly unique) problem with my network adapter here. Been up down half a dozen forums with no hits. This morning, I had a perfectly functional 10.8.2 installation. The internet was working just fine with Lnx2Mac Realtek kext. There were, however, some intermittent connection drops and packet loss problems. I isolated the problem to OSX by checking similar behavior on my Windows partition and my laptop (Windows/Linux dualboot). So then I decided to see if I could fix the issue by trying out a different kext. After backing both the Lnx2Mac and the IONetworkingFamily kexts, I uninstalled the Lnx2Mac kext, replaced it with Slide's newly released R1000SL. Repaired permissions, rebuilt the cache and rebooted. Internet stopped working. I just replaced the backed up files, rebooted to regain the internet, and when I came back in, internet still wasn't working. Now the really weird part is that, OSX still thinks that there's an Ethernet connection active even when I unplug the cable. In network settings, the Ethernet connection is shown as "Connected". It has an IP address (169.254.134.{censored}) and a Subnet Mask (255.255.0.0). However, it doesn't have an IP for the Router, or the DNS Server, or the Search Domains. Sure enough, when I check my router's connected devices page, my Hackintosh isn't visible there either. These settings don't change when I unplug the ethernet cable. The computer still thinks it's connected. I've never seen anything like this in my life. Can't figure out how to fix this for the life of me. I tried everything, including restoring kexts from my installation USB. No success whatsoever. If someone can point me in the right direction, I would really appreciate it. I can provide an IOReg output if that's going to be helpful. Just let me know. Hardware: - Core i7 2600K 3.5GHz - ASRock P67 Extreme4 Gen3 (Realtek RTL8168 on-board) - Gigabyte nVidia GTX 680 Thanks!
  3. Hey folks, First of all, you guys rock. If it wasn't for all the work you do in these forums, I wouldn't be making this post from OSX Mountain Lion. So thanks. Anyways, I recently installed OSX 10.8.2 on my desktop (will give specs below in detail). Almost everything worked flawlessly straight out of the box. Had to install Realtek audio kext but that was it. Unfortunately, HDMI audio is still not working. To fix the problem, I found some guides on the subject at tonymacx86.com. Bit of research revealed that I should be using their HD3000 AMI EFI patch because my motherboard has an Intel 6 series chipset and i7 2600K is a sandy bridge CPU with an HD3000 core in it. The steps I followed: 1) Extract fresh DSDT. Put it through DSDTFixer to clean up compile errors. 2) Read IOReg to determine hardware locations, device ID and layout ID. 3) Make necessary edits to the provided patch file (as best as I could tell, no edits were necessary) 4) Place dsdt.aml into /Extras. 5) Reboot What I got in return is basically repeated kernel panics. I had to go in with the installation USB and delete the dsdt.aml via the terminal to be able to boot back in. Below are my system specs: - Core i7 2600K 3.5GHz (Sandy Bridge) - ASRock P67 Extreme4 Gen3 (Intel 6 series chipset) - Gigabyte nVidia GTX680 2GB (w/ latest nVidia drivers - QE/CI working) - 16GB DDR3 1333MHz - OCZ Vertex4 256GB SSD (OSX Mountain Lion) - OCZ Vertex4 120GB SSD (Windows 8) - Samsung 7200rpm 500GB HDD (misc data) I'm attaching my current IOReg and default dsdt.aml below for your reference. I would really appreciate it if someone could point me in the right direction. Been reading about dsdt editing and trying different things for almost a week now with too many kernel panics to count. Pretty new to this stuff so I feel like I might be missing something obvious. Thanks in advance! CurrentSystem.zip
×