PVR-150 configuration Package: ivtv-kmp-default

I’m very new to LINUX, and this my first attempt at SUSE 11.1. I have a Hauppauge PVR-150. I’ve read all the threads and posts I can find, and I think that I’ve read some that indicate that this PVR should be able to work with 11.1. However, when I try to configure it, I get the following …

WinTV PVR 150
• Configured as TV card number 0
• Driver ivtv
• Package: ivtv (Installed)
• Package: ivtv-firmware (Installed)
• Package: ivtv-kmp-default (Not Installed)

It successfully scans and finds TV stations, but since the the ivtv-kmp-default package doesn’t install, then it won’t complete and save.

I’m not sure where to go from here. I downloaded version 1.3.0 from Download - IVTV.

I installed mythTV, which got the PVR to scan stations.

Any help would be appreciated.

The ivtv version that ships with openSUSE 11.1 should work for your PVR150. Don’t start with new ivtv versions from ivtv.org

If it scans the channels, the card is working.

See if ivtv loaded successfully:
dmesg | egrep -i ‘(ivtv|tveeprom|tuner)’

Make sure the channels are setup in mythtv-setup and start your mythfrontend to watch tv.

more on mythtv wiki: Opensuse 11.x - MythTV

good luck

If you want to try an alternative to mythtv have a look at this one.

Best regards

I have this same card. Does anyone know if it will work with 13.1 or am I just wasting time trying to make it work?

On 04/30/2014 11:46 AM, rushonefan wrote:
>
> I have this same card. Does anyone know if it will work with 13.1 or am
> I just wasting time trying to make it work?

The PVR-150/250/500 all work with 13.1. The only problem will be that the
firmware is not licensed so that it can be included in the kernel-firmware. The
filename needed will be listed in the output of the dmesg command. Search for
that name, and you will find a place to download the firmware.

I do not have a PVR-150, but I am using a PVR-500, which is two 150’s on a
single card. I believe the firmware you need is v4l-cx2341x-enc.fw.

I use my card with mythtv.

Thanks for the reply. Found this page -
http://ivtvdriver.org/index.php/Firmware#Obtaining_and_Installing_the_Firmware

I’m a noob (ok, played around with the os 20 or so years ago) so I have no idea where to put the files.

Sorry if this is too easy…

Thanks!

On 04/30/2014 04:06 PM, rushonefan wrote:
>
> Thanks for the reply. Found this page -
> http://tinyurl.com/eb88n
>
> I’m a noob (ok, played around with the os 20 or so years ago) so I have
> no idea where to put the files.
>
> Sorry if this is too easy…

Firmware is read from /lib/firmware/. Sometimes a particular driver will use a
sub-directory, but not these devices.

Thanks a ton! I’ll try that!

Whooo Hooo!!! I think it worked…

   12.219952] ivtv: Start initialization, version 1.4.3
   12.220316] ivtv0: Initializing card 0
   12.220321] ivtv0: Autodetected Hauppauge card (cx23416 based)
   12.274800] tveeprom 4-0050: Hauppauge model 26582, rev F0B2, serial# 10080997
   12.274806] tveeprom 4-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
   12.274810] tveeprom 4-0050: TV standards NTSC(M) (eeprom 0x08)
   12.274813] tveeprom 4-0050: audio processor is CX25843 (idx 37)
   12.274816] tveeprom 4-0050: decoder processor is CX25843 (idx 30)
   12.274818] tveeprom 4-0050: has no radio
   12.274821] ivtv0: Autodetected Hauppauge WinTV PVR-150
   12.387049] cx25840 4-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
   12.847168] tuner 4-0061: Tuner -1 found with type(s) Radio TV.
   13.070614] wm8775 4-001b: chip found @ 0x36 (ivtv i2c driver #0)
   13.120412] tuner-simple 4-0061: creating new instance
   13.120420] tuner-simple 4-0061: type set to 50 (TCL 2002N)
   13.122201] ivtv0: Registered device video0 for encoder MPG (4096 kB)
   13.122301] ivtv0: Registered device video32 for encoder YUV (2048 kB)
   13.122388] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
   13.122472] ivtv0: Registered device video24 for encoder PCM (320 kB)
   13.122476] ivtv0: Initialized card: Hauppauge WinTV PVR-150
   13.122652] ivtv: End initialization
   13.454273] ivtv-alsa: module loading...
   14.204969] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
   14.404136] ivtv0: Encoder revision: 0x02060039

