Jump to content

Latitude E5440: Ventura WIP


Andres Galeano

Recommended Posts

  • Administrators

You'll need to be specific about your wireless card and tell us what model it is. ITLWM support for Ventura is currently at early alpha stage so, indeed, you may find your model is not fully supported at the present time.

Re: audio, you'll have to identify the codec; being an E5440, I'm tempted to say ALC292 as per other Haswell Latitude E Series in which case injecting layout-id 12 normally does the trick. Basically, the exact same thing as per previous macOS versions. Again, make sure to stay away from any OCLP audio patches as that will affect your system.

Link to comment
Share on other sites

Hello colleagues... I am going to comment on the current situation.

  1. Get Intel WiFi/BT working with kext update from current developers. They are running stable.
  2. The sound (ALC3226 aka ALC292) was recognized after a NVReset after the previous update.
  3. I have noticed that some TXT report files are accumulating in the EFI folder. I want to give it more stability which points I could touch to focus.

Attached IOReg, Config.plist and EFI Folder in Google Drive.

 

Link to comment
Share on other sites

  • Administrators

I'm surprised by your iGPU settings/properties injection:

E5440_iGPU_properties.jpg

 

No need to inject any fbmem or stolenmem patches for Haswell graphics/HD4600. Get rid of those. And cursormem patch is entirely optional, use it only if you experience cursor corruption.

 

Azul framebuffer  #12 0x0a260006 defines the following video memory and ports settings:

ID: 0A260006, STOLEN: 32 MB, FBMEM: 19 MB, VRAM: 1536 MB, Flags: 0x0000000F
TOTAL STOLEN: 52 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 116 MB, MAX OVERALL: 117 MB (123219968 bytes)
Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP
[2] busId: 0x04, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP
00000800 02000000 30000000
01050900 00040000 87000000
02040900 00040000 87000000

 

HDMI output usually attaches to connector con1, not con2. So that's what you'd usually set to HDMI type. Pipe needs to be changed to 12 too for both connectors. So you'd therefore inject the following adjusted settings:

framebuffer-con1-enable      1               NUMBER
framebuffer-con1-pipe        12000000        DATA
framebuffer-con1-type        00080000        DATA
framebuffer-con2-enable      1               NUMBER
framebuffer-con2-pipe        12000000        DATA

 

See here.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...