[mythtv-users] PVR500, PCHDTV 3000, and AMD64

Justin The Cynical cynical at penguinness.org
Fri Mar 10 05:49:06 UTC 2006


jborn at charter.net wrote:
> Well its been a long time since I've been able to work on this, but once I finally sat down and looked into it I found out why /dev/video0 and /dev/video1 were not showing up.  The dmesg for ivtv showed a firmware loading issue.  I no longer had the firmware in the proper spot.
> 
> When I started all of this I was using IVTV 4.0 and I had the proper devices.  I assumed that my fiddling around trying to get the HD3000 card working broke my setup for the PVR500, but in actualality it was the upgrade from IVTV 4.0 to now 4.3.  The following page on the IVTV site about firmware spelled out my problems:
> 
> http://www.ivtvdriver.org/index.php/Firmware
> 
> Now I'm about to put the HD3000 card back in and start getting that up and running.  In this thread I was asked if I meant to use the HD3000 for HD only and that is correct.  I only want to use it for HD.  It also made reference to ATSC drivers only.  Is there a thread that already discusses how to do this?  Or another site that walks me through this process?
> 
> Thanks again for all the support.

Here are the steps I took to get my HD3000 working with a Aver M179 
card.  This is on a FC4 system and IVTV .4.2 from source:


Put the HD3000 in the system.  :-)

Change the tveeprom-ivtv entry in modules.conf to tveeprom.

Rename/remove tveeprom.ko from the modules directory (the rename in 
modules.conf didn't work for some reason).

Put the firmware files in the /lib/firmware directory.

Make sure the /dev/video* and /dev/dvb/* entries are owned/can be 
accessed by the mythtv user.

Tell the backend that the Aver card is now on video1 (video0 was taken 
by the HD3000).

Tell the backend to access the HD3000 via DVB.

During this process, using dmesg | less helped a lot.

Good luck, it was pretty painless for me.


More information about the mythtv-users mailing list