From owner-freebsd-mobile@FreeBSD.ORG Thu Jul 15 14:10:10 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 164CB16A4D0; Thu, 15 Jul 2004 14:10:10 +0000 (GMT) Received: from leviathan.inethouston.com (leviathan.inethouston.com [209.198.171.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDE2143D31; Thu, 15 Jul 2004 14:10:05 +0000 (GMT) (envelope-from dwcjr@inethouston.net) Received: from [192.168.2.16] (unknown [192.168.2.16]) by leviathan.inethouston.com (Postfix) with ESMTP id 6E84B2C9009; Thu, 15 Jul 2004 09:10:00 -0500 (CDT) Message-ID: <40F68FEC.4080507@inethouston.net> Date: Thu, 15 Jul 2004 09:08:44 -0500 From: "David W. Chapman Jr." User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20040714132120.GA69937@minubian.inethouston.net> <200407141450.11977.jhb@FreeBSD.org> <40F58207.3010903@inethouston.net> <200407141604.26452.jhb@FreeBSD.org> In-Reply-To: <200407141604.26452.jhb@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------040903010606050303030400" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: current@FreeBSD.org cc: mobile@FreeBSD.org cc: freebsd-mobile@FreeBSD.org Subject: Re: 5.2-CURRENT still not working on my mitac 8080 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2004 14:10:10 -0000 This is a multi-part message in MIME format. --------------040903010606050303030400 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit John Baldwin wrote: >On Wednesday 14 July 2004 02:57 pm, David W. Chapman Jr. wrote: > > >>John Baldwin wrote: >> >> >>>On Wednesday 14 July 2004 09:25 am, David W. Chapman Jr. wrote: >>> >>> >>>>When I boot in safe mode here is the console output >>>> >>>>pir0: on motherboard >>>>$PIR: BIOS IRQ 10 for 1.4.INTA does not match link 0x61 irq 5 >>>>pci0: on pcib0 >>>> >>>> >>>Look for a BIOS upgrade. It sounds like your BIOS has badly busted >>>interrupt routing. >>> >>> >>I think I can get one, I don't have a problem running 4.X though, would >>that be consistent with the problem you described? >> >> > >4.x isn't smart enough to ask the BIOS how to route interrupts from the BIOS >tables, it just assumes that the way it booted is ok. > > > Unfortunately I have just upgraded to the latest BIOS revision and the problem still exists. I guess I'm dead in the water as far as 5.x goes? --------------040903010606050303030400--