From their FAQ :
http://linux.bytesex.org/xawtv/faq3.html
Q: xawtv doesn't show anything
xawtv supports a wide range of hardware. Chances are good that xawtv simply tries to talk to another device than you expect. That is a common problem with nvidia cards which have a video port (for nvidia's composite input maybe?). xawtv picks that one instead of the TV card by default.
Try "xawtv -hwscan" to get a list of devices xawtv is aware of. Every device you can ask xawtv to use has the command line option needed to do that listed in brackets. The first device in the list is the default which xawtv will use if no other device is specified on the command line. Example:
eskarina kraxel ~# xawtv -hwscan
This is xawtv-3.91, running on Linux/x86_64 (2.6.5-rc1)
looking for available devices
port 69-69 [ -xvport 69 ]
type : Xvideo, video overlay
name : video4linux
port 70-70 [ -xvport 70 ]
type : Xvideo, video overlay
name : video4linux
port 71-71
type : Xvideo, image scaler
name : ATI Radeon Video Overlay
/dev/video0: OK [ -device /dev/video0 ]
type : v4l2
name : BT878 video (Hauppauge (bt878))
flags: overlay capture tuner
/dev/video1: OK [ -device /dev/video1 ]
type : v4l2
name : Proteus Pro [philips reference
flags: overlay capture tuner
Default device in that case is Xvideo port 69, which is a video port driven by the X-Server's v4l module. If I want xawtv speak directly to the WinTV card using the v4l2 API I'll have to start xawtv with the "-device /dev/video0" switch.
Hope that this helps. Damn... did I really hit "bytesex.org" from work?