From owner-freebsd-questions@freebsd.org Tue Jul 21 18:34:04 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 126D99A7FD7 for ; Tue, 21 Jul 2015 18:34:04 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from outbound.ifdnrg.com (outbound.ifdnrg.com [193.200.98.38]) by mx1.freebsd.org (Postfix) with ESMTP id 96CDC109F for ; Tue, 21 Jul 2015 18:34:02 +0000 (UTC) (envelope-from paul@ifdnrg.com) Received: from [192.168.100.230] (cpc72297-sgyl28-2-0-cust55.18-2.cable.virginm.net [81.98.112.56]) (authenticated bits=0) by outbound.ifdnrg.com (8.15.2/8.14.9) with ESMTPSA id t6LIDZt8002184 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 21 Jul 2015 18:13:37 GMT (envelope-from paul@ifdnrg.com) X-Authentication-Warning: outbound.ifdnrg.com: Host cpc72297-sgyl28-2-0-cust55.18-2.cable.virginm.net [81.98.112.56] claimed to be [192.168.100.230] Subject: Re: r220's with serial To: freebsd-questions@freebsd.org References: <55773D18.3060804@ifdnrg.com> From: Paul Macdonald Message-ID: <55AE8BD1.2020707@ifdnrg.com> Date: Tue, 21 Jul 2015 19:13:37 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <55773D18.3060804@ifdnrg.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 18:34:04 -0000 On 09/06/2015 20:23, Paul Macdonald wrote: > > has anyone managed to get serial console access working under dell > r220's. > This was due to an ACPI bug in r220's Marcel Moolenaar provided me with a fix which is: -BIOS- Serial Communication Serial Port Address External Serial Connector -FreeBSD- adding the following line to /boot/loader.conf: hw.uart.console="io:0x2f8,br:57600" ..... From the looks of it, you have a BIOS bug. In particular a bug in the ACPI AML (you can dump the ACPI AML with acpidump -d). If I understand it correctly then the first 2 serial devices (UAR1 and UAR2) have the same H/W registers. What this boils down to is that the kernel only works with 1 serial port (UAR1), which ends up having the H/W configuration of the second serial port (UAR2). With the BIOS redirecting to COM1 (which is H/W address 0x3f8) and serial device 1 assigned to COM1 *and* serial device assigned to the serial port on the chassis, the kernel had no chance to present a login prompt. I worked around the problem by reconfiguring the BIOS so that COM2 (which is H/W address 0x2f8) is assigned to serial port 1 and the BIOS redirecting to COM2. What this does is have COM2 connected to the serial port on the chassis. So, even though I suspect that the kernel thinks it’s talking to the first serial port, it’s actually talking to the second serial port (due to the ACPI/BIOS bus). > > -- ------------------------- Paul Macdonald IFDNRG Ltd Web and video hosting ------------------------- t: 0131 5548070 m: 07970339546 e: paul@ifdnrg.com w: http://www.ifdnrg.com ------------------------- IFDNRG 40 Maritime Street Edinburgh EH6 6SA ---------------------------------------------------- High Specification Dedicated Servers from £100.00pm ----------------------------------------------------