Bug 102933 - Install did not detect pcHDTV 2000 HDTV card
Summary: Install did not detect pcHDTV 2000 HDTV card
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 1
Hardware: i686 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Steffen Winterfeldt
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 02:26 UTC by Doug Beattie
Modified: 2005-09-02 12:43 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug Beattie 2005-08-09 02:26:39 UTC
The install did not detect a pcHDTV 2000 HDTV card. I choose to add it from a
list at the end of the installation. It was not added correctly.
The ID for this card is 7063:2000
Similarly, a pcHDTV 3000 card, ID 7063:3000 was not detected nor handled correctly.
The new driver for DVB should be in this kernel to support this.

BTW - lspci only shows the following:
0000:00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub
(rev 02)
0000:00:01.0 PCI bridge: Intel Corporation 82875P Processor to AGP Controller
(rev 02)
0000:00:03.0 PCI bridge: Intel Corporation 82875P/E7210 Processor to PCI to CSA
Bridge (rev 02)
0000:00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
#3 (rev 02)
0000:00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI
Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface
Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller
(rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX
5200] (rev a1)
0000:02:01.0 Ethernet controller: Intel Corporation 82547EI Gigabit Ethernet
Controller (LOM)
0000:03:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 80)
0000:03:04.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak
378/SATA 378) (rev 02)
0000:03:0c.0 Class 036e: Alacron: Unknown device 036e (rev 9e)
0000:03:0c.1 Class 0878: Alacron: Unknown device 0878 (rev 9e)
Comment 1 Ladislav Slezák 2005-08-09 06:49:15 UTC
Does hwinfo detect also HDTV cards?
Comment 2 Steffen Winterfeldt 2005-08-09 08:29:01 UTC
What should it be, a dvb card? What's the driver? 
Comment 3 Doug Beattie 2005-08-10 04:01:22 UTC
I moved the card to another PCI slot and noticed it was then physically
recognized. This is what lspci now reports:

0000:03:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
0000:03:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)

It appears you do have the modules.pcimap has a brooktree device with ffffffff
mask that is for the bttv - bt878 modules that is being used.

The Manufacture of this card is pcHDTV. It should have a vendor tag of 00007063
with a model tag of 00002000.

I'm not real skilled in this area, but it appears the dvd-bt8xx drivers are
being built and do exist on the system, but depmod -a does not build the
modules.pcimap and perhaps other files so this card will be recognized and used.

My son Brandon spoke with the owner/designer for the pcHDTV cards. They could
possibly send you a 2000 and 3000 card to try if that would be of help.

If anyone is coming to Provo after Linux World who may wish to carry these cards
back with them to Germany for you I will try to get cards for you.

It also appears the dvb driver for the cx88 that the 3000 uses is built, but I
haven't tried to install one and see if it loads properly.

I hope this info helps a littel. Please let me know what I should do next to
help get these devices recognized and working.

Thanks,
Doug
Comment 4 Ladislav Slezák 2005-08-10 07:43:52 UTC
You can use lcpsi -n to get device numbers.

Could you try to load the drives to see if they work properly with this card?

Gerd, are these HDTV cards supported in Linux?
Comment 5 Gerd Hoffmann 2005-08-10 09:14:18 UTC
Not sure about the 2000.  The 3000 should work (and is registered as dvb card in
the dvb core), driver module is cx88-dvb.
Comment 6 Doug Beattie 2005-08-10 14:33:45 UTC
Both the 2000 and 3000 model cards were developed for Linux, not windows. They
are both supported under fedora core releases and I have used the non-dvb
drivers supplied by pcHDTV in the past to get them working. The pcHDTV folks
have worked with the kernel developers to get support for the cards into the
kernel since 2.6.12. In speaking with them last night they said the 2.6.13 dvb
drivers should support the cards well.
The 2000 has both NTSC and ATSC capabilities. As I mentioned in my previous
update, it appears the depmod -a is not building the modules.pcimap file so that
is knows of this cards ID tags specifically, so a generic bttv bt878 option is
chosen instead of the dvb-bt8xx driver.
For more info see www.pchdtv.com
I can get you in touch with Jack Kelliher, the owner/designer of the cards if
you would like.
Also, These are the cards the Electronic Frontier Foundation (eff.org) speaks
about a lot and encourages US people to buy and has worked against possibly FCC
rulings to help keep the "Broadcast Flag" from becoming a reality in the US.
These cards have lots of exposure in the US.
Comment 7 Gerd Hoffmann 2005-08-10 14:54:26 UTC
Ok, so hwinfo just has to learn the Subsystem IDs to identify them correctly as
DVB cards.

