# The resolution used on graphical terminal # Uncomment to disable graphical terminal # Set to 'countdown' or 'hidden' to change timeout behavior, # Uncomment to enable booting from LUKS encrypted devices GRUB_PRELOAD_MODULES="part_gpt part_msdos" # Preload both GPT and MBR modules so that they are not missed GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=DisplayPort-0:1920x1080x32 video=HDMI-A-0:d" GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet" That made me check fbset, which disappointingly provided the following: It seems like the type of console used also isn't the problem, unless both agetty and kmscon independently have the same issue, which leads me to believe that its an issue with where they're pulling their data from. That's why my guess is that this issue is with something that kicks in before X or Wayland, but after the kernel has it's say, so something around systemd taking over from the bootloader? As is probably obvious, I still have much to learn about the linux boot order, so I hope this isn't a totally stupid thought. I don't think the issue is with the kernel at all, as whatever kernel parameters I have tried have changed nothing once the system finally reaches the login prompt. I have two different sized monitors (2560x1440 1920x1080), and my tty's are also duplicated (not a problem) with the smaller monitor at the correct resolution, and the larger monitor at the same resolution, with letterboxing around the right and bottom of the resolution. So, I'm uncertain if this is exactly the problem that branthebuilder was describing, but if it was, I have it too, and I might have a fresh guess as to what the issue is. I've tried adding a kernel parameter at boot for fbcon=map:1 with no joy. Once X11 starts up the displays work independently as expected, but switching to TTYs demonstrates the same weird restriction in size of the display.Īny idea how to have both monitors use the full screen? I don't care as much that they are mirrored, but if there is a way to limit it to a single display that would be even better. Once ly launches this arrangement continues. Shortly before the display manager (ly) launches the screen flashes and the larger, higher resolution monitor displays at full resolution but using only the portion of the screen that appears to correspond to the size of the smaller screen. During post the smaller, lower resolution monitor appears to be set as the primary with both BIOS and kernel boot messages showing up full screen on both but not at full resolution on the larger monitor. TTYs are mirrored on each display, meaning the same text shows up on both and any interaction is shown on both. I have two monitors of different size and resolution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |