[Bug 16011] Ubuntu 5.10 Preview (Breezy Badger) Panics w/ I2O based raid
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Fri Dec 16 18:47:50 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=16011
Ubuntu | linux
------- Additional Comments From scianos at speakeasy.net 2005-12-16 18:47 UTC -------
I did a test with flight 2 and things are improved, but there are still problems
that would prevent the average user (or even sysadmin) from completing an install...
Here's a summary - I'll post additional info as I play around with it...
a) Module detection: Loads i2o_core from the new i2o subsystem layer but forgets
i2o_block, et al and therefore can not autodetect connected i2o disks. The
installer only presents dpt_i2o as an option, but since i2o_core has already
claimed the device dpt_i2o can not bind to the card. The Distribution needs to
settle on the new i2o layer or the traditional dpt_i2o driver. The new i2o layer
does have some compelling things going for it - namely an active development
path in the 2.6x kernels.
It should be noted that once the new i2o layers are hand-loaded, the installer
does successfully install to the disk!
b) The device mappings for GRUB are broken with the new i2o layers. They default
to /dev/sda instead of /dev/i2o/hda, etc. This prevents an automated grub install.
c) Once installed, the initrd does not (of course - due to my manual
installation) include the proper i2o_* drivers.
I'll do the same tests with the dpt_i2o drivers and see if we have better success.
- Stu
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list