| Summary: | sys-kernel/gentoo-sources-2.6.27-r5 no longer works with Hauppauge WinTV 150 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Robert Bradbury <robert.bradbury> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | N/A | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Modules loaded at time when mplayer does not work | ||
|
Description
Robert Bradbury
2008-12-15 22:37:03 UTC
Created attachment 175376 [details]
Modules loaded at time when mplayer does not work
I had hoped that by upgrading to 2.6.27-gentoo-r5 I would be able to get *BOTH* my Hauppauge WinTV PVR 150 working *and* my HP Webcam (Omnivision 519) working. But instead it appears that both have degraded to a non-working state.
See also Bug #251076 regarding the PCI/USB devices present. There is no problem with respect to the OS properly identifying that there may be 2 video input devices (video0 = PSI Hauppauge WinTV 150 input; video1 = USB OmniVision 519 WebCam). The problem is that valid output can be read from neither of them. Robert, you need to be much more precise about the particular kernel versions that worked for you and which did not. Otherwise it's getting really hard, if not impossible, to help you track this down. So, you'll need to provide information like * latest working kernel * earliest failing kernel * does (still not) work on 2.6.28-rc Also, when reproducing the bug on earliest failing kernel, make sure that it does not interfere with your other problem (tuner not detected), i. e. use a kernel with (cx88) driver build as module. Thanks, Axel Maybe your problem is just a v4l <--> v4l2 compatibility issue. Have you tried the v4l2 driver of mplayer/mencoder? According to the demsg output you've attached to the original bug from which this has been split off, your cx88 device is registered as a v4l2 device on your 2.6.26 kernel. If using the v4l2 driver doesn't work you can try to use "lib4vl". See http://freshmeat.net/projects/libv4l/?branch_id=76006&release_id=28947 for further details and on how to "insert the compatibility layer". BTW: libv4l is in portage. Argh, seems I've confused your report with another user's report. Anyway, what's needed is * .config + dmesg from (latest) working kernel * .config + dmesg from (earliest) failing kernel and in case you want to take the issue upstream, you'll need to test with 2.6.28-rcX to see whether the problem has alreayd been fixed. Thanks and sorry for the confusion Axel Please reopen when the info requested in comment #5 has been provided. |