Avatar of AndersBiro
AndersBiroFlag for Sweden asked on

Slipstream NIC driver into Centos 5.2?

Hello, we have this situation that we have a specific automated USB key installation of Centos 5.2 that should work with a special server-appliance that we ship to customers.

However, the old server hardware model is no longer available so it had to be replaced by a more recent model.
The problem is that the new NIC hardware is not available in the Centos 5.2 installation and hence we needed to install a new source driver and compile it for the running kernel creating a new .RPM driver.

This added NIC driver support but it is still a problem since we have a kickstart 5.2 USB key installation that is supposed to take care of everything and so post-install driver addition is not acceptable.

The question is whether the original Centos 5.2 installation can be slipstreamed to include this new driver as well so the NIC will be automatically detected at installation setup?
LinuxLinux DistributionsSoftware

Avatar of undefined
Last Comment
AndersBiro

8/22/2022 - Mon
Duncan Roe

Please post output from:
uname -a
lspci

I am not familiar with Centos revisions, only Linux ones, hence the first request. lspci will show more information about the NIC card - if you could highlight the entry for the card that would be extra help.
You plan to put the new kernel on your Kickstart USB don't you?
Duncan Roe

Actually, if you have the module working with Centos 5.2, could you not just put it on the initrd and in the modules directory? (re-run depmod of course)
gheist

Is update to CentOS 5.5 an option? maybe it has driver?
You can compile module in an RPM and add to installer and to installable sets.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
ASKER
AndersBiro

I am afraid I have only sporadic access to the server and so I have not had opportunity to test anything yet.
However, upgrading to 5.5 is no option since only 5.2 is supported  and since I use a kickstart file the NIC has to be detected during installation.
I have already a precompiled RPM-package so is it possible to add this driver in existing Centos installation files so the NIC will be automatically detected during startup?
Duncan Roe

Yes that's what I was trying to suggest you do in my last post. The module needs to be in the initrd - I assume you have the tools to modify that (it's a gzipped ext2 file system image) and it may or may not need to be in the modules directory as well.
Duncan Roe

I haven't used initrd for a while, but here's what a random old one looks like (Linux 2.4.24)
10:26:54# ls -FxRl /mnt/tmp
/mnt/tmp:
total 9
drwxr-xr-x 2 root root 1024 Jan 10  2004 bin/
drwxr-xr-x 2 root root 1024 Jan 10  2004 dev/
drwxr-xr-x 2 root root 1024 Jan 10  2004 etc/
drwxr-xr-x 2 root root 1024 Jan 10  2004 lib/
-rwxr-xr-x 1 root root  641 Jan 10  2004 linuxrc*
drwxr-xr-x 2 root root 1024 Jan 10  2004 loopfs/
drwxr-xr-x 2 root root 1024 Jan 10  2004 proc/
drwxr-xr-x 2 root root 1024 Jan 10  2004 sbin/
drwxr-xr-x 2 root root 1024 Jan 10  2004 sysroot/

/mnt/tmp/bin:
total 560
-rwxr-xr-x 1 root root 546660 Jan 10  2004 insmod*
-rwxr-xr-x 1 root root  21260 Jan 10  2004 nash*

/mnt/tmp/dev:
total 0
crw-r--r-- 1 root root 5, 1 Jan 10  2004 console
crw-r--r-- 1 root root 1, 3 Jan 10  2004 null
brw-r--r-- 1 root root 1, 1 Jan 10  2004 ram
crw-r--r-- 1 root root 4, 0 Jan 10  2004 systty
crw-r--r-- 1 root root 4, 1 Jan 10  2004 tty1
crw-r--r-- 1 root root 4, 2 Jan 10  2004 tty2
crw-r--r-- 1 root root 4, 3 Jan 10  2004 tty3
crw-r--r-- 1 root root 4, 4 Jan 10  2004 tty4

/mnt/tmp/etc:
total 0

/mnt/tmp/lib:
total 278
-rw-r--r-- 1 root root 145234 Jan 10  2004 ide-core.o
-rw-r--r-- 1 root root   1158 Jan 10  2004 ide-detect.o
-rw-r--r-- 1 root root  20012 Jan 10  2004 ide-disk.o
-rw-r--r-- 1 root root  13656 Jan 10  2004 piix.o
-rw-r--r-- 1 root root  17015 Jan 10  2004 sd_mod.o
-rw-r--r-- 1 root root  79209 Jan 10  2004 sym53c8xx_2.o

