Red Hat Bugzilla – Bug 248028
serial console capabilities are not detected, just forced to vt100-nev
Last modified: 2008-02-14 16:08:11 EST
Description of problem: serial console capabilities are not detected, just forced to vt100-nev here are ways to query console server about capabilities - "ESC CSI c", in response - nothing or "\033[?1;2c" means vt100, "\033[?62;1;2c" means vt220 (colors and goodies). please use that in init.c (anaconda) instead of hardcoding it for serial consoles, and (bah!) Xen consoles. How reproducible: use xterm, or anything else - that is proper console termial with anaconda over serial console or xen serial. You get black/white output, no F keys working, etc, etc. Expected results: expected to work with proper console terminals. I don't really know how to patch it, so that you guys won't reject patch. My best shot would be changing setupTerminal, so before setting TERM=vt100-nav - it also sends "ESC CSI c" and checks the response.
Changing product to Fedora devel since this isn't likely to make it into a RHEL update release...
Think that adding an argument is the way to go here: term=value. It will fall back to vt100-nav (thats what it was doing).
Created attachment 294828 [details] patch for inclusion of term=value argument.
Before commiting: What was the problem with using the utf8 command line argument? That activates vt110.
Tested on installations with serial cables and on xen installations and the vt110, vt220 and vt520 terminal present the same behavior (as far as I can tell). If you feel compelled to getting this into rawhide please give a test case in which vt220 or vt520 has advantages over vt110. Clossing....