Re: smbus & hardware monitoring problem

2003-01-21 Thread Tim Aslat
In the immortal words of Matthew Seaman <[EMAIL PROTECTED]>... > Errr... > > happy-idiot-talk:...sys/i386/conf:% grep amdpm LINT > # amdpm AMD 756 Power Management Unit > device amdpm > > Looks like it is in LINT to me. Hmm... > > >http://www.freebsd.org/cgi/cvsw

Re: smbus & hardware monitoring problem

2003-01-21 Thread Matthew Seaman
On Wed, Jan 22, 2003 at 08:34:17AM +1030, Tim Aslat wrote: > In the immortal words of Matthew Seaman > <[EMAIL PROTECTED]>... > > > Of course, immediately I sent the above, I noticed what was wrong with > > that picture. > > > > Try adding > > > > device amdpm > > > > to you kernel con

Re: smbus & hardware monitoring problem

2003-01-21 Thread Tim Aslat
In the immortal words of Matthew Seaman <[EMAIL PROTECTED]>... > Of course, immediately I sent the above, I noticed what was wrong with > that picture. > > Try adding > > device amdpm > > to you kernel config... Thank you. It worked like a charm, and now that I know what I was lackin

Re: smbus & hardware monitoring problem

2003-01-21 Thread Matthew Seaman
On Tue, Jan 21, 2003 at 09:25:39AM +, Matthew Seaman wrote: > On Tue, Jan 21, 2003 at 10:21:55AM +1030, Tim Aslat wrote: > > > I have a M7MKA mainboard (Biostar) slot A Athlon, with a AMD751/756 > > chipset. According to the documentation I've found it has a winbond > > W83782D hardware moni

Re: smbus & hardware monitoring problem

2003-01-21 Thread Matthew Seaman
On Tue, Jan 21, 2003 at 10:21:55AM +1030, Tim Aslat wrote: > I have a M7MKA mainboard (Biostar) slot A Athlon, with a AMD751/756 > chipset. According to the documentation I've found it has a winbond > W83782D hardware monitor which is supposed to be supported by healthd. > > My current attempt