# echo "PORTDIR_OVERLAY=/usr/local/portage" >> /etc/make.conf
# mkdir /usr/local/portage/app-misc/pvrusb2-firmware
# cd /usr/local/portage/app-misc/pvrusb2-firmware
# wget http://bugs.gentoo.org/attachment.cgi?id=98689
(Make sure you have the latest ebuild available!)
(http://bugs.gentoo.org/show_bug.cgi?id=78570)
# mv attachment.cgi\?id\=98689 pvrusb2-firmware-0.2.ebuild
# ebuild pvrusb2-firmware-0.2.ebuild digest
# emerge pvrusb2-firmware
$
mkfifo test.mpg
$ cat /dev/v4l/video0 >
test.mpg | mplayer
test.mpg
Or,
for radio support added to the >=kernel-2.6.19:
$
mkfifo /tmp/radio.mpg && cat /dev/v4l/radio0 >
/tmp/radio.mpg | mplayer /tmp/radio.mpg
(2005.01.11) I have experimented with several deinterlace filters and it would appear they cause too much cpu overhead on a 1Ghz P3 while watching live tv.
(2005.07.14) Latest news on the pvrusb2 driver
can be found at http://www.isely.net/pvrusb2/pvrusb2.html
.
Mike has taken over and made allot of fixes and modifications.
The /sys/class/pvrusb2 interface works really well! I'm meadling with
trying to get everything working here on my Gentoo box with hopes of
updating the Portage ebuild as soon as I'm successful. FYI: I
have a pvrusb2 device with a "type 58 tuner" returning
"type = 4" value so I had to deactivate the kernel's
tuner.ko & tveeprom.ko code (these modules are hidden under the
bt848.ko code). So deactiving the bt848.ko code in the kernel
to prevent the tuner.ko & tveeprom from automagically being built
and colliding with the tuner modules of this pvrusb2 driver. If
you have a "type 58 tuner", don't fret, try using the
kernel tuner.ko & tveeprom.ko code (by activating the bt848.ko
code) as these modules are maintained at the kernel level and should
work fine for you. If you have this problem, file a bug report
with the pvrusb2 maintainer.
(2005.07.15) If you get a "mpeg: select: timeout (3 sec)" with a snapshot xawtv then try "mv ~/.tv/stations .tv/stations.old". Assuming you used "./configure --prefix=$HOME" then do, "~/bin/scantv" (along with the proper switches for scantv if the correct values are not being used). If you still get this error, trying changing the channels. Also, check to make sure scantv has written new channels found within the ~/.tv/stations file. A very common solution to this problem, try removing the first few channels within the .tv/stations listing. Xawtv starts by always choosing the first station within .tv/stations. If the first station is not properly tuned, this time-out error may occur. I think I've found a solution to a very rare “no sound” issue. Try reloading the pvrusb2 after powering off /on the device.
(2005.08.01) I think I've found a
solution to a very rare “no sound” issue. Try reloading
the pvrusb2 after powering off /on the device. Lirc is working here!
(2005.08.03) For Mythtv, I recommend
using Datadirect for aquiring the channels instead of using
the channels found with xawtv's scantv. It's a free service and
the
instructions are found in section 5.3 of Mythtv's
Documentation.
(2005.08.07) I did have Mythtv
playing live tv just fine until the past day on my Gentoo box.
I'm now getting jerky video. Until I track it down, doing "echo 1
> /sys/class/pvrusb2/sn-7435104/ctl_interlace/cur_val". (And
if you have yet to figure out, using libmpeg2 for playback can
significantly reduce cpu usage.)
(2005.08.08) Noticed Mythtv requires
quite a bit of cpu. However, if you're noticing Mythtv use
>99% on a ~1Ghz pentium3 cpu, you might want to try recompiling
sys-libs/glibc (and ensuring you have included some cflag optimizations
such as "-march=pentium3 -O3 -pipe -fomit-frame-pointer". This
seems to be the second report of compiling glibc w/o any optimizations
caused Mythtv to use more cpu then one would expect. Another
idea, echo 1 >
/sys/class/pvrusb2/sn-7435104/ctl_interlace/cur_val. (These are
some ideas if you have already tried every other config setting within
Mythtv's menus.)
(2006.10.04) I have updated this page and deleted allot of
out-dated literature. I've made several references to Mike
Isely's web page being the primary means for documentation. The
only things I'm concerned with documenting are firmware extractions and
pointers.
(2007.02.14) I have yet to troubleshoot, but I think lirc might be failing with pvr-firmware. When /etc/init.d/lircd is started, it should create a /dev/lirc/0. I'm only getting this when rebooting after loading the Windows XP firmwares or possibly my older firmwares listed below? Please let me know if you can verify this.