Fwd: How to get /dev/smb* ?
02.11.2011, 14:01, Conrad J. Sabatier conr...@cox.net: 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: System Management BIOS 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,
Re: How to get /dev/smb* ?
02.11.2011, 14:01, Conrad J. Sabatier conr...@cox.net: 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: System Management BIOS 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,
Re: How to get /dev/smb* ?
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: System Management BIOS at ...? It's possible that your machine simply has no support for this. # dmesg -a |grep smb - returns nothing. Does it means that it is no way to read temperature sensors on motherboard? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get /dev/smb* ?
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: System Management BIOS at ...? It's possible that your machine simply has no support for this. # dmesg -a |grep smb - returns nothing. Does it means that it is no way to read temperature sensors on motherboard? I don't have a smb device in dmesg listed. But I have those in the kernel configuration: # System management bus device smbus device iicbus device iicsmb device iicbb device iic So I can read temperature values using xmbmon. With the mbmon program, it should work similarly. OS is 8.2-STABLE on x86 here. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get /dev/smb* ?
On Wed, 2 Nov 2011 08:55:56 +0100
Polytropon free...@edvax.de wrote:
I don't have a smb device in dmesg listed. But I have
those in the kernel configuration:
# System management bus
device smbus
device iicbus
device iicsmb
device iicbb
device iic
Do you find that including device smbios makes any perceptible
difference anywhere?
So I can read temperature values using xmbmon. With
the mbmon program, it should work similarly. OS is
8.2-STABLE on x86 here.
*Very* similarly, I would say:
root:/usr/ports/sysutils/xmbmon# cat Makefile
# Ports collection makefile for:xmbmon
# Date created: 2001/08/30
# Whom: k...@kobe1995.net
(NAKAMURA Kauzushi) #
# $FreeBSD: ports/sysutils/xmbmon/Makefile,v 1.23 2008/03/23 23:03:11
miwi Exp $ #
PORTNAME= xmbmon
PORTREVISION= 9
COMMENT=A X motherboard monitor for LM78/79, W8378x, AS99127F,
VT82C686 and ADM9240
MASTERDIR= ${.CURDIR}/../mbmon -- (if you catch my drift)
:-)
--
Conrad J. Sabatier
conr...@cox.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get /dev/smb* ?
On Wed, 02 Nov 2011 11:44:39 +0400 Антон Клесс rc5h...@yandex.ru 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: System Management BIOS 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: System Management BIOS 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 conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get /dev/smb* ?
Антон Клесс rc5h...@yandex.ru writes: 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: System Management BIOS at ...? It's possible that your machine simply has no support for this. # dmesg -a |grep smb - returns nothing. Does it means that it is no way to read temperature sensors on motherboard? Have you tried: $ sysctl -a | grep temperature dev.cpu.0.temperature: 29.2C dev.cpu.1.temperature: 29.2C for your system? I have an AMD cpu and the amdtemp kernel module provides that information. I am not familiar with the Intel cpus, but the coretemp module is supposed to provide the same information for them. I use gkrellm for various thing, and it will display that information directly. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get /dev/smb* ?
Have you tried: $ sysctl -a | grep temperature dev.cpu.0.temperature: 29.2C dev.cpu.1.temperature: 29.2C s/temperature/temp/ some systems will show more, eg: sysctl -a | grep temp | grep -v template dev.cpu.0.temperature: 35.0C dev.amdtemp.0.%desc: AMD K8 Thermal Sensors dev.amdtemp.0.%driver: amdtemp dev.amdtemp.0.%parent: hostb4 dev.amdtemp.0.sensor0.core0: 35.0C dev.amdtemp.0.sensor0.core1: 35.0C dev.amdtemp.0.sensor1.core0: 35.0C dev.amdtemp.0.sensor1.core1: 35.0C Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with ; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to get /dev/smb* ?
I built new PC with MSI Z68A-GD65(G3) motherboard, running 8.2-RELEASE and trying to get /dev/smb working (want to use mbmon with it). MSI Z68A-GD65(G3) have Intel Z68 chipset. Kernel compiled with those options: device cpufreq device coretemp device smb device smbus device ichsmb device iic device iicbus device iicsmb device intpm device alpm device viapm device nfpm device iicbb device ic device cpuctl options ENABLE_ALART # pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x76811462 chip=0x01008086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x76811462 chip=0x01018086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x76811462 chip=0x01028086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0: class=0x078000 card=0x76811462 chip=0x1c3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = simple comms ehci0@pci0:0:26:0: class=0x0c0320 card=0x76811462 chip=0x1c2d8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB pcib2@pci0:0:28:0: class=0x060400 card=0x76811462 chip=0x1c108086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0x76811462 chip=0x1c148086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib4@pci0:0:28:3: class=0x060400 card=0x76811462 chip=0x1c168086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib5@pci0:0:28:4: class=0x060401 card=0x76811462 chip=0x244e8086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI pcib7@pci0:0:28:5: class=0x060400 card=0x76811462 chip=0x1c1a8086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0: class=0x0c0320 card=0x76811462 chip=0x1c268086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB isab0@pci0:0:31:0: class=0x060100 card=0x76811462 chip=0x1c448086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci1@pci0:0:31:2:class=0x010400 card=0x76811462 chip=0x28228086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'Raid Controller (82801HR/HH/HO82801IR/IH/IO(AIE=0)/ICH10R)' class = mass storage subclass = RAID none1@pci0:0:31:3: class=0x0c0500 card=0x76811462 chip=0x1c228086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus em0@pci0:2:0:0: class=0x02 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet atapci0@pci0:3:0:0: class=0x010601 card=0x76811462 chip=0x91231b4b rev=0x11 hdr=0x00 class = mass storage subclass = SATA none2@pci0:4:0:0: class=0x0c0330 card=0x76811462 chip=0x01941033 rev=0x04 hdr=0x00 vendor = 'NEC Electronics Hong Kong' class = serial bus subclass = USB pcib6@pci0:5:0:0: class=0x060400 card=0x76811462 chip=0x10801b21 rev=0x01 hdr=0x01 class = bridge subclass = PCI-PCI none3@pci0:7:0:0: class=0x0c0330 card=0x76811462 chip=0x01941033 rev=0x04 hdr=0x00 vendor = 'NEC Electronics Hong Kong' class = serial bus subclass = USB What should I do to get /dev/smb working? coretemp works fine, if it's matter. Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get /dev/smb* ?
Updating to 8.2-RELEASE-p4 does not help. Any ideas? -- Антон Клесс, http://kless.spb.ru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to get /dev/smb* ?
On Tue, 01 Nov 2011 15:28:55 +0400 Антон Клесс rc5h...@yandex.ru wrote: I built new PC with MSI Z68A-GD65(G3) motherboard, running 8.2-RELEASE and trying to get /dev/smb working (want to use mbmon with it). MSI Z68A-GD65(G3) have Intel Z68 chipset. Kernel compiled with those options: device cpufreq device coretemp device smb device smbus device ichsmb device iic device iicbus device iicsmb device intpm device alpm device viapm device nfpm device iicbb device ic device cpuctl options ENABLE_ALART # pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x76811462 chip=0x01008086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x76811462 chip=0x01018086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x76811462 chip=0x01028086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0: class=0x078000 card=0x76811462 chip=0x1c3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = simple comms ehci0@pci0:0:26:0: class=0x0c0320 card=0x76811462 chip=0x1c2d8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB pcib2@pci0:0:28:0: class=0x060400 card=0x76811462 chip=0x1c108086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0x76811462 chip=0x1c148086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib4@pci0:0:28:3: class=0x060400 card=0x76811462 chip=0x1c168086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib5@pci0:0:28:4: class=0x060401 card=0x76811462 chip=0x244e8086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI pcib7@pci0:0:28:5: class=0x060400 card=0x76811462 chip=0x1c1a8086 rev=0xb5 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0: class=0x0c0320 card=0x76811462 chip=0x1c268086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB isab0@pci0:0:31:0: class=0x060100 card=0x76811462 chip=0x1c448086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci1@pci0:0:31:2:class=0x010400 card=0x76811462 chip=0x28228086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'Raid Controller (82801HR/HH/HO82801IR/IH/IO(AIE=0)/ICH10R)' class = mass storage subclass = RAID none1@pci0:0:31:3: class=0x0c0500 card=0x76811462 chip=0x1c228086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus em0@pci0:2:0:0: class=0x02 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet atapci0@pci0:3:0:0: class=0x010601 card=0x76811462 chip=0x91231b4b rev=0x11 hdr=0x00 class = mass storage subclass = SATA none2@pci0:4:0:0: class=0x0c0330 card=0x76811462 chip=0x01941033 rev=0x04 hdr=0x00 vendor = 'NEC Electronics Hong Kong' class = serial bus subclass = USB pcib6@pci0:5:0:0: class=0x060400 card=0x76811462 chip=0x10801b21 rev=0x01 hdr=0x01 class = bridge subclass = PCI-PCI none3@pci0:7:0:0: class=0x0c0330 card=0x76811462 chip=0x01941033 rev=0x04 hdr=0x00 vendor = 'NEC Electronics Hong Kong' class = serial bus subclass = USB What should I do to get /dev/smb working? coretemp works fine, if it's matter. Thank you! 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: System Management BIOS at ...? It's possible that your machine simply has no support for this. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
