https://bugzilla.novell.com/show_bug.cgi?id=259577 Summary: /etc/rc.d/kbd corrupts video when specified vga= mode is native 132 column Product: openSUSE 10.3 Version: Alpha 2plus Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@ij.net QAContact: qa@suse.de http://bugzilla.kernel.org/show_bug.cgi?id=7513 asserts that "userspace" is the problem and not the kernel, which is why I'm filing this here. Also as noted in 7513, this is far from new behavior, and is not unique to any SUSE version. When a 132 column graphics card native vga mode is specified to the kernel, either directly or with ask, console video initializes at the specified mode. During init, the number of lines output is changed from the correct number to some lesser number, or to the correct number but with insufficient scanlines allotted to each line for full character height to be displayed. For example, I just installed factory fresh via http, with graphical YaST, and on first boot typed in vga=ask, following which I entered scan, and then selected mode 030A, which is 132X43 on mga. Video properly initialized in 132x43, but as init proceded a shift was made to ~24 lines. YaST then failed to come up in graphical mode. In text mode, YaST assumed the correct number of lines, 43, with the result that focus, descriptive text, and entry fields were out of sync, unable to fit on the supposed 43 line screen that was only 24 lines long. This makes using YaST extremely difficult, guessing via some familiarity when the focus is at some appropriate point and what action, enter or tab or arrow or other, should follow to achieve desired result. This unwieldy YaST behavior is similar to that of other ncurses utilities, like SAX, when run on a fully installed and configured system. As noted in 7513 kernel bug, many other graphics cards than mga exhibit similarly corrupt behavior when native 132 column modes are specified to the kernel. Doing as suggested in that bug's comment 7 (removing execute from /etc/rc.d/kbd) avoids the problem. Matrox, among others, supports no better than 800x600 (e.g. 0x314) framebuffer video, which is the reason to want native mode support of more console lines and rows than 100x37 and why this needs to be fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.