From owner-freebsd-hackers@freebsd.org Tue Jan 14 02:40:07 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD6E81F6F03 for ; Tue, 14 Jan 2020 02:40:07 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47xZS72lctz4V68 for ; Tue, 14 Jan 2020 02:40:07 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 8B2A2654 for ; Mon, 13 Jan 2020 21:40:05 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Mon, 13 Jan 2020 21:40:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=QGVU4ikJmgNX8WgOabS88IDRUxnj7bEDFN0Av8vNM 3k=; b=NFMZnmSZ70vyikn/F/p3MDq/rLAadiiJXmjBEzCRuhnDhH/Dpi5TGdwLQ dQTCzNNjBnZMZOdBNrzdglLliaV5Y1PoO6ACW4YzC22lyoqnyB4Jdm/Z+u3Xluxo P2U3dtZNyJxQqnQTnxkG3Hs5LUM7u7COujQDsafyUIledBC8ri8G80Q30cJkkwVY r7kHboV4GmpF1BOdaxivJPu54Y5oaUjJvBZW4BhuTjznnNkNENtvlA2S2rwGJbVM j4gpn90IWRtxQohqV7r9fHQ1Kuy8WIjeV7fRM7yvYM6MsSjIegucZ3Y2Cc9G1UMk ZQdH0332SIuFElyLRvP3ued1zO4cw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdejuddggeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedflfho shhhucfrrggvthiivghlfdcuoehjphgrvghtiigvlheshfhrvggvuefuffdrohhrgheqne cuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecurfgrrhgrmhepmhgrihhlfhhrohhm pehjphgrvghtiigvlheshfhrvggvuefuffdrohhrghenucevlhhushhtvghrufhiiigvpe dt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id CB295E00A2; Mon, 13 Jan 2020 21:40:04 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-754-g09d1619-fmstable-20200113v1 Mime-Version: 1.0 Message-Id: <55931f9f-73ca-41e5-a069-a18b32333430@www.fastmail.com> In-Reply-To: <0E861DC2-D1C3-4E17-A8C1-FD68C60147CA@freebsd.org> References: <0E861DC2-D1C3-4E17-A8C1-FD68C60147CA@freebsd.org> Date: Mon, 13 Jan 2020 20:39:43 -0600 From: "Josh Paetzel" To: "Xin Li via freebsd-hackers" Subject: Re: Console redirection for UEFI and IPMI-SOL Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47xZS72lctz4V68 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.98 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.98)[-0.984,0]; NEURAL_HAM_LONG(-0.99)[-0.994,0]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2020 02:40:07 -0000 On Fri, Jan 10, 2020, at 12:30 PM, Ravi Pokala wrote: > Hi folks, >=20 > I'm trying to bring 12.1-RELEASE up on a new hardware platform. The=20= > system will boot from an NVMe device, so it must boot using UEFI. >=20 > I've installed UEFI-based systems several times before, without any=20= > trouble. But for those previous platforms, the VGA console was all I=20= > needed; on this new platform, I need a serial console, using IPMI=20 > Serial-Over-LAN. I've set up SOL plenty of times before too... but onl= y=20 > on BIOS-based systems. It's the combination of UEFI+SOL which seems to= =20 > be causing me problems. >=20 > When I boot, I see output from loader.efi on both the VGA and the SOL=20= > consoles; they report the console type as "efi". When the kernel start= s=20 > running, I only see the output on the VGA console, not the SOL console= .=20 > My ideal configuration -- which is what I have on my BIOS-based system= s=20 > -- is: >=20 > - bootloader on both VGA console and SOL console > - kernel output on both VGA console and SOL console > - single-user prompt on whichever I selected as the primary (first in=20= > the 'console' list in /boot/loader.conf) > - login prompts on both consoles after `getty' has started. >=20 > =EF=BB=BFOn the aforementioned previous BIOS+SOL systems, /boot/loader= .conf=20 > contains the following: >=20 > | boot_serial=3D"YES" > | console=3D"comconsole vidconsole" > | kern.vty=3D"vt" # 10.x; different on 12.1? > | hw.vga.textmode=3D"1" >=20 > When I used those same settings on the UEFI systems, loader.efi=20 > complains about "vidconsole" not being valid, and I got no more output= =20 > anywhere. Changing that to "efi" let me get the kernel messages on the= =20 > VGA console, but still nothing on the SOL. >=20 > I'm happy to provide more info about the platform; just tell me what=20= > commands to run to gather it. >=20 > Thanks, >=20 > Ravi (rpokala@) >=20 >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.= org" > So in EFI land you're going to want console=3D"comconsole efi" You'll probably also want boot_multicons=3D"YES" Almost certainly the loader needs to be told over what serial port the I= PMI serial port really is. It's probably very helpfully sending all the = output to a header on the motherboard somewhere. dmesg is your friend there. comconsole_port and possibly comconsole_speed may need to be set. ipmitool sol info 1 to see what the volatile and non-volatile bit rates= are set to. --=20 Thanks, Josh Paetzel