Why have all my tty gone to 80x24?

OpenSUSE 11.1 + latest updates

When I reboot I can’t get my tty resolution back to the 1680x1050 it was
running at earlier. The grub configuration shows vga=0x348 which is
1680x1050 and was working a while ago.

On boot I now get messages telling me that this resolution is invalid and
offers a selection of resolutions, all of which are 80x#. Even if I select
80x60, part way through the boot process the resolution switches to 80x25
and that’s what I get for tty1-tty6.

I think this started with the last kernel update but I’m not sure …
I’ve tried other grub vga values (e.g, 0x318, 0x31B) but I always get the
same result - invalid resolution and pick an 80x# size which then goes to
80x25.

Come on. I’ve got this nice big monitor and 80x25 looks bloody stupid at
this size. What can I do to resolve this without reverting to an earlier
kernel?

Alan

Fudokai wrote:
> What can I do to resolve this without reverting to an earlier
> kernel?

log a bug report maybe? http://en.opensuse.org/Submitting_Bug_Reports


palladium

palladium wrote:

> Fudokai wrote:
>> What can I do to resolve this without reverting to an earlier
>> kernel?
>
> log a bug report maybe? http://en.opensuse.org/Submitting_Bug_Reports
>

Just to add to the confusion I’ve just rebooted the machine and this time I
DIDN’T hit ESC to watch the boot process in detail, I just left it in the
graphics screen and now I’ve got my full size screen back!

As an old-fashioned geek I always preferred to watch the text messages
scroll past - I may not understand some of them but I have caught some
system config problems before now. So is watching the text go by the cause?
Do I want to keep rebooting over and over using different procedures? Would
I rather have a life?

It’s Ok now so I’ll just live with it - I just wish I knew why it happened!

Alan

Fudokai wrote:
> I just wish I knew why it happened!

me too…

btw, i do not have to push Esc to see what Gawd intended mankind to
see (the beautiful scroll of stuff happening)!!

and you can too just, open YaST > System > Bootloader

highlight the line used to boot openSUSE (not the fail safe), click
edit and CAREFULLY add


splash=0

on the line labeled “Optional Kernel Command Line Parameter”…

and click on “Ok”…done, next time you boot you will see it as it
should be…


palladium

On 11.2, there is already a splash=silent, would that conflict with that second splash=0 as you suggest? Or should I replace the splash=silent with splash=0?

Replace.

You could also try adding it to the additional parameters line in the grub start screen (before it times out, of course). This won’t change your menu.lst grub file (that’s what the yast module does), so it’s good for testing different boot parameters, as they will be applied to the current boot only.

Note: AFAIK splash=silent is what brings up the nice green graphical progress screen during boot. No splash brings up the “normal” behavior, i.e., the console.

brunomcl wrote:
> Replace.

+1

replace silent with 0


palladium