Jump to content

Hervé

Administrators
  • Posts

    9900
  • Joined

  • Last visited

  • Days Won

    547

Everything posted by Hervé

  1. Can you please open up a Terminal window and type lspci -nn to list your detected hardware and post the results here? This will show us what you have but as JakeLo mentioned, probably an Intel card.
  2. If you intend to use the OSXL bootpack, then you should not choose "Generic" Extra at the end of your installation but "my own", pointing to the OSXL bootpack that you have used on your USB installer (using the same process, i.e. Install Extra->my own-> point to downloaded Zenbook boot pack) and which will be in /Extra of your USB installer. Right now, it appears that you boot your installer with the boot pack but complete your OS X installation with the Generic boot pack! That kind of defeats the purpose of a dedicated bootpack for your model... What you can do meantime is reboot your USB installer and once at installation screen, go to Tools menu, select myHack and opt for "Install Extra" and "my own". Choose your HDD OS X partition as destination and use the /Extra of your USB installer as your source location for the bootpack. This will basically install the Zenbook boot pack on your OS X installation, something you seem to have missed previously.
  3. Well, the problem seems to be that you don't have the correct SSDT for your particular CPU...
  4. You probably need a DSDT patch so that the card is recognised properly and with all its characteristics. I would suggest you use IORegistryExplorer to find out the various details for the card (PCI location, nVidia characteristics, etc.) then extract a clean DSDT table so that we try and patch it. If you manage to boot without any DSDT table, you can use Chameleon Wizard or DSDTEditor to extract it and then decompile it to obtain the dsl source code. Don't hesitate to save your IORegistryExplorer output to file and upload it here together with your DSDT table. I would also recommend that you check your default PCI root level using command ioreg -l | grep -15 "AppleACPIPCI\" | grep UID from a Terminal window. Add your lspci -nn output too.
  5. You need to remove that offending DisableTurboBoostBattery kext from wherever it is (/S/L/E or /E/E) then re-run myfix (quick).
  6. I've been playing with DSDT patching these last few days and decided to try and get rid of the NVenabler64 graphics enabler kext used for the nVidia 9800 GT; that meant a DSDT patch of course. I first extracted the DSDT through Chameleon Wizard since I was not using any patched one. Then, I checked PCI devices in IORegistryExplorer and found the nVidia card to be located at PCI5@4, under PCI3. I therefore patched the DSDT as follows: . under _WAK method, I added: Method (DTGP, 5, NotSerialized) { If (LEqual (Arg0, Buffer (0x10) { /* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44, /* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B })) { If (LEqual (Arg1, One)) { If (LEqual (Arg2, Zero)) { Store (Buffer (One) { 0x03 }, Arg4) Return (One) } If (LEqual (Arg2, One)) { Return (One) } } } Store (Buffer (One) { 0x00 }, Arg4) Return (Zero) } . within PCI5 device, under Method (_ADR, 0, NotSerialized) { [...] Store (0x00040000, Local0) [...] } section, using info from the IORegistry extract, I added: Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { Store (Package (0x1A) { "AAPL,slot-name", "PCIe x16", "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@1,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,device_type", Buffer (0x08) { "display" }, "@1,name", Buffer (0x0F) { "NVDA,Display-B" }, "NVCAP", Buffer (0x14) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00, /* 0008 */ 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x20 }, "device_type", Buffer (0x0C) { "NVDA,Parent" }, "model", Buffer (0x17) { "nVidia GeForce 9800 GT" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Note that most of this derives from RampageDev's excellent blog page on graphics cards DSDT injection. Thank you Andrew! After removing the enabler kext and re-running myFix (quick), I rebooted but system remained without QE/CI, as if graphics card DSDT injection was ineffective. On checking the IOreg a little deeper, I found the system to have a PCI root level I was not expecting... Mac-Pro:~ admin$ ioreg -l | grep -15 "AppleACPIPCI\ " | grep UID Result --> | | | "_UID" = "4" Rebooting with boot option PciRoot=4 subsequently resolved the graphics card DSDT injection issue and got me full QE/CI! The Chameleon boot plist was therefore amended to that effect. Whilst on the Precision 670, I also searched deeper into the Ethernet port issue (seen and recognized, but always down with "Cable disconnected"). I finally found an old universal 32bit (PPC & i386) AppleIntel8254XEthernet kext on the Net and it proved to fix the issue! Yeeha! That old kext is v1.1.2 and possibly from Tiger but that's not important. It made the LAN port work, that's important! I also patched the DSDT to be able to show the Ethernet port + Firewire in the System Profiler->PCI cards section by adding the following sections derived from an IOReg scan. .For Intel Pro/1000MT NIC, within PCI3 device, I added: Device (LAN0) { Name (_ADR, 0x000E0000) Method (_DSM, 4, NotSerialized) { Store (Package (0x0C) { "AAPL,slot-name", Buffer (0x09) { "Internal" }, "class-code", Buffer (0x04) { 0x00, 0x00, 0x02, 0x00 }, "name", Buffer (0x17) { "10/100/1000BT Ethernet" }, "model", Buffer (0x1A) { "Intel Pro/1000MT Ethernet" }, "device-id", Buffer (0x04) { 0x26, 0x10, 0x00, 0x00 }, "vendor-id", Buffer (0x04) { 0x86, 0x80, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } . For Firewire, within PCI6 device, I added: Bad idea - all removed! --------- EDIT - 15Jan2014: Modifying DSDT code for Firewire is actually a very bad idea because, as stated by RampageDev, it breaks Sleep! As such, Firewire patch was totally removed.
  7. Yes I'm 200% sure of the code, I use it in my D630n DSDT. Make sure you copy paste it properly and, if you use TextEdit, that option Smart Quotes is not ticked in menu Edit->Substitutions. That tends to mess up DSDT source code and cause compilation errors if set...
  8. Just do a search on the applications names, you should find them if they're on disk. You can also check they're all valid by launching them...
  9. Why are you booting with -x flag??? That is safe mode! There is absolutely no reason for you to do that. Safe mode does not permit graphics kexts to be loaded so you'll have no graphics acceleration. When you create your USB installer, you should just use my /Extra folder instead of the OSXL bootpack. So redo your "Install Extra" again, pointing to my /Extra folder provided above. Then boot your installer normally. To reflect your AR5B91 wireless card, copy the DSDT table found in the /Extra folder I provided above to your desktop. Assuming you have Chameleon Wizard installed (and not any other EDST editor tool), double click on the dsdt.aml file to decompile it and open the resulting .dsl file in TextEditor. Then replace the whole device (ARPT) section with the following code: Device (ARPT) { Name (_ADR, Zero) Name (_PRW, Package (0x02) { 0x09, 0x03 }) Method (_DSM, 4, NotSerialized) { Store (Package (0x0C) { "model", Buffer (0x26) { "Atheros AR928x 802.11a/b/g/n Wireless" }, "device_type", Buffer (0x08) { "AirPort" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x10) { "AirPort Extreme" }, "AAPL,slot-name", Buffer (0x09) { "Internal" }, "compatible", Buffer (0x0B) { "pci168c,30" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Save the edited .dsl file then double click on it to compile it with Chameleon Wizard DSDT compiler. Place the resulting dsdt.aml to /Extra and reboot. You should then see the Atheros card being properly reported in System Report.
  10. Ok, that's perfect. A regular D630 nVidia with DW1390 Wireless card. I'll prepare a tuned-up /Extra for you to try...
  11. P & C States in Chameleon boot plist are useless with NullCPUPowerManagement. You need to use PState kext + PSMenu app to obtain (emulated) SpeedStep on your CPU.
  12. Sure, I'll send you the necessary DSDT patch.
  13. There's a non-exhaustive list of supported/unsuported wireless cards in R&D->Hardware->Wifi/Bluetooth section of the forum. Did you try patching the Broadcom kext or the BCM43xxFamily kext? BCM4322 cards are supported, so may be a card based on BCM43228 could be too. PS: don't tell your mother-in-law, change the card discreetly! In fact, one should NEVER tell anything to a mother-in-law...
  14. nVidia GeForce 8400GS should be natively supported by the vanilla kexts, so you have nothing to do at all, just boot with GE set to Yes. That card uses the same GPU family (G86) as that used in Quadro NVS 135M/140M or FX 360M (G86M chip - mobile version of G86) found in Latitude D630/D830 or Precision M2300/M4300 laptops to name a few and these enjoy full native graphics support from SL to Mav. nVidia even lists drivers for that card up to 10.8.5...
  15. Well, it all depends on your ability to have a Mac or a Hack system at your disposal at the moment. If you do, then just use myHack to make your USB installer, knowing that an older version such as v3.1.2 is better suited for SL than subsequent releases (v3.2/v3.3). You can point myHack to your SL .dmg image without a problem, although it probably will ask you to mount it first. If you do not have a Mac or a Hack, then you can consider Nawcom's ModCD as a bootable installer (it comes as a downloadable .iso image that you restore to CD/DVD) but that normally requires a retail SL DVD or a USB key with a restored image of retail SL. Since you say you have the imaged .dmg package on your USB key, that probably won't do for ModCD. You'd have to find a way to restore that image to a key and that requires a Mac or a Hack too!
  16. I would try without patched AppleIntelCPUPowerManagement, i.e. the regular Vanilla kext (which means no NullCPUPowerManagement either) + Kozlek's FakeSMC + P&C States enabled in Chameleon boot plist. Regarding sleep, try without SleepEnabler but set the Hibernate mode to 0 through sudo pmset hibernatemode 0 Terminal command, i.e. plain old sleep mode.
  17. Indeed, EDP/myHack will do that in Safe mode. To rebuild permissions and caches, you have to open up Terminal and use "myfix -qt /". Answer "Y" when prompted.
  18. Indeed, that's a bit of a problem so we need to review our bootpack. You should however find the generic PS2 kexts on the USB installer: - either in /ExtraBackups - or in /Applications/Utilities, right click on myHack to open its contents, then browse to Contents/Resources/Extra These normally contain the kexts that are part of myHack's Generic bootpack.
  19. I would suggest 2 different things to try with your USB installer: 1) try and boot with option cpus=1 in case it's the QuadCore CPU that's causing the issue 2) in /E/E, remove NullCPUPowerManagement and replace FakeSMC v4.0 by one of Kozlek's recent FakeSMC versions (latest being v6.0.1042 at time of writing: http://sourceforge.net/projects/hwsensors/ -> download one of the binaries zip further down the page on the right side under "Recent releases", then place the plugin kexts inside the PlugIns subfolder of the FakeSMC kext). The Chameleon boot plist then needs to be modified so that P & C states are selected. Finally re-run myFix (quick) on the USB installer before attempting to boot it.
  20. You can only run Snow Leopard 10.6 with that 32bit Core Duo CPU. Just read up the EDP pages above, they contain the step by step guide, then follow the process. Upgrade your CPU to a 64bit Core 2 Duo (strictly FSB667) and you'll be able to install and run Lion 10.7, even ML with the MLPF hack, in which case head over to the EDP->Supported Models with Guide forum section for a detailed guide. Regular 64bit ML and Mavericks are off mark for the D620, whatever the model.
  21. If you've done a proper myHack installation, the /Extra folder I attached will get you going in a fully tuned mode. Just remember to run myFix (full) and update Chameleon (to r2283 at the moment) through the Wizard. Again, make sure you run BIOS A15 and that it is setup according to the recommended parameters listed in the pinned thread. If you follows those instructions, you cannot go wrong, I guarantee successful results.
  22. Can you please confirm in your BIOS that the audio is Sigmatel 9205 and that lspci -nn Terminal returns the following? 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 02) Thanks.
  23. How did you install ML on your system? Which method? You CPU could be unrecognised because of the boot loader you use. Which is it, which version? Regarding audio, which version of VoodooHDA do you use? Did you try to edit the kext's plist to increase parameter iGain to say 90 or 100?
  24. No. If you don't use myHack, don't use myFix but proceed with your usual method (kext wizard, manual installation or other).
  25. Hervé

    Ar9462

    Only Qualcomm or Apple write these kexts... Conclusion: it's not supported in Mavericks since it's not compatible with 10.9's Atheros40 kext. It might have been compatible with Atheros/Atheros21/Atheros40 kexts of SL, L but it's not with ML and Mavericks -> change your card.
×
×
  • Create New...