From owner-freebsd-bugs Mon Apr 30 17:20: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1E63C37B422 for ; Mon, 30 Apr 2001 17:20:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f410K3797136; Mon, 30 Apr 2001 17:20:03 -0700 (PDT) (envelope-from gnats) Date: Mon, 30 Apr 2001 17:20:03 -0700 (PDT) Message-Id: <200105010020.f410K3797136@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tony Finch Subject: Re: kern/26920: PCI autoconfiguration of USB, dc ether, and pccard broken on SHARP PC-AR10 Reply-To: Tony Finch Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/26920; it has been noted by GNATS. From: Tony Finch To: n_hibma@FreeBSD.ORG Cc: freebsd-gnats-submit@FreeBSD.ORG, Tony Finch Subject: Re: kern/26920: PCI autoconfiguration of USB, dc ether, and pccard broken on SHARP PC-AR10 Date: Tue, 1 May 2001 00:33:26 +0000 n_hibma@FreeBSD.ORG wrote: >With all those strange values in your PCI configuration check that there >is no BIOS setting that says > > PnP OS: yes. > >It should be no. There's no option like that. I wouldn't be surprised if the machine is so new that it assumes "yes". However, I have had fairly good luck in the past with the PNPBIOS kernel option, and when it hasn't worked it has been because I haven't specified device configurations in the kernel configuration file in enough detail, or because the BIOS's PNP config info has been in the wrong order for the console to work properly. Neither of those is the problem here. The problem as I see it seems to be independent of the PNP issue, since it is a PCI problem and AFAIK PNP problems are tied to ISA devices. I have the same problems with GENERIC, but obviously the diagnostics are less helpful. Is there a magic pciconf command I can use to give more useful information? pciconf -l seems unenlightening -- it has the same information as the dmesg I quoted. >Also, disable 'Legacy device support on USB' or 'USB keyboard support' >if there is any. The fact that it can't start the USB controller means >that somehow the thing doesn't respond to the RUN command. Yes, that's off. It looks to me as if the problem is more low level than that. I'm back in England now, so if you have time to look at the machine I can bring it round or we can have a pub meet or something... Thanks for the reply. Tony. -- f.a.n.finch DOVER WIGHT PORTLAND PLYMOUTH: NORTHEAST 5 TO 7, INCREASING GALE 8 FOR A TIME. OCCASIONAL RAIN. GOOD BECOMING MODERATE OR POOR. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message