Inserting a ethernet driver in the bootnet.img

Inserting a ethernet driver in the bootnet.img

Post by Dali Isl » Sat, 28 Dec 2002 07:05:53



Hey! I have a quick question to you. I am trying to add a gigabit
ethernet driver on the bootnet.img so that it can support network load
on the servers that has only gigabit connection.

This is what I did >>

        mount -o loop bootnet.img /mount

        Then I went to the /mount point and tried to gunzip the initrd.img to
get to the module files so I can put the new driver module I typed the
following command >>

        gunzip -d initrd.img  (This didn't work)

Is there any suggestion anybody can give me will be really
appreciated.
(Any other way of doing it!!)

Thanks
Dali

 
 
 

Inserting a ethernet driver in the bootnet.img

Post by Lee Alle » Sat, 28 Dec 2002 23:04:08




Quote:>Hey! I have a quick question to you. I am trying to add a gigabit
>ethernet driver on the bootnet.img so that it can support network load
>on the servers that has only gigabit connection.

>This is what I did >>

>    mount -o loop bootnet.img /mount

>    Then I went to the /mount point and tried to gunzip the initrd.img to
>get to the module files so I can put the new driver module I typed the
>following command >>

>    gunzip -d initrd.img  (This didn't work)

>Is there any suggestion anybody can give me will be really
>appreciated.
>(Any other way of doing it!!)

You're right: the next step is to gunzip it.  gunzip refuses to
operate on the file because it doesn't end in .gz.  So just rename it.

You can find the entire process documented here:
http://www.redhat.com/mailing-lists/kickstart-list/msg02393.html

Warning #1: the process of 'reassembling' the files after you insert
your drivers is finicky.  Pay close attention to the options for the
cpio and gzip commands or your floppy won't work.

Warning #2: Make sure the module you're adding is compatible with the
kernel -- it should really be pulled out of the RedHat 'BOOT'
directory (that's not the right directory name).

-Lee Allen

 
 
 

1. bootnet.img: support for DEC21143 (tulip.o)

Hello,
I am trying to ftp install RedHat Intel 6.0 onto a Crystal CS500.
I am having all sorts of fun and games getting the NIC to work.
The system has an integrated card (CPU, keyboard, mouse, NIC etc all
on one card) and the ethernet subsystem is based on the DEC21143
chipset.

Install sees the NIC but when I try to connect to the network it
fails.  I get errors on the hub (a nice flashing red LED).  RedHat
support are on the case and I am also wading through the readmes, FAQs
and web pages but I have not found anything too helpful.

The Linux-Tulip information page,
http://www.bmen.tulane.edu/~siekas/tulip.html
is being updated and I've not found anything of direct relevance in
Donald Becker's page except for the diagnostic program which I will
try out soon.

I am doing an ftp install because although I have the RedHat Cds I
don't have a SCSI CD for the Crystal.  A colleague originally
installed the system using an IDE CD (powered by *another* PC!) but
the install only worked when an IDE CD was present, removing it (or
not powering it) killed the network connection (?).  Sometimes it
didn't work even with the CD attached.

Given that there is a brain-damaged installation on my system I have
tried using linuxconf to reinstall the tulip driver and I also tried
the de4x5 driver, neither worked.

I have also copied the entire CD set onto the hard disk but I don't
get the option to do a hard disk based install ... I suspect this is
because the cd image is on the system partition ?
I've also tried the expert install without any luck.

I think the problem may be either that the card is trying to run at
100Mb/s when it should be 10Mb/s or the driver embedded in bootnet and
the kernel is not suitable for my system.

So ...

1. has anyone ever successfully ftp installed on a system like mine
using a boot floppy and ftp ?

2. can anyone talk me through making a bootnet.img with the latest
tulip.o ?

If I have to I will recompile the kernel or drop in another NIC but I
would rather crack this problem and do a clean install from scratch so
I can use the integrated NIC and repartiton the hard disk.

If I have missed any information sources or if anyone needs more
information, please feel free to email me.

If anyone posts a reply I would be very graeful if you could also cc

Many thanks in advance for any advice or pointers!

Cheers,
   Andy.

2. Can you help me (ldd error message) Thanks

3. Screen blanks with RedHat 6.0 bootdisk (bootnet.img)

4. tuxtops recommendations

5. bootnet.img

6. Win95 Long File Names

7. how does one create a custom bootnet.img boot disk...

8. What excatly is an ftp or a "http get" file really doing?

9. how to make a custom redhat bootnet.img...i.e predefined package list

10. bootnet.img

11. RedHat 6.2: bootnet.img/DHCP/NFS

12. creating bootnet.img disk inside Linux

13. bootnet.img diskette(s)