Adding drivers to kickstart initrd.img

On 4/12/06, Ryan C. Spaulding <rspauldingmail.arc.nasa.gov> wrote:
> I am attempting to install Redhat 4.0-3 onto some new
hardware with a
> 3ware 9550SX SCSI RAID card.

You'll need to use a driver disk for that.

If you're using x86_64, I could send it to you...

regards,
dan carpenter

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

Hi Dan,

Yes, I am installing on x86_64. Any help you can give would
be  
appreciated. I think I tracked down the problem with the
driver not  
loading. I have added the correct driver into the
modules.cgz cpio  
that is is inside the initrd.img file under the isolinux
directory on  
install disk 1. I noticed that when it bombs out that it is 

attempting to load another 3ware driver from some other
modules.cgz  
file. I found another modules.cgz in stage2.img but when I
mount  
stage2.img it is read only and I have been unsuccessful in
producing  
a duplicate stage2.img with mkfs.cramfs. I think that a
rebuild of  
anaconda could fix this problem but I could be totally going
in the  
wrong direction.



Thank you,

Ryan



On Apr 13, 2006, at 2:40 PM, Dan Carpenter wrote:

> On 4/12/06, Ryan C. Spaulding <rspauldingmail.arc.nasa.gov> wrote:
>> I am attempting to install Redhat 4.0-3 onto some
new hardware with a
>> 3ware 9550SX SCSI RAID card.
>
> You'll need to use a driver disk for that.
>
> If you're using x86_64, I could send it to you...
>
> regards,
> dan carpenter
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

On 4/13/06, Ryan C. Spaulding <rspauldingmail.arc.nasa.gov> wrote:
> I think that a rebuild of anaconda could fix this
problem but I
> could be totally going in the wrong direction.
>

A little bit in the wrong direction, yes.

I'll forward you the driver disk in a seperate email.
`dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0`
Boot from the CD and use "linux dd" to specify
that there is a driver
disk.  You'll need a floppy or USB key or something.

If you want to automate the package.
1)  Download the anaconda source rpm
2)  rpm2cpio anacond-src-foo-rpm | cpio -idmv
3)  make
4)  apply this patch
https://www.redhat.com/archives/a
naconda-devel-list/2005-November/msg00018.html
5)  cd loader2/ ; make loader

6-9) Unpack the initrd.  Replace the old loader with the one
you just
created.  Put the driver disk in the initrd as /dd.img. 
Pack it back
up.

Then it's automatic.  Or you could just put the driver disk
on the
network I suppose but I don't recall the format for that...

regards,
dan carpenter

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

It's been a while since I've done it, but I used the
instructions here:

http://lists.us.dell.com/pipermail/lin
ux-poweredge/2003-August/009343.html

and adapted them into what I needed for the driver I was
installing. 
The above document probably won't give you all of the
answers, but
it's a good start, and it didn't require me to rebuild
anaconda.

Koree

On 4/14/06, Dan Carpenter <error27gmail.com> wrote:
> On 4/13/06, Ryan C. Spaulding <rspauldingmail.arc.nasa.gov> wrote:
> > I think that a rebuild of anaconda could fix this
problem but I
> > could be totally going in the wrong direction.
> >
>
> A little bit in the wrong direction, yes.
>
> I'll forward you the driver disk in a seperate email.
> `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0`
> Boot from the CD and use "linux dd" to
specify that there is a driver
> disk.  You'll need a floppy or USB key or something.
>
> If you want to automate the package.
> 1)  Download the anaconda source rpm
> 2)  rpm2cpio anacond-src-foo-rpm | cpio -idmv
> 3)  make
> 4)  apply this patch
> https://www.redhat.com/archives/a
naconda-devel-list/2005-November/msg00018.html
> 5)  cd loader2/ ; make loader
>
> 6-9) Unpack the initrd.  Replace the old loader with
the one you just
> created.  Put the driver disk in the initrd as /dd.img.
 Pack it back
> up.
>
> Then it's automatic.  Or you could just put the driver
disk on the
> network I suppose but I don't recall the format for
that...
>
> regards,
> dan carpenter
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>


--
Koree A. Smith
--
Senior System Administrator
EV1Servers.net

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

Hi All,

