Red Hat Bugzilla – Bug 853787
RFE:add yenta_socket.ko driver to LIVE:/isolinux/initrd0.img
Last modified: 2012-10-19 06:08:50 EDT
Description of problem: Request For Enhancement (RFE): Please add the yenta_socket.ko driver into the isolinux/initrd0.img initial RAM disk for systems that are distributed on Live media. This would facilitate using an external optical drive connected via PCMCIA (cardbus) to bootstrap and run a Live system. The yenta_socket.ko driver is needed in the initrd0.img so that a copy of initrd0.img (on harddrive accessed by GRUB, using custom boot stanza) can see the LiveOS/squashfs.img on the platter in the optical drive connected via PCMCIA.
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. mount -o ro,loop Fedora-18-Alpha-TC5-x86_64-Live-Desktop.iso /mnt
2. gzip -d </mnt/isolinux/initrd0.img | cpio --list | grep yenta
Actual results: The output from the shell pipeline is empty: there is no yenta_socket.ko driver in syslinux/initrd0.img.
(or some analogous path ending in yenta_socket.ko .)
dracut makes the live initramfs, moving there.
upstream commit ea627292383a893062f64c1c949a102d56fac4e5
dracut-024-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dracut-024-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dracut-0.24-1.fc18 is not enough. When using dracut-0.24-1.fc18.i686 as input to livecd-creator, then yenta_socket.ko is available below /lib/modules/$KVER of the running system, but is not available in /syslinux/initrd0.img. (In particular:
gzip -d < initrd0.img | cpio --list | grep yenta
does not show any 'yenta' modules in initrd0.img.) Thus I cannot put my LIVE root on a device that is accessed via PCMCIA. Does livecd-creator need to do something for me, in addition to what dracut does?
(In reply to comment #5)
> dracut-0.24-1.fc18 is not enough. When using dracut-0.24-1.fc18.i686 as
> input to livecd-creator, then yenta_socket.ko is available below
> /lib/modules/$KVER of the running system, but is not available in
> /syslinux/initrd0.img. (In particular:
> gzip -d < initrd0.img | cpio --list | grep yenta
> does not show any 'yenta' modules in initrd0.img.) Thus I cannot put my
> LIVE root on a device that is accessed via PCMCIA. Does livecd-creator need
> to do something for me, in addition to what dracut does?
Reassigning to livecd-tools. livecd-tools tries to be smarter regarding the kernel modules than dracut.
/usr/lib/python2.7/site-packages/imgcreate/live.py specifies its own set of kernel modules via "drivers+=''" which forces dracut to use only those kernel drivers instead of the default ones.
Created attachment 629620 [details]
add yenta_socket to =pcmcia in live.py
Perhaps =pcmcia should add i82092 and pd6729 also? Those are the other drivers besides yenta_socket in kernel/drivers/pcmcia .
I'm not going to go down the path of adding every module under the sun. If you want to build media with extra modules use the kickstart device command to add them in your kickstart.
dracut-024-5.git20121019.fc18 has been submitted as an update for Fedora 18.