Just spotted that some useful info was sent to me off the kickstart list:

From: Martin Sivak [mailto:msivak@redhat.com]

Sent: 26 January 2012 11:04

Subject: Re: [Fwd: RE: Adding drivers]

Hi,

there were couple of DD versions..

Release notes for 5.1 mention new rpm version of driverdisc indeed. But

that is still the RHEL5 version (eg. containing modules.cgz,

modules.dep, modules-info and rpm files). In RHEL5, anaconda doesn't

care about RPMs, it just passes them to Yum so the used drivers are

also installed to the destination system.

There is a different format for RHEL6, we removed the modules.cgz and

accompanying files and used only RPMS. Here anaconda uses Provides:

kernel-modules to detect the RPMs it needs to look at.

ddiskit should be doing RHEL5 Driver Update disks (you can check it by

looking at the structure), because RHEL6 needs just a rpms/<arch>

directory (and /rhdd3 file) with createrepo done on it.

There is documentation about the RHEL6 format here:

http://git.fedorahosted.org/git/?p=anaconda.git;a=blob;f=docs/driverdisc.txt ;h=dee3a305f415794313327378c5d53a38e8b29103;hb=rhel6-branch

RHEL5 was more complicated because of all the files, so there is no

consistent documentation and we prefer using ddiskit tool.

From: Mike Young [mailto:myoung@wildernessvoice.com] Sent: 31 January 2012 16:29 To: Discussion of Development and Customization of the Red Hat Linux Installer Subject: Re: Driver Disk v3 format

That's very helpful to know Moray. Thank you for that added info.

Best,

Mike

From: Moray Henderson Moray.Henderson@ict-software.org Reply-To: Discussion of Development and Customization of the Red Hat Linux Installer anaconda-devel-list@redhat.com Date: Tue, 31 Jan 2012 14:47:26 +0000 To: anaconda-devel-list@redhat.com Subject: RE: Driver Disk v3 format

From: Mike Young [mailto:myoung@wildernessvoice.com] Sent: 30 January 2012 17:48

Hi, First of all, I apologize re-opening such an old thread. But while I have found some clarifications on the file system layout for the ddv3 drivers, along with some patches, I have been unable to actually find any real documentation on how to create a ddv3 driver. For example, I see the structure is as follows:

DDv3 structure

/ |rhdd3 - DD marker, contains the DD's description string /rpms | /i386 - contains RPMs for this arch and acts as Yum repo | /i586 | /x86_64 | /ppc | /...

But what I don't see is what else it might be looking for. Do I still package these folders into a .iso package? If there's some documentation on this procedure, I'd really appreciate a link to it. The search terms I'm using must be too generic and the only thing that reports anything substantive is ddv3. Unfortunately, everything leads back to this thread. Thanks!

Mike

There's been a bit of discussion of this over on kickstart-list recently J The best way to create driver disks is using ddiskit http://dup.et.redhat.com/ddiskit/ . Beware which distro you're using, though. RHEL 5.1 Release Notes state that Anaconda now supports the v3 rpm format, but the Anacondas of CentOS 5.6 and 5.7 do not contain the necessary code. I needed a JMicron(R) JMC250 PCI-E Ethernet Adapter. After fighting the Big Snake for several days, I gave up, put the kmod-jme rpm from ELRepo http://elrepo.org/tiki/tiki-index.php into my main repository and installed it via kickstart. I don'tconfigure networking until first boot, so I could get away with that.

Moray.

"To err is human; to purr, feline."

_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list