The 3000 should be 14f1:8800 / 7063:3000,
the 2000 should be 109e:0878 / 7063:2000.
Comment 8 Steffen Winterfeldt 2005-08-10 14:55:42 UTC
I still don't know what the pci ids of those cards are. Could you 
attach either 'hwinfo --pci' or 'lspci -vn' or 'lspci -vx'. Something 
that has some numbers in it in any case. 
Comment 9 Steffen Winterfeldt 2005-08-10 14:56:21 UTC
Ah, ok, that should answer that. 
Comment 10 Steffen Winterfeldt 2005-08-10 15:02:15 UTC
Gerd, you're sure it isn't 14f1:8802? 
Comment 11 Gerd Hoffmann 2005-08-10 15:06:38 UTC
Yep, 8802, you are correct.
Comment 12 Steffen Winterfeldt 2005-08-10 15:14:50 UTC
should work in beta2 
Comment 13 Doug Beattie 2005-08-10 17:26:38 UTC
I could not find lcpci so I used the hwinfo --pci util. Here is the part you
should need to verify things.
------------------------------------------------------------------------------
27: PCI 30a.0: 11200 TV Card
  [Created at pci.271]
  Unique ID: d0n+.QxHJcFPZf8F
  Parent ID: 6NW+.c7JTK_YUBi2
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:0a.0
  SysFS BusID: 0000:03:0a.0
  Hardware Class: tv card
  Model: "Brooktree Bt878"
  Vendor: pci 0x109e "Brooktree Corporation"
  Device: pci 0x036e "Bt878"
  SubVendor: pci 0x7063
  SubDevice: pci 0x2000
  Revision: 0x11
  Driver: "bttv"
  Memory Range: 0xefefe000-0xefefefff (rw,prefetchable)
  IRQ: 217 (18364 events)
  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: #18 (PCI bridge)

28: PCI 30a.1: 0480 Multimedia controller
  [Created at pci.271]
  Unique ID: VLGr.QEbe+KjTQI8
  Parent ID: 6NW+.c7JTK_YUBi2
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:0a.1
  SysFS BusID: 0000:03:0a.1
  Hardware Class: unknown
  Model: "Brooktree Bt878 Audio Capture"
  Vendor: pci 0x109e "Brooktree Corporation"
  Device: pci 0x0878 "Bt878 Audio Capture"
  SubVendor: pci 0x7063
  SubDevice: pci 0x2000
  Revision: 0x11
  Driver: "btaudio"
  Memory Range: 0xefeff000-0xefefffff (rw,prefetchable)
  IRQ: 217 (18364 events)
  Driver Info #0:
    Driver Status: bt878 is active
    Driver Activation Cmd: "modprobe bt878"
  Driver Info #1:
    Driver Status: btaudio is active
    Driver Activation Cmd: "modprobe btaudio"
  Driver Info #2:
    Driver Status: btaudio is active
    Driver Activation Cmd: "modprobe btaudio"
  Driver Info #3:
    Driver Status: dvb-bt8xx is active
    Driver Activation Cmd: "modprobe dvb-bt8xx"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #18 (PCI bridge)
------------------------------------------------------------------------------
Comment 14 Doug Beattie 2005-08-10 20:49:54 UTC
I have one other question. I xawtv going to be updated to allow for ATSC
signals/channels?
At this time it knows PAL, NTSC, SECAM, and variations of these.
Comment 15 Gerd Hoffmann 2005-09-02 12:43:25 UTC
Try xawtv4.rpm (stabel/current beta) that one has dvb support and should also
work with atsc cards, assuming they are supported by the dvb subsystem of the
kernel.  ATSC support is completely untested though, and also some features are
still missing (parse ATSC-NITs for channel scanning for example).