From owner-freebsd-questions@FreeBSD.ORG Thu Nov 3 18:50:05 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 33FAD1065705 for ; Thu, 3 Nov 2011 18:50:05 +0000 (UTC) (envelope-from rc5hack@yandex.ru) Received: from forward2.mail.yandex.net (forward2.mail.yandex.net [IPv6:2a02:6b8:0:602::2]) by mx1.freebsd.org (Postfix) with ESMTP id BE6428FC0C for ; Thu, 3 Nov 2011 18:50:04 +0000 (UTC) Received: from web62.yandex.ru (web62.yandex.ru [77.88.46.53]) by forward2.mail.yandex.net (Yandex) with ESMTP id EF43412A4791; Thu, 3 Nov 2011 22:50:03 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1320346204; bh=Im5PLVxEj9nIUlmTl6iWfun6J/HsijMWA1dbe+AxMmU=; h=From:To:Subject:MIME-Version:Message-Id:Date: Content-Transfer-Encoding:Content-Type; b=LeOf3dDvHVfu5KiUP2CGEleX+VYvcpMWTntr2GqEzcOGNxb6Ytjh2ZlMrhWj6qyv7 qWmV2uA6SIUFO4Yqt5IThs7wda6mO9sBVstWaTfc8nyEP/MMUPGZK5hawZ6wnULu8z idtYXio5htlytOajlUeZWslCwJapdi/WSg3Fxoos= Received: from localhost (localhost.localdomain [127.0.0.1]) by web62.yandex.ru (Yandex) with ESMTP id CB6031C4009B; Thu, 3 Nov 2011 22:50:03 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1320346203; bh=Im5PLVxEj9nIUlmTl6iWfun6J/HsijMWA1dbe+AxMmU=; h=From:To:Subject:MIME-Version:Message-Id:Date: Content-Transfer-Encoding:Content-Type; b=q3sTthn1AOx/yzudWFQ859GJmSc6MrzNxZAsdbKTV5rOzPWTGZ5cphO7fTGVDJRXu aLKA4RPaeZmQEMO7cjRe7BgIlgAJ60eGnYUx++yyEj6zlZ8doze3nNlLkDhag+NuAG 8yoqTHMZQflxpf09Byml3PVtEd510/r5Zjcq0Ndk= X-Yandex-Spam: 1 Received: from [188.134.86.249] ([188.134.86.249]) by web62.yandex.ru with HTTP; Thu, 03 Nov 2011 22:50:03 +0400 From: =?koi8-r?B?4c7Uz84g68zF09M=?= To: Conrad J. Sabatier ,freebsd-questions@freebsd.org MIME-Version: 1.0 Message-Id: <64971320346203@web62.yandex.ru> Date: Thu, 03 Nov 2011 22:50:03 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r Cc: 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: Thu, 03 Nov 2011 18:50:05 -0000 02.11.2011, 14:01, "Conrad J. Sabatier" : > šš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. You're actually right! Now, with this lines in kernel, SMBIOS looks more alive: # on-die sensor (added) device šššššššššcoretemp # System management bus device šššššššššsmb device šššššššššsmbus device šššššššššsmbios device šššššššššichsmb device šššššššššnfsmb device šššššššššintpm device šššššššššalpm device šššššššššviapm device šššššššššnfpm device šššššššššiicbus device šššššššššiicbb device šššššššššic device šššššššššiic device šššššššššiicsmb device šššššššššamdsmb # CPU control pseudo-device. Provides access to MSRs, CPUID info and microcode update feature. device šššššššššcpuctl # System Management Bus (SMB) options ššššššššENABLE_ALART ššššššššššš# Control alarm on Intel intpm driver So, system shows it during boot: # dmesg -a |grep smb smbios0: at iomem 0xf0480-0xf049e on motherboard smbios0: Version: 2.7, BCD Revision: 2.7 > šš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. The same thing. # ls -la /dev/sm* ls: /dev/sm*: No such file or directory > šš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. I hope that those chipsets are kind of generic things, that are compatible with modern ones like my Z68. It goes without saying that SOME of modern MB, supporting Intel Core(tm) CPUs are still supported by mbmon - it shows state of MB (not CPU) thermal sensor, for example. I can't give you exact models, but I can give it after some days (need to ask). >> ššš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 As I already say, "coretemp works fine" - I could read CPU thermal sensors with šdev.cpu.#CORE_ID.temperature sysctl after I added "coretemp" device into my kernel. Problem is to read MB sensors, like "chasis (system) temperature", fans RPM, voltages and so on. Now, with smbios device enabled, it still doesn't work the perfect way: # mbmon -V No VIA686 HWM available!! InitMBInfo: Unknown error: 0 # mbmon -S No SMBus HWM available!! InitMBInfo: Unknown error: 0 # mbmon -I No ISA-IO HWM available!! InitMBInfo: Unknown error: 0 # mbmon -A InitMBInfo: Unknown error: 0 This program needs "setuid root"!! # mbmon -D Probe Request: none >>> ššTesting Reg's at ISA-IO <<< [ISA Port IO-Base:0x290] Probing Winbond/Asus/LM78/79 chip: ššCR40:0x44, šCR41:0x00, šCR42:0x00, šCR43:0x00 ššCR44:0x00, šCR45:0x00, šCR46:0x00, šCR47:0x00 ššCR48:0x00, šCR49:0x00, šCR4A:0x00, šCR4B:0x00 ššCR4C:0x00, šCR4D:0x00, šCR4E:0x80, šCR4F:0x00 ššCR56:0xFF, šCR58:0xFF, šCR59:0xFF, šCR5D:0x19 ššCR3E:0xFF, šCR13:0x00, šCR17:0xFF, šCRA1:0xFF ššCR20:0xD1, šCR22:0x37, šCR23:0x78, šCR24:0x8A ššCR27:0xC7, šCR29:0xFF, šCR2A:0xFF, šCR2B:0xFF No Hardware Monitor found!! InitMBInfo: Unknown error: 0