Hi all. I have noticed that several people have received hd3000's I have as of today ordered mine. I have noticed mixed messages as of late. On the official myth boards people have said they use HD3000 with knoppmyth, but cesman said r4v5 wasnt coperating with the modules. So i just started this thread to try and concolodate information on this card.

if anyone is wondering what the Hd3000 is this is it:
http://www.pchdtv.com/

its a hidef capture card that will only be sold to june30th or until supplies last. It in the short term is the future of myth (imho)

so to start it out, anyone have any experiences on r4v5?

Well, I've been trying all weekend, with no luck.

Tonight, I tried again, with a clean KnoppMyth install. Configuring MythTV, it knows about the card (though I assume it thinks it's an HD2000, not HD3000; no model is listed). However, it does not list the proper input devices (television should be the correct input device; instead it thinks it has composite1-4).

/dev/video32 doesn't work, nor does video or video0, for live TV or recording. /dev/dtv doesn't exist in the pulldown bar, and typing it in manually leaves no inputs to select, and it doesn't seem possible to manually add them in the MythTV GUI.

So, downloading, building, and installing the latest HD3000 drivers (which are now LKMs, rather than requiring a kernel rebuild), causes a GPF once the machine has rebooted and attempted to load tuner.o.

I tried to eliminate the possibility of a conflict between the modules that existed in the v4l directory vs. the misc directory under /lib/modules, to no avail. I'm thinking at this point (I don't know, I haven't checked) that the kernel that comes with a stock R4V5 has the kernel-reconfiguration done, which is enough to get the card recognized, but not new enough to work. That, or the stock V4L build is being a problem.

I've played around enough (loaded FC3 and tested the card) to know that the card itself works.

modconf isn't being helpful, because it's not showing anything as configured to be loaded, so I can't make use of it.

At this point, I'm trying to learn more about MythTV and Knoppix/Debian (I always despised apt-get/dselect, so I've avoided Debian when I could) before going further.

I'd like to find out:
1) how to remove the existing MythTV install in KnoppMyth and instead install MythTV within KnoppMyth from MythTV's CVS
2) how to get the old kernel mods for the HD2000 out of the KnoppMyth kernel and instead use the newest HD2000/HD3000 module drivers that were made available on 11/19
3) how to accomplish 1) and 2) without completely breaking the KnoppMyth environment, thus pretty much eliminating the attractiveness of KnoppMyth, and reducing the situation to a choice between backwards-engineering KnoppMyth or just starting with a totally fresh distro and doing 1) and 2) without having to wrangle with the customizations KnoppMyth introduced.


I mention 3) because I /really/ /like/ KnoppMyth, and want to get this card working with it, rather than installing a clean distro from scratch and rolling my own MythTV installation. In other words, I want to figure out what needs to be done, and then do it while breaking as little as possible about KnoppMyth, and sharing what I had to do to KnoppMyth to get everything cooperating.

I have given up on knoppmyth and resorted to FC2. It just seems to be too difficult to get a 2.6 kernel working properly on knoppmyth which I need for the DVICO FusionHDTV card I recently purchased. I had a great time with knoppmyth with my old bt878 based card and am looking forward to R5 when I think i'll give knoppmyth another go.

The knoppmyth kernel installed by default does not have the pchdtv patches applied. if you want the kernel with the patches applied you would have to install it. It is in /usr/src somewhere, and obviously it is only for the hd2000 as the 3000 wasn't out when R4V5 came out.

on another note, does linux actually give you a gpf error? I thought that was a microsoft thing. I've never seen linux be that vague with it's error messages.

also note that If I'm not mistaken the default kernel in knoppmyth is patched for v4l2.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

I dont have an HDTV so i havent really spent too much time figuring this stuff out. Since this is a "round table" please help me understand this.

All of this talk about HD is limited to over the air HD, right. I've read that "a PC card will never be able to capture cable HD" Are both of these true?

do those of you with these HD cards also have cable? Do you have an antenna on the roof or attic?

When/if cable goes completely digital will we all required to got to IR Blasters to get the signal out of the cable box?

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

The PC3000 has the ability to do QAM, which is how digital cable signals (both SD and HD) are transmitted. However, it can only do unencrypted QAM. It depends on the cable company as to which channels are sent via unencrypted QAM, if any. Obviously the pay channels like HBO and Showtime will be encrypted; one would hope that the local over-the-air (OTA) signals would be sent unencrypted.

