Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About HazMatt

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
    MN, USA
  • Interests
    FileMaker, Halo.
  1. Well, I chatted with an Adobe employee tonight and kindly asked them to fix the problem, and they opened up another activation slot for me. So, next time I mess with things I shouldn't be messing with, I'll be sure to deactivate software that relies on things like serial numbers and stuff. Ugh.
  2. So iMessage wasn't working for me and I was attempting to fix it by editing org.chameleon.Boot.plist and installing some NVRAM files. It didn't work, but I did succeed in borking my Adobe CS 5.5 installation. Now whenever I launch Photoshop or Dreamweaver I get the Adobe Activation prompting me to enter a new serial number or retrying the activation. Retrying fails, and I don't have another serial number (we have a legitimate copy of CS 5.5, where the SN is only installed on my and my wife's computers, which is allowed). So, I'm positive Adobe thinks I am trying to use this on a new computer or something. I've tried reverting the changes and even replaced some Adobe files from a backup of my boot volume from yesterday, restarted, and I'm getting the same problem when I launch an Adobe app. Do I have to go crawling back to Adobe and beg them to reset a license activation? Here's a screenie:
  3. I'll PM you the .kext I use. I don't know why they took down that page.
  4. Some updates… Over the last couple of days I kept an eye on the level of RAM that kernel_task was consuming, and this time it did NOT ramp up to eat it all up. For the first day I left the cable unplugged and it remained at 1.45 GB. It climbed to 1.77 GB and then I plugged in the ethernet cable. A day later it was still at 1.77 GB. I don't really know what that all means, but perhaps my previous RAM usage was a fluke. I decided to give my original .kext file a try again (the now defunct one, formerly available here), and it worked, but only after I deleted both my existing WiFi and Ethernet interfaces from System Preferences > Network. So, the good news is I'm back up and running, but I'm not using the .kext available in this thread. I'm going to watch this thread and will likely be able to test out newly released versions.
  5. I restarted, left the ethernet cable unplugged overnight and my RAM usage appears to be back at a more reasonable level. kernel_task is still steadily eating up RAM (currently at 1.81 GB), but I don't know if that's abnormal for my system or not. This is with the driver installed. I still have yet to run those Wireshark tests, hopefully I'll have some results by the end of the weekend.
  6. New information… Apparently something in the kernel_task process is mucked up, because it is eating up all of my spare RAM:
  7. I downloaded and successfully installed Wireshark on my wife's MacBook Pro but didn't have time to really dive into the program (wife needed it for work). By "connect the machine directly to the remote machine", I'm assuming you mean via a crossover cable? There was a heck of a lot of noise going on when I was doing a "Capture" (due to all of the other devices on our network), so I think it would be wise to isolate that a little bit. During my initial ping tests with a manual IP config, I was getting "No route to host" error messages. While I'm familiar with the Ping tool and have used it many times before, the extra diagnostic steps you're describing are new to me, so I'll have to muddle my way through it and post back later.
  8. Yes, all I meant was that my ethernet port appears to be able to communicate successfully with the outside world to some minimal extent. While it knows what speed it should be connecting at, I get the same problem, regardless of the switch on the other end. var/log/system.log: Output of ifconfig -v -a: I'll look into the Wireshark test in a moment and post back…
  9. Yeah I don't know what to say. I've gone back and forth, installing both the regular and debug versions using the same exact install procedure. I have had good luck before using Kext Wizard, as permissions are set automatically for me. Kext Wizard also has some maintenance utilities that repair permissions and rebuild mkext on /Extra, which I have done after each install as well. I'm running OS X 10.8.4. Using the debug version: • Ethernet interface disappears from System Preferences > Network. • System Information > Hardware > Ethernet Cards reports that no cards are connected. Using the regular version: • Ethernet interface is recognized correctly in System Preferences > Network. • Using DHCP, the IP address is always 169.254.XXX.XXX; the X's are the only numbers to change after renewing the DHCP lease. • Physically unplugging the ethernet cable causes the Ethernet interface to report "Not Connected / Cable Unplugged", which is good. • The LED on my 10/100 Netgear switch is always blinking like mad when plugged in, even though no traffic is probably getting through. See screenshots below for more details… Thanks for the attention, Alex! Since I'm in the mood to be thorough, I bypassed my 10/100 switch and plugged my computer directly into a gigabit port on one of our Netgear switches. Things appear to have switched over successfully to 1000baseT (full-duplex) in System Preferences > Network > Advanced > Hardware. I'm not sure if this proves anything, but it's additional information that might be helpful.
  10. … continued discussion from here … Briefly, I'm having trouble with my Ethernet interface disappearing after reboot (System Prefs > Network says "Cable Unplugged" with red icon). 'Ethernet' is not in the add list. I installed BCM5722D 2.3.5 (ML_BCM5722D.kext.zip) and now Ethernet is showing up again. BUT, the DHCP pulls a bogus IP address (169.254.XXX.XXX) and manual assignment doesn't work either. Alex has suggested I install the debug version, which I have just done, but now the Ethernet interface is gone again. Maybe the debug version is an older version that doesn't include the 2.3.5 fix? I'm very motivated to fix this problem, so I'll pretty much do whatever anyone suggests!
  11. Alex, I followed your link and was excited to see this note(!): Now the Ethernet interface shows up (YAY!!!), but I'm still having problems connecting with it. I'm getting an invalid 169.254.XXX.XXX IP address, and setting an IP manually doesn't work either. Here are my exact steps I've done: 1) Downloaded the ML_BCM5722D.kext.zip 2) Copied original IONetworkingFamily.kext from System > Library > Extensions 3) In this copy, placed BCM5722D.kext into Contents > Plugins, like you suggested 4) Installed modified IONetworkingFamily.kext into Extra > Extensions with Kext Wizard 5) Rebooted 6) Went to System Preferences > Network and immediately was notified of a new interface (and added it successfully) Here's what System Information reports: I've done some furtive searching elsewhere on the invalid 169.254.XXX.XXX IP address issue and the only advice seems to be to make sure to use the right .kext file. Should I be concerned that the fix only seems to list BCM5722D, when my actual ethernet card is a BCM57781? Thanks for the tip, and I hope to finally solve this annoying problem!!
  12. Just chiming in here since we have the same motherboard 'n stuff. I've had the ethernet port working off and on, including 10.8.3 and 10.8.4. Lately when I've been restarting the ethernet port stops working and in the Network preference pane it just lights up as red saying "Cable Unplugged." Then when I delete the Ethernet interface and try adding it back again it's completely gone from the choices. I've gotten it to work but for the life of me, I can't figure out what really is the "magic" setting. I was using the IONetworkingFamily.kext file from this link (http://www.osx86.net/view/3089-broadcom_netlink_bcm57781.html) but that link goes nowhere now (apparently). Basically, the ethernet port has worked great for me… when it works.
  13. I should poke around the BIOS and try to find that… but… suppose I want to make it work, now that I rediscovered this wonderful feature that I never use? Here's what I see in Apple System Profiler: Ultra Fast Media Reader: Product ID: 0x4064 Vendor ID: 0x0424 (SMSC) Version: 1.90 Serial Number: 000000264001 Speed: Up to 480 Mb/sec Manufacturer: Generic Location ID: 0x1d131100 / 8 Current Available (mA): 500 Current Required (mA): 96 I see this post here from nikkpap has a method for editing a couple of Apple kext files. Are there any other (better) solutions out there?
  14. Wow, I'm surprised at myself; I DO have a card reader. It's built into the left-side of my Dell U3011 display, and I never used it. I suppose it was causing problems because it was detected along with the rest of the USB hub in the monitor. I will have to look into this more specifically when I have time. In the mean time I have unplugged my monitor's USB cable and am routing my mouse and keyboard directly to the ports on the back of the computer. EDIT: I should mention that I have indeed isolated the cause of this problem to the USB hub on the monitor.
  15. I'm perfecting my 2nd Hackintosh; the Mattintosh 2 (see signature for specs). I have a few nagging issues that I can't seem to fix, and I figure it's best to start with the first ones that pop up, and maybe when they get fixed, some or all of the others down the line will get fixed too. Here's what I'm seeing on startup, immediately following the ASRock boot screen: EBIOS read error: Error 0x31 Block 0x0 Sectors 0 EBIOS read error: Error 0x31 Block 0x0 Sectors 0 EBIOS read error: Error 0x31 Block 0x0 Sectors 0 EBIOS read error: Error 0x31 Block 0x0 Sectors 0 Here's what spits out when I run lspci from the Terminal: pcilib: 0000:03:00.0 64-bit device address ignored. pcilib: 0000:03:00.0 64-bit device address ignored. pcilib: 0000:00:02.0 64-bit device address ignored. 00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Ivy Bridge PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4) 00:1c.3 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 4 (rev c4) 00:1c.4 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 5 (rev c4) 00:1c.6 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 7 (rev c4) 00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04) 01:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN adaptor (rev 01) 03:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57781 Gigabit Ethernet PCIe (rev 10) 04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10) 05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller At this point I don't know which hardware component is causing those EBIOS read errors, or even if it's a hardware thing to begin with. The few threads I've dug up online have pointed to card readers, but I don't have a card reader. I will happily list further details if requested.