Jump to content
InsanelyMac Forum

FUT1L1TY

Members
  • Content count

    110
  • Joined

  • Last visited

  1. FUT1L1TY

    New Driver for Realtek RTL8111

    Thank you for the pointer in the right direction. I wound up using darkwake=8 as suggested in this in-depth article and now everything is working as expected. http://www.cnpbagwell.com/mac-os-x/bonjour-sleep-proxy I'd also like to thank Mieze for his work on this awesome driver. It's nice to have WOL working on my machine again.
  2. FUT1L1TY

    New Driver for Realtek RTL8111

    Can anyone reproduce this WOL bug I'm seeing? I'm using version 1.1.3 of the driver and OS X 10.9.1. Steps: 1) put the machine to sleep (using the apple menu) 2) Wait a minute or so (going to sleep takes forever in mavericks) 3) Use a second machine to send a wake-on-lan packet to the sleeping machine Result: The machine wakes up but the screen stays asleep. I can wiggle the mouse to wake the screen up. Comments: The monitor wakes up correctly when I wake up the machine using a more traditional method such as the keyboard. I know it's a rather small bug but I'm curious if others are seeing this. Great driver. I just switched from Linx2Mac. Thank you.
  3. Very cool news indeed. Do you know by any chance if true hot swap is working properly with this chipset? If you or anyone else with this card is capable, please try the following: 1) hook a drive up to the card and turn on your machine 2) open system profiler and make a note of the negotiated link speed 3) eject the drive by dragging to trash 4) disconnect the sata data cable to the drive and wait 5 seconds 5) reconnect the sata cable to the drive Questions: 1) does the drive remount? 2) if yes to above, please check the negotiated link speed, is it the same as in step 2 above? Thank you!
  4. Please read my edit to my original post.
  5. Hello Rankrotten and Dajjal, In my experience trying to get hot swap to work, I would get 3.0 Gigabit negotiated speed only if the drive was mounted at startup. Any drive the was mounted or remounted at a later point would connect at 1.5 Gigabit. This drove me crazy so I stopped using it. I was however able to get true hotswap (except for the full speed part) using this thread and JMB36X chipset. I inserted this code at the end of Device (PEX0) Device (EATA) { Name (_ADR, Zero) OperationRegion (BAR0, PCI_Config, 0x40, 0x04) Field (BAR0, WordAcc, NoLock, Preserve) { Offset (0x00), M1, 8, Offset (0x01), M2, 8, Offset (0x02), M3, 8 } Method (_DSM, 4, NotSerialized) { Store (0xb3, M1) Store (0xa1, M2) Store (0xc2, M3) Return (0x00) } } Device (EPTA) { Name (_ADR, One) OperationRegion (BAR0, PCI_Config, 0x40, 0x04) Field (BAR0, WordAcc, NoLock, Preserve) { Offset (0x00), M1, 8, Offset (0x01), M2, 8, Offset (0x02), M3, 8 } Method (_DSM, 4, NotSerialized) { Store (Zero, M1) Store (Zero, M2) Store (Zero, M3) Return (Zero) } } Unfortunately, I can't remember if I was using a PCIe card with a Jmicron chip or the onboard chip. The above code will work with either, it's just a matter of inserting it into to the proper location/address space within the DSDT. EDIT: The above DSDT edit is for JMB 36x chipsets only where true hot swap is not working. True hot swap is defined by the ability to mount a drive, physically eject it, and insert a different drive on the same port and have it automatically mount. If hot swap is already working for you on your JMB 36x ports then you do not need this edit. Drives mounted in this fashion will connect at 1.5 Gigabits regardless of their interface speed. This is not fixable as far as I can tell. Finally, the location of the above edit varies based on your motherboard. Do not insert it without first checking the address of your Jmicron chipset(s).
  6. I just checked my kernel log and found that I haven't had turbo ratios since June 17. I don't remember making any changes on that day. What's interesting is that you can see the log message changed on the 23rd when I installed 10.6.8. Any thoughts? Jun 17 13:00:06 localhost kernel[0]: AppleIntelCPUPowerManagement: Turbo Ratios 1112 Jun 17 13:00:06 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete Jun 17 13:00:06 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 17 15:26:58 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete Jun 17 15:26:58 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 17 18:25:11 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete Jun 17 18:25:11 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 19 18:42:48 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete Jun 19 18:42:48 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 23 16:49:38 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete Jun 23 16:49:38 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 23 16:58:22 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 16:44:42 Jun 7 2011) initialization complete Jun 23 16:58:22 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 23 17:06:24 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 16:44:42 Jun 7 2011) initialization complete Jun 23 17:06:24 localhost kernel[0]: AppleIntelCPUPowerManagementClient: readyGo Jun 23 17:10:17 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 16:44:42 Jun 7 2011) initialization complete Jun 23 17:10:17 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 24 22:36:26 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 16:44:42 Jun 7 2011) initialization complete Jun 24 22:36:26 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready Jun 24 22:51:12 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 16:44:42 Jun 7 2011) initialization complete Jun 24 22:51:12 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
  7. What a coincidence? I was having the exact problem and I finally had the time to fix it. I was not scientific about the process but I will tell you everything I did. 1) Even though I was running 10.6.6 I re-installed 10.6.6. using the Combo Update (approx 1gig) 2) Repaired permissions using disk utility 3) Ran Disk Warrior (do not do this if your bootloader is on your mac partition) 4) Ran Onyx and cleaned up as much I could think of (sorry I can't be more specific) 5) Ran Activity Monitor and looked for processes that were questionable or not needed and got rid of them 6) Ran Console and looked for error message and fixed the causes. There were a lot of these. 7) Set my Energy Saver control panel as pictured below Auto and manual sleep are now working again and I can wake up via keyboard and mouse. Good luck.
  8. I was thinking about checking out the new AnVAL bootloader. Does anyone on this thread have any firsthand experience with it? If so, do you have any tips or tricks that I should know given my config (below)? Any and all information is appreciated. Thanks.
  9. Installed 10.6.6 via Software Update this morning. Rebooted. Ran Geekbench. No perceivable problems at this moment. Your mileage may vary.
  10. 1 & 2. A boot cache is technically only needed if you are have kexts that are plists only. IOAHCIBlockStorageInjector.kext and LegacyIntel82574L.kext are really just plists. Whatever you do don't have kexts in /Extra/Extensions/ and an Extensions.mkext. That causes problems. Stored_Kexts allows you to have kexts in a folder that the bootloader doesn't see. It's a convention taken from Digital Dreamers installer script. 3. Nope, as far as I know you have to install a ethernet driver for the realtek chip on your mobo. The alternative, would be to purchase an ethernet card that works with with Mac OS built in drivers. You can find a list of such cards by googling. 4. IOAHCIBlockStorageInjector.kext is purely cosmetic. LegacyIntel82574L.kext is a plist that makes Mac OS built in driver work with my ethernet card. PlatformUUID.kext is so that my software licenses don't get messed up. All the C2R4 based bootloaders changed how hardware UUIDs are generated. By using PlatformUUID.kext I get to keep my old hardware UUID.
  11. I would be glad to assist since I'm am a strong advocate for installing the bootloader onto a usb flash drive. Anyone who is interested should try the following: 1) place the usb stick into a working usb port and launch apple's disk utility 2) format the usb stick as GUID Mac OS Extended (Journaling is not necessary for this application) 3) quit disk utility 4) select the usb stick in the finder and rename EFIBOOT1 (you'll know why later) 5) press command-I (get info) 6) in the EFIBOOT1 info window, authenticate by clicking the lock in the lower righthand corner 7) Deselect (uncheck) "Ignore ownership on this volume" 8) Close info window and reboot your computer (because of a weird Mac OS bug) 9) After reboot open EFIBOOT1 in the finder and create the 5 folders with the same hierarchy you see in the picture below 10) download the bootloader of your choice and place the 3 files in the Bootloader directory of EFIBOOT1 11) unzip the attached file below and place the two files in EFIBOOT1 in the location indicated by the picture below 12) launch terminal and type "disktutil list" without the quotes for steps 12, 14, 15, and 16 13) look for EFIBOOT1 in the list. To the right you will see an identifier diskXs1. Make a note of the value of X. 14) type "sudo fdisk -f /Volumes/EFIBOOT1/Installer/Bootloader/boot0 -u -y /dev/rdiskX" replacing X with the value in step 13 15) type "sudo dd if=/Volumes/EFIBOOT1/Installer/Bootloader/boot1h of=/dev/rdiskXs1" replacing X with the value in step 13 16) type "sudo cp /Volumes/EFIBOOT1/Installer/Bootloader/boot /Volumes/EFIBOOT1/" 17) put whatever kexts you want in Extra/Stored_Kexts folder (only fakesmc.kext is required) 18) Create a kext cache by double-clicking on Update_Boot_Cache 19) The last three things you need are com.apple.boot.plist, DSDT.aml, and smbios.plist. You can find these pretty easily by perusing the forums. Place these in /Extra. 20) Reboot, hold the Delete key down to enter BIOS. Set the usb stick to be the boot drive. Save BIOS and exit. 21) The computer will reboot. Right before the bootloader launches hold the F8 key. 22) Select the drive you would like to boot from using the arrow keys and press enter. Good luck. That should hopefully work for you. Please check all your spellings including case. Your boot stick should look just like mine except for the kexts. Also, please note the com.apple.boot.32.plist is identical to com.apple.boot.plist with the exception of the x86 flag. I don't normally use the 32 version. I just keep it around in case I need to switch back to 32 bit mode. files.zip
  12. For those who are interested I've had partial success with SATA hot swap as I will describe below: I purchased a Highpoint 620a 2 Port internal SATA 6gb card ($30) and connected it to my pair of Kingwin KF-1000-BK trayless hotswap bays. The good news is that I finally was able to eject a drive in the finder, physically remove it, re-insert the drive, and it would automatically mount. Not only that but I could also remove a drive and replace it with another drive and that drive would also mount. In bad news, I discovered that the drives were negotiating a 1.5 megabit connection even though they were 3.0gb drives. The only way I could negotiate a 3.0gb link was if the drive was inserted before my machine powered up. In that scenario, the drive would be linked at 3.0gb. As soon as I hot swapped the drive it was down to 1.5gb. I'm assuming that is a bug/limitation in the card. Needless to say, I've been given some hope. I've finally seen with my own two eyes what others have described. I'm certain that true sata hot swap is possible on a "mac" and I don't mind paying $30 for this feature. If anyone knows of a PCI/PCIe card that supports SATA II/NCQ/hot plug that is AHCI based please let me know. AHCI is a must so that attached drives can be booted. Thank you again for helping/listening.
  13. Hmmmm indeed. What incarnation of iStat are you using? The widget, the menu, other? I don't see these message in my console with the menu version.
  14. That's good to know. Can you also try this: 1) Eject a drive by drive by dragging to trash 2) Remove the drive physically 3) Re-attach the drive physically Afterwards, please open up Console and look for any related messages in: DATABASE SEARCHES/All Messages FILES/system.log There might be some valuable clues here. Thanks again.
  15. Thanks again Rankrotten. It will take me a while to go through all of this. In the meanwhile, I have more easy question. What kexts are in your /Extra folder? Thanks.
×