On Sun, 2004-08-01 at 07:58, John Thompson wrote: > meherenow@xxxxxxxxxxxxx wrote: > > > I'm having real problems installing FC2 on a machine with an adaptec 2100S scsi > > raid controller. > > > > I knew to expect problems after finding the discussion on the mailing list, but > > it seemed to be surmountable. I appear to have reached a brick wall however. > > > > I get the same results when installing either FC2 or the new beta. According to > > http://www.redhat.com/archives/fedora-list/2004-May/msg03906.html I should just > > be able to wget the correct module, insmod it and away I go! > > > > However either I'm doing something stupid (entirely possible) or this route just > > isn't working for me. > > > > I extract the module from the correct kernel rpm, wget it across to the target > > machine, do a quick lsmod to see that two existing i2o modules are present, but > > not i2o_proc. So I run: > > > > # insmod ./i2o_proc.ko > > Is there a reason why you don't use "modprobe" instead of "insmod"? > Modprobe will install any prerequisite modules as well, which may help. Yes. That's what Warren Togami has instructed us to use in step 4 of the HOWTO. No matter. Any amount of rummaging with insmod, lsmod, modprobe, or rmmod at that stage of the installation will load the i2o_proc.ko driver fetched via wget from another system into /tmp. This problem now seems specific to the Zero Channel RAID cards (Adaptec models 2000S, 2010S, ...). Other I2O products are said to work correctly with Warren's HOWTO. There is an alpha patch mentioned. I've downloaded it and tried to recompile the i2o_xxx modules. I gave up when I realized that, even it fixes whatever is preventing the module from loading, it cannot be applied to yield a bootable system since there's no way to add it into and replace the initrd images on either FC2 or FC3t1 CD#1 ISOs. This is why we must wait for the FC3t2 release, originally planned for mid-September but possibly now pushed back. > > followed by: > > > > # lsmod > > > > but for some reason i2o_proc does not appear! Hence the install fails as it > > cannot find any devices to install on. > > > > There are no error messages upon running the command and no indication as to > > what is wrong. > > Does anything appear in /var/log/messages when you try to load the module? See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123567 Any error messages will appear in the ALT-F4 console at this stage of the installation. In two out of about ten installation attempts, a list of ten "Unknown symbol i2o_xxxx" messages appeared on that console in response to 'insmod i2o_proc'. Significant or artifact, we don't know. --Doc Robert G. (Doc) Savage, BSE(EE), CISSP, RHCE | Fairview Heights, IL Fedora Core 1 kernel 2.4.22-1.2197.nptl on P-III/M IBM Thinkpad A22p "Perfection is the enemy of good enough." -- Admiral of the Fleet Sergei G. Gorshkov
