Using a serial console during the OS installation, shows corrupted characters. Under a RDP unattended install, we lay down a DOS partition on the server and copy over Linux files onto the harddrive. At the next reboot, loadlin is used to start the install, "loadlin vmlinuz ks=nfs:10.0.0.3:/usr/cpqrdp/ss.620/rh81/bl10.ks.cfg initrd=initrd.img text console=tty0 console=ttyS0, 115200n8". In watching the installation through the serial console as the primary console, corrupted characters occur, for example the rQm 232401 issue of waiting on user input for network device, appears on the screen barely readable as "etwork..." and cannot see ethernet choices. Since I know this issue, just pressing return, will continue with the installation, but the text and package installation status bar are not clear, but can tell something is installing/progressing. When I know that the installation is complete, I can shut down the serial console window and open another to come to the Linux prompt. The serial console is good after the installation reboot. This issue is for during the installation. This same command line is used with RH80 installs with no issues. The text mode installation appears as black/white text not blue/red color where this corrupted view for RH81 is in blue/red. Things I tried to correct this without success. * Thinking this is a emulation problem, added the ",vt100" to end of console=ttyS0,115200n8. Searched on web for advice on how to indicate vt100 emulation via the serial console argument but didn't find anything. * Thinking the kernel command line text isn't working (like we found with UL), put "text" in bl10e.ks.cfg kickstart file. * The only diff between RH80 and RH81 call is the version of loadlin (and obviously the vmlinuz and initrd.img that are RH81) -- rQm 232368, where I need to use the 1.6c version versus 1.6. Using loadlin 1.6 with RH80 hasn't been an issue for me. I did a RH80 install test using loadlin 1.6c and the serial console install was just fine, no corrupted characters. Removing the console=ttyS0,115200n8 from the command line, then the console view through a debug adapter connected on the front of the blade, shows the install with no issues. ---------- Action by: Bryan.Leopard Issue Registered ISSUE TRACKER 15384, opened as sev 2
Do you have a UTF-8 capable serial console attached? This seems like a dup of 83024.
Response: No we have a vt100 serial console. It is not UTF-8 capable. We have attempted to change the term type to vt100 trying the TERM=vt100 parameter in the loadlin vmlinuz kernel command line. This did not work. Either the kernel needs to default to vt100 for *serial console* when it is the primary console OR we need a way to indicate on the kernel command line that we need vt100 terminal type. Attached is an example screen shot showing the corrupted characters using hyperterminal. File uploaded: hyperterm.jpg
Created attachment 90072 [details] hyperterm.jpg (scren capture) Screen Capture
*** This bug has been marked as a duplicate of 83024 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.