From owner-freebsd-stable@FreeBSD.ORG Fri Apr 20 18:08:07 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA39916A401 for ; Fri, 20 Apr 2007 18:08:07 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.200.83]) by mx1.freebsd.org (Postfix) with ESMTP id 921F313C44C for ; Fri, 20 Apr 2007 18:08:07 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-71-198-0-135.hsd1.ca.comcast.net[71.198.0.135]) by comcast.net (sccrmhc13) with ESMTP id <20070420180806013003err4e>; Fri, 20 Apr 2007 18:08:06 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E38831FA03D; Fri, 20 Apr 2007 11:08:05 -0700 (PDT) Date: Fri, 20 Apr 2007 11:08:05 -0700 From: Jeremy Chadwick To: Marcel Moolenaar Message-ID: <20070420180805.GA18977@icarus.home.lan> Mail-Followup-To: Marcel Moolenaar , Stefan Lambrev , freebsd-stable@FreeBSD.org References: <4628D63A.3050909@sun-fish.com> <20070420152329.GA16702@icarus.home.lan> <049954BE-364B-4897-87C3-342D0A824C00@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <049954BE-364B-4897-87C3-342D0A824C00@mac.com> User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-stable@FreeBSD.org, Stefan Lambrev Subject: Re: sio0: port may not be enabled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2007 18:08:07 -0000 On Fri, Apr 20, 2007 at 09:45:43AM -0700, Marcel Moolenaar wrote: > > On Apr 20, 2007, at 8:23 AM, Jeremy Chadwick wrote: > > >Look closely at the dmesg line, note what device sio0 is claiming > >to be > >associated with (acpi0, not isa0): > > > >>sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags > >>0x10 on acpi0 > > > >This is one of the drawbacks to using ACPI. > > This is not a drawback. It's partly why ACPI was designed and > implemented: > to describe legacy hardware. It's a drawback in the sense that if the technology is newer than what FreeBSD can handle/is made for, then administrators are forced to look at alternatives (other hardware or operating systems). > >Some systems apparently tie the serial port to ACPI functionality in a > >different way. For example, I have a couple boxes which have sio0 > >attached to acpi0 that work fine. In some other cases, I have ones > >which result in a non-working serial port unless I disable ACPI (thus > >sio0 shows up as being attached to isa0). > > Could you try uart(4) instead. It seems quite excessive to have to > disable ACPI just to get a serial port working. I'd like to know > if this is related to the sio(4) driver or something else. Can you provide some directions explaining how to configure the kernel (other than "device uart") and loader.conf or device.hints for appropriate variables? I'll be more than happy to try this out. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |