Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
I had a similiar problem with freevo but my issue stemmed from running a 2.4 kernel instead fo a 2.6. after upgrading to a 2.6 kernel the problem went away. I have not idea if this helps or not. evan On 1/15/06, Geert Decorte [EMAIL PROTECTED] wrote: A short clarification from my side could shine a light onto the case. I have a epia MII1000 Nehemiah mobo with a Hauppage MCE500 and went for the epios distribution as the tool for the job. (epios is a gentoo based distro with specific epia motherboard optimalisations) This was the snapshot I've used for the install http://www.epios.net/viewtopic.php?t=339 Basicly installing would be as simple as emerging and configuring ivtv and freevo. This should be enough for resolving dependencies. The portage tree of epios has only freevo 1.5.2 available, but this should do the trick for most dependencies. Afterwards, I've downloaded 1.5.4 directly from sourceforge, unpacked it, and installed. Didn't see any error in the install. Now I checked .../freevo-1.5.4/build/lib/freevo/tv/v4l2.py And as Jason stated, it didn't contained the obstructing line. But the installed version did contain it. /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py So it should be the v4l2.py version installed by 1.5.2 which didn't get up to date after installing 1.5.4 The only problem should be in updating 1.5.4 from a prior (unused?) version or something specific with the distro I'm using. I've followed the installation instructions literaly To install Freevo, run 'python setup.py install' as root. So if there are files who didn't went up-to-date probably I need to copy them manualy from the build directory? Is there a clear way to check these out? This is the output when rebuilding the setup of 1.5.4 epios freevo-1.5.4 # python setup.py install checking for mmpython... found checking for pygame... found checking for Image... found checking for twisted...found running install running build running build_py running build_scripts running install_lib byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/ivtv.py to ivtv.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py to v4l2.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/plugins/mixer.py to mixer.pyc running install_scripts changing mode of /usr/bin/freevo to 755 running install_data Geert On Fri, 2006-01-13 at 18:49 +0100, Robert Winder wrote: Jason and Gerrit Hannaert already looked into it. Both provided a patch on the userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix release freevo 1.5.4 I did have a private correspondence with Geert Decorte who experienced the following python 2.4 error Assuming by both patches you mean the two patches you attached that were posted here some time ago, both of those _did_ make it into the Freevo 1.5.4 bugfix release. It would definitely have been a major SNAFU if they didn't, because the entire point of the 1.5.4 release was to include these fixes. :) Just to make sure I wasn't losing my sanity, I redownloaded the 1.5.4 tarball from sf.net and indeed these patches were correctly included. r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val) OverflowError: long int too large to convert to int This line of code doesn't exist anywhere in Freevo 1.5.4. It shouldn't happen. http://gedeco.no-ip.org -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
On Fri, 2006-01-13 at 18:49 +0100, Robert Winder wrote: Jason and Gerrit Hannaert already looked into it. Both provided a patch on the userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix release freevo 1.5.4 I did have a private correspondence with Geert Decorte who experienced the following python 2.4 error Assuming by both patches you mean the two patches you attached that were posted here some time ago, both of those _did_ make it into the Freevo 1.5.4 bugfix release. It would definitely have been a major SNAFU if they didn't, because the entire point of the 1.5.4 release was to include these fixes. :) Just to make sure I wasn't losing my sanity, I redownloaded the 1.5.4 tarball from sf.net and indeed these patches were correctly included. r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val) OverflowError: long int too large to convert to int This line of code doesn't exist anywhere in Freevo 1.5.4. It shouldn't happen. and after applying the attached patches provided by Jason and Gerrit it worked again. Although i haven't looked if there are more instances which could trigger this error within Freevo. I did do a search for all instances of ioctl in the code in order to determine of the request identifier needed to be wrapped in i32(). But I might have missed some. Here's a patch that I've done for this problem: http://www.linuxowl.com/patches/freevo-1.5.4-v4l2.py.patch Python was using 'L' for 64bit ints and the interface wanted 32bit ints. dischi/rshortt -- how does this patch look to you? It seems sensible to me (in terms of logic), but there are many places in v4l2.py where 'L' is used in the struct format, and many cases that Duncan didn't modify that might require it. Maybe Duncan could comment as well. If everything is good, I'll merge this patch with both the 1.5 and trunk branches. def getfmt(self): -val = struct.pack( FMT_ST, 1L,0,0,0,0,0,0,0) +val = struct.pack( FMT_ST, 0,0,0,0,0,0,0,0) r = fcntl.ioctl(self.device,GET_FMT_NO,val) return struct.unpack( FMT_ST, r ) Given that this is the code now present in trunk, I've committed this fix to the 1.5 branch as well. Are there any other issues with Freevo 1.5.4 and Python 2.4? How about with AMD64? Considering Freevo 2.0 won't be out for many months, it might be a good idea to fix some more of these bugs and release a 1.5.4.1. dischi? Cheers, Jason. signature.asc Description: This is a digitally signed message part
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
A short clarification from my side could shine a light onto the case. I have a epia MII1000 Nehemiah mobo with a Hauppage MCE500 and went for the epios distribution as the tool for the job. (epios is a gentoo based distro with specific epia motherboard optimalisations) This was the snapshot I've used for the install http://www.epios.net/viewtopic.php?t=339 Basicly installing would be as simple as emerging and configuring ivtv and freevo. This should be enough for resolving dependencies. The portage tree of epios has only freevo 1.5.2 available, but this should do the trick for most dependencies. Afterwards, I've downloaded 1.5.4 directly from sourceforge, unpacked it, and installed. Didn't see any error in the install. Now I checked .../freevo-1.5.4/build/lib/freevo/tv/v4l2.py And as Jason stated, it didn't contained the obstructing line. But the installed version did contain it. /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py So it should be the v4l2.py version installed by 1.5.2 which didn't get up to date after installing 1.5.4 The only problem should be in updating 1.5.4 from a prior (unused?) version or something specific with the distro I'm using. I've followed the installation instructions literaly To install Freevo, run 'python setup.py install' as root. So if there are files who didn't went up-to-date probably I need to copy them manualy from the build directory? Is there a clear way to check these out? This is the output when rebuilding the setup of 1.5.4 epios freevo-1.5.4 # python setup.py install checking for mmpython... found checking for pygame... found checking for Image... found checking for twisted...found running install running build running build_py running build_scripts running install_lib byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/ivtv.py to ivtv.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py to v4l2.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/plugins/mixer.py to mixer.pyc running install_scripts changing mode of /usr/bin/freevo to 755 running install_data Geert On Fri, 2006-01-13 at 18:49 +0100, Robert Winder wrote: Jason and Gerrit Hannaert already looked into it. Both provided a patch on the userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix release freevo 1.5.4 I did have a private correspondence with Geert Decorte who experienced the following python 2.4 error Assuming by both patches you mean the two patches you attached that were posted here some time ago, both of those _did_ make it into the Freevo 1.5.4 bugfix release. It would definitely have been a major SNAFU if they didn't, because the entire point of the 1.5.4 release was to include these fixes. :) Just to make sure I wasn't losing my sanity, I redownloaded the 1.5.4 tarball from sf.net and indeed these patches were correctly included. r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val) OverflowError: long int too large to convert to int This line of code doesn't exist anywhere in Freevo 1.5.4. It shouldn't happen. http://gedeco.no-ip.org -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
A short clarification from my side could shine a light onto the case. I have a epia MII1000 Nehemiah mobo with a Hauppage MCE500 and went for the epios distribution as the tool for the job. (epios is a gentoo based distro with specific epia motherboard optimalisations) This was the snapshot I've used for the install http://www.epios.net/viewtopic.php?t=339 Basicly installing would be as simple as emerging and configuring ivtv and freevo. This should be enough for resolving dependencies. The portage tree of epios has only freevo 1.5.2 available, but this should do the trick for most dependencies. Afterwards, I've downloaded 1.5.4 directly from sourceforge, unpacked it, and installed. Didn't see any error in the install. Now I checked .../freevo-1.5.4/build/lib/freevo/tv/v4l2.py And as Jason stated, it didn't contained the obstructing line. But the installed version did contain it. /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py So it should be the v4l2.py version installed by 1.5.2 which didn't get up to date after installing 1.5.4 The only problem should be in updating 1.5.4 from a prior (unused?) version or something specific with the distro I'm using. I've followed the installation instructions literaly To install Freevo, run 'python setup.py install' as root. So if there are files who didn't went up-to-date probably I need to copy them manualy from the build directory? Is there a clear way to check these out? This is the output when rebuilding the setup of 1.5.4 epios freevo-1.5.4 # python setup.py install checking for mmpython... found checking for pygame... found checking for Image... found checking for twisted...found running install running build running build_py running build_scripts running install_lib byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/ivtv.py to ivtv.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py to v4l2.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/plugins/mixer.py to mixer.pyc running install_scripts changing mode of /usr/bin/freevo to 755 running install_data Geert On Fri, 2006-01-13 at 18:49 +0100, Robert Winder wrote: Jason and Gerrit Hannaert already looked into it. Both provided a patch on the userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix release freevo 1.5.4 I did have a private correspondence with Geert Decorte who experienced the following python 2.4 error Assuming by both patches you mean the two patches you attached that were posted here some time ago, both of those _did_ make it into the Freevo 1.5.4 bugfix release. It would definitely have been a major SNAFU if they didn't, because the entire point of the 1.5.4 release was to include these fixes. :) Just to make sure I wasn't losing my sanity, I redownloaded the 1.5.4 tarball from sf.net and indeed these patches were correctly included. r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val) OverflowError: long int too large to convert to int This line of code doesn't exist anywhere in Freevo 1.5.4. It shouldn't happen. http://gedeco.no-ip.org -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
On Thursday, January 12, 2006, 10:07:52 PM, John wrote:
I'm cross posting this onto the devel list (and top posting - sorry).
Looks like another python2.4 and ivtv driver issue and they are running
1.5.4. Can someone (Rob again :)) take a look?
Jason and Gerrit Hannaert already looked into it. Both provided a patch on the
userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix
release freevo 1.5.4 I did have a private correspondence with Geert Decorte who
experienced the following python 2.4 error
r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val)
OverflowError: long int too large to convert to int
and after applying the attached patches provided by Jason and Gerrit it worked
again. Although i haven't looked if there are more instances which could trigger
this error within Freevo.
The other error in this thread
r = fcntl.ioctl(self.device, i32(QUERYCAP_NO), val)
IOError: [Errno 22] Invalid argument
is already fixed in 1.5.4
/Robert
Thanks,
John
Geert Decorte wrote:
This is a simple metoo reply.
None of the patches John described worked for me.
Have the impression this is specific on python 2.4 acting different then
python 2.3
I have a hauppage MCE 500 working under linux on a epia motherboard.
(using epios: gentoo derivative for epia mobo's)
brian wrote:
brian wrote:
File /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py, line
225, in querycap
r = fcntl.ioctl(self.device, i32(QUERYCAP_NO), val)
IOError: [Errno 22] Invalid argument
Sounds like Freevo != 1.5.4 and Python 2.4. Please update Freevo.
Dischi
I just checked my install and it was 1.5.4. but just to make sure i
removed it and installed from the SourceInstallation, and have the
same problem. Any other suggestions would be greatly appreciated.
Hi Brian,
by coincedence I just had a similar problem solved, unfortunately it
wasn't the exact same. The discussion is on the devel list if you want
to look up the archives. Here are two suggestions that might apply to
you though.
From Duncan:
I now remember that I send a message back in November about a problem
with v4l2.py and the AMD64 maybe this problem is not limited to the AMD64.
Here's a patch that I've done for this problem:
http://www.linuxowl.com/patches/freevo-1.5.4-v4l2.py.patch
Python was using 'L' for 64bit ints and the interface wanted 32bit ints.
Regards,
Duncan
--- freevo-1.5.4/src/tv/v4l2.py.orig2005-10-16 11:18:50.0
+0200
+++ freevo-1.5.4/src/tv/v4l2.py 2005-11-13 15:13:15.0 +0100
@@ -100,6 +100,7 @@
SETFREQ_NO_V4L = _IOW('v', 15, L)
QUERYCAP_ST = 16s32s32sLL16x
+QUERYCAP_ST = 16s32s32sII16x #NEW
QUERYCAP_NO = _IOR('V', 0, QUERYCAP_ST)
ENUMSTD_ST = LQ24s2LL16x
@@ -112,11 +113,13 @@
ENUMINPUT_ST = L32sLLLQL16x
ENUMINPUT_NO = _IOWR('V', 26, ENUMINPUT_ST)
-INPUT_ST = L;
+INPUT_ST = L
+INPUT_ST = I; #NEW
GETINPUT_NO = _IOR('V', 38, INPUT_ST)
SETINPUT_NO = _IOWR('V', 39, INPUT_ST)
FMT_ST = L7L4x168x
+FMT_ST = L7I4x168x #NEW
GET_FMT_NO = _IOWR ('V', 4, FMT_ST)
SET_FMT_NO = _IOWR ('V', 5, FMT_ST)
From RobertW:
What i recall is when DEBUG is set in local_conf.py some extra
informational ioctl is called. This bug is there for a year or maybe
more :-) . User can workaround this by disabling DEBUG or removing (if
DEBUG: v.print_settings()) in ivtv_record.py as Rob already pointed
out or apply the following oneliner patch provided by Duncan Web back
in september and not the one he mentioned earlier in this thread ;-)
--- v4l2.py 2006-01-05 20:56:22.0 +0100
+++ v4l2.py.orig2006-01-05 20:53:54.0 +0100
@@ -243,7 +243,7 @@
def getfmt(self):
-val = struct.pack( FMT_ST, 1L,0,0,0,0,0,0,0)
+val = struct.pack( FMT_ST, 0,0,0,0,0,0,0,0)
r = fcntl.ioctl(self.device,GET_FMT_NO,val)
return struct.unpack( FMT_ST, r )
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
http://gedeco.no-ip.org
freevo-recordserver-python-2.4.patch
Description: Binary data
mixer_i32.patch
Description: Binary data
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
I'm cross posting this onto the devel list (and top posting - sorry).
Looks like another python2.4 and ivtv driver issue and they are running
1.5.4. Can someone (Rob again :)) take a look?
Thanks,
John
Geert Decorte wrote:
This is a simple metoo reply.
None of the patches John described worked for me.
Have the impression this is specific on python 2.4 acting different then
python 2.3
I have a hauppage MCE 500 working under linux on a epia motherboard.
(using epios: gentoo derivative for epia mobo's)
brian wrote:
brian wrote:
File /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py, line
225, in querycap
r = fcntl.ioctl(self.device, i32(QUERYCAP_NO), val)
IOError: [Errno 22] Invalid argument
Sounds like Freevo != 1.5.4 and Python 2.4. Please update Freevo.
Dischi
I just checked my install and it was 1.5.4. but just to make sure i
removed it and installed from the SourceInstallation, and have the
same problem. Any other suggestions would be greatly appreciated.
Hi Brian,
by coincedence I just had a similar problem solved, unfortunately it
wasn't the exact same. The discussion is on the devel list if you want
to look up the archives. Here are two suggestions that might apply to
you though.
From Duncan:
I now remember that I send a message back in November about a problem
with v4l2.py and the AMD64 maybe this problem is not limited to the AMD64.
Here's a patch that I've done for this problem:
http://www.linuxowl.com/patches/freevo-1.5.4-v4l2.py.patch
Python was using 'L' for 64bit ints and the interface wanted 32bit ints.
Regards,
Duncan
--- freevo-1.5.4/src/tv/v4l2.py.orig2005-10-16 11:18:50.0
+0200
+++ freevo-1.5.4/src/tv/v4l2.py 2005-11-13 15:13:15.0 +0100
@@ -100,6 +100,7 @@
SETFREQ_NO_V4L = _IOW('v', 15, L)
QUERYCAP_ST = 16s32s32sLL16x
+QUERYCAP_ST = 16s32s32sII16x #NEW
QUERYCAP_NO = _IOR('V', 0, QUERYCAP_ST)
ENUMSTD_ST = LQ24s2LL16x
@@ -112,11 +113,13 @@
ENUMINPUT_ST = L32sLLLQL16x
ENUMINPUT_NO = _IOWR('V', 26, ENUMINPUT_ST)
-INPUT_ST = L;
+INPUT_ST = L
+INPUT_ST = I; #NEW
GETINPUT_NO = _IOR('V', 38, INPUT_ST)
SETINPUT_NO = _IOWR('V', 39, INPUT_ST)
FMT_ST = L7L4x168x
+FMT_ST = L7I4x168x #NEW
GET_FMT_NO = _IOWR ('V', 4, FMT_ST)
SET_FMT_NO = _IOWR ('V', 5, FMT_ST)
From RobertW:
What i recall is when DEBUG is set in local_conf.py some extra
informational ioctl is called. This bug is there for a year or maybe
more :-) . User can workaround this by disabling DEBUG or removing (if
DEBUG: v.print_settings()) in ivtv_record.py as Rob already pointed
out or apply the following oneliner patch provided by Duncan Web back
in september and not the one he mentioned earlier in this thread ;-)
--- v4l2.py 2006-01-05 20:56:22.0 +0100
+++ v4l2.py.orig2006-01-05 20:53:54.0 +0100
@@ -243,7 +243,7 @@
def getfmt(self):
-val = struct.pack( FMT_ST, 1L,0,0,0,0,0,0,0)
+val = struct.pack( FMT_ST, 0,0,0,0,0,0,0,0)
r = fcntl.ioctl(self.device,GET_FMT_NO,val)
return struct.unpack( FMT_ST, r )
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
http://gedeco.no-ip.org
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: ivtv not working
This is a simple metoo reply.
None of the patches John described worked for me.
Have the impression this is specific on python 2.4 acting different then
python 2.3
I have a hauppage MCE 500 working under linux on a epia motherboard.
(using epios: gentoo derivative for epia mobo's)
brian wrote:
brian wrote:
File /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py, line
225, in querycap
r = fcntl.ioctl(self.device, i32(QUERYCAP_NO), val)
IOError: [Errno 22] Invalid argument
Sounds like Freevo != 1.5.4 and Python 2.4. Please update Freevo.
Dischi
I just checked my install and it was 1.5.4. but just to make sure i
removed it and installed from the SourceInstallation, and have the
same problem. Any other suggestions would be greatly appreciated.
Hi Brian,
by coincedence I just had a similar problem solved, unfortunately it
wasn't the exact same. The discussion is on the devel list if you want
to look up the archives. Here are two suggestions that might apply to
you though.
From Duncan:
I now remember that I send a message back in November about a problem
with v4l2.py and the AMD64 maybe this problem is not limited to the AMD64.
Here's a patch that I've done for this problem:
http://www.linuxowl.com/patches/freevo-1.5.4-v4l2.py.patch
Python was using 'L' for 64bit ints and the interface wanted 32bit ints.
Regards,
Duncan
--- freevo-1.5.4/src/tv/v4l2.py.orig2005-10-16 11:18:50.0
+0200
+++ freevo-1.5.4/src/tv/v4l2.py 2005-11-13 15:13:15.0 +0100
@@ -100,6 +100,7 @@
SETFREQ_NO_V4L = _IOW('v', 15, L)
QUERYCAP_ST = 16s32s32sLL16x
+QUERYCAP_ST = 16s32s32sII16x #NEW
QUERYCAP_NO = _IOR('V', 0, QUERYCAP_ST)
ENUMSTD_ST = LQ24s2LL16x
@@ -112,11 +113,13 @@
ENUMINPUT_ST = L32sLLLQL16x
ENUMINPUT_NO = _IOWR('V', 26, ENUMINPUT_ST)
-INPUT_ST = L;
+INPUT_ST = L
+INPUT_ST = I; #NEW
GETINPUT_NO = _IOR('V', 38, INPUT_ST)
SETINPUT_NO = _IOWR('V', 39, INPUT_ST)
FMT_ST = L7L4x168x
+FMT_ST = L7I4x168x #NEW
GET_FMT_NO = _IOWR ('V', 4, FMT_ST)
SET_FMT_NO = _IOWR ('V', 5, FMT_ST)
From RobertW:
What i recall is when DEBUG is set in local_conf.py some extra
informational ioctl is called. This bug is there for a year or maybe
more :-) . User can workaround this by disabling DEBUG or removing (if
DEBUG: v.print_settings()) in ivtv_record.py as Rob already pointed
out or apply the following oneliner patch provided by Duncan Web back
in september and not the one he mentioned earlier in this thread ;-)
--- v4l2.py 2006-01-05 20:56:22.0 +0100
+++ v4l2.py.orig2006-01-05 20:53:54.0 +0100
@@ -243,7 +243,7 @@
def getfmt(self):
-val = struct.pack( FMT_ST, 1L,0,0,0,0,0,0,0)
+val = struct.pack( FMT_ST, 0,0,0,0,0,0,0,0)
r = fcntl.ioctl(self.device,GET_FMT_NO,val)
return struct.unpack( FMT_ST, r )
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
http://gedeco.no-ip.org
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: ivtv not working
brian wrote:
brian wrote:
File /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py, line
225, in querycap
r = fcntl.ioctl(self.device, i32(QUERYCAP_NO), val)
IOError: [Errno 22] Invalid argument
Sounds like Freevo != 1.5.4 and Python 2.4. Please update Freevo.
Dischi
I just checked my install and it was 1.5.4. but just to make sure i
removed it and installed from the SourceInstallation, and have the
same problem. Any other suggestions would be greatly appreciated.
Hi Brian,
by coincedence I just had a similar problem solved, unfortunately it
wasn't the exact same. The discussion is on the devel list if you want
to look up the archives. Here are two suggestions that might apply to
you though.
From Duncan:
I now remember that I send a message back in November about a problem
with v4l2.py and the AMD64 maybe this problem is not limited to the AMD64.
Here's a patch that I've done for this problem:
http://www.linuxowl.com/patches/freevo-1.5.4-v4l2.py.patch
Python was using 'L' for 64bit ints and the interface wanted 32bit ints.
Regards,
Duncan
--- freevo-1.5.4/src/tv/v4l2.py.orig2005-10-16 11:18:50.0 +0200
+++ freevo-1.5.4/src/tv/v4l2.py 2005-11-13 15:13:15.0 +0100
@@ -100,6 +100,7 @@
SETFREQ_NO_V4L = _IOW('v', 15, L)
QUERYCAP_ST = 16s32s32sLL16x
+QUERYCAP_ST = 16s32s32sII16x #NEW
QUERYCAP_NO = _IOR('V', 0, QUERYCAP_ST)
ENUMSTD_ST = LQ24s2LL16x
@@ -112,11 +113,13 @@
ENUMINPUT_ST = L32sLLLQL16x
ENUMINPUT_NO = _IOWR('V', 26, ENUMINPUT_ST)
-INPUT_ST = L;
+INPUT_ST = L
+INPUT_ST = I; #NEW
GETINPUT_NO = _IOR('V', 38, INPUT_ST)
SETINPUT_NO = _IOWR('V', 39, INPUT_ST)
FMT_ST = L7L4x168x
+FMT_ST = L7I4x168x #NEW
GET_FMT_NO = _IOWR ('V', 4, FMT_ST)
SET_FMT_NO = _IOWR ('V', 5, FMT_ST)
From RobertW:
What i recall is when DEBUG is set in local_conf.py some extra
informational ioctl is called. This bug is there for a year or maybe
more :-) . User can workaround this by disabling DEBUG or removing (if
DEBUG: v.print_settings()) in ivtv_record.py as Rob already pointed
out or apply the following oneliner patch provided by Duncan Web back
in september and not the one he mentioned earlier in this thread ;-)
--- v4l2.py 2006-01-05 20:56:22.0 +0100
+++ v4l2.py.orig2006-01-05 20:53:54.0 +0100
@@ -243,7 +243,7 @@
def getfmt(self):
-val = struct.pack( FMT_ST, 1L,0,0,0,0,0,0,0)
+val = struct.pack( FMT_ST, 0,0,0,0,0,0,0,0)
r = fcntl.ioctl(self.device,GET_FMT_NO,val)
return struct.unpack( FMT_ST, r )
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
[Freevo-users] Re: ivtv not working in freevo
brian wrote: File /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py, line 225, in querycap r = fcntl.ioctl(self.device, i32(QUERYCAP_NO), val) IOError: [Errno 22] Invalid argument Sounds like Freevo != 1.5.4 and Python 2.4. Please update Freevo. Dischi -- Q: Why do programmers always get Christmas and Halloween mixed up? A: Because DEC 25 = OCT 31 pgpH4OITyl8x0.pgp Description: PGP signature
[Freevo-users] Re: ivtv not working
brian wrote: File /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py, line 225, in querycap r = fcntl.ioctl(self.device, i32(QUERYCAP_NO), val) IOError: [Errno 22] Invalid argument Sounds like Freevo != 1.5.4 and Python 2.4. Please update Freevo. Dischi I just checked my install and it was 1.5.4. but just to make sure i removed it and installed from the SourceInstallation, and have the same problem. Any other suggestions would be greatly appreciated. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
