RE: Adding drivers

> From: Vratislav Podzimek [mailto:[email protected]]
> Sent: 20 December 2011 13:54
> On Tue, 2011-12-20 at 12:50 +0000, Moray Henderson wrote:
> > On the point of releasing the CentOS 5-based system I've spent the
> last 8
> > months developing, I find the manufacturers of the hardware it was
> designed
> > for have changed their specs and it won't install any more.  Grrr.
> >
> > I now have kernel modules for the relevant hardware - does anyone
> know how
> > to build a driverdisk?  So far everything I've tried results in
> Anaconda
> > complaining "can't find either driver disk identifier, bad driver
> disk".
> For RHEL5, there is the ddiskit tool which could help you. See
> http://dup.et.redhat.com/ddiskit/ for more details.

Thanks for that pointer - exactly what I need.  I did notice a few things, though: 

The "latest version", ddiskit-0.9.9, provides "kernel-modules = ${verrel}${variant}" in the rpms it builds.  The el5 driver builds from elrepo.org seem to be built from a different ddiskit which provides "kabi-modules" instead.  Is there documentation to say which is correct for which distro release?

ddiskit-0.9.9 supports the new rpm form of driver disk, and the release notes for RHEL 5.1 say Anaconda supports it - but looking at the source for anaconda-11.1.2.224 (CentOS 5.6) and anaconda-11.1.2.242 (CentOS 5.7) I don't see any of the code for it.  Is that an RHEL-only feature?

The docs/anaconda-release-notes.txt file for both releases states you can use a supplemental driver disk image called drvnet.img to supply extra network device drivers.  Again, the only occurrences of "drvnet" anywhere in the source are anaconda-release-notes.txt and ChangeLog.  Are you still supposed to be able to include supplemental drivers with your install media?


Moray.
“To err is human; to purr, feline.”


_______________________________________________
Kickstart-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/kickstart-list