|
Bugzilla – Full Text Bug Listing |
| Summary: | Tv card changes are only valid after a restart | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michael Stather <kontakt> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Alpha 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-10-05 18:50:52 UTC
Please be a little more verbose. What module do you mean? Are we talking about a YaST-setup? Then please read: http://www.opensuse.org/Bug_Reporting_FAQ#YaST Besides the y2logs, the output of ``hwinfo --tv'' (as root) would also be helpful. hwinfo output:
r098088:/home/michael # hwinfo --tv
22: PCI 406.0: 11200 TV Card
[Created at pci.277]
UDI: /org/freedesktop/Hal/devices/pci_109e_350
Unique ID: +QnG.ei6eMzKDZY3
Parent ID: H0_h.Xi7km9jxxp1
SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:04:06.0
SysFS BusID: 0000:04:06.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: 0xbfeff000-0xbfefffff (rw,prefetchable)
IRQ: 7 (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
Attached to: #6 (PCI bridge)
I didn´t configure the default "bt848 video capture" device in YaST but added a
"Miro PCTV pro" device (the card isn´t detected correctly). There´s no /dev/vbi*
created until after a restart.
Created attachment 51634 [details]
YaST2 logs
My guess it that there may be problem related to loading the module, I will check the logs. |