From owner-freebsd-questions@FreeBSD.ORG Wed Nov 2 10:01:31 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 990311065672 for ; Wed, 2 Nov 2011 10:01:31 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo202.cox.net (eastrmfepo202.cox.net [68.230.241.217]) by mx1.freebsd.org (Postfix) with ESMTP id 3C5F18FC1A for ; Wed, 2 Nov 2011 10:01:30 +0000 (UTC) Received: from eastrmimpo210.cox.net ([68.230.241.225]) by eastrmfepo202.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20111102100125.RZVK3788.eastrmfepo202.cox.net@eastrmimpo210.cox.net>; Wed, 2 Nov 2011 06:01:25 -0400 Received: from serene.no-ip.org ([98.164.86.236]) by eastrmimpo210.cox.net with bizsmtp id sA1Q1h00555wwzE02A1Qmu; Wed, 02 Nov 2011 06:01:25 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020203.4EB114F5.0029,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=vbhHURzOYu7sh/H2nQFtZsDvZuFIa++ww+VfbjuztNE= c=1 sm=1 a=gH2l33NO9zgA:10 a=r6cevgW6SK4A:10 a=G8Uczd0VNMoA:10 a=Fdkxr_5KmFUA:10 a=uAbGmPAyUfLL1M3oYAsfuA==:17 a=kviXuzpPAAAA:8 a=_RbA5VCFaaCI8SGRZ_0A:9 a=WMuhgDWOEbcL6OcpCW4A:7 a=pvA44qeTxYYA:10 a=4vB-4DCPJfMA:10 a=uAbGmPAyUfLL1M3oYAsfuA==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id pA2A1OiW075030; Wed, 2 Nov 2011 05:01:24 -0500 (CDT) (envelope-from conrads@cox.net) Date: Wed, 2 Nov 2011 05:01:19 -0500 From: "Conrad J. Sabatier" To: =?koi8-r?Q?=E1=CE=D4=CF=CE_=EB=CC=C5=D3=D3?= Message-ID: <20111102050119.4ff96620@cox.net> In-Reply-To: <416061320219879@web4.yandex.ru> References: <70871320146936@web106.yandex.ru> <20111101104226.1241f2a1@cox.net> <416061320219879@web4.yandex.ru> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Cc: freebsd-questions@freebsd.org Subject: Re: How to get /dev/smb* ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 10:01:31 -0000 On Wed, 02 Nov 2011 11:44:39 +0400 áÎÔÏÎ ëÌÅÓÓ wrote: > > > > mbmon is very old. šI've never gotten it to work on any machine I've > > every tried it on. > > > > Does your boot time output show anything smb-related at all, such as > > maybe "smbios0: at ..."? šIt's possible > > that your machine simply has no support for this. > > > > # dmesg -a |grep smb > > - returns nothing. I just noticed, looking back at your previous mail, that you don't seem to have a "device smbios" line in your kernel config. Try adding that and see if the smbios facility shows up at boot time. I don't really understand the inner workings of this particular feature. On my box, I so see an indication in the boot time messages: smbios0: at iomem 0xfcd20-0xfcd3e on motherboard smbios0: Version: 2.5 Although no "smbios0" device actually shows up under /dev. Perhaps some more knowledgeable individual might enlighten us as to what capabilities having this in your kernel config actually enables. Also, just looking at the (x)mbmon port, the COMMENT line in the Makefile states: A X motherboard monitor for LM78/79, W8378x, AS99127F, VT82C686 and ADM9240 So, this port appears to be useful only on a very specific range of motherboards. > Does it means that it is no way to read temperature sensors on > motherboard? > Well, it depends. :-) I'm not at all familiar with your particular processor/motherboard, so I can only offer some rather limited advice that may steer you in the right direction for further exploration. There are a number of devices you can enable in your kernel config that may provide some of what you're looking for. Here, on my amd64 box, for instance, "device amdtemp", along with "device cpuctl" and "device cpufreq" makes the following dev.cpu.* sysctls available, which are one way to (manually) monitor your system. As you can see below, this provides information on CPU temperature and frequency. # sysctl dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.P001 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.temperature: 47.0C dev.cpu.0.freq: 2200 dev.cpu.0.freq_levels: 2200/23500 1100/14280 dev.cpu.0.cx_supported: C1/0 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% last 1931us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.P002 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.temperature: 47.0C dev.cpu.1.cx_supported: C1/0 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% last 4658us dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=\_PR_.P003 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%parent: acpi0 dev.cpu.2.temperature: 47.0C dev.cpu.2.cx_supported: C1/0 dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_usage: 100.00% last 3551us dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=\_PR_.P004 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%parent: acpi0 dev.cpu.3.temperature: 47.0C dev.cpu.3.cx_supported: C1/0 dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_usage: 100.00% last 4943us I've never really delved that deeply into any hardware monitoring tools, to be honest. You're kind of getting into an area where I am admittedly no expert. :-) But I'd suggest looking very carefully at both /sys/conf/NOTES and /sys/$ARCH/conf/NOTES (as well as the GENERIC kernel config) for some possible clues. Refer to the man pages for any specific devices of potential interest to see exactly what they're about, and possibly ask some more questions here as you start to narrow down the items that my possibly be useful to you. Seriously, people here don't mind questions being asked, if they're even semi-intelligent ones. We're a friendly bunch, for the most part. :-) Perhaps someone may offer you some more useful information on how to monitor and/or control other aspects of your specific hardware configuration besides CPU temperature and frequency. Hope this helps in some small way. Good luck! :-) -- Conrad J. Sabatier conrads@cox.net