Frans Pop <[EMAIL PROTECTED]> writes:
> $ cat /sys/bus/pci/devices/\:01\:00.4/class
> 0x0c0701
>
> The last is close, but still does not match the 0x0c0700 in modules.pcimap.
> Is there some fuzzy matching going on there?
The last byte (prog-if) is masked out: 0xff00.
Andreas.
--
Andr
Hello!
> Hmm, is lspci truncating the class code?
>
> > 01:00.4 Serial bus controller [0c07]: Intel Corporation 82573E KCS (Active
> Management) [8086:108e] (rev 03)
>
> Because this smells like an IPMI-ish device.
Yes, it is a IPMI class code, only older versions of lspci know nothing
about
On Sunday 21 October 2007, Dave Jones wrote:
> On Sun, Oct 21, 2007 at 03:34:11PM +0200, Frans Pop wrote:
> > AFAICT from modules.pcimap, ipmi_si should only be loaded for PCI ID
> > [103c:121a] (which I don't have), or for devices with class c0700
> > (which I also don't have).
>
> Hmm, is lspc
On Sun, Oct 21, 2007 at 03:34:11PM +0200, Frans Pop wrote:
> AFAICT from modules.pcimap, ipmi_si should only be loaded for PCI ID
> [103c:121a] (which I don't have), or for devices with class c0700 (which I
> also don't have).
Hmm, is lspci truncating the class code?
> 01:00.4 Serial bus
Last week I sent this same question to the openipmi-developer list on
sourceforge, but did not get any replies.
Does anyone here know the answer?
AFAICT my system does not support ipmi, but despite that fact something is
loading the ipmi_msghandler module and trying to load the ipmi_si
5 matches
Mail list logo