Michael Robinson wrote:
> 
> "Ron 'The InSaNe One' Rosson" <[EMAIL PROTECTED]> writes:
> >> However, when I run lmmon, it just prints, "IOCTL: Device not configured" and
> >> exits.  What else do I need to do to get this to work?
> >
> >Make sure you have /dev/io. It worlks great here.
> 
> When I use "lmmon -i" to use /dev/io instead of /dev/smb0, it gives me this:
> 
>  Motherboard Temp               Voltages
> 
>  255C / 491F / 528K        Vcore1:   +3.984V
>                            Vcore2:   +3.984V
>     Fan Speeds             + 3.3V:   +3.984V
>                            + 5.0V:   +6.654V
>     1:    0 rpm            +12.0V:  +15.938V
>     2:    0 rpm            -12.0V:  -15.938V
>     3:    0 rpm            - 5.0V:   -6.654V
> 
> There are two things wrong here.  First, the temperature value is completely
> bogus.  Second, the voltage values are identical to all three decimal
> places on two different machines from two different manufacturers, running
> two entirely different configurations (one a three-way redundant hotswap
> power bus on a Dell PowerEdge, and one a single-power 1RU TruSolutions server,
> both genuine Intel motherboards).
> 
> So, I conclude that /dev/io is not giving me satisfaction.  For what it's
> worth, I get the exact same voltages, temperature, and fan speed with the
> '-I' switch to the consolehm port.  Using consolehm with /dev/smb0, I get:

<cutcut>

Going back to your problem with smbus, I have the same problem myself
with a new system running 3.4-stable. That is, smbus is configured and
detected somewhat, but doesnt work (maybe a resource confliction). As
far as /dev/io goes, its not going to work for everyone, in particular,
those who have different hardware monitoring chipsets than the authors
of these two programs (Chris Faulhaber and myself) however smbus may be
a different story (then again, it might not). What chipset does your
motherboard use for monitoring hardware?

mike.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to