IFL 3.63 does not honor display resolution choice

[OldNavyGuy]

Haven't seen this before...

No matter what number is selected, it does not honor the selection.

Other than that, IFL functionality works.

[TeraByte Support]

It's using DRM and letting GRUB pick the video resolution you choose instead of forcing it since you tend to end up with X only taking up part of the screen.

What does "fbset" show for your system. you can try this: ctrl-alt-backspace to end the x session, fbset -xres xxxx -yres xxx to the mode that is available (should see them in cat /sys/class/graphics/fb0/modes ); then enter in: startx

The first item lets grub pick without any input, the others with specific sizes tell grub to use that and if it is not available, to auto pick it.

[OldNavyGuy]

It's using DRM and letting GRUB pick the video resolution you choose instead of forcing it since you tend to end up with X only taking up part of the screen.

What does "fbset" show for your system. you can try this: ctrl-alt-backspace to end the x session, fbset -xres xxxx -yres xxx to the mode that is available (should see them in cat /sys/class/graphics/fb0/modes ); then enter in: startx

The first item lets grub pick without any input, the others with specific sizes tell grub to use that and if it is not available, to auto pick it.

The mode is U:1600x900-0, no matter what is selected.

This is the maximum display mode for the laptop monitor in Windows.

In IFL 3.62, the mode is U:1024x768-75, which is what I selected.

[OldNavyGuy]

Looks like this is the code in 3.63 grub.cfg that has changed from 3.62...

set default=0

menuentry "IFL (GUI) Network Boot Disk - Frame buffer mode" {
set background_color=black
gfxpayload='auto'
echo ''
echo 'Loading vmlinuz...'
linux /vmlinuz uefimode=yes switchx=yes iflkmap=us ktl=qwerty iflbflag=0
echo 'Loading initrmfs.gz...'
initrd /initrmfs.gz

[TeraByte Support]

the latest version is using drm - those chip specific drivers handle things differently. What would happen is you'd get a part of the screen with the gui and the outside edges black. Using DRM may be faster but also allows wake after sleep to work which was desirable for using partwork sleep option for wiping. Does it fill up the full screen? Is it too small?

You can see what it's doing in /tbu/.xsession

You can setup a /tbu/utility/xres file with 1024x768x32 in it and startx will be forced to use that.

what was in: /sys/class/graphics/fb0/modes

?

[OldNavyGuy]

As mentioned above...mode is U:1600x900-0, no matter what is selected.

[OldNavyGuy]

What would happen is you'd get a part of the screen with the gui and the outside edges black. Does it fill up the full screen? Is it too small?

I've never seen outside edges black...

It does fill the full screen, but the font and display is a little wonky.

Regardless, it seems like if it's offering a menu of alternative resolutions, it should honor the user's choice.

[TeraByte Support]

It's leaving it to GRUB to select the requested mode and to fall back to another mode if it wasn't found.

The chipset frame buffer items will most likely be removed here soon, that may make a difference.

[OldNavyGuy]

The 12/14 release fixed the issue.

Thanks.

[TeraByte Support]

Just for information, what shows in your modes file now?