Changes between Initial Version and Version 1 of Ticket #17370, comment 3
- Timestamp:
- Oct 31, 2021, 10:07:21 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17370, comment 3
initial v1 4 4 I am currently working on gen9, which also has DDI circuits for sending signals to the screens, and this interface is still down. I'll do a small update where I ask this interface to do a EDID scan (again) which will fail since also DDC/EDID is still down on this interface or the full chipset. 5 5 6 For the other ticket I'd like to ascertain you have the exact same problem before this ticket is marked as a duplicate. I expect we should best have a look at other tickets as well, containing chipsets with DDI as they probably all suffer from the same trouble. So this is later gen7 devices, gen 8 and gen9: I think newer chipsets are not yet 'supported' (ID missing in drive R).6 For the other ticket I'd like to ascertain you have the exact same problem before this ticket is marked as a duplicate. I expect we should best have a look at other tickets as well, containing chipsets with DDI as they probably all suffer from the same trouble. So this is later gen7 devices, gen 8 and gen9: I think newer chipsets are not yet 'supported' (ID missing in driver). 7 7 8 8 After the EDID scan for bleedsa the driver will detect zero displays, foregoing full modesetting, thereby 'restoring functionality'. 9 Please note that after this you cannot chance resolution (should be at the boot res, that will work), but you -can- set virtualscreens and colordepth: that should work since some revisions now (at least it does over here on gen9 DDI) 9 Please note that after this you cannot change resolution (should be at the boot res, that will work), but you -can- set virtualscreens and colordepth: that should work since some revisions now (at least it does over here on gen9 DDI) 10 11 For now you can also use failsafe video at boot which will make the system not start the intel_extreme driver for app_server. 10 12 11 13 Thanks!