-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only native resolution listed for internal panel #949
Comments
I don't seem to have this issue on stable firmware release (v0.9.0 for V54).
|
Can you provide more details about your setup? I re-checked with final 0.9.0 and still can see only |
I am using Fedora Linux with 6.10.7 kernel. |
I tried 6.10.7 on Qubes OS, and still only native resolution is available. Maybe it's about specific panel model? It should be the same in all V540TU but who knows... It can be found in |
I see. Maybe it is an issue with X Window System, since I am using KDE desktop environment, and the file you mentioned is not on my system. |
In KDE indeed I see more resolutions available. I wonder what is the difference compared to V560TU... |
Ok, so I have two findings:
|
@aker256 are you able to set 120Hz refresh rate? The panel seems to support that, but I don't see it on your listing. |
Yes, but I must do so through the settings application. Here is the output of xrandr after doing so:
|
I have the same model and the same issue.
How do you set that? Is it according to the EDID you enumerated? It would be great to know how to set that up so I could use it for screen sharing and decrease resolution since it is very hard to read anything. |
Modified edid: So, this is how to do it:
Now you should be able to set 2880x1800 with 120Hz and any other resolution with 60Hz (some are listed also with other refresh rates, but those will not work). |
@marmarek yes, it works thank you. Couple small corrections if one would like to follow the same.
07393931ef6a7f2538fba3be242c6b1cca2e9d3bf0f50f0772d61ccb63df8e7a edid_v540tu_rangeonly60.bin
I still have to test that with external projector/tv to see how it works and it doesn't cause additional issues. |
You may need other resolutions (even if result in some areas on your screen being black) if you want for example to mirror with 16:9 projector or so. |
Since the issue happens in Xorg but not in Wayland, I've reported it at https://gitlab.freedesktop.org/xorg/xserver/-/issues/1761 |
Add a package with a patch for NovaCustom V54 resolution issue Dasharo/dasharo-issues#949
Dasharo/dasharo-issues#949 This also needs a backport to correctly calculate refresh rate.
@pietrushnic I have an update that hopefully fixes this issue without extra user changes. Can you check if it works for you too?
|
As for the "fix", it isn't clean fix unfortunately (see commit linked to this issue above). But with the help from upstream and few more people from the community, I found the right place to put "if Novacustom V54" check... |
I confirmed it works correctly. What I did:
|
@wessel-novacustom do you have list of all display models used in V54? Currently in the patch I hardcoded the check to "TMX 8196" (vendor, model number) - that's how the one I have is presented. Is that the only model, or maybe there are some others too? |
@marmarek The only panel we are currently offering for this laptop series is: TIANMA TL140ADXP24-00 |
Component
Dasharo firmware
Device
NovaCustom V54 14th Gen
Dasharo version
0.9.0-rc7
Dasharo Tools Suite version
No response
Test case ID
No response
Brief summary
xrandr lists only 2880x1800 resolution
How reproducible
always
How to reproduce
Boot Linux on v540tu with 2880x1800 panel and call xrandr.
Expected behavior
A wide range of resolutions available, similar to other models.
For example on v560tu with 1920x1200 panel I get:
EDID for this one is:
Actual behavior
EDID for this panel looks like this:
Screenshots
No response
Additional context
This breaks mirroring screen to external display (or a projector) of any other resolution.
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: