On Sunday, 25 August 2024 20:37:37 BST Dale wrote: > Alan Mackenzie wrote: > > Hello, Dale > > > > On Sun, Aug 25, 2024 at 13:28:14 -0500, Dale wrote: > >> Alan Mackenzie wrote: > >>> Somehow I don't think that will work (which doesn't mean I won't try > >>> it). > >>> There is something in the motherboard which is throwing off the desired > >>> resolution by those extra 192 horizontal pixels, even in the BIOS. > >> > >> Do you have x11-apps/xrandr installed? If you do, see what this says. > > > > I didn't, but I do now. After trying (and failing) to run it on the > > console, I tried in X-Windows (the display of which is miserably > > unstable at the moment). > > > >> xrandr --listmonitors > >> > >> This is mine: > >> > >> root@Gentoo-1 / # xrandr --listmonitors > >> Monitors: 3 > >> 0: +*DP-2 1920/698x1080/393+0+1080 DP-2 > >> 1: +DP-1 1920/698x1080/393+0+0 DP-1 > >> 2: +DP-7 1920/1150x1080/650+1920+1080 DP-7 > >> root@Gentoo-1 / # > > > > That's one tremendous monitor you've got on DP-7. :-) > > > > I've got just the one monitor. I got back: > > > > 0: +*HDMI-A-0 1920/521x1080/293+0+0 HDMI-A-0 > > If I read that and my thinking is right, that is what it should be.
Yes. > I > don't completely understand everything that output is saying. But, I > technically have three monitors. I have two in front of me that have > different displays. Those are DP2 and DP-2. The third, DP-7, is my TV > that I watch. It goes to a splitter which goes to a TV in my bedroom > and one in the living room. I can cook, clean etc while watching TV. > DP-7 is to the right of DP-2 which may be why it shows something larger. > > Some of this monitor stuff is a bit confusing. > > >> DP-2 is my primary display and if you have only one monitor, should be > >> the only line for you but might be DP-1 instead. Micheal might can > >> explain this better, or even more correctly, but I think the important > >> part for this is where mine says +0+. I think, just think, if yours > >> says something like +192+ instead of 0, that might be a clue. If it > >> says 0 as it should, then this may be the wrong track to look down. > >> What I'm wondering, is the monitor set to show a blank, or black, > >> section on that side for some reason. This could very well not be the > >> case tho. If it shows correctly like mine does, then ignore this and > >> know that isn't causing the problem at least. > > > > No, I've got the +0+, too. > > > >> This is a odd problem. I don't think I ever saw this even during the > >> old CRT days. o_O > > > > I'm convinced this isn't a problem in Linux. It's something having got > > wedged in the motherboard's firmware, seeing as how the blank strip > > appears even when going into the BIOS. The plot thickens! If the resolution in the BIOS menu is also wrong and offset, it sounds like an MSI bug of sorts - "Try disabling CSM" in your UEFI settings: https://forums.tomshardware.com/threads/low-resolution-boot-uefi-bios.3530375/ https://superuser.com/questions/1209012/uefi-and-therefore-linux-console-isnt-displayed-at-native-resolution I have no idea why CSM affects the video resolution of the firmware, but it may have to do with how much space is available on the NOR flash chip where the UEFI firmware is stored. Enabling CSM may be eating up some/more resources, leaving less to initialise and run the graphics capability of the MoBo. :-/ > > I suspect I'm going to have to > > reinitialise the CMOS ram, which I really don't want to do, though > > Michael doesn't think that's the problem. We'll see. I wasn't aware this display issue is present *before* the OS has even loaded. This is not a linux issue and the linux driver itself does not seem able to correct it. OK, in the first instance disable the CMS in the UEFI settings and reboot. Some boards do not lose some of their cached settings when you simply shutdown. Remove the power cable, depress and hold the power button for 10-20 seconds. Any capacitors will discharge. Reconnect the power and boot normally. If the above gymnastics do not fix it, then you'll have to try resetting the MoBo. Make a note of any changed settings and check the CSM option is left disabled. > Ahhhhh. If it does it in the BIOS, it's either a monitor or video card, > or mobo if video is built in, problem. On modern APUs video graphics chips are integrated within the CPU die itself as separate graphics cores. > If a monitor isn't right in the > BIOS screen, odds are it won't be when booted either. Can you install a > video card and test? If it works, mobo has a video driver problem. If > not, could be monitor or cables or something. > > At least we know one thing it isn't. ;-) > > Dale > > :-) :-) Let's hope this is an MSI/CSM specific issue rather than a hardware fault.
signature.asc
Description: This is a digitally signed message part.
