Date: Tue, 19 Sep 2006 18:24:28 -0700 From: Nick Barkas <snb@threerings.net> To: Doug Ambrisko <ambrisko@ambrisko.com> Cc: "J. Martin Petersen" <jmp.lists@alvorlig.dk>, ports@freebsd.org, Michael Graziano <mikeg@bsd-box.net> Subject: Re: FreeBSD Port: ipmi-kmod-20060418_1 Message-ID: <6756C97D-A0AF-4D7E-93F0-11D76F03E324@threerings.net> In-Reply-To: <200609191703.k8JH3ZEe088920@ambrisko.com> References: <200609191703.k8JH3ZEe088920@ambrisko.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 19, 2006, at 10:03 AM, Doug Ambrisko wrote: > Michael Graziano writes: > | I believe our 2950 is BIOS Rev. A03 as well, I'll reboot it tomorrow > | if I have a chance and get the Dell version ID. > | > | dmesg-wise, my first iomem range is the same as for A02, but my > | second is not. I'm leaning toward the explanation that Dell moved > | something on us and done went and broke the module :-/ > | > | ipmi0: <System Management BIOS> at iomem 0xfd040-0xfd05e, > | 0xcffbc000-0xcffbcc3a on isa0 > | ipmi0: SMBIOS Version: 2.04, revision: 2.04 > | ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa > | ipmi0: couldn't configure smbios io res > > FYI, this will be fixed in -current soon. jhb has been doing some > work > in the area to greatly improve some WIP that I gave him. Dell put > a hole in the address range via their ACPI so it can't attach the > range. That's great. I'll keep an eye on the commits to the IPMI code in - current, and can update the sysutils/ipmi-kmod port with a new snapshot when that new code gets in. Nick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6756C97D-A0AF-4D7E-93F0-11D76F03E324>