Bug 131969 - anaconda doesn't include old style modules (.o) when building images, only new style (.ko)
Summary: anaconda doesn't include old style modules (.o) when building images, only ne...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-07 15:56 UTC by Leonardo Quijano Vincenzi
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-09-07 16:04:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Leonardo Quijano Vincenzi 2004-09-07 15:56:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040808 Firefox/0.9.3

Description of problem:
When building a custom 2.4.x kernel based distro, its modules aren't
correctly packaged in the installer images (initrd.img). The installer
tries to find (*.ko) to package the modules, even though you can
specify a 2.4 kernel in mk-images and such.

Version-Release number of selected component (if applicable):
anaconda-10.0-5

How reproducible:
Always

Steps to Reproduce:
1. Create a custom 2.4 kernel based distro.
2. Use buildinstall or mk-images to build the distro's images.
3. Check initrd.img to see there are no modules.
    

Actual Results:  The images where not created with all the
corresponding modules.

Expected Results:  Anaconda should ask, in its scripts, for the kernel
version number. If 2.6, then use the .ko suffix. If 2.4, use .o.


Additional info:

For example, in mk-images:

findmodule () {
    if [ ! -f $CACHE ]; then
        find $KERNELROOT/lib/modules/ > $CACHE
    fi
    
    grep "/$1\.ko" $CACHE
}

Comment 1 Jeremy Katz 2004-09-07 16:04:37 UTC
There are a lot of other things that won't work with that anaconda and
a 2.4 kernel as well.

2.6 kernel or higher is required for it.


Note You need to log in before you can comment on or make changes to this bug.