Also, the support for QAM isn't there right now: supposedly coming soon.

http://gossamer-threads.com/lists/mythtv/users/89504

Yep, I have an antenna on my roof for OTA broadcasts. Rabbit ears can work too depending on how close you are to a broadcast antenna. You can check http://www.antennaweb.org/ to find out where your closest transmitter is.

I don't think cable boxes and IR blasters will help the situation: the problem will be getting the HD signal out of the box. After the broadcast flag rule takes effect, cable boxes will be required to limit the analog output to 480p, and the digital signal will have the infamous "broadcast flag" attached to it.

yes it's almost as if they are trying to water off the 3million plus people (like myself) who bought hdtv's before there were digital inputs on them. I have this great tv that will do 1080i, but If I use the official channels to get my signal it will be limited to 480p. I really wish there were an alternative to the RIAA and MPAA, so they could see that screwing their customers is not a good business practice, but I guess it doesn't really matter when you have a monopoly.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Hm. That'd mean it's actually either using a newer module-based driver, or a generic cx8800/cx88xx set of drivers that are recognizing the card. Either way, they're not working.



General protection faults are by no means the sole purview of windows. It's also not vague; there's about 15-20 lines of additional detail (e.g., stack state, call backtraces) to go along with it, and an "oops", which suggests to me it's causing an unexpected stack condition beyond the lack of bounds checking on the memory access that caused the gpf. Were I the masochistic sort, I'd type the whole thing in here (or spend time looking up the steps necessary with LILO to get the detail saved to disk so I could pull it off later).



Where I mentioned v4l above, I meant v4l2. I was just being lazy.

I believe it does have the cxwhatever drivers in there, one thing you might try is using the pchdtv kernel that is in /usr/src/ it is patched for pchdtv2000 and does not have the v4l2 patches applied I also don't think it will have the cxwhatever drivers in it. Also did you happen to notice what module generated the kernel oops?

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

it looks like it. Things can change so keep checking.

I'll give it a shot.

It looked like it was tuner.o generating the oops. However, it'd actually make it to trying to load the audio modules before it hung. I tried removing everything from the computer but the HD3000 and video card, and disabling everything I could in the BIOS (serial, parallel, USB, LAN, sound, etc.), but it still hung in the same place.

I also booted with the KnoppMyth disk, mounted the HD, chrooted, and removed the post-install directives for the modules, and even the bttv install directive (and ran update-modules, of course), but it still hung at the same place and in the same manner, leading me to belive the driver's in the kernel, not a module. At least, I didn't see anything instructing the system to load the cx* modules during the boot process.

Then again, I'm more of a BSD person, so the various approaches to LKM management in Linux in general and Knoppix in particular tend to leave me a bit bewildered at times...I haven't used Linux heavily since around 1996.

Well, I just tried the pchdtv kernel in /usr/src instead of the default kernel. It does in fact still have the cx* drivers:



The only changes I've made from the default KnoppMyth install are:



Here's the output of lsmod after a reboot:




Here's the output of lsmod before the change to the pchdtv-specific kernel debs in /usr/src/debs/pchdtv:




Hm. I just tried the approach I found in the message here:
http://www.gossamer-threads.com/lists/m ... 000;#95366

...and now my system's hung again. Looks like I'm back to doing yet another fresh KnoppMyth install. *sigh*

A few links of interest:

Answers about pcHDTV HD-3000 support in Myth, QAM support, and more
http://gossamer-threads.com/lists/mythtv/users/89504

PCHDTV Forums on Debian http://pchdtv.com/forum/viewtopic.php?t ... a5287cdf3f

Wendy Seltzer's working debian
http://wendy.seltzer.org/mythtv/

one thing to definitely take note of the pchdtv kernel on knoppmyth R4V5 is only patched for the pchdtv2000 NOT for the 3000 and they do use different drivers.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Is there an unpatched version of the KnoppMyth kernel laying about somewhere, or would it be best to just download the latest 2.4.x kernel and build it from scratch? Would there be any KnoppMyth "gotchas" to watch out for using the latter approach? (I looked at the KnoppMyth kernel config, and it looked fairly innocuous were I to use it with a fresh kernel sourcetree).

I'm assuming that V4L2 is necessary, and IVTV isn't?