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 iFrodo

  • Rank
    InsanelyMac Protégé
  1. I finally got the new version (.156) working. Before I had black screen with spinning wheel with my NVidia 980 Ti graphic card. Here what I did: 1) Uninstalled existing (patched) driver (.106) using the NVidia Uninstaller (Open Uninstaller... button in NVidia Driver Manager preferences pane) 2) Activated SIP in Clover (0x0 instead of 0x67) 3) Restarted 4) After reboot (so with VESA display mode), reinstalled the new driver. 5) Reboot, still with SIP enabled and voilà, it worked. I think some files/kexts from previous version (don't know which ones exactly) aren't deleted/replaced by new driver version on installation correctly and are incompatible with the new version. The key here is the full uninstallation of previous version. I don't know if enabling SIP helped or not, but it doesn't hurt. And so far no lag observed.
  2. Broadcom 570x and 575x

    You can still use the Leopard driver, patched as indicated on this thread. But as it's 32bits, it'll only work when booting in 32bits mode (arch=i386 or -x32 depends on the bootloader you are using).
  3. I'm looking for a 32/64 bits version of BCM5751 ethernet driver. I'm still using the old 2.1 version of the driver I found on another topic, but it's 32 bits version only. And Snow Leopard doesn't provide any vanilla version of it that I could patch. Is that imaginable that someone create an open source BCM5751 ethernet driver that could be available in 32/64bits universal binary version? Maybe it does already exist, in that case where can I find it?
  4. Cool thanks The only missing thing now for me to be fully 64 bits ready is a 32/64bits AppleBCM5751Ethernet.kext with the associated compatible IONetworkingFamily.kext (if the vanilla one doesn't fit with it)...
  5. I'm using Disabler.kext to disable AppleHPET.kext that cause issues on my machine with rear USB ports not being available. I tried to use the NullCPUPowerManagement.kext to do the same work, adding the properties in the Info.plist: <key>AppleHPETDisabler</key> <dict> <key>CFBundleIdentifier</key> <string>org.tgwbd.driver.NullCPUPowerManagement</string> <key>IOClass</key> <string>NullCPUPowerManagement</string> <key>IONameMatch</key> <string>PNP0103</string> <key>IOProbeScore</key> <string>2000</string> <key>IOProviderClass</key> <string>IOACPIPlatformDevice</string> </dict> But it doesn't works. NullCPUPowerManagement.kext disable the IntelCPUPowerManagement.kext based on its IOResourceMatch, but doesn't seem to support, like Disabler.kext, disabling kext based on IONameMatch. And in order to prepare myself to future use of 64bits kernel, I'm looking to 64bits version of the kest I'm using. But I still don't have a 64bits Disabler.kext, that's why I'm asking of anyone can provide me a download link to a 32/64bits version.
  6. Ok, I solved my sound issue downloading VoodooHDA here: VoodooHDA 0.2.2 SL
  7. Hello, I've got Snow Leopard up and running, but I still have two small issues: - The sound is not working: On Leopard I used the ACL-262 package, which is a patched AppleHDA.kext from iPC 10.5.6. Of course this doesn't work on Snow Leopard (it Kernel Panics). Any solution to suggest, the cleanest one, the better. - The second issue, is not as big, and happens randomly. Sometimes, when I boot, the Kernel doesn't find the root device and wait indefinitely for it (printing a message saying "Still waiting for root"). I'm booting using the partition UUID. Also the disk partition table is using the MBR format, not the GUID format (I didn't want to reformat my drive). Any idea why this happens? Also, I'm using the netkas' IntelPIIXATA.kext as the original vanilla kext kernel panics. Thanks in advance to all who can help Bye
  8. I'm using the Boot-123 method to boot the Retail DVD, and it works just fine, but I've a question: Is there a way to still use MBR as partition table format, because my current Leopard installation is on MBR, and I just want to do an upgrade without reformating. Does anyone know a trick to install it on MBR anyway?
  9. Ok I solved my problem myself. I just changed the SATA mode in the BIOS from RAID+AHCI (unsupported apparently) to AHCI, and then Chameleon loaded just fine and the OS too.
  10. Hello, I've tried to install the iPC 10.5.6 Final on an HP Workstation xw4400 (Core2Duo 2GHz, Intel i975X chipset) with Intel 82801G (ICH7 Family) SATA controller, and I have issues to have my installed system booting from the harddisk installed bootloader. The DVD boots just fine, and all my hardrives and partitions are detected just fine. I've installed OS X on the second SATA connector, which make the partition identified as /dev/disk1s1 I've installed with ICH7 SATA Chipset drivers (for SATA support) and Legacy PIIX IDE driver for my DVD drive support (connected using IDE not SATA), also I installed the natit video driver (I've an ATI FireGL v3350 card), AC97 audio driver, apple Broadcom 5751 network driver (for the Broadcom 5755 integrated adapter), USB driver fix, the SMBIOS ToH fix, USB Mount fix, the Voodoo power management, PCI detection fix, the shutdown/restart fix. When I try to boot, what happens is that it keeps saying 'still waiting for root device' Also I've error on AppleUSBEHCI initialization saying: USBF: 0.435 AppleUSBEHCI[0x6102000]: unable to get filterInterruptEventSource USBF: 0.437 AppleUSBEHCI[0x6102000]::UIMInitialize - Error occured (0xe00002be) USBF: 0.459 AppleUSBEHCI: unable to initialize UIM This last line is repeated 3 times at least. Then I've: From path: "uuid" Waiting fot boot volume with UUID 741BA0CD-741B-3603-9F6C-916B4E81173C Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict> Then after several seconds: Still waiting for root device. Repeated indefinitely. I tried to boot with -v and -f -v options with no better result. What I noticed is that no line about a SATA driver being loaded is written on the boot log, is that normal? I've also tried with both vanilla kernel and voodoo kernel. In all cases it fails to boot with 'still waiting for root device'. I also tried to specify the boot device on the booloader: rd=disk1s1, but it still not booting... Other strange thing is that if I boot from the DVD Install bootloader (using rd=disk1s1) it starts just fine. I've tried putting the DVD kernel on the OS X partition, and boot using the harddisk bootloader, and it still fails the same way as with vanilla kernel installed by the installer. So it definitely not seem to be kernel related, but rather either bootloader related or extensions related. I've tried to install Chameleon 2.0RC1 also, but it fails miserably saying: "boot1: error", so no go with it If anyone can help, that would be greatly appreciated
  11. Are you sure the CD is correctly burnt (Have you burnt it using Disk Utility? Have you verified it?)
  12. The restore CD has been specifically designed to restore the firmware in the eventuality that a firmware update process has been interrupted: "The Firmware Restoration CD can restore the firmware of an Intel-based iMac (Early 2006), Mac mini (Early 2006), or MacBook Pro to original factory condition. You can only use this to restore the Firmware after an interrupted or failed update. If your computer is already in this state, you'll need to download the software and create the CD on another Macintosh computer, or you can take your computer to an Apple Store or Apple Authorized Service Provider to restore your firmware. This CD can be created on both PowerPC and Intel-based Macintosh computers." So it's specifically designed to solve a problem like yours, and so it MUST works. You probably didn't follow the instructions strictly. Follow the instruction for the restore CD exactly as stated on the Apple page. It's important that you follow the instruction strictly!: http://docs.info.apple.com/article.html?artnum=303469 To restore your computer's firmware, first create a CD using the disk image named "FirmwareRestorationCD.dmg": 1) Launch Disk Utility (located in /Applications/Utilities). 2) Click on the Burn icon or select the "Burn..."menu from the Images menu. 3) Navigate to where FirmwareRestorationCD.dmg is located and click the Burn button. 4) Insert a blank recordable CD or DVD. 5) Click the Burn button to create the Firmware Restoration CD. The files are burned to the disc. Using the Firmware Restoration CD, restore your Firmware back to factory condition: 6) Insure that the machine you are trying to restore is plugged into an AC outlet. 7) Power on the computer and hold down the power button until the LED blinks rapidly followed immediately by a successive series of blinks (3 quick blinks, 3 slow blinks, 3 quick blinks), then release the Power button. 8) Insert the Firmware Restoration CD into the optical drive. After 30-60 seconds, the startup beep sound is played and a progress bar appears beneath the Apple logo on a gray screen. The progress bar indicates the firmware is being updated. DO NOT unplug, shut down, or restart the computer during the update or you will need to restart the restoration process beginning with step 6. 9) The computer will restart automatically after the firmware is updated. It's important that you follow the instruction strictly! So important points are: - Burn the CD with Disk Utility and NOTHING ELSE! - Plug your MBP to AC power - Release the power button ONLY when the successive series of blinks appear. Power on the computer and hold down the power button until the LED blinks rapidly followed immediately by a successive series of blinks (3 quick blinks, 3 slow blinks, 3 quick blinks), then release the Power button. - Once you got the sequence of blinks and that you've inserted the restore CD, wait some minutes that something happens, there will be no reaction before 30 to 60 seconds according to Apple doc, and only after this amount of time you should hear a startup sound (so it's normal you don't get startup sound before, there will be no startup sound before this very point) and then the firmware update progress bar appears. Of course DO NOT TOUCH ANYTHING during this process. The computer will restart automatically after the update anyway. The fact that your MacBook Pro have the successive series of blinks, as you apparently indeed have, indicates that your computer works enough to process a firmware restore from the restore CD, but of course this require that you burnt the CD correctly (using Disk Utility and nothing else) and followed the instructions correctly. Btw, if you prefer to let an Apple Store or Apple Authorized Service Provider do the restore of the firmware, just find some time one day to go to one of them, they can do it for you (according to the documentation on the Restore CD: "you can take your computer to an Apple Store or Apple Authorized Service Provider to restore your firmware.").
  13. The purpose of a graphic card firmware is to initialize it. That's why the ATI firmware on the iMac must be made for EFI as a BIOS compatible firmware wouldn't run otherwise (as Apple didn't even provided CSM). So the firmware have no importance at all for the OS, the driver don't take car of it at all. It's useful to initialize the card before starting the OS, so that the stuff displayed before the OS loads its own driver can be displayed. In a nutshell: The OS driver is "firmware type independant". The graphic card could have had an Open Firmware verison of its firmware, the OS driver would have loaded as well without any problem.
  14. Bochs 2.2.5

    You can get a Universal Binary build here: http://ifrodo.free.fr/Bochs-2.2.5.dmg But don't except impessive performance, it's as fast as Bochs on any other x86 OS, i.e: it's damn slow!