Bug 36636
Summary: | Wrong driver loaded | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alan Cox <alan> |
Component: | kudzu | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | rvokal |
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: | 2001-05-03 15:36:04 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
Alan Cox
2001-04-19 12:10:04 UTC
i960 is now 'unknown' as of 0.99-1. Should we actively be trying to load i2o stuff for anything that claims to be i2o, or is that not stable enough yet? For the current -ac i2o should be solid for everything. There is one catch, some boards provide both i2o and 'native' interfaces. Notably the AMI Megaraid, so match on PCI idents, only take an unknown of class i2o through the i2o drivers |