07-09-2018, 05:57 PM
(This post was last modified: 07-09-2018, 09:54 PM by ab1jx.
Edit Reason: Added Mali link
)
Seems a bit sledgehammerish (doesn't that replace the kernel too?) but maybe it will get Ayufan's attention to the fact there's a problem. My guess is this only happens with monitors 5 years or so old and more because the EDID is a different version. The USB keyboard thing still needs the manual printk fix too.
My workaround is less drastic and less permanent. Find an randr client that works in your case, I used lxrandr. Set the screen size to something that should fit, like 1024x768. That works for me, at least for X, but it reverts to 1920x1080 on reboot. I think it only changes something in X and the change doesn't get written to the Mali. I tried fbset, xvidtune, xset, none will do. Probably a modeline would be a waste of time. It wouldn't surprise me if there's some utility that controls the Mali but I haven't found it yet. Maybe it can only be set at boot. I have an adapter to get a serial console (https://www.adafruit.com/product/954) on order, a guy I was chatting with at Armbian says all the important stuff is done through serial. The errors I get seem like the Mali refuses to listen to X. I think there's a lot of documentation we don't have, maybe it's all in Chinese.
This is close, but more about features rather than controlling it. https://developer.arm.com/docs/dui0505/l...troduction Maybe the interference with control comes from Xorg itself as some sort of security measure. I'm not the client so I can't set certain things. But no, the problem is the console size too. Resizing the framebuffer seems like what needs to be done. Maybe the size can only be set at boot.
I'm looking at a 1024x768 screen I set with lxrandr, it looks right, my monitor says it's 1024x768. But fbset or fbset -i says it's 1920x1080. ls /dev/fb* finds only fb0, and lsof | grep "/dev/fb" shows nothing has it open. They're 2 different things. What does lxrandr connect to? I thought it was just an interface to randr. But I rebooted, my console is 1920x1080, brought up X and it's 1024x768. They're 2 different things.
Posted question at https://unix.stackexchange.com/q/454406/192145
My workaround is less drastic and less permanent. Find an randr client that works in your case, I used lxrandr. Set the screen size to something that should fit, like 1024x768. That works for me, at least for X, but it reverts to 1920x1080 on reboot. I think it only changes something in X and the change doesn't get written to the Mali. I tried fbset, xvidtune, xset, none will do. Probably a modeline would be a waste of time. It wouldn't surprise me if there's some utility that controls the Mali but I haven't found it yet. Maybe it can only be set at boot. I have an adapter to get a serial console (https://www.adafruit.com/product/954) on order, a guy I was chatting with at Armbian says all the important stuff is done through serial. The errors I get seem like the Mali refuses to listen to X. I think there's a lot of documentation we don't have, maybe it's all in Chinese.
This is close, but more about features rather than controlling it. https://developer.arm.com/docs/dui0505/l...troduction Maybe the interference with control comes from Xorg itself as some sort of security measure. I'm not the client so I can't set certain things. But no, the problem is the console size too. Resizing the framebuffer seems like what needs to be done. Maybe the size can only be set at boot.
I'm looking at a 1024x768 screen I set with lxrandr, it looks right, my monitor says it's 1024x768. But fbset or fbset -i says it's 1920x1080. ls /dev/fb* finds only fb0, and lsof | grep "/dev/fb" shows nothing has it open. They're 2 different things. What does lxrandr connect to? I thought it was just an interface to randr. But I rebooted, my console is 1920x1080, brought up X and it's 1024x768. They're 2 different things.
Posted question at https://unix.stackexchange.com/q/454406/192145
