Jump to content

José A.

  • Content Count

  • Joined

  • Last visited

Everything posted by José A.

  1. Hi. With God's help, using the Pandora's Box tool, I was able to install a decently working El Capitan system on my existing hardware. The system works just fine. The only thing not working is the audio and I'm wondering if someone out there can help. My hardware uses the Realtek ALC269Q High Definition Audio Codec. Would someone have some idea how I can make the audio work in this El Capitan system? I'm using the Enoch bootloader.
  2. So I used a kext utility called "Kext Utility" to install both kexts to /System/Library/Extensions/ and the audio is working just fine on this system. Thanks for the help.
  3. Thanks for replying. I tried installing both kexts using Pandora's Box. First I installed the AppleHDADisabler.kext in /System/Library/Extensions and then in /Extra/Extensions. I also installed the VoodooHDA.kext in /System/Library/Extensions and then in /Library/Extensions. When I installed the kexts, I got errors such as the one in the included screenshot. I don't know if these errors are the cause, but after installing the kexts and rebooting, audio still does not work. This is not very important for what I do on this system; I just wanted everything to work so if I can't get it to work it's okay. My boot options (in the /Extra/org.chameleon.Boot.plist file) are: -v -f darkwake=0 nv_disable=1 dart=0 kext-dev-mode=1 Maybe the system is not recognizing the kexts?
  4. Hi. I just used the Pandora's Box tool to successfully upgrade my previous Yosemite system to El Capitan. The system runs fine, but for some reason, it doesn't recognize my iPhone 5s when I plug it into one of the USB ports. The system recognizes USB disks, and my Deskjet 2600 printer connected via one of the USB ports. But for some reason it does not recognize the iPhone 5s. Would someone have some idea as to why the system does not recognize the phone? Any help appreciated.
  5. So I discovered that the problem was the USB cable of the iPhone. My previous cable stopped working so I began to use one I had in my car to be able to charge the phone in the car. It seems that that cable is old and the USB connection is not secure so the computer could not recognize it. I used a new cable and the phone is recognized. Thanks for helping.
  6. What happened is that I upgraded to a new desktop (the new system is reflected in my signature). My previous system had the following specs: GA-M68M-S2P (rev. 1.0) Motherboard | AMD Athlon II X2 250 CPU | GeForce 7025 / nForce 630a/integrated/SSE2. When I upgraded to the new desktop, Yosemite failed to recognize the iPhone 5s also so I decided to upgrade to El Capitan to see if that made a difference. I've never used a DSDT because I didn't want to have to figure out how to do it, but if it's necessary I would use one. Once I upgraded to El Capitan, I deleted all the kexts that I had installed for the previous system. Pandora's Box installed a default FakeSMC.kext in /Extra/Extensions and I copied a NullCPUPowerManagement.kext in /Extra/Extensions also. I used Pandora's Box to create a new "org.chameleon.Boot" file; it is shown below (it also created a default kernel.plist file, also shown below). But I've done nothing more beyond that. Will I have to create a DSDT? ----------org.chameleon.Boot---------- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>BlackMode</key> <string>Yes</string> <key>CsrActiveConfig</key> <string>103</string> <key>EthernetBuiltIn</key> <string>Yes</string> <key>Graphics Mode</key> <string>1920x1080x32</string> <key>GraphicsEnabler</key> <string>Yes</string> <key>Kernel Flags</key> <string>-v -f darkwake=0 nv_disable=1 dart=0</string> <key>SMBIOS</key> <string>/Extra/smbios.plist</string> <key>SkipIntelGfx</key> <string>Yes</string> <key>Theme</key> <string>Pandora</string> <key>USBBusFix</key> <string>Yes</string> </dict> </plist> -------------------------------------- ------------kernel.plist------------- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>KernelBooter_kexts</key> <string>Yes</string> <key>KernelLapicError</key> <string>Yes</string> <key>KernelLapicVersion</key> <string>Yes</string> <key>KernelPm</key> <string>Yes</string> <key>KernelcpuFamily</key> <string>Yes</string> </dict> </plist> --------------------------------------
  7. Hi. I recently successfully upgraded from a Mavericks system I had been using spuriously in a virtual machine to Yosemite. I somehow managed to run the system not just in the virtual machine (using VirtualBox) but also on the physical system itself. This was possible because I used an actual partition in which to install the system and configured VirtualBox to use the partition as a virtual disk. Now, both in and out of the virtual machine the system runs fine (right now I'm entering this message running Yosemite on the physical machine). I have on small problem I'm hoping someone can help me with. I've attached screen shots of the information about the computer both in the physical machine and in the virtual machine. The problem I'm experiencing is that in the virtual machine, the information about the machine (i.e., the CPU, memory, etc.) is slightly different than in the actual physical machine (most significantly to me is the CPU speed). This makes the AppStore deny attempts to upgrade software in the virtual machine because it reports that it does not recognize the device. Can someone give me information as to how I can have the virtual machine appear exactly as the physical machine appears? Thanks.
  8. @Gismo: Unfortunately, the kexts (in /System/Library/Extensions) did not make a difference.
  9. I'm experiencing a curious problem with networking in Mavericks (10.9.3) and the recently released rc7 kernel (I think the problem is in the previous kernels also). It seems that the network controller is recognized but the running system does not have internet access. Someone else posted the same problem starting at the following post: http://www.insanelymac.com/forum/topic/293219-nforce-os-x-mavericks-109-app-store-download-install-guide-on-a-series-6-or-7-nforce-chipset-intel-cpu-mobo/?p=2029507 and I replied about it also after a few posts in the following post: http://www.insanelymac.com/forum/topic/293219-nforce-os-x-mavericks-109-app-store-download-install-guide-on-a-series-6-or-7-nforce-chipset-intel-cpu-mobo/?p=2030844 I'm not sure it's a kernel issue, but in case it is, I'm reporting the problem here.
  10. I'm experiencing something similar with my system. The system boots fine and everything. After following the instructions in the last few posts to make sure that the nForceLan.kext is loaded at the system boot, the kext loads fine as shown by the below lines from the dmesg: nForceLAN: found nVidia MCP61 Ethernet Controller device 10de:03ef with flags 0x0101774a nForceLAN: Version 0.64.5 starting However, when the system comes up, I have no internet access. I've attached the full dmesg with this post in case there's anything interesting in it. I can also run the system in a virtual machine I've set up in VirtualBox in Linux with access to the raw partition which provides a different Ethernet controller (in Linux, the lspci command in the virtual machine (also attached) shows it to be an Intel 82543GC Gigabit Ethernet Controller (Copper) (rev 02)). After startup in the virtual machine, there is no internet access. (It looks like it should work because in the /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns directory there is a kext called "AppleIntel8254XEthernet.kext" which looks like a plugin that should support the controller. I also have a Mountain Lion installation that I can run in the same virtual machine which recognizes the controller without problems which leads me to believe that there is something wrong in the Mavericks system. I'm using the mach_10.9_2_rc7_fixed kernel from a recent post in the AMD kernel development thread with a Mavericks 10.9.3 system. The system runs perfectly fine, except for the networking problem describred in the last few posts.) dmesg.06-15-14.txt Virtual Machine Device List (lspci).txt
  11. Hi. Some time ago I decided to explore Mac OS X so I decided to install Snow Leopard (10.6) on my computer. Since I wasn't serious about using it as an OS, I installed it as a virtual machine in VirtualBox under Linux (ubuntu to be precise) using the EmpireEFI4AMD BootCD and a retail DVD. It worked well so I kept the virtual machine. Later, I decided to upgrade to Mountain Lion (10.8) so I used ##### (with a custom AMD kernel) on a small VirtualBox partition I created for that and the upgrade was successful. Presently, the virtual machine works just fine (see below image), but I'd like to have the OS on my actual computer so that it runs as fast as it can. The way my system is configured is that I have a Linux partition, an HFS+ partition for OS X and another small HFS+ partition which contains the ##### installer. The grub bootloader boots Linux and the VirtualBox virtual machine is configured to directly access the two HFS+ partitions. I have a Chameleon Boot CD and when I boot the computer using it, the two HFS+ partitions are available for booting (see below image). I wanted to see if it was possible to at least get the ##### installer up and running outside of the virtual machine (it runs fine inside it) so I tried booting the installer partition with the Chameleon Boot CD using the "-v npci=0x2000" flags (without the npci flag the boot process gets stuck at "[ PCI configuration begin ]"). The below picture shows as far as I got (It gets stuck at "Still waiting for root device"). At the present, my system has one SATA drive and the latest BIOS for this motherboard does not have an enable/disable AHCI option so I placed the kexts from the following thread in /System/Library/Extensions (I also tried having them in /Extra/Extensions) but I'm still not successful: http://www.insanelymac.com/forum/topic/290644-installing-os-x-on-non-ahci-drive-laptop/ I'm wondering if there's something that I can do to further the process. Also, might it also be possible to use the OS X partition installed under VirtualBox outside of the virtual machine? Any help would be appreciated. By the way, I'm willing to use any other install method (other than the ##### method) if it also works. Thanks so much.
  12. Hi. It took a while, but I was able to find a solution to this problem. What I did was to create a new install USB with the latest Mavericks installer app (10.9.3). I also placed a custom AMD kernel in place of the existing kernel on the install disk and upgraded the system in the virtual machine to Mavericks. Afterwards, in the virtual machine, I used Kext Wizard to install the "AppleNForceATA.imk64bit.kext" found in the support files [1] from the "nForce OS X Mavericks (OS X 10.9) APP STORE DOWNLOAD INSTALL GUIDE on a Series 6 or 7 nForce chipset / Intel CPU MOBO" topic [2] under the "OSx86 Project->OSx86 Installation->OSx86 10.9 (Mavericks)" category on the install disk and on the newly installed system in /System/Library/Extensions. With the kext, the installer sees my drive. The install disk also boots the system fine outside the virtual machine because of the kext. [1] http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=131030 [2] http://www.insanelymac.com/forum/topic/293219-nforce-os-x-mavericks-109-app-store-download-install-guide-on-a-series-6-or-7-nforce-chipset-intel-cpu-mobo/
  13. Sorry, I expected an automatic link and had not signed in to be able to get the download. Thanks. Edit: Actually, I think I was clicking on the many "Download" buttons which kept sending me to download the "Torch" browser. I finally got the zip file. Thanks.
  14. Hi. I posted the following question in the OSx86 10.8 (Mountain Lion) section of the forums asking about how I could go about migrating an existing OS X 10.8 virtualbox installation to the actual physical computer and was directed to this very intricate, complete and pretty clear tutorial: http://www.insanelymac.com/forum/topic/294335-migrating-present-os-x-108-system-from-virtualbox-to-actual-computer/?p=1973180 At the present, I'm only trying to see if I can manage to get the installation disk to boot successfully in the actual computer to make sure that running the full system is possible. I'm thinking of trying to install one of the injection kexts to see if that enables my drive to be seen by the OS but I can't seem to be able to download Mountain Lion support files from the sendspace link because the link seems to be broken. Can someone direct me as to how I can download the support files? Thanks.
  15. Thanks for the information. I'll try to follow and report back. Thanks.