From owner-freebsd-current@FreeBSD.ORG Sat May 31 17:26:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4243537B401 for ; Sat, 31 May 2003 17:26:52 -0700 (PDT) Received: from ip68-14-60-78.no.no.cox.net (ip68-14-60-78.no.no.cox.net [68.14.60.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 092E943F85 for ; Sat, 31 May 2003 17:26:51 -0700 (PDT) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: from ip68-14-60-78.no.no.cox.net (conrads@localhost [127.0.0.1]) h510Qkl3006101; Sat, 31 May 2003 19:26:46 -0500 (CDT) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: (from conrads@localhost)h510QiSD006100; Sat, 31 May 2003 19:26:45 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 31 May 2003 19:26:44 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: Conrad Sabatier To: Julian Elischer cc: FreeBSD current users Subject: viapm attach failure (was Re: loader vs PCI) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 00:26:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20-May-2003 Julian Elischer wrote: > > Is there any capability in the loader to do such things as get/set a PCI > config space register? > > Looking at the man page I'd say not, but there is mention of > some PNP capacity (though not currently working). > > > Reason.. > > ASUS disable the SMBus on their new mother boards and have no BIOS entry > to enable it, but it can be enabled from the PCI config regs. Without > it you can not easily read the voltages, temperatures and Fan speeds. > > You can use pciconf to enable it but by then it's too late > for the ichsmb(4) driver to find it. The only other answer is to > enable it, and then kldload the ichsmb module, but the best answer > would be to enable it from the loader so that it shows up on the PCI > bus during normal boot. > > (ASUS need to get a clue on this.. a BIOS option would be real nice..) I have a related problem. I'm trying to get the viapm (viapropm0) device to attach properly at boot, but to no avail. The device is recognized, but I always get the following: smbios0: at iomem 0xf7a20-0xf7a3e on motherboard smbios0: Version: 2.03, Revision: 1.08 found-> vendor=0x1106, dev=0x3057, revid=0x10 bus=0, slot=7, func=4 class=06-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 4, range 32, base 00001080, size 6, enabled viapropm0: SMBus I/O base at 0x4000 viapropm0: port 0x4000-0x400f at device 7.4 on pci0 viapropm0: failed to enable port mapping! viapropm0: could not allocate bus space device_probe_and_attach: viapropm0 attach returned 6 I have all the requisite devices configured into the kernel. I'm not sure what hint, if any, might help resolve this issue. Ideas? TIA - -- Conrad Sabatier - "In Unix veritas" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+2Ug5p1KR3mGnrrgRAiYGAKC+Pfw+xAMpmC1zs1IET8YDYCgV+QCgr2b/ tOCc4pN5DSmMqVxHUWjzZWM= =DNDt -----END PGP SIGNATURE-----