my pocket hasn’t arrived yet, but for the framebuffer, at least, would it possible to mitigate this with fbset or kernel framebuffer video parameters until a hardware fix is possible? i’ve had to do similar recently with a raspi to resolve hdmi overscan shenanigans that the normal config options couldn’t resolve
Same thing with sway.
If this behavior is normal then is there anything I should try to do to mitigate?
I’m a beginner with Linux but can follow instructions like a pro 
Thank you!
Thank you, can you show a photo where this problem is visible in sway?
Sorry I had to put this down for a few days but jumping back in.
I’ve attached a couple images:
one is a system screenshot taken within sway, with the right side being an extreme close up emphasizing the pad between the characters and the left most edge of the display.
The other image is a photograph taken of the screen where it meets the bezel.
Hoping this is a simple line of commands I can write to a config file, but if the issue requires a bit of digging then all good I’ll pin it for a later date.
And THANK YOU for your time!!