/mnt/tmp/loopfs:
total 0

/mnt/tmp/proc:
total 0

/mnt/tmp/sbin:
total 0
lrwxrwxrwx 1 root root 3 Jan 10  2004 bin -> bin
lrwxrwxrwx 1 root root 9 Jan 10  2004 modprobe -> /bin/nash

/mnt/tmp/sysroot:
total 0
10:28:25#

Open in new window

Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
AndersBiro

I am afraid I am still a bit confused, for the time being the installation media is a USB stick containing the installation folders below:

Centos -> All RPM packages
Images/pxeboot/initrd.img
ISOLINX
Repodata

The installation is automatically triggered by a kick-start file so is the NIC driver RPM supposed to be added to the initrd.img file by opening it with a ext2 file system tool?
gheist

new-kernel-pkg will make a new kernel package with initrd suited to your needs.
ASKER
AndersBiro

So basically if we have a functioning server with all drivers included you can run the "new-kernel-pkg" utility that generates a initrd.img file that should replace the previous one or have I misunderstood?
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
gheist

it creates a good kernel rpm, you might need to add netcard driver to mkinitrd option files (i dunno where in centos), then create a good kernel RPM and replace one on your install CDs with good one....
Duncan Roe

I am not familiar with the new-kernel-pkg command (I run Slackware), but I imagine it will do what you want.
If you get stuck though, and would like to put the kernel module (.ko) file directly into the initrd then post back.
ASKER
AndersBiro

Thanks, but since I am not very familiar with this I am afraid a need a step-by-step approach so have I understood things correctly:

1. Create the RPM that installs NIC driver on a post-install server.
2. Create kernel RPM using new-kernel-pkg command, add RPM NIC driver to mkinitrd option files (how?)
3. Replace the current installation kernel with the newly generated kernel RPM in the mediar

OR  

Put kernel modules (.ko) files (what is it) to initrd (how?)

I really think I would need a step-by-step approach here since I am quite new to this.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
AndersBiro

Just  to complicate things even further I need to know how to edit ISO-files as I have followed the instructions according to the site http://wiki.centos.org/HowTos/InstallFromUSBkey in order to create the kick-started USB-stick and it does not seem to be an option to use  extracted files instead so how would I inject the new files into the installation ISO?
Duncan Roe

I can't help you with RPM package creation - maybe someone else can - but I'm happy to help you inject stuff, though it may take a bit of time.
ISO images are fairly easy: make a copy of the ISO file system as a directory on the hard drive; add / delete / change files in that directory as you wish; make a new ISO image with mkisofs.
Updating the initrd is the proof of concept though, so let's do that first.
We need to convert your initrd into a directory tree on the hard drive (e.g. in /tmp) just as we would do for an ISO. I'll try to stick to the conventions in the web page How to Set Up a USB Key to Install CentOS that you posted, so let's say you have mounted your USB partitions as /media/BOOT and /media/DATA. Post the output from the following:
cd /media/BOOT
cat initrd.img | gzip -d > /tmp/initrd.unzipped
file /tmp/initrd.unzipped
cat syslinux.cfg
ls -Fxl

