View Full Version : xawtv gives no signal when
svcdprayer
6th January 2007, 01:24
im trying to get xatw to work for me but i got no signal,
heres what i got
xawtv -hwscan
This is xawtv-3.95, running on Linux/i686 (2.6.9-34.EL)
looking for available devices
port 61-92
type : Xvideo, image scaler
name : NV Video Blitter
/dev/video0: OK [ -device /dev/video0 ]
type : v4l2
name : BT878 video (Hauppauge (bt878))
flags: overlay capture tuner
Notice on /dev/video type is vl42
when i try to do modprobe v4l
i got: FATAL: Module v4l not found.
that means that theres no video4linux builtin inside the kernel right?
my next question is is v4l neccessary as well as v4l2 in order to get a picture from tv?
if so is there any way that i can download it and install it and make it running like its possible with bttv ?
In other way what is neccessary for me in order to get a signal from tv?
Thanks!
nm
6th January 2007, 13:12
when i try to do modprobe v4l
i got: FATAL: Module v4l not found.
that means that theres no video4linux builtin inside the kernel right?
No, that would mean that either v4l is built-in to the kernel (and therefore is not available as a loadable module), or that there simply is no module called v4l because it is not included at all in your kernel build or because such a name is not used. In this case the last one is the correct explanation: in recent kernels, v4l2 is the only v4l implementation and the modules you could look for are called v4l1-compat and v4l2-common. However, they are most likely already loaded since the /dev/video0 device exists. If you want to see for yourself, take a look at the lsmod output: lsmod | grep v4l.
In other way what is neccessary for me in order to get a signal from tv?
Your V4L drivers should be fine, the real problem is elsewhere. What kind of a picture do you get when you run xawtv? Or does it print some sort of an error message? If you get white noise on all frequencies, check your antenna. That could also mean that there is something wrong with your tuner hardware or driver.
Take a look at the V4L Wiki, it should help with most common problems:
http://linuxtv.org/v4lwiki/
http://linuxtv.org/v4lwiki/index.php/Bttv_devices_%28bt848%2C_bt878%29
svcdprayer
7th January 2007, 19:23
when i start xawtv i get blue screen
and heres what i get from the shell
This is xawtv-3.95, running on Linux/i686 (2.6.9-34.EL)
ioctl VT_GETSTATE: Invalid argument
v4l-conf had some trouble, trying to continue anyway
v4l2: WARNING: framebuffer base address mismatch
v4l2: me=0xf6000000 v4l=(nil)
game over
EDIT: ive installed v4l-conf just to see... i removed it and then theres no error messages anymore but theres still blue screen. on wiki page i see that model number on my tv card hauppauge doesnt match the one on the webpage, does that mean that maybe bttw dosent have support on my hauppauge although is hauppauge bt878?
on tvtime i got no error msgs but blue screen with state no signal
nm
7th January 2007, 22:19
From the Wiki:
?: I have a blue screen.
!: Good, the overlay is working. A blue screen is what you get if the grabber chip has no input signal. You are probably using the wrong video source, pick another. Also happens sometimes if the tuner type is wrong, check the driver configuration.
If you're sure you have selected the correct video source in xawtv or tvtime, the driver is probably confused about the tuner type. You need to find out which tuner your card has and make sure the bttv module is loaded with correct parameters. See the first general hint they give:
1. Make sure if your board is recognized correctly. The bttv driver should print a line like this one (use the 'dmesg' command to see the kernel messages):
bttv0: model: BT848 (Hauppauge old)
If your card isn't autodetected correctly, you have to specify the board type as insmod argument (card=n). You might also have to specify tuner=x and pll=x.
Check the driver documentation for details and a list of supported cards. The standard kernel has the bttv documentation in the Documentation/video4linux/bttv directory.
You can also identify your card and see the necessary parameters here: http://www.bttv-gallery.de/
svcdprayer
7th January 2007, 22:55
ive checked that page
44354 Rev.B121 (Model 718) "WinTV PCI-FM"
thats mine, but i dont see any parameters, or i didnt get it, can you check it for me to see if theres something, maybe i missed something.
Thanks alot for help!
EDIT: ive checked tuner type on the card and its FM1216/I but when i installed bttv in CARDLIST.tuner list theres no tuner FM1216/I, and on the webpage you gave me its listed, but i dont see parameters.
Thanks again!
nm
7th January 2007, 23:51
See what kernel log says about your hardware by running dmesg. There should be something like this (just google by card model string such as "44354 rev B121" to find other people's logs):
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00ffffdb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
tveeprom 0-0050: Hauppauge model 44354, rev B121, serial# 2122426
tveeprom 0-0050: tuner model is Philips FM1216 (idx 21, type 5)
tveeprom 0-0050: TV standards PAL(B/G) (eeprom 0x04)
tveeprom 0-0050: audio processor is MSP3415 (idx 6)
tveeprom 0-0050: has radio
bttv0: Hauppauge eeprom indicates model#44354
bttv0: using tuner=5
bttv0: i2c: checking for MSP34xx @ 0x80... found
msp3400 0-0040: MSP3415D-B3 found @ 0x80 (bt878 #0 [sw])
msp3400 0-0040: MSP3415D-B3 supports nicam, mode is autodetect
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
tuner 0-0061: chip found @ 0xc2 (bt878 #0 [sw])
tuner 0-0061: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: registered device radio0
Apparently modprobe bttv card=10 tuner=5 would load the driver properly, but take a look at your logs first to see if there is a problem at all.
svcdprayer
8th January 2007, 10:51
yes that works! thanks!
can you tell me have you used default page http://www.bttv-gallery.de/
because when i visited it i havent seen any logs, or its different url? but when i googled from your logs about my tv card, it appears on google that its on www.bttv-gallery.de so im a bit confused, because some tv cards on that page i see logs, but some dont, or maybe u used high resolution page wich i didnt?
thanks!
nm
8th January 2007, 13:35
because when i visited it i havent seen any logs, or its different url? but when i googled from your logs about my tv card, it appears on google that its on www.bttv-gallery.de so im a bit confused, because some tv cards on that page i see logs, but some dont, or maybe u used high resolution page wich i didnt?
I found the logs from a post (http://www.mail-archive.com/debian-user-german@lists.debian.org/msg165990.html) to a Debian mailing list.
svcdprayer
8th January 2007, 15:06
okie thanks alot, i got it up and running, works without a problem!
btw wheres the best to look for logs, i got quite a few cards ill test soon, like technisat airstar2, pinnacle 330e etc?
nm
8th January 2007, 17:26
dmesg output on your own system is the first and most important source of information in case of problems. Then search on Google with specific strings from your own logs to see if others have had similar problems. Good search strings are error messages that seem to have something to do with the problematic equipment.
If Google doesn't reveal anything, LinuxTV.org's (http://www.linuxtv.org) Wiki pages and mailing lists (http://www.linuxtv.org/lists.php) are the next stop for finding information about analog television and DVB cards. Search the mailing list archives and ask on the lists if you have a problem that nobody else has had before (thats not likely).
svcdprayer
8th January 2007, 22:32
thanks buddy that would be all for now :)
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.