Date: Sun, 24 Jul 2005 00:41:51 -0300 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= <jonny@jonny.eng.br> To: "Gary W. Swearingen" <garys@opusnet.com> Cc: questions@freebsd.org Subject: Re: nForce3 SMB and Power Management Message-ID: <42E30DFF.4050000@jonny.eng.br> In-Reply-To: <am4qam1by5.qam@mail.opusnet.com> References: <42DE8877.6050808@jonny.eng.br> <8xoe8x9qtu.e8x@mail.opusnet.com> <42DFAF63.5080708@jonny.eng.br> <am4qam1by5.qam@mail.opusnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary W. Swearingen wrote: > Joćo Carlos Mendes Luis <jonny@jonny.eng.br> writes: > > >>gaia::root ~ [647] mbmon -I >>No ISA-IO HWM available!! >>InitMBInfo: Unknown error: 0 >>gaia::root ~ [648] > > > I don't get that with -I (just with -S). It pretends to work OK; just bad data, > which might be related to the bogus temp. seen in BIOS setup screen. > > >>none0@pci0:1:1: class=0x0c0500 card=0x813f1043 chip=0x00e410de rev=0xa1 hdr=0x00 >> vendor = 'NVIDIA Corporation' >> device = 'nForce PCI SMB Controller' >> class = serial bus >> subclass = SMBus > > > I get: > > ichsmb0@pci0:1:1: class=0x0c0500 card=0x0c111458 chip=0x00e410de rev=0xa1 hdr=0x00 > vendor = 'NVIDIA Corporation' > device = 'nForce PCI System Management' > class = serial bus > subclass = SMBus What's your FreeBSD version? At 5-stable, ichsmb attachs only to Intel devices, that means that only chips numered 0x????8086 are accepted: /* PCI unique identifiers */ #define ID_82801AA 0x24138086 #define ID_82801AB 0x24238086 #define ID_82801BA 0x24438086 #define ID_82801CA 0x24838086 #define ID_82801DC 0x24C38086 #define ID_82801EB 0x24D38086 #define ID_6300ESB 0x25a48086 I'll give it a try, anyway. Maybe compiling a kernel with ALL smb devices. > It looks like I got at least one correct driver (ichsmb) in the kernel > and that you didn't. I don't know what to make of the different "device" > strings, or whether that's from the kernel or the MB. > > I see a couple more SMB things in /sys/conf/NOTES that don't sound > necessary, but I'll probably try; namely, > > options NETSMB #SMB/CIFS requester > options LIBMCHAIN > options LIBICONV > options SMBFS #SMB/CIFS filesystem These are for the SMB/CIFS filesystem, which is the network filesystem used by MS Windows networks. These are not related to power control. > > Here's what I've got now: > > device smbus > device smb # requires smbus > #options ENABLE_ALART # Control alarm on Intel intpm driver [machine=i386]; Not a typo! > device iicbus > device iicbb # requires iicbus > > device ichsmb > device ic > device iic > device alpm > device amdpm > device intpm # requires smb > device viapm > device pcf
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42E30DFF.4050000>