| Home | Changes | Download | FAQ | Benchmark | Fedora | RHEL4 | Survey | Survey results | Impressum |
Status of I2O support in Fedora Core 3 ====================================== Updated: Friday, May 27th, 2005 FC3 theoretically can install and run most Adaptec or DPT I2O SCSI cards, however upgrading from a 2.4-kernel based distribution like RH9 or FC1 that used dpt_i2o is not recommended, because it requires post-install manual fixing in Rescue Mode to include the i2o_block driver in the initrd. Some users have reported that the Anaconda installer of FC3 fails to autodetect and install the driver, but it works when selected from the driver menu. If this happens to you, please report your "lspci -n" so the kernel maintainers may be able to fix that in the future. There are rare instances where GRUB fails to install into the boot sector. If this happens to you please read this page for a simple procedure to solve this problem and create a bootable system. Status of I2O support in Fedora Core 4 ====================================== FC4 contains a fix to grub where installation is now theoretically fully reliable. Otherwise FC4 is expected to work every bit as well as the upstream 2.6.12-rc kernel that it is built upon. If you do run into any problems with the I2O drivers, please discuss I2O kernel problems on linux-scsi mailing list. File Fedora specific problems in Red Hat Bugzilla. Warren Togami wtogami@redhat.com
THE SOFTWARE AND INFORMATION ON THIS SITE IS PROVIDED BY SHADOW CONNECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SHADOW CONNECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE OR INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Sponsored by