Fwd: How to get /dev/smb* ?

看板FB_questions作者時間14年前 (2011/11/04 03:01), 編輯推噓0(0推 0噓 0→)
留言0則, 0人參與, 最新討論串1/1
02.11.2011, 14:01, "Conrad J. Sabatier" <conrads@cox.net>: > ⒐ just noticed, looking back at your previous mail, that you don't seem > 惗o have a "device smbios" line in your kernel config. ⒛ry adding that > 嵻nd 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 骚骚骚骚嶤oretemp # System management bus device 骚骚骚骚恾mb device 骚骚骚骚恾mbus device 骚骚骚骚恾mbios device 骚骚骚骚幈chsmb device 骚骚骚骚徱fsmb device 骚骚骚骚幈ntpm device 骚骚骚骚嵻lpm device 骚骚骚骚愌iapm device 骚骚骚骚徱fpm device 骚骚骚骚幈icbus device 骚骚骚骚幈icbb device 骚骚骚骚幈c device 骚骚骚骚幈ic device 骚骚骚骚幈icsmb device 骚骚骚骚嵻mdsmb # CPU control pseudo-device. Provides access to MSRs, CPUID info and microcode update feature. device 骚骚骚骚嶤puctl # System Management Bus (SMB) options 骚骚骚骚ENABLE_ALART 骚骚骚骚骚騣 Control alarm on Intel intpm driver So, system shows it during boot: # dmesg -a |grep smb smbios0: <System Management BIOS> at iomem 0xf0480-0xf049e on motherboard smbios0: Version: 2.7, BCD Revision: 2.7 > ⒈lthough no "smbios0" device actually shows up under /dev. ⒗erhaps > 恾ome more knowledgeable individual might enlighten us as to what > 嶤apabilities having this in your kernel config actually enables. The same thing. # ls -la /dev/sm* ls: /dev/sm*: No such file or directory > ⒈lso, just looking at the (x)mbmon port, the COMMENT line in the > ⒔akefile states: > > ⒈ X motherboard monitor for LM78/79, W8378x, AS99127F, VT82C686 and > ⒈DM9240 > > ⒚o, this port appears to be useful only on a very specific range of > 彲otherboards. 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? > 尣ell, it depends. 騺-) > > ⒐'m not at all familiar with your particular processor/motherboard, so I > 嶤an only offer some rather limited advice that may steer you in the > 怣ight direction for further exploration. ⒛here are a number of devices > 慐ou can enable in your kernel config that may provide some of what > 慐ou're looking for. > > ⒏ere, on my amd64 box, for instance, "device amdtemp", along with > 騢device cpuctl" and "device cpufreq" makes the following dev.cpu.* > 恾ysctls available, which are one way to (manually) monitor your > 恾ystem. ⒈s you can see below, this provides information on CPU > 惗emperature and frequency. > > 騣 sysctl dev.cpu > 嶫ev.cpu.0.%desc: ACPI CPU > 嶫ev.cpu.0.%driver: cpu > 嶫ev.cpu.0.%location: handle=\_PR_.P001 > 嶫ev.cpu.0.%pnpinfo: _HID=none _UID=0 > 嶫ev.cpu.0.%parent: acpi0 > 嶫ev.cpu.0.temperature: 47.0C > 嶫ev.cpu.0.freq: 2200 > 嶫ev.cpu.0.freq_levels: 2200/23500 1100/14280 > 嶫ev.cpu.0.cx_supported: C1/0 > 嶫ev.cpu.0.cx_lowest: C1 > 嶫ev.cpu.0.cx_usage: 100.00% last 1931us > 嶫ev.cpu.1.%desc: ACPI CPU > 嶫ev.cpu.1.%driver: cpu > 嶫ev.cpu.1.%location: handle=\_PR_.P002 > 嶫ev.cpu.1.%pnpinfo: _HID=none _UID=0 > 嶫ev.cpu.1.%parent: acpi0 > 嶫ev.cpu.1.temperature: 47.0C > 嶫ev.cpu.1.cx_supported: C1/0 > 嶫ev.cpu.1.cx_lowest: C1 > 嶫ev.cpu.1.cx_usage: 100.00% last 4658us > 嶫ev.cpu.2.%desc: ACPI CPU > 嶫ev.cpu.2.%driver: cpu > 嶫ev.cpu.2.%location: handle=\_PR_.P003 > 嶫ev.cpu.2.%pnpinfo: _HID=none _UID=0 > 嶫ev.cpu.2.%parent: acpi0 > 嶫ev.cpu.2.temperature: 47.0C > 嶫ev.cpu.2.cx_supported: C1/0 > 嶫ev.cpu.2.cx_lowest: C1 > 嶫ev.cpu.2.cx_usage: 100.00% last 3551us > 嶫ev.cpu.3.%desc: ACPI CPU > 嶫ev.cpu.3.%driver: cpu > 嶫ev.cpu.3.%location: handle=\_PR_.P004 > 嶫ev.cpu.3.%pnpinfo: _HID=none _UID=0 > 嶫ev.cpu.3.%parent: acpi0 > 嶫ev.cpu.3.temperature: 47.0C > 嶫ev.cpu.3.cx_supported: C1/0 > 嶫ev.cpu.3.cx_lowest: C1 > 嶫ev.cpu.3.cx_usage: 100.00% last 4943us As I already say, "coretemp works fine" - I could read CPU thermal sensors with 嶫ev.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 >>> ⒛esting Reg's at ISA-IO <<< [ISA Port IO-Base:0x290] Probing Winbond/Asus/LM78/79 chip: 骚CR40:0x44, ⒊R41:0x00, ⒊R42:0x00, ⒊R43:0x00 骚CR44:0x00, ⒊R45:0x00, ⒊R46:0x00, ⒊R47:0x00 骚CR48:0x00, ⒊R49:0x00, ⒊R4A:0x00, ⒊R4B:0x00 骚CR4C:0x00, ⒊R4D:0x00, ⒊R4E:0x80, ⒊R4F:0x00 骚CR56:0xFF, ⒊R58:0xFF, ⒊R59:0xFF, ⒊R5D:0x19 骚CR3E:0xFF, ⒊R13:0x00, ⒊R17:0xFF, ⒊RA1:0xFF 骚CR20:0xD1, ⒊R22:0x37, ⒊R23:0x78, ⒊R24:0x8A 骚CR27:0xC7, ⒊R29:0xFF, ⒊R2A:0xFF, ⒊R2B:0xFF No Hardware Monitor found!! InitMBInfo: Unknown error: 0 _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
‣ 更多 rc5hack. 的文章
文章代碼(AID): #1EikJlFZ (FB_questions)