Bug 134465
Summary: | Kudzu doesn't detect my tv card | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | drago01 | ||||||
Component: | kudzu | Assignee: | Bill Nottingham <notting> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 2 | CC: | mattdm, rvokal | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2005-04-28 18:32:50 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: | |||||||||
Attachments: |
|
Description
drago01
2004-10-03 11:13:36 UTC
lspci output? Created attachment 104726 [details]
lspci output
the output of lspci -vv
Does the output of 'kudzu -p -b pci' show a class: OTHER device mapped to the saa1734 driver? (Make that saa7134, of course.) yes it does: class: OTHER bus: PCI detached: 0 driver: saa7134 desc: "Philips Semiconductors|SAA7134" vendorId: 1131 deviceId: 7134 subVendorId: 11bd subDeviceId: 002b pciType: 1 pcidom: 0 pcibus: 0 pcidev: 7 pcifn: 0 A fix added in CVS, will be in 1.1.93-1. will this fix be in a fc2 update or will it only be in fc3 ? Created attachment 104727 [details]
patch for pci.c
Here's the patch, it allows more classes to be mapped to CLASS_CAPTURE.
Probably only in FC3. Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. I just want to add that this problem has never existed in FC3 ;) |