Bug 619367
Summary: | weak-modules doesn't find symvers file | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Wilck <martin.wilck> |
Component: | driver-update-program | Assignee: | Jon Masters <jcm> |
Status: | CLOSED NOTABUG | QA Contact: | Qian Cai <qcai> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | bzeranski, gasmith, ltroan, peter.pols, rpacheco, tao |
Target Milestone: | rc | Keywords: | RHELNAK |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-03 14:05:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Wilck
2010-07-29 11:57:24 UTC
opened issued tracker 1201243 for this bug. This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** Martin, are you invoking weak-modules directly? It looks like you're calling it with the following value for the uname-r: 2.6.32-52.el6 Actually, in RHEL6, it should always include the architecture: 2.6.32-52.el6.x86_64 For example. Can you confirm, by looking at rpm -q --scripts kernel that your kernel is calling the correct script options? If you are doing this manually, please let me know why you need to call it without the full uname value. Jon. My bad, I'm sorry. User error :-/ I had been wondering why no weak-modules links had been created, and in order to find out, called weak-modules by hand - wrongly. I apologize for the noise. Per comment #6, closing as not a bug. |