Hans Verkuil wrote:
On Tuesday 04 December 2007 22:47:46 Mark Paulus wrote:
Mark Paulus wrote:
I posted this on users, but didn't get any nibbles,
so I'll try it here:
I have 2 boxes that have AMD 64 3800+ X2 processors,
and are running Debian etch with a 2.6.18 kernel.
Last night I tried to install a 64 bit flavour debian kernel
(linux-image-2.6.18-5-amd64), which worked fine. I also
tried to compile/install ivtv0.10, and that "seemed"
to work fine. At least, dmesg seemed to work fine.
However, when I went into mythtv, the cards aren't there.
And, v4l2-ctl doesn't see/recognize the cards.
Just wondered if anyone had seen this before, or had
any ideas about 64-bit incompatibilities.
The first box (output below) has a PVR-250 and PVR-150.
All works fine in a standard 32-bit 2.6.28 kernel.
The second machine has a PVR-150, an Air2PC OTA card, an
Avermedia A180 and a pcHDTV RT5 Lite in it. The RT5,
A180 and Air2PC cards all seem to be initialized correctly
with the 64-bit kernel, but the PVR-150 is not there.
I have been working this off and on, and wanted to post what
I found, so that others can follow along.
My initial goal was to have my mythtv boxes on an AMD 64
3800+ X2 CPU running a 32-bit debian etch system, and
32-bit mythtv. There was one particular piece of code
that I wanted to run in a 64 bit environment ([EMAIL PROTECTED]
64-bit/SMP beta client). However, because of the effort
and amount of "stuff" on these boxes, I didn't want to
completely convert them over to 64-bit installations. So,
I was hoping to be able to run a 32-bit system on a 64-bit kernel
and then run foldingathome in a 64-bit chroot on the
32-bit system.
That proved to not be possible, since the ivtv kernel module
absolutely DOES not like being in a hybrid environment. I have
proved to my self that ivtv drivers seem to be 64-bit compatible
but they are not mixed mode. I went into my 64-bit chroot
environment, build the ivtv modules within, did a 'rmmod ivtv'
to get rid of the borked load, then I did a 'modprobe ivtv'
within the chroot, and everything seemed to work fine. v4l2-ctl
was able to see and correctly identify the pvr-150, which it
could not do in the 32-bit environment.
Bottom line, guess I'll need to create a bootable chroot on a
separate hard drive, and migrate to a fully 64-bit system.
Hi Mark,
It would be interesting to see if using the latest bleeding edge driver
(see http://www.ivtvdriver.org/index.php/Download#Bleeding_Edge_driver)
would fix this issue. I will definitely not fix the 0.10 series, but if
the bleeding edge driver also has the same problems in a mixed
environment, then I will look at it. As an alternative to using the
bleeding edge driver (the preferred option for me) it would also be OK
to upgrade to a 2.6.22 or up kernel, at least to see whether it is
fixed in those newer kernels or not.
Regards,
Hans
I will try the bleeding edge drivers. I did try a 2.6.22 kernel
from backports.org with the ivtv1.0.0 driver, and I think I had
the same issues (otherwise I would have stayed with it).
However, as long as we are working on my secondary box, I am willing to
do most any kind of expirement.
begin:vcard
fn:Mark Paulus
n:Paulus;Mark
org:MCI;Lec Interfaces / 40419
adr;dom:;;2424 Garden of the Gods Rd;Colorado Springs;CO;80919
email;internet:[EMAIL PROTECTED]
title:Mark Paulus
tel;work:719-535-5578
tel;pager:800-pagemci / 1406052
tel;home:v622-5578
version:2.1
end:vcard
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
