On Fri, 2007-09-21 at 11:26 -0700, der.hans wrote:
> Am 21. Sep, 2007 schwtzte R P Herrold so:
> 
> > On Thu, 20 Sep 2007, der.hans wrote:
> >
> >> I was able to boot the rescue image, load the 3ware module
> >> and open up the initrd being used for the boots. The initrd
> >> has the 3ware module as well as the scsi_mod driver and ext3
> >> driver. It looks like everything is there.
> >
> > the latest 3-ware PCI-X cards need a later 3ware driver
> > variant than centOS and their upstream presently ship.  One
> 
> Yup.
> 
> > installs with the driver disk (dd) option; one may also also
> 
> If one had a disk...
> 
> At first I was loading via a SATA drive I borrowed from another machine. I
> then looked and found out the install shell has wget available. Bliss :).
> 
> I run pump to set up a network interface. I wget the driver package. I
> unpack the driver package. I unpack the driver. I insmod the driver.
> 
> If I'm in the install, I switch back to the install.
> 
> If I'm in rescue mode I need to also mknod the nodes needed to see the
> disk partitions. I don't know how to trigger whatever the normal drive
> search tools use. I can't seem to get a shell early enough to install the
> driver before the point where the nodes would be made.
> 
> > need to make a custom initrd with the altered module.  If not
> > needed at boot time, one may be able to wait and let the usual
> > module probing call it in as well, when a mount occurs.
> 
> Yeah. The problem, I think, is that I was was presuming the driver wasn't
> already in the kernel tree, so when had the module in the initrd I figured
> it was the driver I'd loaded. Now I think that's not the case and the
> initrd has been loading the driver without support for the card.
> 
> > I doco the custom mkinitrd part generally at:
> > 	http://www.owlriver.com/tips/driver-modules/
> 
> The problem is that mkinitrd was looking for things that weren't in the
> chroot environment. Things like /bin/bash. Nothing insurmountable, I
> think, but I was thinking I didn't need it, so I didn't want to expend a
> bunch of wasted effort.
> 
> > I'll turn this piece into another 'tip' when it comes back
> > around in my email spool.
> >
> >
> > Additionally it turns out that the sources for the later
> > 3-ware version are available from 3-ware, so that one may
> > compile and add it to the tree traversed by the depmod, after
> > moving the unwanted one away to another name:
> 
> Yeah, building a custom kernel is an option once I get the install done.
> Getting the install working should be possible since I have a working
> driver.
> 
> I will try again when I get a chance. Now that I think we know the actual
> problem I should be able to compensate for it.
> 
> Any idea where the install puts the modules for creating the initrd? In
> /lib/modules/$kernel_version/ like normal?
----
should be
/lib/modules/$kernel_version/kernel/drivers/scsi/WHATEVER.ko
or
/lib/modules/$kernel_version/extra/WHATEVER.ko

usually former rather than latter but depends on methodology...

-- 
Craig White <craig@tobyhouse.com>

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss