| View previous topic :: View next topic |
| Author |
Message |
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 776
Location: Close to Annecy (France)
|
 Posted: Sun Sep 27, 2020 12:32 pm Post subject: Framebuffer resolution issue |
 |
|
Hello,
I have a strange issue while using framebuffer.
Up to now, I was using following resolution : D:1280x768p-59
but after a system reboot without any change (nor system update, screen change, ...) this resolution is now not available :
| Code: | torchwood ~ # cat /sys/class/graphics/fb1/modes
U:720x480p-60
D:1920x1080p-50
D:1280x720p-50
D:1920x1080i-50
D:1920x1080i-60
D:720x576p-50
V:1280x1024p-75
V:1024x768p-70
V:1024x768p-60
V:800x600p-75
V:800x600p-72
V:800x600p-60
V:800x600p-56
V:640x480p-75
V:640x480p-72
V:640x480p-60
D:800x480p-60
|
and now
| Code: | torchwood ~ # echo D:1280x768p-59 > /sys/class/graphics/fb1/mode
bash: echo: erreur d'écriture : Argument invalide
|
Why this mode disappeared ?
Thanks
Laurent |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47142
Location: 56N 3W
|
| Posted: Sun Sep 27, 2020 9:45 pm Post subject: |
|
|
destroyedlolo,
What framebuffer driver were you using.
Has it changed?
Which framebuffer driver is in use?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 776
Location: Close to Annecy (France)
|
| Posted: Sun Sep 27, 2020 11:02 pm Post subject: |
|
|
Hello,
the kernel is configured for SUNXI_HDMI.
A found a way to cheat a bit, by enabling scaller using : https://github.com/hglm/a10disp
So
| Code: | | ./a10disp --screen 1 rescale 1366 768 1280 720 |
"scalls" to custom resolution I'm looking for.
The only issue is the kernel is still reporting 1280 720 but it's better than nothing.
[edit] hum, I'm not so sure it will work, because as the kernel is still reporting 1280x720, I think it will be also the size of mapped memory, no ? Will try tomorrow ...[/edit]
Anyway, it doesn't explain why 1280x768 is not anymore available.
Best regards,
Laurent |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47142
Location: 56N 3W
|
| Posted: Mon Sep 28, 2020 10:13 am Post subject: |
|
|
destroyedlolo,
SUNXI_HDMI?
Is this an arm SoC ?
VESA FB can only use the resolutions programmed into the Video BIOS.
The others read the EDID data from the display and choose the first resolution on the list. That's supposed to be the panel native resolution.
We need to know the actual driver in use.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 776
Location: Close to Annecy (France)
|
| Posted: Mon Sep 28, 2020 12:00 pm Post subject: |
|
|
Yes, It's an A20 driven BananaPI.
It has 2 output configured :
- the native 3.5'' panel on LVDS for which I have no issue.
- another one connected thru HDMI
About driver, how can I check that ?
It isn't SunXI's ? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47142
Location: 56N 3W
|
| Posted: Mon Sep 28, 2020 12:04 pm Post subject: |
|
|
destroyedlolo,
The driver will be in dmesg.
Pastebin the whole thing if you can't spot it.
There may be several, so check for a framebuffer handover in dmesg too.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47142
Location: 56N 3W
|
| Posted: Mon Sep 28, 2020 12:05 pm Post subject: |
|
|
Moved from Kernel & Hardware to Gentoo on ARM.
So that the arm peeps are more likely to spot it.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Gentoo on ARM
