|
Bugzilla – Full Text Bug Listing |
| Summary: | mirovideo TV card doesn´t work | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Stather <kontakt> |
| Component: | Installation | Assignee: | Kay Sievers <kasievers> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | lslezak |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | YaST2 logs | ||
|
Description
Michael Stather
2005-09-28 15:16:13 UTC
I just rebooted several times and now there´s a "bt848 video capture" detected by YaST (I don´t know why it didn´t work before). But when I try to configure it, when I clock on "search channels" I get the following error: vbi: open failed [/dev/vbi] and no channels are detected. I seached for a /dev/vbi and there´s only /dev/vbi0 Please attach y2logs (http://www.opensuse.org/Bug_Reporting_FAQ#YaST) and 'hwinfo --tv' oputput. Michael, please also add hwinfo (see http://www.opensuse.org/Bug_Reporting_FAQ#YaST) michi:/home/michael # hwinfo --tv
08: PCI 09.0: 11200 TV Card
[Created at pci.277]
UDI: /org/freedesktop/Hal/devices/pci_109e_350
Unique ID: WL76.ei6eMzKDZY3
SysFS ID: /devices/pci0000:00/0000:00:09.0
SysFS BusID: 0000:00:09.0
Hardware Class: tv card
Model: "Brooktree Bt848 Video Capture"
Vendor: pci 0x109e "Brooktree Corporation"
Device: pci 0x0350 "Bt848 Video Capture"
Revision: 0x12
Driver: "bttv"
Memory Range: 0xcffff000-0xcfffffff (rw,prefetchable)
IRQ: 10 (no events)
Module Alias: "pci:v0000109Ed00000350sv00000000sd00000000bc04sc00i00"
Driver Info #0:
Driver Status: bttv is active
Driver Activation Cmd: "modprobe bttv"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Created attachment 51144 [details]
YaST2 logs
btw: I don't maintain v4l any more. I can't see why /dev/vbi is missing. There is a udev rule in /etc/udev/rules.d/50-udev.rules which creates the /dev/vbi => vbi0 symlink, so just opening /dev/vbi should do fine. It's also possible to explicitly specify the device (see "scantv -h"). I have no idea either. Could there be a bug in udev or the 50-udev.rules? I just have fixed the yast module to use /dev/vbiN and /dev/videoN devices instead of default (it's needed anyway to support more TV cards). (yast2-tv-2.13.2) My system has the vbi link, I don't know where maight be a problem... Kay? Udev problem? I can't tell without access to the system. Should be fixed, regarding to comment #11. |