RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 463558 - [LTC 6.0 FEAT] 201137:Overriding of built-in kernel modules during install
Summary: [LTC 6.0 FEAT] 201137:Overriding of built-in kernel modules during install
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: All
high
high
Target Milestone: alpha
: 6.0
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 356741
TreeView+ depends on / blocked
 
Reported: 2008-09-23 21:21 UTC by IBM Bug Proxy
Modified: 2009-09-16 17:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-21 20:38:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description IBM Bug Proxy 2008-09-23 21:21:00 UTC 
=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-16 18:03 EDT
1. Feature Overview:
Feature Id:	[201137]
a. Name of Feature:	Overriding of built-in kernel modules during install
b. Feature Description
RHEL5 (pre 5.2) did not allow overriding modules at install time.  This functionality is often
required to allow vendor supported drivers the ability to be used at install time (via a DUD with
warm xfer agreements in place).    This is covered by Red Hat bugzilla: 
https://bugzilla.redhat.com/show_bug.cgi?id=233992

2. Feature Details:
Sponsor:	xSeries
Architectures:
x86
x86_64

Arch Specificity: Purely Common Code
Affects Installer: Yes
Delivery Mechanism: Request Red Hat development assistance
Category:	xSeries
Request Type:	Installer - Enhancement from Distributor
d. Upstream Acceptance:	No Code Required
Sponsor Priority	1
f. Severity: High
IBM Confidential:	no
Code Contribution:	no
g. Component Version Target:	module-init-tools

3. Business Case
Several request have occurred as to why this functionality is not present.  If an in box driver does
not support a particular chipset we need to have a solution for our hardware.  This is typically
handled as a DUD with a warm xfer agreement with Redhat.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Monte Knutson, mknutson.com, 877-894-1495

Technical contact(s):
Kevin Stansell, kstansel.com
Chris McDermott, mcdermoc.com

IBM Manager:
Julio Alvarez, julioa.com
Comment 1 Bill Nottingham 2008-10-02 19:53:23 UTC 
I believe this is more of an anaconda issue.
Comment 2 Chris Lumens 2009-05-19 17:43:13 UTC 
How does the driver update disk not provide this functionality?  It seems to me that's exactly what it is designed to do - allow you to use a new kernel driver that includes support for a new piece of hardware that the driver we shipped with did not.  What more is required here?
Comment 3 IBM Bug Proxy 2009-09-16 17:31:00 UTC 
------- Comment From lcm.com 2009-09-16 13:29 EDT-------
Evidently, this has already been fixed post RHEL5.2/3. So, as long as that remains true for the RHEL6 installer, then there's nothing to do here and this can be closed.
Note You need to log in before you can comment on or make changes to this bug.