[Bug 22220] Re: Correct modules for I2O-based raid are not loaded

Colin Watson cjwatson at canonical.com
Tue Aug 7 10:21:14 UTC 2007


hw-detect 1.32ubuntu8 uploaded to dapper-proposed for approval. This
will also need a trivial debian-installer upload afterwards to rebuild
the initrd against it.

** Description changed:

  Ubuntu 5.10 Preview experiences a system panic w/ I2O based raid controler at
  kernel boot after controller is detected. Current controller that this is
  experienced on is a Adaptec 2400a Hardware Raid (IDE). I do not have any other
  I2O based controllers on which to test this.
  
  5.4 did not experience this (we currently are using it), so this must be a
  regression in the preview version.
  
  Details for hw-detect dapper proposed update:
  
    The installer offers a menu of disk drivers when disks are not
  automatically detected. This list fails to include the drivers from
  drivers/message/fusion and drivers/message/i2o (mpt* and i2o_*). Thus,
  users of these devices have no obvious manual fallback if automatic
  detection fails.
  
    The bug was addressed in hw-detect 1.33 (in edgy) by adding these
  directories to the list of directories to be searched for drivers to
  offer, and adding a guard in case either directory doesn't exist.
  
+   A proposed patch for dapper is linked here:
+ https://bugs.launchpad.net/ubuntu/+source/hw-
+ detect/+bug/22220/comments/33
+ 
    You can reproduce this bug by removing the kernel module responsible
  for your disk from the running installer before it has a chance to load
  it (be quick!), and looking at the list of disks offered. Alternatively,
  it might be easier to boot in VMware with no disks attached.
  
    I haven't yet thought of any regression possibilities here, but they
  ought to be limited to the path where no disks were automatically
  detected.

** Changed in: hw-detect (Ubuntu Dapper)
       Status: Confirmed => In Progress

-- 
Correct modules for I2O-based raid are not loaded
https://bugs.launchpad.net/bugs/22220
You received this bug notification because you are a member of Kernel
Bugs, which is a bug contact for linux-source-2.6.15 in ubuntu.




More information about the kernel-bugs mailing list