From nobody Sat Nov 02 00:01:08 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XgHvK1wPVz5cjRc for ; Sat, 02 Nov 2024 00:01:17 +0000 (UTC) (envelope-from rwp@proulx.com) Received: from havoc.proulx.com (havoc.proulx.com [198.99.81.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XgHvJ3lslz4rvS for ; Sat, 2 Nov 2024 00:01:16 +0000 (UTC) (envelope-from rwp@proulx.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=proulx.com header.s=dkim2048 header.b=BjCVzOC3; spf=pass (mx1.freebsd.org: domain of rwp@proulx.com designates 198.99.81.74 as permitted sender) smtp.mailfrom=rwp@proulx.com; dmarc=pass (policy=none) header.from=proulx.com Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTPS id D3052632 for ; Fri, 1 Nov 2024 18:01:08 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1730505668; bh=y9OnH7JSzou+28vtjOw2lHomQrBBbMU1WhHEv1wYhJI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=BjCVzOC3Vj7p3egMZu8N9GZK3o9BOFBQVuCc9xkAylmEK3avO0bpJ3bOA/DR5VG7G nQ9gsOApyIlODkGOt5xicvryQojBphVeNhnxS17IswvZIfCy9EzAt/Y9BD0tHT9Om1 YwA5ZU107z8iREPmeHzGaxis91XvN+RZjtKdX9AQtV/bv7wtgdKevJynBCqz7I2K6B sIRSaf3U13M94FZ/8J6/PnPGhsUdRTtoBeKGLySWBQkM76ZyiBG/HwTl+hyeySkrKr nQAJITm9DfZZro5vYKDA/mZ2NjIwwbFItCK+OP+zplUEA35iGZfWF5/SO2XYfdm04/ gOF400SiQ7yfw== Received: from madness.proulx.com (madness.proulx.com [192.168.230.122]) by joseki.proulx.com (Postfix) with ESMTP id A50877A068 for ; Fri, 1 Nov 2024 18:01:08 -0600 (MDT) Received: by madness.proulx.com (Postfix, from userid 1000) id A02A811037; Fri, 01 Nov 2024 18:01:08 -0600 (MDT) Date: Fri, 1 Nov 2024 18:01:08 -0600 From: Bob Proulx To: freebsd-questions@freebsd.org Subject: Re: Recover serial console after upgrade Message-ID: <20241101175138735359595@bob.proulx.com> Mail-Followup-To: freebsd-questions@freebsd.org References: <1a2a9184-51de-44c4-af7e-07c9da7b12dd@nethead.se> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1a2a9184-51de-44c4-af7e-07c9da7b12dd@nethead.se> X-Spamd-Result: default: False [-3.70 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[proulx.com,none]; FORGED_SENDER(0.30)[bob@proulx.com,rwp@proulx.com]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[proulx.com:s=dkim2048]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:397142, ipnet:198.99.80.0/22, country:US]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; FROM_NEQ_ENVFROM(0.00)[bob@proulx.com,rwp@proulx.com]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[proulx.com:+] X-Rspamd-Queue-Id: 4XgHvJ3lslz4rvS X-Spamd-Bar: --- Per olof Ljungmark wrote: > I am in the process of upgrading an old server, a Proliant DL360 G7. The > virtual serial port at uart1 worked with 13.2, but after 13.4 it only works > until some point in the boot process, then its gone. Do you have Boot Environments? If so then you could boot the previously working one and then compare between the two and get the newer one working. I had serial console working on my 13.4R systems (Supermicros) before upgrading them to 14 RELEASE. Seems like it should work for you. > I just assume this is a change with acpi? but unfortunately I have no idea > how to get the console back, sysctl only reports uart0 and so does dmesg. That almost sounds like an upgrade to the boot firmware (can't say BIOS anymore with UEFI systems I guess) made a change there that disabled uart1. Is the onboard iLO working for you? Can you use it to look at the console to reconfigure the firmware? If so then check that serial console on that port is enabled. If you don't have iLO then I guess it would be attaching a physical display and keyboard to debug this. But I would be looking very closely at the firmware configuration. > loader.conf: > console="comconsole" If you add vidconsole then you get both working and can see the screen output on the video console too. console="comconsole,vidconsole" I'll just note that at the beastie boot screen you can select "Escape to the loader prompt" and then type in custom settings for that boot. It would be possible to type this in there. Which is how I have had to find which port is active, by trying each of them in turn until I found the connected one. set comconsole_port=...someotherportaddress... set console="comconsole,vidconsole" boot > comconsole_speed=115200 > comconsole_port="0x2F8" I have run into systems where the system console is on this port or that port. I suspect that some update has changed the system console port to a different com port. Bob