Set normal display resolution
- Inicie sesión ou rexístrese para enviar comentarios
I'm setting up Trisquel on a school laptop. The only problem is display resolution. I have 800x600 on normal boot. *Note: If I enter UEFI at first and exit it booting Trisquel, then I get the normal resolution (1920x1080). There is 800x600 after reboot again.* Please help me set 1920x1080 permanently.
I've played around xrandr, but achieved nothing.
Some wiki about resolution on X: https://wiki.Trisquel_is_based_on_iT.com/X/Config/Resolution
Hello,
Can you please share the model of the laptop computer ?
Laptop: DEPO
Model: VIP C15A11
(inxi -M):
Machine:
Type: Laptop System: DEPO s product: DPA156 v: Version 1.0
serial:
Mobo: DEPO s model: DPA156 v: Version 1.0 serial:
UEFI: American Megatrends LLC. v: 0.13 date: 09/14/2022
--VIP C15A11--
This is new to me as this is the first time I see a russian brand computer and it's fascinating. Apparently it's designed to run with a GNU/linux distro, most probably an ubuntu forK as I see in video I44ECA5-9Ug.
The AMD R3 5400U CPU that comes with it has an integrated GPU the Radeon Vega 6, sadly the source code of AMD for GPUs isn't fully compatible with free/libre software, and depending on the hardware some will require blobs just for screen resolution or other function like dual screen, sleep mode etc...
https://trisquel.info/en/forum/set-normal-display-resolution#comment-181826
--If I enter UEFI at first and exit it booting Trisquel, then I get the normal resolution (1920x1080). There is 800x600 after reboot again."--
I also had this issue with one laptop in the past, we concluded at the time it's either the UEFI that injects blobs at that moment or that reminiscences in the ram is somewhat fetched by the kernel and stored until the next boot.
I sadly cannot help you with this. So far the least problematic gpus are intel (and they still proprietary bits like for hardware acceleration).
> reminiscences in the ram
Reminiscent of this unsolved dual-boot case:
https://trisquel.info/en/forum/fresh-install-aramo-laptop-radeon-vega-gpu
The last suggestion in that thread remains unanswered: Did you try "gfxmode=auto"?
--This is new to me as this is the first time I see a russian brand computer and it's fascinating. Apparently it's designed to run with a GNU/linux distro, most probably an ubuntu forK as I see in video I44ECA5-9Ug.--
> My school got those machines in the past year. Some version of RED OS was preinstalled.
--I also had this issue with one laptop in the past, we concluded at the time it's either the UEFI that injects blobs at that moment or that reminiscences in the ram is somewhat fetched by the kernel and stored until the next boot.--
> Ooh!
Your laptop has a Ryzen APU, you won't get display output to work properly because it requires amdgpu to work, which is proprietary.
Well, it works, as I've noted before:
"Note: If I enter UEFI at first and exit it booting Trisquel, then I get the normal resolution (1920x1080). There is 800x600 after reboot again."
Also I have 2560x1440 on my own laptop with Ryzen APU, running Trisquel.
It's giving you issues which is telling me something's broken, any commonly known GPU released in the last eight years must run proprietary software loaded by the kernel for them to work, partially or fully, Intel is somehow the exception.
If you're getting the X11 or Wayland server to start at all then it likely runs with software rendering, which means worse performance and battery life, but the most expected behavior is to fail to start the display server and throw you back into tty.
Don't expect these GPUs to work with Linux-libre, manufacturers go out of their way to ensure these misbehave with free GNU/Linux distributions.
Understand you, but I am sure, this result can be achieved permanently, isn't it?
After-uefi-boot:
(xvidtune -show):
"1920x1080" 207.38 1920 1952 2192 2432 1080 1084 1088 1104 -hsync -vsync -csync
P.S. I could say the teacher, they should hit F2+ESC+ENTER every time they boot (and I would certainly do that, freedom is worth the inconvenience), but they (windows, ibad useds) would say I am crazy, most important - I am sure this can be fixed. We should try xrandr again.
You could run lspci in each situation you mentioned:
$ lspci -k | grep -EA3 'VGA|3D|Display'
That may give you some further hints about what is happening.
I haven't thought about doing this when it happened on the hardware I had a few years ago, but I don't have it anymore. This could maybe point out what is happening/happened considering what I posted previously.
$ lspci -k | grep -EA3 'VGA|3D|Display'
gives:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c3)
Subsystem: Device 1e50:8015
Kernel modules: amdgpu
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
in both situations.