RHL9 Building driver disks for 2.4.20-8BOOT

Eric kernel at spirilis.net
Wed Mar 2 17:21:00 CST 2005

I finally got around to using dkms and I think I figured it out, and successfully hacked the e1000 source with
a 'redhat_driver_disk' and 'dkms.conf' file such that I can build the e1000 driver for whatever kernel/arch I need.

However, I ran into another problem that's probably more RH9-related-
I can kickstart the server just fine now with the driver disk, however once it reboots, the e1000 driver is no longer
available (I thought this would happen, seeing as I couldn't fit the 2.4.20-8smp version of the driver on the same disk
without anaconda complaining and claiming the driver disk doesn't contain any valid modules...)

This seems like an obvious problem, I'm sure there's a solution--does anyone have any ideas/pointers?

The only way out I can imagine is by writing a creative script in the %postinstall portion to copy & install the e1000
driver and DKMS over NFS, then on next boot, build the module and install it (then bring up eth0 using /sbin/ifup)...

Would it also be possible to generate a binary RPM of the e1000 driver for the intended kernel version, and specify that
in the packages portion of ks.cfg, throwing the binary RPM into our RedHat/RPMS dir on the NFS mount?


On Fri, Feb 18, 2005 at 02:13:24PM -0600, Matt Domsch put into existance:
] On Thu, Feb 17, 2005 at 03:17:29PM -0500, Eric wrote:
] > Hi-
] > This isn't too specific to the topic of Dell servers as it is RedHat Linux.  I am attempting to build my own driver disk
] > for the e1000.o driver to kickstart a PowerEdge 1850 using RedHat 9.  I have built a driver disk, however, the driver built
] > is of version 2.4.20-8smp--I need to build it for 2.4.20-8BOOT.  I almost have this feeling that I've done this before, but
] > it was over a year ago.  Does anyone have a quick tutorial on making this work?  I'm preferring not to interrupt/reboot a
] > running system if possible...
] http://linux.dell.com/dkms
] can generate the driver disk for you. You 'dkms build' once for each kernel
] you need (2.4.20-8BOOT, 2.4.20-8, 2.4.20-8smp, ...), then 'dkms
] mkdriverdisk' to generate the disk.
] Thanks,
] Matt
] -- 
] Matt Domsch
] Software Architect
] Dell Linux Solutions linux.dell.com & www.dell.com/linux
] Linux on Dell mailing lists @ http://lists.us.dell.com

More information about the Linux-PowerEdge mailing list