On Wed, 28 Aug 2002, Bruce M Simpson wrote: > On Wed, Aug 28, 2002 at 12:01:15AM +0200, Dan Larsson wrote: > > While trying to get hardware monitoring to work on my computer I > > found the below procedure to enable the smbus device. > > It didn't get me any closer to actually monitoring the hardware with > > xbmon, lmmon or healthd. But the device is there. > > I'd like to add to this. uname is: > FreeBSD triage.dollah.com 4.6-STABLE FreeBSD 4.6-STABLE #1: Sun Aug 25 11:23:33 BST >2002 [EMAIL PROTECTED]:/usr/src/sys/compile/TRIAGE i386 > > pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard > ... > intpm0: <Intel 82371AB Power management controller> port 0x1040-0x104f irq 9 at >device 7.3 on pci0 > intpm0: I/O mapped 1040 > intpm0: intr IRQ 9 enabled revision 0 > smbus0: <System Management Bus> on intsmb0 > smb0: <SMBus general purpose I/O> on smbus0 > intpm0: PM I/O mapped 8000 > > This supports APM just fine, but SMB goes nowhere. Any clues? When ktracing > processws which use /dev/smb0, it seems that the ioctls simply don't > get handled. I assume this is because something somewhere didn't attach. > >From the above dmesg output I'd infer that nothing's being seen on the smbus.
What error is open or ioctl returning in your ktrace? EINVAL? boot -v will give you more info about the attach progress. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
