Red Hat Bugzilla – Bug 68796
I2O support is broken
Last modified: 2007-04-18 12:44:09 EDT
Loading I2O support requires i2o_pci is loaded, then i2o_block/scsi/tape... Anaconda in bets3 never loads i2o_pci so never sees the controllers.
*** Bug 72070 has been marked as a duplicate of this bug. ***
Should work as of Milan-re0823.nightly although I couldn't dig up an i2o card around here last night to test with
A little odd In expert no probe I have to pick "i2o pci" then "i2o block" (i2o_pci is something i2o_block needs as a module rather than different kind of device. There isnt a direct module dependancy however) If I do that it detected my disks In autodetect mode I can't test it currently - my test card gets eaten by the megaraid driver (not an installer bug) not i2o. The cards that dont are in production boxes at the moment. Anyway, its possible to do the install now, so worst case its gone from failure to slightly quirky
Okay, that's at least okay for now. We can probably fix it better for Gin Gin, but I don't want to rock the boat now.
Sounds sensible to me
Alan, I know you installed GinGin on an i2o box and found a mkinitrd bug. Was i2o reasonable otherwise?
Will retest with final once I have it and confirm. I think we are ok now
Assuming its fixed.
I said I would test it when I had the final images. Right now I don't. I've only just got the new ADSL line.
Did the final images download yet?
Sorry feel off my tasklist. Just kicked off a test install. Will report back in about an hour
Install works initrd built loads i2o_pci/i2o_core/i2o_block not the needed i2o_core/i2o_pci/i2o_block. You'll be glad to know in 2.6 i2o_pci/core are one module and avoid that mess. Hand fixed initrd works, so its 99.9% right
Hrmm... what are the contents of /etc/modules.conf and what's the version of mkinitrd? I thought I had fixed the order flip-flop :/
Closing due to inactivity - please reopen if you have additional information to add.
Re-opening because its still not fixed in RH9 and NOTABUG isnt a valid way to close it.
*** Bug 83447 has been marked as a duplicate of this bug. ***
How does this look with Fedora? I'm still in the "don't have hardware, so grasp at straws" situation as far as actually making changes for this stuff.
Ok in Fedora 1, other 2.6 kernel specific issues in FC2 which are documented elsewere , closing