Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Jan 2003 09:31:04 +0000
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Re: smbus & hardware monitoring problem
Message-ID:  <20030121093104.GB94103@happy-idiot-talk.infracaninophi>
In-Reply-To: <20030121092539.GA94103@happy-idiot-talk.infracaninophi>
References:  <20030121102155.74ecef63.tim@spyderweb.com.au> <20030121092539.GA94103@happy-idiot-talk.infracaninophi>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 21, 2003 at 09:25:39AM +0000, 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 monitor which is supposed to be supported by healthd.
> > 
> > My current attempt at kernel configuration has the following differences
> > from GENERIC.
> > ---- additional entries to GENERIC ------------------------
> > # trying to get smbus working for hardware monitoring
> > device          smbus           # Bus support, required for smb below.
> > device          intpm
> > device          alpm
> > device          ichsmb
> > device          viapm
> > device          smb
> > 
> > device          iicbus          # Bus support, required for 
> > device          iicbb
> > device          ic
> > device          iic
> > device          iicsmb          # smb over i2c bridge
> > device          pcf0    
> > ---- end addition entries -------------
> > 
> > dmesg doesn't come up with any indication that smbus or smb devices are
> > found/configured and I'm beginning to tear my hair out.
> 
> Well, you've done everything pretty much right so far --- however,
> although you seem to have added all of the possible variants of SMBus
> controller chips, your kernel isn't picking up the hardware on your
> motherboard.  That might simply be because the exact chipset you have
> isn't recognised, although from what you've said above, I'd expect the
> amdpm driver to probe successfully.

Of course, immediately I sent the above, I noticed what was wrong with
that picture.

Try adding

    device      amdpm

to you kernel config...

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030121093104.GB94103>