Jump to content

cinoyter

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

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

cinoyter's Achievements

Private

Private (2/17)

0

Reputation

1

Community Answers

  1. The problem was that I used the VoodooI2CHID bundled with AlpsHID (as in the AlpsHID instructions), but when I used the VoodooI2CHID bundled with VoodooI2C, the touchpad worked.
  2. Hi again, I have managed to install Ventura on my Latitude 7480. However now I am trying to get the touchpad working and I am having lots of difficulty with ACPI. I have no reason to believe that my touchpad is in any way unusual for this laptop. I dumped my DSDT using a Linux live-USB key distribution (Puppy Linux) and used this to generate a SSDT-GPI0.aml as described. I also have been trying to use the four prebuilt DSDT files for Kaby Lake machines. (This computer is i7 7600U.) A priori, I don't really care which solution is used as long as it works. If I use the four prebuilt DSDT files (but no GPI0) and AlpsHID is not installed, the system boots but there is no trackpad. If I use the prebuilt DSDT files + SSDT-GPIO.aml and AlpsHID + custom VoodooI2C.kext are installed, then I have this screenful followed by a reboot. If I use my own DSDT + SSDT-USBX.aml + SSDT-GPIO.aml and AlpsHID + custom voodooI2C.kext, I have the following screenful and it stays onscreen forever. I am not sure where to go from here. Do you have any idea? Thanks custom_dsdt.zip config.plist.zip
  3. LOL sigh, I guess I'm a moron. I reset the NVRAM, immediately the text in the OpenCore picker was way smaller, etc. So who knows which one of these changes fixed it! Thanks for your help.
  4. I injected my EDID with the hex data obtained via NirSoft's "Monitorview", I removed fbmem and stolenmem from config.plist, and I executed setup_var 0x795 0x2 and setup_var 0x796 0x3 in a modified GRUB shell that I added to my installer USB key's EFI partition, and unfortunately, it still doesn't work. So perhaps my theory is incorrect... Is there another obvious thing to try? I have attached the current state of my config.plist.config.plist.zip
  5. Merci Hervé. I tried your suggestions without success. For the display settings, I had taken the configuration from here mostly. In the meantime I have also tried disabling VT-d, wireless and bluetooth but this also hasn't changed the outcome. I also tried the other device ID (00001B59) but this also didn't change anything. Most of the time when I look up this symptom (grey screen with cursor) on the Internet, the response is "read Dortania's guide closer". But when I dig into it it mostly seems like the grey screen is often a symptom of a misconfigured graphics setup. Many people seem to have success with this particular device but it seems that few people have the HiDPI screen. Thanks
  6. Hi all, I am having a grey screen with moving mouse cursor when I boot from a USB installer (Ventura). So it seems to "boot up" but instead of showing any UI, it shows a grey screen. I have tried to make my own configuration (attached) and have also tried the one in this thread and I have the same results. I am telling myself it is most likely because of the high-resolution screen on this computer but I'm not sure what to do. I'm not sure where to go from here because I can't dump the boot messages nor are they logged anywhere but I'm happy to produce any logs that are available. System specs: i7-7600U, 16GB RAM, 512GB M.2, Intel HD 620, 2560x1440 screen. Thanks! config.plist.zip
×
×
  • Create New...