On Fri, Jun 14, 2024 at 01:49:08PM -0400, Felix Miata wrote:
> Michael Kjörling composed on 2024-06-14 17:11 (UTC):
> 
> > On 14 Jun 2024 17:47 +0100, from Mike:
> 
> >> I'd be grateful if anyone could give me any pointers to get the
> >> terminals looking vaguely sensible, please?  I think the first isse it
> >> working out how to stop the screen turning off, which I assume is
> >> because the display is out of range for the monitor.  I can't seen to
> >> figure out how to change that.
> 
> > That would be the first thing I would want to rule out, too.
> 
> > In GRUB, try "e"diting the boot command sequence and on IIRC the
> > "kernel" line (the one that specifies the kernel and kernel
> > parameters), add one of vga=0; vga=0x0f04 (leave current settings); or
> > vga=ask followed by "scan" at the prompt and then select a reasonable
> > one. See https://www.kernel.org/doc/html/latest/admin-guide/svga.html.
> 
> The following applies with all FOSS drivers I've ever used except possibly 
> mga:
> vga= only works until KMS starts. video= does the desired job while KMS is
> engaged. e.g.
> 
>       video=DP-1:1440x900@60
> 
> Causes 1440x900 with refresh 60Hz to be applied only to DP-1. Leave off DP-1: 
> to
> have it applied to all displays. Leave off @60 to allow the system to 
> determine
> refresh.
> 
> https://www.kernel.org/doc/Documentation/fb/modedb.txt
> -- 
> Evolution as taught in public schools is, like religion,
>       based on faith, not based on science.
> 
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>

Hi Felix,

Thanks for your input.  I tried the video= and it made no difference.
However, I did discover that removing "quiet" creates a lot more output.
Funny that, isn't it?  Quite nice too!

I should probably have mentioned earlier, that if one launches X and
then quits X to return to the terminal, the monitor does not turn off
again, howeer, the mode is a bit crazy.  It appears to display 80x25 but
when one starts a new line at line 25, you do not get the usualy
scrolling behaviour, things just appear to get printed out "below the
monitor" if you know what I mean.  Eventually the screen does scroll but
after maybe 200 lines or so and it does so in a big jump.

I seem to recall reading that the Nvidia driver was a bit cavalier and
reinvented various parts of X, so I wondered if there was some crazyness
whereby starting X started some of a necessary components of the driver.
Checking the output of lsmod, as well as ps for anything nvidia related
doesn't appear to be any difference between before X and after X.

I'm also pondering if it's something to do with the port it's plugged
into.  The card has 3 DP ports and 1 HDMI.  Two have displayed plugged
into them.  That said, the UEFI manages to output to a screen and so
does Grub / Kernel, so does X, so one would imagine the bit in the
middle might get it right too?

Any ideas?

Kind regards,
Mike.

Attachment: signature.asc
Description: PGP signature

Reply via email to