linux-kernel - Re: megaraid vs i2o for PCI device ID 101e:1960

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110715154832.09647266@lxorguk.ukuu.org.uk>
Date:	Fri, 15 Jul 2011 15:48:32 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Neela Syam Kolli <megaraidlinux@....com>, 632187@...s.debian.org,
	operator@....uni-bonn.de, Vasily Averin <vvs@...ru>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: megaraid vs i2o for PCI device ID 101e:1960

> Should this device be blacklisted from i2o_core?  Are there likely other
> MegaRAID devices that use the I2O PCI class but don't work with this
> generic driver?

I²O will probe I²O class devices. How well it works depends upon the
firmware version of the specific board.

The fix in this case is either updated firmware, or to go into the
configuration for the board and turn off I2O support in the bios config.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/