Bug 15141
| Summary: | No full configuration of TV cards | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Enrico Scholz <rh-bugzilla> |
| Component: | kudzu | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | rvokal |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-12-15 00:37: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
Enrico Scholz
2000-08-02 18:22:29 UTC
That's the biggest problem; those modules aren't necessarily used by everything, and the only way to find out is to scan the i2c bus, which we don't currently have code for. The line 'below bttv tuner msp3400' should be obligatorily in most cases. With bttv 0.7 (only kernel 2.4 or heavily patched 2.2) this setting can be omitted, but Pinstripe needs it, Until kudzu has i2c code I am suggesting to put commented templates into /etc/modules.conf, so the user will be pointed to a list of options (the src/MODULES file of http://me.in-berlin.de/~kraxel/v4l/bttv-0.6.4h.tar.gz or CARDLIST & Insmod-options of http://me.in-berlin.de/~kraxel/v4l/bttv-0.7.37.tar.gz). Else the user won't have sound, can not change the channel and hasn't a clue where the flaw lies. Btw: a pitfall being difficulty to find is to use tuner-type 2 instead of 5. Some Hauppauge cards are working fine with both settings but with one exception: _exactly_ 1 channel (SE7 in european freqtab) can not be tuned in with type 2. Perhaps this should be mentioned seperatedly somewhere in the documentation... |