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 CurlyBird

  • Rank
    InsanelyMac Protégé
  1. I now have Yosemite Public Beta 2 running in Windows 8.1 VirtualBox. Everything seem to work, but need more testing on sound. I followed XDA thread to find that you need to configure a couple of special VM variables to fool bootloader to thinks its a real mac. Find the YB2VB.dmg and mount in new VM. Boot!
  2. Clover General discussion

    That is an awesome list, have you had a chance to update it to 10.9.4 and Yosemite? We're having problems with Yosemite...
  3. Virtualbox SL/L/ML and Core I7 Hasweel

    Here's a list of the latest Mac processors, now we just need to figure out what their cpuidset are. 306A9 2.5 GHz (i5-3210M) dual-core Intel Core i5 Ivy Bridge processor with 3 MB shared L3 cache 2.9 GHz (i7-3520M) dual-core Intel Core i7 Ivy Bridge processor with 4 MB shared L3 cache 2.6 GHz (i5-3230M) dual-core Intel Core i5 Ivy Bridge processor with 3 MB shared L3 cache 3.0 GHz (i7-3540M) dual-core Intel Core i7 Ivy Bridge with 4 MB shared L3 cache 2.4 GHz (i5-4258U) dual-core Intel Core i5 Haswell processor with 3 MB shared L3 cache 2.6 GHz (i5-4288U) dual-core Intel Core i5 Haswell with 3 MB shared L3 cache 2.8 GHz (i7-4558U) dual-core Intel Core i7 Haswell with 4 MB shared L3 cache 2.6 GHz (i5-4278U) dual-core Intel Core i5 Haswell processor with 3 MB shared L3 cache 2.8 GHz (i5-4308U) dual-core Intel Core i5 Haswell with 3 MB shared L3 cache 3.0 GHz (i7-4578U) dual-core Intel Core i7 Haswell with 4 MB shared L3 cache 2.3 GHz (i7-3615QM) quad-core Intel Core i7 Ivy Bridge with 6 MB on-chip L3 cache 2.6 GHz (i7-3720QM) with 6 MB on-chip L3 cache 2.7 GHz (i7-3820QM) with 8 MB on-chip L3 cache 2.4 GHz (i7-3630QM) quad-core Intel Core i7 Ivy Bridge with 6 MB on-chip L3 cache Optional 2.7 GHz (i7-3740QM) with 6 MB on-chip L3 cache 2.8 GHz (i7-3840QM) with 8 MB on-chip L3 cache 2.0 GHz (i7-4750HQ) quad-core Intel Core i7 Crystal Well with 6 MB on-chip L3 and 128 MB L4 cache 2.3 GHz (i7-4850HQ) with 6 MB on-chip L3 cache 2.6 GHz (i7-4960HQ) with 6 MB on-chip L3 cache 2.2 GHz (i7-4770HQ) quad-core Intel Core i7 Crystal Well with 6 MB on-chip L3 and 128 MB L4 cache 2.5 GHz (i7-4870HQ) with 6 MB on-chip L3 cache 2.8 GHz (i7-4980HQ) with 6 MB on-chip L3 cache Basically we need everyone who has areal mac to tell us: 1. Their processor and 2. the output of: VBoxManage.exe list hostcpuids
  4. Hi, I'm successfully running (Niresh) Mavericks 10.9.4 in a VirtualBox VM on a Windows 8.1 host. Most things work there, so I decided to download and try to install the latest Yosemite Public Beta 2 (20 August,2014). Running the Yosemite Installer App, results in what seem successful update, but when the installer finishes and reboots, I get a crash. Shutting down the VM in the regular way and rebooting you'd think it would try to reboot in the same way, but no, instead it boot right back up into Mavericks. WTF!? I'm new to everything that is Apple so I'm really at loss here. So I tried a second method. I took the Yosemite PB2 App and made both an ISO and an DMG using detailed instructions from this site and others. I.e. Using sparse methods etc. Now I mounted either of these images as an external CD/DVD from virtual box and they appear and run in Mavericks. However, this time, when I try to run the installer I get this picture. Any ideas what's going on, and why I can run this from withing Mavericks as an installer App, but not as a ISO/DMG image? Is there a way to circumvent this?
  5. Mavericks Realtek ALC AppleHDA Audio

    Well given the name of this thread, I don't see how it can possibly be "OFF Topic". In addition, it would be more helpful if perhaps you could point to the place it would be "ON Topic"?
  6. Mavericks Realtek ALC AppleHDA Audio

    Hello, First off. I'm completely fresh to the Hackingtosh scene, albeit with a very long experience with pretty much any other form of computer, apart Apples. So that means, I'd probably need a little "hand holding" for any of your explanations. My problem is the following: I have installed an OSX Mavericks (10.9.4) "guest" in a VirtualBox VM on my Windows 8.1 (x64) "host". I used the Niresh Distro in order to get started and avoid any potential nightmares for trying to boot. Everything worked out-of-the-box except Audio. The hardware I'm using is: Hardware: ASUS N550JK Motherboard: Intel HM86 (Lynx Point) Processor: Intel Core i7-4710HQ (Haswell 2014) Audio Adapter: Intel Lynx Point PCH - High Definition Audio Controller [C2] Vendor:Device/8086:8C20 Audio Codec: Realtek High Definition Audio (Realtek ALC668) Vendor:Device/10EC:0668 As you can see it is using the ALC668 codec, which is not listed in OP. I have not been able to find any Apple Kext or whatever either, matching that codec. However, I did find the codec mentioned in ALSA sources, (as linked from Realtek site) in ..\alsa\alsa-kernel\pci\hda\patch_realtek.c: * ALC662 is almost identical with ALC880 but has cleaner and more flexible * configuration. Each pin widget can choose any input DACs and a mixer. * Each ADC is connected from a mixer of all inputs. This makes possible * 6-channel independent captures. ... { .id = 0x10ec0668, .name = "ALC668", .patch = patch_alc662 }, This seem to imply two things: 1. That it is pin compatible with ALC662 2. That it may be codec compatible with ALC880. Problem-1: I cannot find any of these codecs mentioned in Apple context. Does anyone know? If there is none, what can I do? Now on to the next problem. When using a virtual machine, things get worse and more complicated as the Audio Codec presented to the VM is different from what is physically present in HW. In the latest VirtualBox, when set to use the "Intel HD Audio", the OSX finds a completely different Audio device/codec, namely: On OSX 10.9.4 (Intel HD Audio): sudo lspci -m -v Device: 00.05.0 Device: 82801FB (ICH6) High Definition Audio Controller SVendor: SigmaTel SDevice: Device 7680 sudo lspci -m -n -vvv Class: 0403 Vendor: 8086 Device: 2668 SVendor: 8384 SDevice: 7680 This we find from PCI ID DB, is another codec called: "SigmaTel STAC9221 HD Audio Codec" [8384:7680]. Problem-2: I cannot find anything Apple related to this codec either... Please help!? Extra Credit Question: (a.) How does VirtualBox (or any other vitualization platform for that matter) forward and select what codec is used in the VM? (I thought PCI was just passed through?) (b.) If we find/make and use the "real" driver (in this case ALC668) in the VM guest, will the VM host software be smart enough to forward the "real" HW "signals"? I think I'm not the only one who have or will have problems with VirtualBox Audio support when using "unsupported" OSX in a VB VM. So resolving my issue, would potentially resolve the same issue for hundreds of other users trying to run OSX in VM on a windows host with new HW.
  7. On my VB VM machine the Audio is recognized as: Vendor:Device/8384:7680 SigmaTel STAC9221 HD Audio Codec But I haven't seen any Kext for this... So if someone else using VB is getting audio to work, I'd like to know how. Also, it's not clear to me how VB is presenting the Audio card to the VM. My "real" audio card is ALC668 (662 compatible?). But unless VB is also able to patch the signals through without changing stuff, I guess there's little hope I can use that. Or what?
  8. I have KW 3.7.10 that came with Niresh distro. However, trying to update with "Check for updates.." always fails with "Update Error!". Any ideas? PS. I'm on 10.9.4.
  9. Would you know if building VB would also build the VB guest add-ons? If, so then perhaps it would be worthwhile building from scratch, but then I would naturally wonder, why it hasn't already been done?
  10. How did you setup your Audio in VB and in OSX to work properly?
  11. Hello, I installed Niresh's OSX Mavericks on an ASUS Laptop in the latest VirtualBox, following the detailed instructions at MacBreaker. --------------------------------------------------------------------- Hardware: ASUS N550JK Processor: Intel Core i7-4710HQ Video-1: Intel HD Graphics 4600 Video-2: NVIDIA GeForce GTX 850M Audio: Realtek High Definition Audio Memory: 16 GB DDR3 SDRAM Host OS: Windows 8.1 (64bit) Guest OS: OS X Mavericks 10.9.0 ? (Niresh Distro) VirtualBox: 4.3.14r95030 --------------------------------------------------------------------- Everything* worked pretty much flawless, by carefully setting up the VM. The only thing that doesn't work is Audio. I get weird clicking and other noises when changing and typing in terminal. I have tried changing stuff in the Audio settings, but the problem prevails and the noises change only slightly. Also at one point when trying mess with VoodooHDA settings, there must have been some kind of kernel crash as the machine suddenly refused to respond and CPU at 100%. So my first guess is that I don't have the right kernel drivers for the Audio provided by the VirtualBox machine. The second guess is that I'm just clueless as to what the correct Audio settings should be for both OSX and VB to communicate. --------------------------------------------------------------------- The VirtualBox Audio settings are: --------------------------------------------------------------------- Host Driver: Null Audio Driver * Windows DirectSound Controller: * Intel HD Audio ICH AC97 SoundBlaster16 --------------------------------------------------------------------- And on the OSX "Sound" settings side they are: --------------------------------------------------------------------- Sound Effects: Speaker (Black Unknown) * Headphones (Green Front) SPDIF-out (Black Rear) Output: Speaker (Black Unknown) Apple speaker port * Headphones (Green Front) Headphone port SPDIF-out (Black Rear) Optical digital-out port Input: Microphone (Pink Front) Microphone port SPDIF-in (Black Rear) Optical digital-in port CD (ATAPI) --------------------------------------------------------------------- And on the OSX "VoodooHDA" settings side they are: --------------------------------------------------------------------- * 1: Speaker (Green Rear) 2: Headphones (Green Front) 3: SPDIF-out (Black Rear) 4: Line-out (blue Rear) 5: Microphone (Pink Front) 6: SPDIF-in (Black Rear) 7: CD (ATAPI) * /AppleACPIPlatformExpert/PCI0@1e0000/AppleACPIPCI/HDEF@5 [ ] Use SSE2 [ ] Enhance stereo --------------------------------------------------------------------- I have no idea what would be the proper settings for this controller. Any suggestions? Please note that I'm new to OSX and have little experience and understanding of how to find/use/install Kext files and editing plists. So any help would be much appreciated. * Well, "Everything" apart file/folder and clipboard sharing, since there still are no official VB Host Additions for OSX.
  12. 1. The file/folder sharing. 2. The shared clip board. Where is that Oracle repo located? Sorry dumb question: https://www.virtualbox.org/browser/vbox/trunk I would guess that both are using some kind of network socket on both (VB and VMw), and thus one may hope to hack a wrapper to/from that socket to translate to the other. But I really have no idea how they do it. Do you know anything about that? ----------------- EDIT ----------------- Ok, I have no idea what I'm talking about, but certainly it seem that they are maintaining this quite well. For example: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/common/VBoxGuest/VBoxGuest-darwin.cpp was updated only 3 months ago. So what would it take to make out own host additions? It seem that we need to make a Kext and a few other files...
  13. While going through these forums looking for a filesharing solution when running OSX Mavericks in VirtualBox, I had this brilliant (?) idea, that perhaps we can use the VMWare Tools for OS X instead? Have anyone considered this? What are the issues involved? I'd like to hear from some more talented people as my OSX developer experience is basically NULL. Basically we'd need to know how the VB and WMware Toolboxes communicate with the host. and how to write a simple wrapper for making this successful.
  14. Dude, I just did this, following the exact instructions from the link, so either you're wrong, or I don't understand what you're saying? Yes, it's a distro, so NO, you probably can't from original Apple DVD, without first mounting a bootable kernel on a separate disk. But why would you? Go through all the hassle of tuning your OSX to VB VM use, by messing around with all sorts of Kexts?
  15. This works! http://www.macbreaker.com/2014/05/os-x-mavericks-in-virtualbox-with-niresh.html