Jump to content

skrub

Members
  • Content Count

    17
  • Joined

  • Last visited

About skrub

  • Rank
    InsanelyMac Protégé

Contact Methods

  • MSN
    Wouldn't your MSN account be the same for Skype?
  • Website URL
    http://These things ain't cheap man
  • ICQ
    What?
  • Yahoo
    Google FTW
  • Jabber
    I don't know what this is.
  • Skype
    Have one but you don't need it

Profile Information

  • Gender
    Male
  • Location
    In The Matrix
  • Interests
    Doesn't matter, don't have a life anyways.
  1. skrub

    Need help booting into OS X

    So I reinstalled the bootloader using your method and booted from a Windows 7 install USB, went to the command prompt and set the boot file to CLOVERX64.efi. Clover appears now but I have another problem. I'll try to address it myself though. If you're wondering what appears when I boot from verbose it's just +++++++++++++++ . Thanks for the help in getting it to work.
  2. skrub

    Need help booting into OS X

    I'm not using Chameleon, I'm using the boot0hfs file in the binary in the trunk to load Clover. I can't load OS X in verbose because the bootloader is broken, as in the image. I can get into OS X using a USB drive as a bootloader and that's the only way I can get in, and I want to load Clover on my hard drive so I don't need to boot off the USB every time.
  3. I have Windows 7 and OS X El Capitan on a single GPT formatted Hard Drive. Both OSes work fine, and I already have everything working on OS X. The problem is booting into OS X. I need to use an MBR formatted USB flash drive to start Clover to boot into it, which means I have to always have it to load OS X. I installed Clover and told it it to put it's files in the ESP. I extracted the boot0hfs file from Chameleon's binaries and put it at the root of my EFI partition. My computer uses a legacy BIOS interface but I think it has some form of UEFI because Clover does come up when I boot from my hard drive. I can't use it though because it appears in a weird resolution, only shows my bootable partitions and when I load OS X, it freezes at the Apple logo and won't go any further. I've uploaded an image of the result below showing what Clover looks like when I load it. EDIT: Images always appear upside down when uploaded from my phone. EDIT 2: Sorry, wrong subforum. I don't know how to move it.
  4. Alright, it worked and I updated to OS X 10.11! Thanks!
  5. Not sure if it's corrupted, I've done this at least 3 times, all with the same error. But I'll give it a go. I forgot to mention in my first post that I was ready to download the update, and didn't know how to avoid this error again. Where exactly would I find system.kext and sandbox.kext in the update, since it's from the App Store?
  6. So the other day I went and updated my Yosemite installation to 10.10.5, first through the App Store, then directly through Apple's website. After the update completed, my computer restarted and went to Clover. I booted using verbose, as I always do after an update like that. Halfway through booting I got a bunch of "Sandbox: deny" errors flood my screen, all the way until the end of the boot, as seen in the image below. The GUI failed to load, and from the looks of it, a lot of other things too. I am now typing this from a new Yosemite installation and wish to try updating to 10.10.5 again, without damaging my installation. I've searched this error on Google, but none of the methods to fix it work for me. Strangely enough, I can boot into 10.10.5 using Chameleon, but I want to get it to work on Clover because Chameleon messes with my install. On Clover I'm only using the boot-flags rootless=0 , kext-dev-mode=1 , and slide=0. This is a new install and it only has Clover as the bootloader. Please help.
  7. Yup, mendietinha was right, it was a bad distro indeed. Just used a flash drive to make a vanilla Yosemite install from my partially working one. All is good now, I have working QE/CI with 1366x768 resolution.
  8. So should I use an alternative distro, or try a vanilla install? I'll try and inject the EDID first though.
  9. Never once have I booted up my Yosemite installation with working QE/CI. I can't get my native 1366x768 resolution working, and I'm stuck at 1024x768. QE/CI works in Mountain Lion but I'm trying to get it working on Yosemite because a lot of programs I use need 10.9 or higher (Please don't recommend for me to use 10.9 or 10.8, I'm trying to get this installation to be compatible with my iPhone and the latest Apple programs)
  10. Using GraphicsEnabler=No does the same thing IGPEnabler=Yes does, my GPU is identified as "Display" and I have 3mb VRAM. Deleting the GraphicsEnabler=Yes boot-flag and using your DSDT still gives me the SNB Framebuffer did not show up, unload. I've tried several boot-flags, including -f and nothing works. It seems however that Yosemite will ONLY identify my HD3000 using GraphicsEnabler=Yes, anything else and it shows up as "Display" in System Information.
  11. Thanks, my installation is now reporting battery information. It turns out that System Information will only identify my HD3000 when I use GraphicsEnabler=Yes instead of IGPEnabler, (I'm using Chameleon, Clover stops booting halfway and there's no kernel panic or information that seems to help) So any IGP related DSDT edits may not work. They will probably have to use the GFX0 device name.
  12. Allan, Nothing seems to be working, with the DSDT you uploaded I still get the same error. I'm mostly only concerned about the "SNB Framebuffer did not show up, unload" It appears twice, the first time it appears nothing happens for about 30 seconds and the second time, the mouse cursor appears right after and the login screen appears.
  13. Allan, I've taken your example and filled it with my information. My motherboard doesn't have an identifier though. CPU: Intel Core i7 2640M (Sandy Bridge) | GPU: Integrated Intel HD Graphics 3000 | RAM: 8GB | Mobo: Not sure, I'm using a laptop. | Chipset: Mobile Intel® HM65 Express Chipset (Intel® BD82HM65 PCH) | Audio: VoodooHDA, no sound though. Hardware is ALC272 I'll try the DSDT you uploaded later, my battery's dead.
  14. So the error no longer appears at boot, but I still have 1024x768 resolution and no QE/CI. My graphics are now identified as "Display" and still with 3mb RAM as shown in the screenshots.
  15. Upon accessing that site I get a "400: Invalid request"
×