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 red_team316

  • Rank
    InsanelyMac Protégé
  1. New OS X compatible motherboard -> QUO

    @BugsB, I reconfigured my drives in my case and labeled them all so that they would be easy to identify: P0: Linux/Grub MBR P1: OSX 10.8.5 GPT P2: Win7 GPT If you are installing all of those on a single drive, that might work okay, but if you have separate drives, and Windows 8 is anything like Windows 7, you will have a problem. I left my Linux and OSX drives connected while I tried to install Windows 7 this time around and here is what happens: Windows 7 will create the Recovery and Primary NTFS Partition on the correct drive(P2 in my case), but it will not create the EFI Partition. It just dumps all the EFI stuff onto the OSX drive, arg. This leaves you with the Windows Boot Manager on the OSX drive(which still has 3 Partitions), but the Windows drive(only 2 Partitions) and Windows will not even finish the installation after the first reboot. You will be greeted by a 0xC0000225 error, presumably because it stuck the Bootloader on the wrong drive. I would suggest anyone with a setup like this to install Windows first and have it lower in the P-list than any other GPT drive present. It's possible that OSX might try to do the same thing though if a Windows GPT drive is present, but I haven't tried that. So Multibooters beware
  2. New OS X compatible motherboard -> QUO

    KiNG and BugsB, I just reinstalled Mountain Lion to another drive(I'm running out of drives lol). Only took about an hour so installing the rest of the software will probably take another(After reinstalling an OS plenty of times, you get quicker. Having a ML disc now helped considerably). Mounting partitions isn't really experimenting, but it's possible that may have had something to do with it. If it happens again, I should have a better idea of how it happens. I'm glad the swapping thing was a joke, because from what I could tell, it was the culprit I do install windows fresh every time, I know well enough not to mix it with other OS on the same drive or try to have it upgrade itself. And I never let windows access my other OS files BugsB I'll play around with the EFI shell some more now. I would like to be able to eventually figure out how to chainload it or boot directly to the .efi straight from GRUB or GRUB2. Thanks again for the info.
  3. New OS X compatible motherboard -> QUO

    KiNG, It's not just my Windows drive thats hosed. OSX is now hosed too... I have never had a single problem swapping drives in my old desktop. There has to be a better answer than just startover. OSX took an entire day to install, Windows took a few hours, Linux less than an hour (Ordered in decending headache). It sounds like hadcia may be running into the same issue.
  4. New OS X compatible motherboard -> QUO

    Thanks KiNG, but it only gives me fs0: thru fs5: for my Linux MBR drive only, nothing for the other two drives. In fact, now that I've been swapping the drives around again, the OSX drive is now unbootable... I'm back on my Linux drive posting this, and I can still mount the Win7 and OSX partitions just fine under Linux after running 'sudo modprobe hfsplus' and then 'sudo mount /dev/sdb2 /my/mount/point'. Here is a screenshot of the win7 drive in the efi shell: http://img.photobucket.com/albums/v77/red_team316/linux/efi-shell-win-drive.jpg Here is a screenshot of the linux drive in the efi shell: http://img.photobucket.com/albums/v77/red_team316/linux/efi-shell-linux-drive.jpg Is there something else I need to do? My OS'es are vanishing faster than I can install them lol.
  5. New OS X compatible motherboard -> QUO

    I doubt the installer issue has nothing to do with the MBR drive, I can physically unplug the Linux MBR drive and all other drives and OSX still boots fine and the Nvidia installer fails in the same way. I will try the Pacifist again a bit later. I do have a bigger problem though, related to the EFI or something: I installed Windows 7 a day or two ago on a 2TB drive. I unplugged all other drives before installing Win7. It seems that Windows 7 must have known to do an EFI install because the drive is GPT. After getting it all setup, I replugged in the Linux and OSX drives. I can boot to my Linux and OSX drives just fine but there was an entry for "Windows Boot Manager" in my boot list, but now it has disappeared, and booting to Windows 7 is a no-go. Here is fdisk output of all of the drives hooked up currently: $ sudo fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0002ad88 Device Boot Start End Blocks Id System /dev/sda1 * 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdb: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 * 1 488397167 244198583+ ee GPT Partition 1 does not start on physical sector boundary. Disk /dev/sdc: 400.1 GB, 400088457216 bytes 255 heads, 63 sectors/track, 48641 cylinders, total 781422768 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0008c78c Device Boot Start End Blocks Id System /dev/sdc1 * 63 1992059 995998+ 82 Linux swap / Solaris /dev/sdc2 1992060 3984119 996030 83 Linux /dev/sdc3 293138055 781417664 244139805 83 Linux /dev/sdc4 3984181 293136383 144576101+ 5 Extended /dev/sdc5 3984183 82124279 39070048+ 83 Linux /dev/sdc6 82124343 130945814 24410736 83 Linux /dev/sdc7 248133632 293136383 22501376 83 Linux /dev/sdc8 130947072 248123391 58588160 83 Linux Partition table entries are not in disk order fdisk doesn't report the GPT correctly, but essentially there is this on the Windows 7 drive: Partition | File System | Label | What it really is | Flags /dev/sda1 | fat32 | no-label | efiPartition | boot /dev/sda2 | unknown | no-label | windowsRestorePartition | msftres /dev/sda3 | ntfs | no-label | windowsStandardPartition | <no flags> and here is the OSX drive: Partition | File System | Label | What it really is | Flags /dev/sdb1 | fat32 | EFI | efiPartition | boot /dev/sdb2 | hfs+ | OSX-MtLion | osxStandardPartition | <no flags> /dev/sdb3 | hfs+ | Recovery HD | osxRecoveryCrap | <no flags> How do I boot from the EFI Shell into an .efi file so that the OS will load? Windows lost all ability to boot after plugging the other drives in... I've googled all kinds of stuff to no avail...
  6. New OS X compatible motherboard -> QUO

    xpamamadeus, bs0d, THe KiNG, I am a programmer and I am interested in the source. I mostly do application development, but also have experience in embedded programming. It seems that since hackintosh development is mostly the focus at this point, I would say that the reason it isn't released yet is that it needs more polish and so that when it is released, that the chance of someone bricking their system is minimized. Also, as BugsB mentioned, addressing the kickstarter is an important factor. One benefit of having it open source though is that other tools could be made to improve the development process. Anyone who is not a programmer could certainly improve the documentation, tutorials or help by collaborating in some other way. 1) lockup - occasionally the computer locks up at boot when holding down a key rather than entering BIOS, boot menu, flash menu, etc... 2) Boot screen - since this apparently runs on more than one mobo, maybe that is the reason for not displaying the proper keys to press at boot. Regardless, this should and could be easily improved. I've done custom windows(XP, 2000, 98) and linux boot screens(usplash, plymouth) in the past and I'm sure this isn't much more complicated than that. I'm sure it's just an embedded image. This would be relatively easy for others to handle while the core devs focus on more complex tasks. 3)Why do I have a list of 16 boot options even if I disable all of them? Refreshing the screen when the boot menu is changed to reflect lesser or more entries would be a nice addition. It's possible the menu entry generation is based on an index the first time the computer boots rather than incrementing the number of boot options to the index. Just a guess, but without source, can't be sure. This probably isn't a complex task either. I'm quite pleased with how the Oz BIOS works with the Quo mobo. There are some rough edges I've probably encountered that aren't listed that I forget, but otherwise it's great. This mobo/BIOS combo lives up to "Any OS" when it comes to the 3 major OS. I'm going to try BSD at some point in the future, but I would guess that it probably works fine too as from my understanding, it's closer to Linux than OSX.
  7. New OS X compatible motherboard -> QUO

    1) It's MBR and contains a bunch of Linux paritions, only the GPT are the OSX installs which are on separate drives. 2) No, not that I know of. I did look into chainloading OSX from GRUB and GRUB2 and tried, but it seems that Chameleon is needed on the OSX drive for this to work. If Chameleon is purely a bootloader like GRUB and will not mess up OSX updates or anything, I may play around with it in the future. 3) Thanks, I will definitely look into this more. I was setting up other partitions properly after getting the card working yesterday. I think getting Pacifist working with the driver is basically the last major configuration item I am looking at OS-wise, then I'll start looking at overclocking, more into OSX inner workings and other stuff like actually making proper .app/.pkg/.dmg
  8. New OS X compatible motherboard -> QUO

    Thank you both so much. I've been battling the beeps all night long. I certainly did not understand what he was getting at. like yoda, joe speaks
  9. New OS X compatible motherboard -> QUO

    sTaN, According to the changelog: 816M Fix loading SSDT table overrides. 801M 10.8.5 audio distortion fixed. The 801M BIOS also does not POST with my EVGA GTX680 Mac Edition card. How many other BIOS are there? I have a 739M also that I will try to narrow down where the problem started, or if all of the OZ BIOS are like this. The stock F2N BIOS wont boot into Mountain Lion at all, yet it POST's properly with the card. What I need is a mix of the two...
  10. New OS X compatible motherboard -> QUO

    joe75, I'm still trying to figure out why I even care about this EFI BS The OZ BIOS clutter up the boot list with all kinds of entries for my single linux drive(which contains about 8 different partitions of various *nixes) so it looks like it adds an EFI entry for each separate partition. The drive came out of my old desktop which had no EFI stuff whatsoever. I use a custom GRUB bootloader to chainload any partition in my box. I'm not sure if I can chainload OSX yet as I haven't tried but I will eventually. I wonder how many people here have 16 different entries to boot from in their BIOS because I did when all my drives were hooked up lol. minimig, I unplugged my OSX drive, flashed back to the stock F2N BIOS and left everything on defaults and it POST's fine. I'm on my linux drive right now and just built the Nvidia driver for it and installed it. It's clear now that the 816M BIOS definitely was the problem, I'll try 801M and see if it fairs better. http://img.photobucket.com/albums/v77/red_team316/linux/nvidia-linux.png I'm making progress, but it all seems backwards BTW, Is the source code for the BIOS available? I thought I read that somewhere it was going to be open source.
  11. New OS X compatible motherboard -> QUO

    It's this card, which is specifically marketed as an upgrade for Mac Pro: http://www.evga.com/products/pdf/02G-P4-3682.pdf Regardless of that fact, whether or not I am using it in a Mac, it should POST, even if there isn't a single operating system installed... Is it possible that something in the Ozmosis BIOS is preventing it from loading properly?
  12. New OS X compatible motherboard -> QUO

    Just as a test, after resetting the Init Display to iGPU and Integrated Graphics to Enabled in the BIOS, I booted into OSX with the HD4000. I popped the DVI cord off of the HD4000 port and onto my GTX680 Mac Edition port. Video immediately popped up, so the basic Nvidia driver on the system at least works. That still doesn't solve the problem of booting with it connected to the GTX680 card, as I rebooted and was greeted by the 4 beeps of death again. Getting the computer to boot from the card at all is my main priority as Linux is my primary OS and this is to be my multi-boot development box. @BugsB, I downloaded Pacifist and it was able to extract the contents of the driver package. It's got a .plugin file, two .bundle files and several kext files in it, and two .prefPane files. I found some info on installing kexts here: http://www.insanelymac.com/forum/topic/277344-what-is-a-kext-and-how-do-you-install-and-patch-it/ I found similar files under /System/Library/Extensions although one of the files is named exactly the same, so it would need overwritten I'm guessing. Then updating the cache. Is that correct? I've never done this before so I'm not sure if I'm missing something else thats necessary. I was kind of thinking that updating /System/Library/CoreServices/SystemVersion.plist might be a more elegant solution to trick the Nvidia Installer into actually running...
  13. New OS X compatible motherboard -> QUO

    I finally got 10.8.5 up and running and I'm using the Ozmosis 816M BIOS. The HD4000 graphics are working good (in Snow Leopard 10.6.8 it was semi-working). I'm trying to get my EVGA Geforce 680 Mac Edition Card working now. The driver is supposed to require 10.8.3 or later but yet the installer complains that it still wont work on Mountain Lion and that I need to upgrade my OS. Furthermore, I'm having problems getting the board to boot at all when the monitor is hooked up to the discreet card. It gives me 4 beeps(one long and 3 short beeps) and refuses to POST. Is there some trick to getting discreet graphics to work? If I set the Init Display to iGPU and the Integrated Graphics to Enabled, I can boot with the monitor plugged into the HD4000 and it does recognize the Nvidia card but thats about as far as I can get.....it seems a bit odd that the Mac Edition card is not easier to setup, the only reason I got it was specifically because it is supposed to be an officially supported card and I thought it would be less headache
  14. New OS X compatible motherboard -> QUO

    Well I have a 3770K and I loaded the H3A BIOS and was able to install Snow Leopard with no problems. Then I grabbed Mountain Lion from the store, and tried to make a bootable USB with it using Lion DiskMaker. It appears that the USB was done but the Lion DiskMaker app mentioned something about audio not working, yet when I replugged the USB in it seemed to be fine and I can actually boot off of it. I copied the InstallESD.dmg to the Desktop so I have an extra copy, and then proceeded to "upgrade" using the downloaded installer from the store. It rebooted twice, which seemed normal, and then started the install. After awhile the Apple logo turned to a blocked symbol(a circle with a slash through it) and wouldn't proceed any farther. And now booting into OSX doesn't work at all... So I figured I would try out the USB I made, and it will not work either but actually gives me a message to try reinstalling. Do I have to fix the audio with the legacy files before trying to create a USB or is there some other catch? My EVGA 680 Mac card(which is not even installed into the machine yet) says it requires Mountain Lion. The H3A BIOS is layed out differently(at least the drive booting portion) than the stock F2N BIOS and genuinely feels more unstable. The boot logo disappears long before my 10 second timeout to a black screen. Also, I'm not sure why, but the H3A BIOS doesn't even show the keys to press when booting. At least I remember DEL is the BIOS access, gotta love randomly smashing keys at startup if you don't know them