SuSE 9.3 is not seeing my PVR-350 capture card

[David Kramer]

I just put a PVR-350 capture card in my SuSE 9.3 box.  When I brought it up
again and started X, I got a "Found new hardware" box recognizing it as a
PVR-350.

However, when I went to YaST and clicked on TV Tuner in Hardware, it didn't
automatically find it.  I was able to add it manually.

No other commands see it though:

uninew:~ # l /dev/video*
lrwxrwxrwx  1 root root        6 Aug  6 16:03 /dev/video -> video0
crw-rw-rw-  1 root video  81,  0 Mar 19  2005 /dev/video0
crw-rw----  1 root video  81,  1 Mar 19  2005 /dev/video1
crw-rw----  1 root root  171, 16 Mar 19  2005 /dev/video1394
crw-r--r--  1 root root  171, 16 Aug  6 17:52 /dev/video1394-0
crw-rw----  1 root video  81,  2 Mar 19  2005 /dev/video2
crw-rw----  1 root video  81,  3 Mar 19  2005 /dev/video3

uninew:~ # lsmod | egrep  '(v4l|vttv)'
v4l2_common             5760  1 bttv


uninew:~ # dmesg | grep bttv
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture


However,
uninew:~ # xawtv
This is xawtv-3.94, running on Linux/i686 (2.6.11.4-21.9-default)
can't open /dev/video0: No such device
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: No such device
v4l2: open /dev/video0: No such device
v4l: open /dev/video0: No such device
no video grabber device available


KWinTV produces diferent output, but it's meaningless to me.
uninew:~ # kwintv
kbuildsycoca running...
ALSA lib control.c:739:(snd_ctl_open_noupdate) Invalid CTL
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
proxy_msg: connect: error 2, No such file or directory
kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connection via
socket failed, server not running.
Try to open V4L2 0.20 VBI device, libzvbi interface rev.
  $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
kdetv: WARNING: VBIDecoder: vbi_capture_v4l2_new error: Cannot open
'/dev/vbi': 19, No such device.
Try to open v4l vbi device, libzvbi interface rev.
  $Id: io-v4l.c,v 1.28 2004/12/30 02:23:59 mschimek Exp $
/dev/vbi permissions: user=1000.33 mode=020600, I am 0.0
kdetv: WARNING: VBIDecoder: vbi_capture_v4l_new error: Cannot open
'/dev/vbi': 19, No such device.
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
proxy_msg: connect: error 2, No such file or directory
kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connection via
socket failed, server not running.
Try to open V4L2 0.20 VBI device, libzvbi interface rev.
  $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
kdetv: WARNING: VBIDecoder: vbi_capture_v4l2_new error: Cannot open
'/dev/vbi0': 19, No such device.
Try to open v4l vbi device, libzvbi interface rev.
  $Id: io-v4l.c,v 1.28 2004/12/30 02:23:59 mschimek Exp $
/dev/vbi0 permissions: user=1000.33 mode=020600, I am 0.0
kdetv: WARNING: VBIDecoder: vbi_capture_v4l_new error: Cannot open
'/dev/vbi0': 19, No such device.
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
proxy_msg: connect: error 2, No such file or directory
kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connection via
socket failed, server not running.
Try to open V4L2 0.20 VBI device, libzvbi interface rev.
  $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
kdetv: WARNING: VBIDecoder: vbi_capture_v4l2_new error: Cannot open
'/dev/vbi1': 19, No such device.
Try to open v4l vbi device, libzvbi interface rev.
  $Id: io-v4l.c,v 1.28 2004/12/30 02:23:59 mschimek Exp $
/dev/vbi1 permissions: user=0.33 mode=020660, I am 0.0
kdetv: WARNING: VBIDecoder: vbi_capture_v4l_new error: Cannot open
'/dev/vbi1': 19, No such device.
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
proxy_msg: connect: error 2, No such file or directory
kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connection via
socket failed, server not running.
Try to open V4L2 0.20 VBI device, libzvbi interface rev.
  $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
kdetv: WARNING: VBIDecoder: vbi_capture_v4l2_new error: Cannot open
'/dev/vbi2': 19, No such device.
Try to open v4l vbi device, libzvbi interface rev.
  $Id: io-v4l.c,v 1.28 2004/12/30 02:23:59 mschimek Exp $
/dev/vbi2 permissions: user=0.33 mode=020660, I am 0.0
kdetv: WARNING: VBIDecoder: vbi_capture_v4l_new error: Cannot open
'/dev/vbi2': 19, No such device.
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
proxy_msg: connect: error 2, No such file or directory
kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connection via
socket failed, server not running.
Try to open V4L2 0.20 VBI device, libzvbi interface rev.
  $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
kdetv: WARNING: VBIDecoder: vbi_capture_v4l2_new error: Cannot open
'/dev/vbi3': 19, No such device.
Try to open v4l vbi device, libzvbi interface rev.
  $Id: io-v4l.c,v 1.28 2004/12/30 02:23:59 mschimek Exp $
/dev/vbi3 permissions: user=0.33 mode=020660, I am 0.0
kdetv: WARNING: VBIDecoder: vbi_capture_v4l_new error: Cannot open
'/dev/vbi3': 19, No such device.
kdetv: WARNING: [VBIDecoder::restart()] no permission to access device
kdetv: WARNING: MainWindow::setupInfraRed(): Lirc not available
kdetv: WARNING: SaverControl: Error in DCOP communication. Unable to disable
KDE Screensaver.

uninew:~ # l /dev/vbi*
lrwxrwxrwx  1 root  root        4 Aug  6 16:03 /dev/vbi -> vbi0
crw-------  1 david video 81, 224 Mar 19  2005 /dev/vbi0
crw-rw----  1 root  video 81, 225 Mar 19  2005 /dev/vbi1
crw-rw----  1 root  video 81, 226 Mar 19  2005 /dev/vbi2
crw-rw----  1 root  video 81, 227 Mar 19  2005 /dev/vbi3




What can I look at next?