Thank you for the instructions. I was looking over the
kickstart  
documentation again and it looks like it has been updated
with 4.0  
release 3. I am going to attempt using what looks like a new
option  
called --driverdisk (with Dan's driver disk). Looks like I
can  
specify a driver disk via ftp, http and nfs.

I will let you all know how it goes.

Thank you,

Ryan



On Apr 14, 2006, at 1:02 AM, Dan Carpenter wrote:

> On 4/13/06, Ryan C. Spaulding <rspauldingmail.arc.nasa.gov> wrote:
>> I think that a rebuild of anaconda could fix this
problem but I
>> could be totally going in the wrong direction.
>>
>
> A little bit in the wrong direction, yes.
>
> I'll forward you the driver disk in a seperate email.
> `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0`
> Boot from the CD and use "linux dd" to
specify that there is a driver
> disk.  You'll need a floppy or USB key or something.
>
> If you want to automate the package.
> 1)  Download the anaconda source rpm
> 2)  rpm2cpio anacond-src-foo-rpm | cpio -idmv
> 3)  make
> 4)  apply this patch
> https://www.redhat.com/archives/anaconda-devel
-list/2005-November/ 
> msg00018.html
> 5)  cd loader2/ ; make loader
>
> 6-9) Unpack the initrd.  Replace the old loader with
the one you just
> created.  Put the driver disk in the initrd as /dd.img.
 Pack it back
> up.
>
> Then it's automatic.  Or you could just put the driver
disk on the
> network I suppose but I don't recall the format for
that...
>
> regards,
> dan carpenter
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

On 4/14/06, Koree A. Smith <koreesmithgmail.com> wrote:
> It's been a while since I've done it, but I used the
instructions here:
>
> http://lists.us.dell.com/pipermail/lin
ux-poweredge/2003-August/009343.html
>

That's just instructions on how to build a driver disk.  I
already
built the driver disk and forwarded it...  That was step 0. 
:P

Rebuilding anaconda is optional but it helps if your going
to load
hundreds of systems or it needs to be completely automated
for some
reason...

regards,
dan carpenter

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

Hmm.  I helped create a rather large system that does
completely
automated and unattended installs without rebuilding
anaconda.  What
does one gain from doing so?

Koree

On 4/14/06, Dan Carpenter <error27gmail.com> wrote:
> On 4/14/06, Koree A. Smith <koreesmithgmail.com> wrote:
> > It's been a while since I've done it, but I used
the instructions here:
> >
> > http://lists.us.dell.com/pipermail/lin
ux-poweredge/2003-August/009343.html
> >
>
> That's just instructions on how to build a driver
disk.  I already
> built the driver disk and forwarded it...  That was
step 0.  :P
>
> Rebuilding anaconda is optional but it helps if your
going to load
> hundreds of systems or it needs to be completely
automated for some
> reason...
>
> regards,
> dan carpenter
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>


--
Koree A. Smith
--
Senior System Administrator
EV1Servers.net

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

Hi All,

I had to download the new driver from 3ware for the '-34'
kernel that  
release 3 uses. All I had to do was add 'dd' to my
kickstart line and  
put in the floppy. Thank you everyone for all of your help


Thank you,

Ryan



On Apr 14, 2006, at 10:02 AM, Koree A. Smith wrote:

> Hmm.  I helped create a rather large system that does
completely
> automated and unattended installs without rebuilding
anaconda.  What
> does one gain from doing so?
>
> Koree
>
> On 4/14/06, Dan Carpenter <error27gmail.com> wrote:
>> On 4/14/06, Koree A. Smith <koreesmithgmail.com> wrote:
>>> It's been a while since I've done it, but I
used the instructions  
>>> here:
>>>
>>> http://lists.us.dell.com/pipermail/linux-poweredg
e/2003-August/ 
>>> 009343.html
>>>
>>
>> That's just instructions on how to build a driver
disk.  I already
>> built the driver disk and forwarded it...  That was
step 0.  :P
>>
>> Rebuilding anaconda is optional but it helps if
your going to load
>> hundreds of systems or it needs to be completely
automated for some
>> reason...
>>
>> regards,
>> dan carpenter
>>
>> _______________________________________________
>> Kickstart-list mailing list
>> Kickstart-listredhat.com
>> https://www.redhat.com/mailman/listinfo/kickstart-list
>>
>
>
> --
> Koree A. Smith
> --
> Senior System Administrator
> EV1Servers.net
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-listredhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list

On 4/14/06, Koree A. Smith <koreesmithgmail.com> wrote:
> Hmm.  I helped create a rather large system that does
completely
> automated and unattended installs without rebuilding
anaconda.  What
> does one gain from doing so?
>
> Koree
>

You're right of course.  The network route is the correct
way to go in
many cases.

My way is still kind of useful if you need a network driver
disk and
so you can't get it over the network...  Etc.  I have a
bunch of
configs like that so I eventually end up patching anaconda
for each
new redhat release.

Plus the subject was about putting the drivers in the initrd
and I was
trying to spread some anaconda-recompiling-joy.  ;P

regards,
dan carpenter

_______________________________________________
Kickstart-list mailing list
Kickstart-listredhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list