http://bugzilla.opensuse.org/show_bug.cgi?id=971885 http://bugzilla.opensuse.org/show_bug.cgi?id=971885#c8 --- Comment #8 from Felix Miata <mrmazda@earthlink.net> --- Created attachment 670084 --> http://bugzilla.opensuse.org/attachment.cgi?id=670084&action=edit /etc/X11/xinit/xinitrc.d/setup Attachment is in raw condition. Before starting X, an appropriate xrandr line is uncommented, or not, as when /etc/X11/xorg.con* is used for global X configuration instead of xrandr. /etc/X11/xinit/xinitrc.d/setup is actually a symlink to the real file on a filesystem shared by all Linux installations on each of my many multiboot systems. ***** (In reply to Egbert Eich from comment #3)
(In reply to Felix Miata from comment #2)
Host t2240, Intel gfx, TW32 20160203#1, vga=791 video=1440x900@60 on cmdline, KDE3: (simply) startx: 1680x1050@108 aka success from KDM3: 1680x1050@108 aka success
To set the console mode, you need to specify the output together with the 'video=' command.
We seem to be from different planets on this (and possibly one or two other elements of the problem reported). Left to choose on their own, or use some defaults from whatever source, display outputs here are invariably uncomfortable, usually making everything too small, occasionally too big (e.g. BIOS 80x25 text mode on any but the tiniest of displays). Almost immediately on first use of Linux many moons ago, I discovered this discomfort WRT vttys, and only WRT vttys, was readily handled via the bootloader's kernel cmdline vga= option. Prior to KMS, it was rare to boot here without vga=<something> on kernel cmdline. Most often it was any of vga=0x314 or vga=0x317 or vga=791. Necessarily, vga= became inadequate for dealing with tiny vtty text with the advent of KMS, but I routinely continue to include it for its impact in the few seconds prior to KMS switching the console to the video= mode provided on the bootloader's kernel cmdline. With KMS, video=<horizontal-resolution>x<vertical-resolution> took over most of the duty from vga=. I habitually append @<refresh-rate> as insurance against the odd occasion when some happenstance causes an unsupported refresh that puts the display to sleep. Except in any test when the possibility exists that video= on cmdline may adversely impact the test, vga=<something> and video=<something> are virtually always present here, normally absent only when removed on the fly at boot time. Grub stanzas here number in the thousands. When using a 22" 1680x1050 LCD, my bootloader kernel cmdlines customarily include vga=791 and video=1440x900@60 Typically the latter is preceded by 1280x720@60 and/or 1024x768@60, and I backspace away when necessary at boot time to leave a more desired one last. Plymouth in openSUSE installations here does not exist, tabooed at installation time. Grub2, for several reasons, is also tabooed. For the entire life of KMS in openSUSE, I cannot remember video= on Grub's kernel cmdline ever being insufficient to produce a desired framebuffer (aka console) mode for the balance of init, and surviving on all 6 vttys. So, what is it you were telling me? (more follow-up to prior comments to come...) -- You are receiving this mail because: You are on the CC list for the bug.