Closed Ferrarisrex closed 2 months ago
Hi @Ferrarisrex
Thank you for reporting this. I'll run some tests to try replication and let you know the results once I have more to share.
A few questions that can help clarify the issue:
I can not change to any native resolutions or custom resolutions it happens on all monitors I do not know, as i just downloaded IGCC for use Changing the resolution via windows settings works fine
Thank you @Ferrarisrex
That's a strange situation. I'm not able to reproduce at this time, but I'll keep testing different configurations and discuss with my team.
In the meantime, the ssu seems to have trouble getting the driver information. This is a sanity check I'm sure you've tried, but can you confirm you tried a clean install of the driver and IGCC beta?
In addition, are there other settings within IGCC that return the same error when trying to configure?
Yes, I had done a clean install of both driver and software, I can not change the scale to anything except Maintain Display Scaling, and Custom I have tried using both the HDMI and DisplayPort, both have the same problem, they are connected to the DVI-D port of an older monitor that has a resolution of 1280x1024, however it has the same problem when connected directly to the HDMI port of a different monitor, but after some messing about, I was able to get it somewhat working on a Samsung monitor
Hi @Ferrarisrex
Thank you for the update. I know converters to DVI can sometimes cause issues if they're a passive adaptor in not being able to properly display resolutions, but the fact that you can still change the resolutions in Microsoft Display settings is very confusing.
Can you let me know if the resolution changes in Microsoft Display settings get reflected in IGCC once they are changed, as well as what you were able to change to get it working on the Samsung monitor?
The changes are reflected in IGCC, and then it will let me change the resolution to a few different resolutions, but only once The way I was able to get the Samsung monitor to work was messing with the scale for a while.
Le mer. 7 août 2024, 9:51 AM, Zack-Intel @.***> a écrit :
Hi @Ferrarisrex https://github.com/Ferrarisrex
Thank you for the update. I know converters to DVI can sometimes cause issues if they're a passive adaptor in not being able to properly display resolutions, but the fact that you can still change the resolutions in Microsoft Display settings is very confusing.
Can you let me know if the resolution changes in Microsoft Display settings get reflected in IGCC once they are changed, as well as what you were able to change to get it working on the Samsung monitor?
— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/828#issuecomment-2273794339, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVWQQQGNZZSNOBP52GES2O3ZQI7B5AVCNFSM6AAAAABLZXTAGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZTG44TIMZTHE . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/828/2273794339@ github.com>
Hi @Ferrarisrex
After some testing, I'm not able to see the issue on my end with a similar configuration. It might be helpful if you can share what resolutions you're trying to get alongside each monitor's edid info, which can be collected in the sys diagnostic report within IGCC.
Hi @Ferrarisrex
Do you have additional information regarding the edid information to share? If you need help, I can also provide additional instructions on how to collect it
It seems to have been a problem with the cable, as changing it makes it not a problem, and putting it back makes it a problem again. This problem doesn't exist when using this cable with other computers and monitors
Le mer. 4 sept. 2024, 4:16 PM, Zack-Intel @.***> a écrit :
Hi @Ferrarisrex https://github.com/Ferrarisrex
Do you have additional information regarding the edid information to share? If you need help, I can also provide additional instructions on how to collect it
— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/828#issuecomment-2330248187, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVWQQQDWJQCZFQDI6VMZVO3ZU6BFDAVCNFSM6AAAAABLZXTAGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGI2DQMJYG4 . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/828/2330248187@ github.com>
It seems to have been a problem with the cable, as changing it makes it not a problem, and putting it back makes it a problem again. This problem doesn't exist when using this cable with other computers and monitors Le mer. 4 sept. 2024, 4:16 PM, Zack-Intel @.***> a écrit :
Thank you for the update. Very strange that it's only that cable and monitor configuration. Sometimes certain adaptors and edids for monitors can clash and lead to corner cases where it doesn't work. I'm glad you were able to resolve this.
I will go ahead and close the ticket. If there are additional issues relating to this, feel free to open a new ticket with the edid information and we can pick up where you left off.
Checklist [README]
Application [Required]
Intel Graphics Command Center (beta)
Processor / Processor Number [Required]
I5-12400F
Graphic Card [Required]
Intel ARC A750
GPU Driver Version [Required]
32.0.101.5768
Other GPU Driver version
No response
Rendering API [Required]
Windows Build [Required]
Windows 10 22H2
Other Windows build
No response
Intel System Support Utility report
cheese.txt
Description and steps to reproduce [Required]
open Intel Graphics Command Center (Beta) open "Display" tab open "General" under "Resolution" change it to anything
Device / Platform
DESKTOP-B6MGHVD
Crash dumps [Required, if applicable]
No response
Application / Windows logs
No response