+++ This bug was initially created as a clone of Bug #424531 +++ Description of problem: RHEL4.6 did not build i2c-piix4 into the kernel or as a module, although the driver patch of AMD SBX00 SMBus has been added into source. Would you please modify your config file and build i2c-piix4 as a module? So that our customer need not build the kernel source by themselves if they need the SMBus driver. They only need to load the driver module. Version-Release number of selected component (if applicable): N/A How reproducible: Always Steps to Reproduce: 1. # modinfo i2c-piix4 in RHEL4.6 2. check the config file in /boot/ Actual results: 1. No such module i2c-piix4 can be found in RHEL4.6 2. If you check the config file in the /boot/, you will find that CONFIG_I2C_PIIX4 is not set. Expected results: 1. i2c-piix4 and the description should be found when run "modinfo i2c-piix4" 2. CONFIG_I2C_PIIX4=m should be found in the config file in /boot/ Additional info: I need not provide any patch here, what you need do is to re-configure the config file with "make menuconfig" or some commands else, and select the CONFIG_I2C_PIIX4 as a module, and provide it in RHEL4.7
I checked the kernel config of RHEL4.5 again, confirmed that CONFIG_I2C_PIIX4 has been built as module in x86. But kernels for x86_64 has not built it. Can you build it too under x86_64? Is there any problem which make you disable it? Thanks
Yes, this is done and submitted to RH in the nick of time as yesterday was the code cut off date. It's a simple config change for plain x86_64, debug and xen kernels. I'll let your team handle the testing. ;) Bhavana
Sorry, my comment pertained to R5.2, ignore but agree should be done for R4.7. R4.7 as I recall has a !64BIT from a prvious issue with 64-bit kernels with no longer exist. Removing this condition and providing configs would help get this in. Bhavana
monitoring as per BZ#424531.
*** Bug 434814 has been marked as a duplicate of this bug. ***
This issue has not been fixed in the up to date kernel-2.6.9-68.17.EL.x86_64.rpm Please check and fix it, thanks.
Remove !64BIT from i2c-piix4 driver so that it will build as a module in x86_64. Seems safe to do given upstream's removal of the same flag -- at one point i2c-piix4 didn't appear on 64-bit systems and when it did eventually show up on 64-bit systems upstream removed the flag. P.
Created attachment 297775 [details] RHEL4 fix for this issue
This patch is okay to me. Thanks
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
added to RHEL4.7 release notes under "Driver Updates => General Driver Updates": <quote> i2c-piix4 kernel module is now enabled to support the AMD SBX00 SMBus. </quote> please advise if any further revisions are required. thanks!
Committed in 68.24.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
Hi, the RHEL4.7 release notes deadline is on June 17, 2008 (Tuesday). they will undergo a final proofread before being dropped to translation, at which point no further additions or revisions will be entertained. a mockup of the RHEL4.7 release notes can be viewed here: http://intranet.corp.redhat.com/ic/intranet/RHEL4u7relnotesmockup.html please use the aforementioned link to verify if your bugzilla is already in the release notes (if it needs to be). each item in the release notes contains a link to its original bug; as such, you can search through the release notes by bug number. Cheers, Don
~~~~~~~~~~~~~~ ~ Attention: ~ Feedback requested regarding this **High Priority** bug. ~~~~~~~~~~~~~~ A fix for this issue should be included in the latest packages contained in RHEL4.7-Snapshot1--available now on partners.redhat.com. After you (Red Hat Partner) have verified that this issue has been addressed, submit a comment describing the passing results of your test in appropriate detail, along with which snapshot and package version tested. The bugzilla will be updated by Red Hat Quality Engineering for you when this information has been received. If you believe this issue has not properly fixed or you are unable to verify the issue for any reason, please add a comment describing the most recent issues you are experiencing, along with which snapshot and package version tested. If you believe the bug has not been fixed, change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and bugzilla will be updated for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you Red Hat QE Partner Management
Verified with RHEL4.7 Beta (kernel 2.6.9-70.EL)
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2008-0665.html
Partners, I would like to thank you all for your participation in assuring the quality of this RHEL 4.7 Update Release. My hat's off to you all. Thanks.