I had that exact problem on Tuesday. Ended up taking my volume back to VM, dedicating the OSAs, and fixing my config there.
Keep linux under VM where god intended it to be is my advice ;) If you figure it out, please share. In my experience, the sysascii prompt pops up way after tons of messages fly by. -----Original Message----- From: Linux on 390 Port <[email protected]> On Behalf Of Alan Altmark Sent: Thursday, June 10, 2021 1:43 PM To: [email protected] Subject: [LINUX-390] integrated console overflow from the Linux installer A colleague is installing RHEL 8.4 in an LPAR via ftp server. The system loads, but early in the installer boot process there's a network error that he can't scroll back to look at because the Operating System Messages console "rolls off" after about 475-500 messages. Can he update the generic.prm file to reference the integrated ASCII console instead? And will that give him better console management to let him see early boot errors? Regards, Alan Alan Altmark Senior Managing z/VM Consultant IBM Lab Services Phone: 607-429-3323 | Mobile: 607-321-7556 E-mail: [email protected] Endicott, NY USA ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit https://urldefense.com/v3/__http://www2.marist.edu/htbin/wlvindex?LINUX-390__;!!F9svGWnIaVPGSwU!4mNyTra0X0P0Tn2Ks6fVxC97Li7Y54FqxXinfr3SOl1t3gYGydUPql2i2t0PEAq8E7xuG9g$ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
