Administrators Hervé Posted May 23, 2016 Administrators Share Posted May 23, 2016 I cannot understand why you'd binmod your Azul FB kext in such a way. You should never overwrite replace an existing layout by the id of another existing one! You end up with a Azul FB kext where there are 2 x entries for layout id 0a260006. That is just wrong to me. Afaik, playing with port number will not change anything regarding backlight control. It's the display type recognition that's key here. Issue such as yours are usually encountered on dual GPU system but yours was not listed as such... Go back to the vanilla kext and try to use the other layout-ids until you hopefully find the one that matters (there are 15 or 17 layouts for Azul). Link to comment Share on other sites More sharing options...
Chao_bee Posted May 24, 2016 Author Share Posted May 24, 2016 Dear sir, sorry for my uncleared description. I didn't change 0x0d220003 to 0x0a260006, I use everything vinilla now. The only working ig-platform-id is 0x0d220003. It's a desktop one. How to make the internal display to be recognized as Applebacklightdisplay instead of Appledisplay? Thanks in advance, sir. In the former post, I just want to tell u something I did a few days before. I changed the data under 0x0a260006, but not the layout id itself. I know it's wrong and meaningless. Just sorry for that. Link to comment Share on other sites More sharing options...
Chao_bee Posted May 27, 2016 Author Share Posted May 27, 2016 Dear sir, if I just wanna turn my screen to be recognized as internal, (because it looks like an external one with AppleDisplay), what should I do then? It's very very appreciated for ur help. Thx & best wishes. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted May 27, 2016 Administrators Share Posted May 27, 2016 When the built-in LCD is not detected as such, the fix usually consists of patching the PNLF device in DSDT and/or adding boot display info to the IGPU device @0x00020000. The patched DSDT I upload previously included this. But I think you're not using the correct config for your graphics/display. You have a laptop with HD4200 graphics and, as such, you should be using a mobile layout such as 0x0a260006, not a desktop one like you currently do with 0x0d220003. Desktops don't have built-in LCD per se... To me, that's where your issue is. Link to comment Share on other sites More sharing options...
Chao_bee Posted May 28, 2016 Author Share Posted May 28, 2016 Yes sir, I think u r quite right. But for the moment, I cannot use any laptop Framebuffer to make the screen working. Shall I modify the AppleIntelFramebufferAzul.kext ? Thanks a lot and wish u a happy day! Link to comment Share on other sites More sharing options...
Administrators Hervé Posted May 28, 2016 Administrators Share Posted May 28, 2016 No, why would you do that? You'd only modify the FB kext to gain VGA/DVI/HDMI output if not natively supported. You cannot modify the FB to make your internal LCD recognised as such. You have to get graphics supported under a mobile HD4x00 layout. Try them all and see how it goes. I believe you'll never get anywhere with a desktop layout. Your Clover config.plist also showed a custom EDID, did you try without it? Link to comment Share on other sites More sharing options...
Chao_bee Posted May 30, 2016 Author Share Posted May 30, 2016 Yes sir, I've tried to inject EDID by dsdt or even not, but both black screens. The only way to make the screen working so far, is injecting EDID through clover. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted May 30, 2016 Administrators Share Posted May 30, 2016 What resolution is your built-in LCD screen? Link to comment Share on other sites More sharing options...
Chao_bee Posted June 1, 2016 Author Share Posted June 1, 2016 Extracted contents: header: 00 ff ff ff ff ff ff 00 serial number: 4c 83 48 4c 00 00 00 00 17 17 version: 01 04 basic params: 85 18 0d 78 0a chroma info: 3a 75 a2 56 4d 9b 27 0e 50 54 established: 00 00 00 standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 descriptor 1: 52 35 80 80 70 38 1f 40 20 20 23 00 ef 86 00 00 00 1a descriptor 2: a8 2a 80 80 70 38 1f 40 20 20 23 00 ef 86 00 00 00 1a descriptor 3: 00 00 00 fe 00 46 56 30 30 44 80 31 30 38 48 4c 0a 20 descriptor 4: 00 00 00 00 00 03 41 15 28 01 00 00 00 0b 01 0a 20 20 extensions: 00 checksum: 94 Manufacturer: SDC Model 4c48 Serial Number 0 Made week 23 of 2013 EDID version: 1.4 Digital display Color depth is undefined DisplayPort interface Maximum image size: 24 cm x 13 cm Gamma: 2.20 Supported color formats: RGB 4:4:4, YCrCb 4:2:2 First detailed timing is preferred timing Chroma Info: Red X: 0.632812 Y: 0.338867 Green X: 0.302734 Y: 0.607422 Blue X: 0.153320 Y: 0.057617 White X: 0.313477 Y: 0.329102 Established timings supported: Standard timings supported: Detailed mode: Clock 136.500 MHz, 239 mm x 134 mm 1920 1952 1984 2048 hborder 0 1080 1082 1085 1111 vborder 0 +hsync -vsync Detailed mode: Clock 109.200 MHz, 239 mm x 134 mm 1920 1952 1984 2048 hborder 0 1080 1082 1085 1111 vborder 0 +hsync -vsync ASCII string: FV00D Manufacturer-specified data, tag 0 Checksum: 0x94 (valid) EDID block does NOT conform to EDID 1.3! Missing name descriptor Missing monitor ranges Detailed block string not properly terminated Link to comment Share on other sites More sharing options...
Recommended Posts