[syslinux] PXE, Intel, and FC4 problems
strange at nsk.no-ip.org
Thu Aug 2 02:59:32 PDT 2007
On Wed, Aug 01, 2007 at 11:00:44AM -0700, Kevin G. J. Freels wrote:
> > 1. Expand the FC4 initrd (it should be a compressed ext2 image or a
> > compressed cpio archive);
> > 2. Expand the file modules/modules.cgz. It's a compressed cpio archive;
> > 3. Replace the original e1000 driver with the one that works;
> > 4. re-create the file modules.cgz (cpio -Hnewc | gzip > modules.cgz);
> > 5. re-create the initrd;
> > 6. save the new iso or replace the initrd in the tftp server.
> I actually did all that (several times, I learned that the initrd
> changed from the ext2 image to a cpio archive after FC2). The
> modules.cgz has op hex codes for the cards based (I think) on the card
modules.cgz only has the modules object files. For upgrading, only
replacing the file is needed. Be sure to keep the structure, though
> I tried using the one that was included in FC4 and the one
> that was included with FC6, but neither worked.
> Without getting into serious hardware specs, I have no idea how to get
> the information for the op code I need for the correct entry in the
> modules.cgz file for that rev of the card.
Only if new PCI IDs are supported by the driver do you need to update
the other module* files:
Add (if not exists) to module-info:
Add (if not exists) to modules.dep:
<dependencies> can be found with: modinfo <driver> | grep depends
For modules.pcimap, add the new module to an existing
lib/modules/<version>, run depmod -a <version>, and update the entries
in modules.pcimap for the module with the ones in the new
I think that should be enough.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the Syslinux