From owner-freebsd-stable@FreeBSD.ORG Sat Apr 21 08:07:46 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 4478916A400 for ; Sat, 21 Apr 2007 08:07:46 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id EF0B213C4B0 for ; Sat, 21 Apr 2007 08:07:45 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id AB5791B10F1B; Sat, 21 Apr 2007 10:07:44 +0200 (CEST) Received: from [192.168.3.125] (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id A84A11B10ED2; Sat, 21 Apr 2007 10:07:44 +0200 (CEST) Message-ID: <4629C650.2030607@sun-fish.com> Date: Sat, 21 Apr 2007 11:07:44 +0300 From: Stefan Lambrev User-Agent: Thunderbird 1.5.0.10 (X11/20070326) MIME-Version: 1.0 To: Marcel Moolenaar References: <4628D63A.3050909@sun-fish.com> <20070420152329.GA16702@icarus.home.lan> <049954BE-364B-4897-87C3-342D0A824C00@mac.com> In-Reply-To: <049954BE-364B-4897-87C3-342D0A824C00@mac.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: Jeremy Chadwick , freebsd-stable@FreeBSD.org 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: Sat, 21 Apr 2007 08:07:46 -0000 Hello, 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 b= e >> 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=20 > implemented: > to describe legacy hardware. > >> 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. This did the trick: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 ports are swapped but this is probably because I swap them in bios, but=20 this is ok. Serial is working and now I can start working on the main problem :) So it's not acpi problem, but instead problem with sio? Thank you very much for your help! > > =04Thanks, > > --Marcel Moolenaar > xcllnt@mac.com > > --=20 Best Wishes, Stefan Lambrev ICQ# 24134177