Jump to content

Hervé

Members
  • Content count

    3,469
  • Joined

  • Last visited

  • Days Won

    14

Hervé last won the day on September 17

Hervé had the most liked content!

3 Followers

About Hervé

  • Rank
    InsanelyMacaholic

Profile Information

  • Gender
    Male
  • Location
    Rennes, BZH of course!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hervé

    GT430 et dual screen

    Ok, donc, en IOReg, on voit la carte GT430 sous le bridge PCI @3 (0x00030000) avec: la partie video sous le device "display"@0 la partie audio sous le device "10de,bea"@0,1 On va pouvoir essayer d'injecter les propriétés de la carte dans la DSDT (qui est loin d'être un top en la matière...). Pour le 1er port vidéo Display-A@0, on voit: port number = 0 connector-type = HDMI (0008 0000) display-cfg = 0301 0300 boot display = true Pour le 2nd port vidéo Display-B@0, on voit: port number = 2 pas de connector-type display-cfg = FFFF 0001 Questions: combien de ports sur la carte et quel type? quel port était utilisé quand tu as pris ton extrait IOReg? DVI ou VGA? peux tu passer en simple écran sur l'autre port et reprendre un extrait IOReg et le poster? En attendant, j'ai corrigé les quelques petites erreurs de la DSDT d'origine et injecté ceci sous le device AZAL: Device (PEG0) { Name (_ADR, 0x00030000) // _ADR: Address Device (GFX0) { Name (_ADR,0x00) Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@0,device_type", Buffer () { "display" }, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 // HDMI connector-type for 1st display output @0, port #0 }, "@0,display-cfg", Buffer (0x04) { 0x03, 0x01, 0x03, 0x00 }, "@1,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@1,name", Buffer (0x0F) { "NVDA,Display-B" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,connector-type", Buffer (0x04) { 0x00, 0x02, 0x00, 0x00 // DVI connector-type for 2nd display output @1, port #2 }, "@0,display-cfg", Buffer (0x04) { 0xFF, 0xFF, 0x00, 0x01 }, "NVCAP", Buffer (0x14) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00, /* 0008 */ 0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x40 // 1024MB VRAM }, "device_type", Buffer (0x0C) { "NVDA,Parent" }, "model", Buffer () { "Gigabyte GeForce GT 430" }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) } } Device (HDAU) { Name (_ADR,0x01) } } Ci-dessous la DSDT patch. Copie la dans le répertoire Clover ACPI/patched et redémarre. Prend les IOReg avec un seul écran connecté (HDMI / VGA / DVI) et poste les IOReg correspondants. DSDT.aml.zip
  2. Hervé

    GT430 et dual screen

    我是你父親!
  3. Try this Clover config file. It should work much better. You incorrectly faked iGPU 0x412, instead of 0x04128086 and that's not required since you already have a desktop HD4600 iGPU with that id! config.plist.zip
  4. Hervé

    GT430 et dual screen

    Peut-être un injection des propriétés nVidia dans ta DSDT. Poste un extrait IOReg depuis l'application IORegistryExplorer + ton répertoire EFI Clover. Pour l'injection des propriétés de ta carte dans ta DSDT, ça serait un truc dans le genre ci-dessous (récupéré sur un autre forum) à rajouter sous le device associé à ta GT430 que tu devras identifier dans ton IOReg. Ca, je ne sais pas le deviner. Le code est éventuellement à adapter en fonction des ports disponibles sur ta carte: VGA/DVI/HDMI. Method (_DSM, 4, NotSerialized) { Store (Package () { "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,connector-type", Buffer (0x04) { 0x00, 0x02, 0x00, 0x00 // DVI connector-type for 1st display output @0 }, "@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 // HDMI connector-type for 2nd display output @1 }, "@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 */ 0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x40 // 1024MB VRAM }, "device_type", Buffer (0x0C) { "NVDA,Parent" }, "model", Buffer (0x16) { "nVidia GeForce GT 430" }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Tu pourras éventuellement rajouter un 3ème port @2 avec le connector-type VGA (0x00010000) si nécessaire ou modifier le 2nd port @1. Après, je ne garantie rien pour les données NVCAP. On pourra déjà regarder ce que ça donnera dans ton extrait IOReg. Sinon, fais une recherche sur "dual screen GT430" et tu trouveras pas mal de choses sur le Net.
  5. Desktop HD4600 with id 0x0412 is normally supported OOB as long as you inject Azul layout-id/framebuffer 0x0d220003. No obvious reason why it would be different with your Intel i5-4590. Without this basic requirement, you will not gain graphics acceleration and will experience degraded graphics/system performance. Please post your zipped Clover EFI folder with your patched DSDT (but without the Themes subfolder) if you want further support.
  6. Ok, I found that, if I apply Dosdude1's patcher to my Mojave PB1 installation package, the USB installer is unbootable and loops indefintely with SIGKILL/SIGDEV errors, no matter what. I did notice an error at the end of the patcher's execution related to some incorrect DP1-related path when trying to copy OSXInstall.mkpg package or something like that. On the other hand, no such issue with the createinstallmedia method but then I cannot use it on officially unsupported platforms... I guess it'll all be sorted once Dosdude1 updates his patcher for the GA release that come sout on Mionday. Regarding your Atheros card, it is an AR9285-based AR5B95 (168c,2b); there is no such thing as an AR5B29... AR5B95 works OOB with a little DSDT patch to declare compatibility with a natively supported model based on Atheros chips such as AR9380 (168c,30) or AR9280 (168c,2a) as detailed here: https://osxlatitude.com/forums/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/ If you patch your DSDT, you'll never have to patch the Atheros40 kext again.
  7. The default write com.apple.universalaccess reduceTransparency -boot [true|false] command just does what it's always done. What leads to claim there is "hybrid transparency" is that, after executing the command to disable transparency, the script only restarts Finder and Spotlight, not the Dock or anything else. However, after a reboot, transparency is completely disabled, as anyone would expect, i.e. white Finder bar, dark Dock, etc.. So the "hybrid transparency" is only effective for as long as you run the script from a system with transparency enabled and you do not reboot. You need to restore default transparency settings before a reboot or shutdown if you want to enjoy the results of that script again (i.e. you need to either run the script and select option 2, or enter the default write command to set reduction to false or use the Accessibility->Display PrefPane to untick Reduce transparency parameter). All in all, it's nice for a few times but probably rapidly quite annoying to do in the long run. Example on non-Metal HD3000 system in light mode... * with default transparency: * without transparency: * after executing the script under default transparency mode: * after rebooting the system without restoring default transparency settings: So, yes, the trick with Finder brings a nicer look but you have to restore default settings to avoid total loss of transparency on reboot. This would need to be refined through an automated process at boot and restart/shutdown to be properly usable.
  8. Hmm... ok, so all in all, all that your script does is apply the good old command that disables/enables transparency: defaults write com.apple.universalaccess reduceTransparency -bool [true|false] What's new? the partial restart of macOS functionalities?
  9. Hervé

    HP 8710P Can't install No USB.

    Wow, what a mess! Tons of inappropriate and useless things in there... Where did you get that from??? Use the attached kexts set + Clover config file instead. If USB ports don't fully work, you may have to build your own USB injector kext once you identify all your USB ports in IOReg. Clover_setup.zip
  10. Hervé

    HP 8710P Can't install No USB.

    When it does that, take out the USB key and replug it into another port. See if that resumes booting process. This being said, your Clover configuration is probably incorrect for your laptop. Why don't you post a zipped copy of your Clover EFI folder (less the Themes subfolder)?
  11. -> They have their own web site and forum for support.
  12. Hervé

    Can't find AMD 8000 Controller.kext

    Erm... "not new", huh? Well, no need to look for the kext on the Internet... Unless you're running on an old version of OS X like Mavericks or earlier, you'll find the kext in /S/L/E... It's part of the vanilla installation! Since Yosemite if I'm not mistaken...
  13. Hervé

    HP 8710P Can't install No USB.

    Starting with El Capitan, you need to disable SIP; did you do that? set CsrActiveConfig to 0x67 set BooterConfig to 0x28
  14. Hervé

    HP 8710P Can't install No USB.

    As I said, you need to add Rehabman's USBInjectAll kext; you'll find it at his repository. Add it to your Clover kexts folder.
  15. Hervé

    HP 8710P Can't install No USB.

    Tried to look at the list of patches?
×