Please correct any trivial errors yourself (like if initrd.image is the wrong name and there's another file with name starting initrd)
Later, we'll need to copy directory trees around, for which I'll use my trecpy command below. Please put it somewhere in your PATH (e.g. /usr/local/bin or $HOME/bin), and ensure it's executable by chmod a+x trecpytrecpy
ASKER
AndersBiro

Hello, I have attached the output files using the commands below and is the next step to actually mount /initrd.unzipped as a image-directory?
uname.txt
output.txt
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Duncan Roe

No you can't mount /initrd.unzipped because it is a cpio archive. That seems to be the modern way of doing things - Slackware 13 is the same.
Sorry it's too late at night for me to post coherent instructions - extract the archive using cpio if you can else post and I'll explain how to do it once I figure it out myself. Extract to /tmp/initrd say. Also please post the output from an rpm -qpl of your RPM containing the new kernel module.
Duncan Roe

Also the output from ls -FxRl of both BOOT and DATA (I didn't think to specify R last time - will show all sub_directories)
ASKER
AndersBiro

I have now been able to extract the initd contents to a folder using "cat file <  cpio -idmv" and i have attached the module output from the driver RPM package so have I understand things correctly that you should copy these module-files to an appropiate extracted folder and then turn it to a init image again to be copied over the existing one?

In this case, under which folders should the modules reside (module folder?)
nicmodule.txt
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Duncan Roe

You're getting it! There's a little more to it, but while I'm working on that could you post the output from ls -FxlR done at the top of the extracted directory tree? Thx
Duncan Roe

cat file <  cpio -idmv wasn't what you typed, was it? You typed cat file |  cpio -idmv
Had me confused for a bit
Duncan Roe

You posted a link to How to Set Up a USB Key to Install CentOS in http:#a34301096. Assuming you have the 2 partitions on the USB key mounted as /media/BOOT and /media/DATA, please post the output from:

cd /media/BOOT
ls -FxlR
cd /media/DATA
ls -FxlR


I need some time to satisfy myself that I can get the next bit right, will post later
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
Duncan Roe

I have downloaded Centos 5.5 (couldn't get 5.2) and am following the instructions in the web page. So I don't need you to post BOOT and DATA contents now.
Duncan Roe

Just as well I did that - it seems the modules are in a cgz file (zipped cpio archive I expect). I think that's pretty silly seeing it's inside a gzipped image, but we'll have to unpack it an repack afterward.
Well it's past the witching hour now so I'm going to stop for today - sorry not to have more for you but it was a busy day - Saturday always is. Will continue tomorrow
SOLUTION
Duncan Roe

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
AndersBiro

So far I have tried the following steps:

mkdir /tmp/initrd
cd /tmp/initrd
cat /media/BOOT/syslinux/initrd.img | gzip -d | cpio -idmv

but following is returned:
"var
var/run
var/lib
var/lib/xkb
var/state
var/lock
var/lock/rpm
init
selinux
.buildstamp
sbin

gzip: stdin: invalid compressed data--format violated
cpio: premature end of file
"

This is quite annoying as I was able to extract the contents before but obviously not anymore.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Duncan Roe

Agreed - it is annoying but the file must have become corrupt somehow. You had better replace it with a fresh copy from the CD / ISO image. The USB stick will not boot anywahere with that corruption. It still works fine for me btw, so you're doing it right
10:11:55$ mkdir /tmp/initrd
10:12:07$ cd /tmp/initrd
10:12:07$ cat /media/BOOT/syslinux/initrd.img | gzip -d | cpio -idmv
.
modules
modules/modules.alias
modules/pci.ids
modules/module-info
modules/modules.cgz
modules/modules.dep
selinux
etc
etc/arch
etc/loader.tr
etc/terminfo
etc/terminfo/s
etc/terminfo/l
etc/terminfo/l/linux
etc/terminfo/v
etc/terminfo/v/vt100
etc/terminfo/v/vt100-nav
etc/terminfo/v/vt102
etc/terminfo/a
etc/terminfo/a/ansi
etc/terminfo/x
etc/terminfo/d
etc/terminfo/b
etc/screenfont.gz
etc/passwd
etc/keymaps.gz
etc/lang-table
etc/mtab
dev
tmp
proc
var
var/state
var/run
var/lock
var/lock/rpm
var/lib
var/lib/xkb
bin
.buildstamp
.profile
init
sbin
sbin/loader
sbin/halt
sbin/modprobe
sbin/init
sbin/rmmod
sbin/sh
sbin/poweroff
sbin/insmod
sbin/reboot
sys
18141 blocks

Open in new window

ASKER
AndersBiro

I am not completely sure I understand the requested information but so far I have done the following:

1. Extract the contents of an intact initrd.img to /tmp/initrd with no errors this time
2. Extracting the contents from /tmp/intit/modules/modules.cgz to /tmp/lib/modules/2.6.18.92.el5/i686
3. Extracting all *.ko files from the new driver RPM to the generated folder with other modules
4. Running depmod -b /tmp without no errors and confirming with the timestamps of the files in tmp/lib/modules/2.6.18.92.el5 that they were newly generated

Here I lost the track though," find /lib/modules/2.6.18-92.el5PAE -name '*.ko' | wc -l" did generate the result 1173

The length of /tmp/initrd/modules/modules.dep are 13301 bytes so is this what you need or have I completely misunderstood things?
Duncan Roe

All fine except the last line. By length I meant number of lines, i.e. comparing like with like, so I wanted the result from cat /tmp/initrd/modules/modules.dep | wc -l
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Duncan Roe

Guess I assumed you would just recognise wc -l as a synonym for number of lines, i.e. length - a trap for old players :)
Some explanation of what we're doing here: find /lib/modules/2.6.18-92.el5PAE -name '*.ko' will output a list of all matching files, i.e. one line of output for each .ko file. Count the lines with wc -l, and you have a count of how many .ko files there are. For each .ko file, there should be 1 line in modules.dep to say what that file's dependencies are. So, in the absence of comments and blank lines, the number of lines in modules.dep should equal the number of .ko files.
What I suspect is, the modules.dep that is shipped in the initrd has entries for all the .ko files that are shipped in the main release (i.e. far more lines than there are .ko files in the initrd). I have no idea why they have done it that way, but it might be important to preserve it.
ASKER
AndersBiro

Aha, "cat /tmp/initrd/modules/modules.dep | wc -l" did now generate the number 441

"find /lib/modules/2.6.18-92.el5PAE -name '*.ko' | wc -l" does however result in 1173 which is quite a difference so can this problem be dealt with?
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
AndersBiro

Hello, the first diff after  depmod did not prove any difference at all and then I did a rpm -ivh [driver.rpm] and another depmod but afterwards "modules.dep.orig modules.dep" did not result in any differences.  Is this a problem?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
AndersBiro

I do not know whether it is relevant but if i try to uninstall with command "rpm -e [driver.rpm] I get
"error: package xxxxxx is not installed"

However, if a try to reinstall the package using "rpm -ivh" I get "package xxx is already installed" so perhaps this indicates and installation problem? Or perhaps not relevant to why I do not get a diff above?
Duncan Roe

An empty diff is what we want! That means the files are identical. I can't help with the RPM nonsense - I never use it. I think you miss off the .rpm suffix when removing though. If the package is installed, copy over / edit files as I posted in http:#a34376474
ASKER
AndersBiro

Well, since I could not find any diff prior to after the driver installation I simply did the following:

1. Copy extracted NIC *.ko files to /tmp/lib/modules/2.6.18.-92.el5/i686

2. Copy /sbin/bnx2id to /tmp/initrd/sbin

So what is the next step please?

I might emphasize that no new lines were generated after new depmod after driver installation but perhaps this is fine?
Your help has saved me hundreds of hours of internet surfing.
fblack61
Duncan Roe

No - it's not fine. Sorry, I didn't pick up from your previous post that there was no change to modules.dep after you installed the new modules (.ko files) - something is wrong there. Unless, that is, the modules were there already - could that have been the case? rpm would have run depmod as part of the install.
If you use rpm to remove the slipstream driver, modules.dep should change. Please try that - if it doesn't change then re-run depmod and re-check. I was a bit short regarding rpm last night - when you install a package, you have to give rpm the name of the file containing the package. That name is usually the package name followed by .rpm. Once the package is installed, you must give rpm the package name, i.e. no .rpm suffix.

Please also post drivers.rpm so I can experiment.
ASKER
AndersBiro

Duncan Roe

Will look at it when I get time (might be a few days - back at work this week and work Xmas function tonight). Meanwhile, please try rpm -e netxtreme2-5.2.55-1.i386; if that works for you then re-run depmod and diff modules.dep.orig modules.dep as before
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
AndersBiro

This is rather troublesome as I still cannot notice any differences, I did the following:

1. Uninstall existing driver using rpm -e netxtreme2-5.2.55-1.i386
2. mv modules.dep modules.dep.orig       under /lib/modules/2.6.18-92.el5
3. depmod
4. diff modules.dep.orig modules.dep gives no diff
5. install driver
6. new depmod - both files are same identical

However, I did notice something that might be of relevance and that is that the driver package did install all *-ko files to /lib/modules/2.6.18-92.el5PAE/updates/ while I did the depmod from /lib/modules/2.6.18-92.el5 which includes all modules.depmod files while  /lib/modules/2.6.18-92.el5PAE/ is empty with the exception of a updates folder containing the new .ko files.

The updates folder under /lib/modules/2.6.18-92.el5 is however empty.

Clearly I think the new modules is not installed in the right path so should I copy the  /lib/modules/2.6.18-92.el5PAE/ updates contents to the empty  /lib/modules/2.6.18-92.el5\updates or what do you think is going on?






Duncan Roe

This explains the depmod anomaly but raises a new issue. I assumed you were running the same Linux version as you were installing but it seems you are not.
No you can't copy / move the modules - they will only work with the exact Linux they were built for. That is, unless the entire system was built using module versioning but I don't know whether Red Hat does that. You will be able to discover that if you can find the .config for your current kernel. Look for CONFIG_MODVERSIONS. This is the help from make xconfig:
Module versioning support (MODVERSIONS)

CONFIG_MODVERSIONS:

Usually, you have to use modules compiled with your kernel.
Saying Y here makes it sometimes possible to use modules
compiled for different kernels, by adding enough information
to the modules to (hopefully) spot any changes which would
make them incompatible with the kernel you are running. If
unsure, say N.
By the way, it doesn't matter in which directory you are when you run depmod - in the absence of a version argument it wall always work on /lib/modules/$(uname -r).
You need to install /lib/modules/2.6.18-92.el5PAE complete, from wherever you have it now. Next run depmod 2.6.18-92.el5PAE. Rename modules.dep, install the Slipstream update, re-run depmod 2.6.18-92.el5PAE and compare.
I'm assuming here that that is the version you are installing. If you are installing some other version, you need to rebuild the NIC driver against that version.
ASKER
AndersBiro

Aha, the problem was that I have only sporadic access to the server in question so I was using a virtual machine in order to prepare the initrd.img and as I built the driver on the hardware server that should explain the different directories so I guess I should just repeat the same process on the physical server?
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Duncan Roe

Yes. You really would do well to bring a problem server back to your office so you could work on it at will. With the timezone difference, you're only getting 1 answer a day from me (except if I happen to stay up late) so you're still looking at weeks to get through. Here in Australia, Christmas is in summer so I'll be away a bit over the next few weeks. Are you happy to persist? I get the feeling that this is all a bit new to you.
Duncan Roe

Or at least put up an exact copy of the server on another VM
ASKER
AndersBiro

Yes, this is indeed new for me and in case I would succeed I wonder what the next step is after doing a successful depmod difference, identifying the new lines in modules.dep and modifying the new lines to existing format and adding the new driver *.ko files to other *.ko directory in /lib/modules/2.6.18-92.el5

I suppose I should create a new initrd.img from  /lib/modules/2.6.18-92.el5 and replace the one on the USB stick but how? Thanks!
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Duncan Roe

OK - working on that. Just realised that for testing you will need a physical system - a VM won't have the new NIC card.
Duncan Roe

Remember to work on /lib/modules/2.6.18-92.el5PAE
Leave the new modules.dep in that directory as_is.
Add the modules to the i686 directory in /tmp/lib/modules/2.6.18-92.el5PAE.
I think you had better add /sbin/bnx2id to /tmp/initrd/sbin as I mentioned before.
Reformat the new modules.dep lines to match the format of those in the modules.dep in /tmp/initrd, and append the reformatted lines to that file.
Create a new modules.cgz. I need to research that a bit - will post when I'm done. Haven't sent Xmas cards yet though (what I should be doing tonight).
ASKER
AndersBiro

OK, merry christmas.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
ASKER
AndersBiro

Hello, I decided to do the process all over from the beginning and did build the driver from scratch to 2.6.18-92.el5PAE and uname -a shows that it is the right version and installing the drivers copies them to the right /lib-modules/2.6.18-92.el5PAE folder where also the depmod files resides.

This is all very well but doing "cat /tmp/initrd/modules/modules.cgz | gzip -d | cpio -idmv" does generate a "2.6.18-92.el5" folder under modules instead and hence of course I cannot verify with "depmod -b /tmp"as it looks for the "2.6.18-92.el5PAE" path instead.

I did copy the initrd.img directly from the DVD media and to the USB stick which installed just fine so hopefully you will be able to help me out when you are back. Thanks!
ASKER
AndersBiro

I did simply just change the folder name and now I was able to progress to
modules.init.dep.txt
ASKER
AndersBiro

I accidently pressed submit so I will continue here:

This time depmod did generate addition lines after installing the new RPM driver and accordingly to comment #34376474 and I would add the new files to "/tmp/initrd/modules/modules.dep" after formatting them to the original initrd format.

I did a diff between "/lib/modules/2.6.18-92.el5PAE" prior and after the driver installation and added it to the modules.dep in initrd but I must admit I got stuck here.

The initrd modules format:
"qla4xxx: scsi_transport_iscsi scsi_mod"

Does look nothing like the new lib modules:
"/lib/modules/2.6.18-92.el5PAE/updates/bnx2.ko:"

Just removing path and *.ko does not seem to cut it so do you know how to change the format? Thanks!



modules.dep.txt
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Duncan Roe

Renaming the folder to do the an install test is OK but it won't fly. The memory addresses inside the el5PAE will not match those inside el5. Can you put up a VM running el5 by installing it from the DVD? You really need to work on that version, if that's what you plan to install.
Duncan Roe

I've just noticed something really odd about modules.init.dep. There are no lines for modules with no dependencies. But, the line count still matches the number of modules. This is achieved by having duplicate lines, e.g. there are 2 lines vfat: fat but no line for fat. I cannot think how you would persuade depmod to generate a file like that. Needs more investigation but I don't have time right now. I wonder if there's anything on Google - could you have a look for me?
Merry Christmas
ASKER
AndersBiro

I found it a bit strange that the operating system and NIC drivers were installed for el5PAE but the extracted "modules.cgz " from the corresponding initrd.img resulted in a el5-folder instead.

Nevertheless, I am actually having two years leave of absence (to Australia as a matter of fact) after new years eve and I do not think we will finalize this before the end of the year so I had a different strategy in mind.

The original problem was that the automatic kickstart USB installation did not include NIC drivers and so it was not possible to add it manually afterwards as it must be accessed remotely from the network.

What I had in mind was that perhaps the rpm package can be installed in the kick-start postinstall script instead basically adding "rpm -ivh driver.rpm" but so far i have not been that successful.
For starters the module is not loaded after installation but it seems you can use modprobe for such purposes?
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Duncan Roe

I am not aware of a mainstream facility for modprobe to understand RPMs but possibly RedHat have put it in their distributions.
I'm just back in Melbourne for a day so not able to help much - was thinking myself that it'd be good to find the scripts that build the initrd. If you can find them, you might get home.
What parts of Australia will you be visiting?
2 years leave sounds awesome - are you in academia?
gheist

... still waiting for PCI ID of a mystery adapter....
ASKER
AndersBiro

I suppose the PCI ID is the one attached?
lspci.txt
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER
AndersBiro

As a matter of fact I plan to do my masters in Tasmania and I previously I did spend three years in Melbourne so it will not be completely unfamiliar.

Regarding the issue it seems as I am slowly doing progress but in order to save time I wonder how you would write a script to automatically set static IP settings to an adapter?
The reason is that I am doing automatic install using kickstart and since the NIC is not available during the installation boot it has to be set afterwards in the kickstart post-install part.
ASKER
AndersBiro

It seems as I am doing progress as I have copied the *.ko file to the /lib/modules/.../drivers/net directory and after doing depmod -a the NIC seems to work fine after reboot.

The question is just why reboot is necessary and if this can be circumvented? Adding "depmod -a" and reboot in the post-install kickstart script did not seem to do any good either.
ASKER CERTIFIED SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Duncan Roe

The reboot runs init scripts which can now see the NIC. You could perhaps re-run these script after depmod -a without rebooting, but it could get messy depending on how much the scripts managed to do last time.
Good result - well done!
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ASKER
AndersBiro

Solved myself