danny at ricin.com
Sun Jun 11 11:21:05 UTC 2006
On Sunday 11 June 2006 10:23, Naram Qashat wrote:
> I've been having problems with my bktr-based TV Tuner card. It's a
> Hauppauge WinTV GO-Plus, and a pretty recent model too. Next is the
> messages for the driver upon bootup:
> bktr0: <BrookTree 878> mem 0xdc000000-0xdc000fff irq 11 at device 9.0 on
> bktr0: [GIANT-LOCKED]
> bktr0: Hauppauge Model 29440 @ %
> bktr0: Warning - Unknown Hauppauge Tuner 0xd5
/usr/src/sys/dev/bktr/bktr_card.c has some interesting comments about (some?)
bt878 based cards that have an EEPROM. In short: they've been broken by the
time MT2032 tuner support was added, and they're still broken. I've had
similar problems with an (old) WinCast TV card; it stopped working somewhere
around FreeBSD-5.3 or so, also because tuner detection fails and it can't be
bullied into using the correct one with sysctl. I tried to raise the issue
several times but never got a response.
> bktr0: Hauppauge WinCast/TV.
> Now for my problems:
> I'm unable to watch TV with the tuner, only use the component a/v. I use
> FXTV, and for the component a/v, it works great. But when I try to use it
> to watch TV, it was bombing on me. I can't remember if this started
> happening before or after I upgraded from 5.4 to 6.1, but I believe it was
> 6.1 where the problem really started. I've attached a gdb log of what I
> get from FXTV when I compile it in debug mode and trace it. When FXTV gets
> to the ioctl of TVTUNER_SETCHNL, my system's X freezes, but oddly enough,
> my keyboard still works. But when I try to use CTRL+ALT+F1 to switch back
> to a console, the system reboots, either that or I just did it at the same
> time it was rebooting anyways. Prior to having this problem, I was able to
> get a signal. That's one part of the problem.
> The other problem was that when I was able to get a signal, it wasn't a
> very good one. Or rather, it was wrong. Every "channel" up to 24 shows
> the exact same thing. Above channel 24, it's mostly static, and it seems
> that sometimes something changes, but there's too much static to tell. I
> was only able to get any signal at all by manually setting hw.bt848.tuner
> to 1 for Temic NTSC, since the card isn't properly detected at bootup.
> None of the other settings for hw.bt848.tuner work for me. What could be
> done about this?
> Naram Qashat
More information about the freebsd-multimedia