Bug 113195

Summary: Hauppauge PVR-350 not autodetected
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Dan Elder <delder>
Component: InstallationAssignee: Steffen Winterfeldt <snwint>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Enhancement    
Priority: P5 - None CC: lslezak
Version: Beta 3   
Target Milestone: ---   
Hardware: i686   
OS: All   
Whiteboard:
Found By: Third Party Developer/Partner Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Dan Elder 2005-08-25 23:58:07 UTC
I have a system with a PVR-350 card in it for tv capture that is not detected by
the installation in yast or anytime thereafter. The kernel module (ivtv) is
included and works just fine for it, however.  The firmware for the card isn't
included (I imagine for legal reasons) but everything else works just fine after
a "modprobe ivtv"

hwinfo identifies it as:
17: PCI 0a.0: 0400 Multimedia video controller
  [Created at pci.277]
  UDI: /org/freedesktop/Hal/devices/pci_4444_803
  Unique ID: bSAa.imWknO0JzYD
  SysFS ID: /devices/pci0000:00/0000:00:0a.0
  SysFS BusID: 0000:00:0a.0
  Hardware Class: graphics card
  Model: "Hauppauge computer works WinTV PVR-350"
  Vendor: pci 0x4444 "Internext Compression Inc"
  Device: pci 0x0803 "iTVC15 MPEG-2 Encoder"
  SubVendor: pci 0x0070 "Hauppauge computer works Inc."
  SubDevice: pci 0x4000 "WinTV PVR-350"
  Revision: 0x01
  Memory Range: 0xe8000000-0xebffffff (rw,prefetchable)
  IRQ: 10 (no events)
  Module Alias: "pci:v00004444d00000803sv00000070sd00004000bc04sc00i00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

lspci -vv

0000:00:0a.0 Multimedia video controller: Internext Compression Inc iTVC15
MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc. WinTV PVR-350
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (32000ns min, 2000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at e8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Comment 1 Ladislav Slezák 2005-08-26 07:31:18 UTC
hwinfo identifies the card as "graphics card" not as "tv card".
Comment 2 Ladislav Slezák 2005-08-26 08:46:08 UTC
I just have updated yast tv module to offer also ivtv and saa7* drivers from
extra kernel driver directory in manual card configuration. The fix is included
in yast2-tv-2.12.6.

You will need to select "ivtv" driver manually until hwinfo reports the correct
driver.
Comment 3 Steffen Winterfeldt 2005-08-29 15:12:44 UTC
added as dvb card   
   
Gerd, do you have an id list of the other boards supported by ivtv? 
Comment 4 Gerd Hoffmann 2005-09-01 13:03:15 UTC
No, and modinfo doesn't list them either :-/

Probably it's hidden somewhere in the sources.  I think you don't have to match
the subsystem ID, pci id should be good enougth, IIRC ivtv drives all of them.

Ah, and it isn't a dvb card, it's a analog card with hardware mpeg encoder.
Comment 5 Steffen Winterfeldt 2005-09-01 13:09:46 UTC
Yes, but you want to treat it as DVB card, or not? 
Comment 6 Gerd Hoffmann 2005-09-01 15:00:11 UTC
Well, partly, when it comes to recording it is more like a dvb card (you'll get
a mpeg stream from the hardware and basically just have to put it to disk). 
Tuning is not different from non-compressing analog tv hardware like bttv cards
though.  Also pure dvb-focused apps like vdr don't support these cards.  I'd
tread them as analog tv cards ...
Comment 7 Steffen Winterfeldt 2005-09-01 15:40:51 UTC
Ok, I'll make it an analog card, then. Ladislav, is that ok with you? 
Comment 8 Steffen Winterfeldt 2005-09-02 13:56:10 UTC
Reporting all cards from ivtv-cards.c now.