Thanks again, you rock!

Ok, so now when I try and do a channel scan - (to memorize the channels) i get a msg saying it’s busy. This is a windows 7 box that i’m trying to replace. I’m almost there, just need my tv tuner card and DLNA to work. Not sure if this is a bug, but the system literally crawled until i got the fw for the tv card working. It would take 3 mins or so to logoff or shutdown. Is there some ‘patch’ or whatever to tell the system to ignore an addon card if the correct drivers are not loaded?

Thanks!
-Mark

On 05/01/2014 09:06 PM, rushonefan wrote:
>
> Ok, so now when I try and do a channel scan - (to memorize the channels)
> i get a msg saying it’s busy. This is a windows 7 box that i’m trying
> to replace. I’m almost there, just need my tv tuner card and DLNA to
> work. Not sure if this is a bug, but the system literally crawled until
> i got the fw for the tv card working. It would take 3 mins or so to
> logoff or shutdown. Is there some ‘patch’ or whatever to tell the
> system to ignore an addon card if the correct drivers are not loaded?

You are mixing drivers with firmware. A driver is the code that runs in the host
CPU. Firmware is the code that runs in the CPU that is embedded on the device.
Among other things, the driver uploads the firmware into the device. Simple
devices have their firmware in ROM, but complicated ones usually need an easy
means of fixing bugs in their firmware, which is why it is stored in a disk
file. In the early days of Linux, firmware was distributed with the kernel;
however, the amount of firmware grew too large for it to be part of the kernel.
At present, there is over 100 MB of firmware available.

When the kernel is starting, it scans the PCI and USB buses and finds the PCI of
USB IDs. For each device, it tests for a driver that claims that ID, and if that
driver is not blacklisted, it is loaded, and control is passed to its start
point. That code then checks to see if the device matches its requirements. If
it does, and the device needs firmware, the driver then tells the system to load
the appropriate firmware files. That happens in user space. If the file is
available, it is loaded to memory where the driver can access it and download it
to the device. What happens if it is not available depends on the particular
driver. Blacklisting is the only way to tell the system to ignore a card that is
physically attached to the computer.

If a driver has problems because firmware is not available, there is little you
can do other than make the firmware available, or not load the driver.

I do not know what program you are trying to use to view the output from the
PVR-150. It produces mpeg-2 info that can be output by VLC. I hope you are aware
that the PVR-150 can only handle analog signals, thus it can no longer process
over-the-air signals in the US. My PVR devices are connected to
standard-definition TV through my cable connection.

Yes, that is exactly the way my pvr-150 is connected. I use media ctr in win7. Perhaps i don’t have the correct codecs installed for it to work with say ‘motv’ tv? Almost there i think :slight_smile:

Thanks again for all the help!

Close. The issue is that motv doesn’t work with mpeg2 encoded streams … it expects the input bitsream to be raw and uncompressed.

I could have sworn I wrote a wiki article on LinuxTV listing viewing apps for mpeg2 encoding TV devices, but I couldn’t find it on a quick look. Anyway, now you know that the app will have to specifically support such devices*. Off the top of my head, mplayer (and you might want to see TV-Viewer - LinuxTVWiki ) is one of the top choices.

  • As a side note, you can use your device with most apps, though you will have to grab the raw video bitstream before its routed through the mpeg2 encoder. This, of course, kind of defeats the purpose of having an mpeg2 encoding device … Anyway, you’d do that by utilizing /dev/video0, whereas /dev/video1 will be the output from the mpeg2 encoder … I may have got those backwards (don’t remember), but you get the picture (pun intended).

Almost there i think :slight_smile:
Indeed!

EUREKA! I got tv-viewer to work! So what about DLNA? I tried minidlna but i have no idea how to specify the directory i want to add. The physical location is (disk2)\media\videos. Any suggestions?

Thanks a ton for all the help!