Bug 448161
Summary: | e100 module missing after kernel upgrade | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Fales <redhat.com> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | nhorman, roland |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-24 01:14:21 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
Peter Fales
2008-05-23 20:22:39 UTC
The file /lib/modules/2.6.25.3-18.fc9.i686/kernel/drivers/net/e100.ko does exist in a proper installation. Check rpm -V kernel and that the file is there. If it is, does "modprobe e100" give any errors, or messages in dmesg? Sorry - that's something I should have checked. Yes, rpm -V shows that lots of files are missing. I'm not sure what happened. I jumped to conclusions because the problem showed up right after the "yum update" and there were no obvious problems or errors in the update process. It seems like there still may be a bug buried here somewhere, but it's not this one. Never mind! |