From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 1 09:58:09 2005 Return-Path: X-Original-To: hardware@FreeBSD.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D883916A41F; Thu, 1 Dec 2005 09:58:09 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FF7E43D5D; Thu, 1 Dec 2005 09:58:08 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jB19w78n023522; Thu, 1 Dec 2005 20:58:07 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jB19w5VV023503; Thu, 1 Dec 2005 20:58:06 +1100 Date: Thu, 1 Dec 2005 20:58:04 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Joe Rhett In-Reply-To: <20051130181757.GA29686@svcolo.com> Message-ID: <20051201204625.W41849@delplex.bde.org> References: <20051117050336.GB67653@svcolo.com> <200511171030.36633.jhb@freebsd.org> <20051117220358.GA65127@svcolo.com> <20051130181757.GA29686@svcolo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hardware@FreeBSD.org, John Baldwin , freebsd-hardware@FreeBSD.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 09:58:10 -0000 On Wed, 30 Nov 2005, Joe Rhett wrote: >>> On Thursday 17 November 2005 05:03 pm, Joe Rhett wrote: >>>> We can't. Serial A is a 9pin serial port, and Serial B is the rj45 console >>>> port. This is how the motherboard is built. We need Serial B to be the >>>> console. >>>> >>>> /boot/device.hints clearly indicates that 3f8 should map to sio1. Why >>>> isn't it using these hints? > >> On Thu, 17 Nov 2005, John Baldwin wrote: >>> What if you disable ACPI? I think the ACPI bus doesn't use the port >>> information to honor "wiring" requests but just reads the flags. >> >> On Thu, 17 Nov 2005, John Baldwin wrote: >> ACPI me harder :-). >> >> If it doesn't match the port info then it probably gets the flags wrong >> too, by applying the flags intended for the port at 0x3f8 (intended unit 0) >> to the port that ends up as unit 0 (0x2f8 here). > > Pardon me, what is "it"? The BIOS or the apci module? ACPI in FreeBSD. It sees the ACPI configuration and can/should see the static configuration. >> Console initialization uses the flags to decide the console port(s), >> so swapped flags probably give swapped console ports. > > I don't know if this is related, but ACPI also seems to find devices which > are disabled (ie parallel parts, etc) and then complains because it can't > allocate resources for them. It's not clear that disabling in the BIOS should disable for all OSes. > It sounds like ACPI isn't reading the BIOS data correctly at all. What > debug options can I enable to get more information? Don't know. I avoid ACPI if possible :-). I suspect that FreeBSD can see ACPI tables but not all BIOS tables, so any soft disabling in the BIOS gets lost. Bruce