Rajesh Perumal wrote:
----- Original Message -----
From: Rajesh Perumal <[EMAIL PROTECTED]>
Date: Sunday, September 17, 2006 2:06 pm
Subject: Re: [ivtv-users] unable to open firmware v4l-cx2341x-init.mpg
----- Original Message -----
From: Sander Sweers <[EMAIL PROTECTED]>
Date: Sunday, September 17, 2006 1:31 pm
Subject: Re: [ivtv-users] unable to open firmware v4l-cx2341x-init.mpg
Rajesh Perumal wrote:
-rwxrwxrwx 1 root root 262144 May 29 15:31 v4l-cx2341x-dec.fw
-rwxrwxrwx 1 root root 376836 Jan 17 2005 v4l-cx2341x-enc.fw
-rwxrwxrwx 1 root root 155648 Sep 17 13:50 v4l-cx2341x-init.mpg
Here is another cut and paste of dmesg:
ivtv: no version for "struct_module" found: kernel tainted.
ivtv: ==================== START INIT IVTV
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Decoder revision: 0x02020023
So i've been looking at this all afternoon and I finally noticed something out
of the ordinary. In the dmesg for IVTV, there are two lines that stick out to
me based on the amount of bytes listed in the brackets:
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
But if I do a directory listing on where the files are located in /lib/firmware, the size of v4l-cx2341x-enc.fw firmware is 376836 bytes. That differs from what is listed in dmesg. The v4l-cx2341x-dec.fw file is the correct size at 262144 bytes. This makes me think that it is not actually reading /lib/firmware and getting the files from somewhere else. I did an updatedb and then did a locate on v4l-cx2341x-enc.fw and I can only find the actual file in /lib/firmware, and all the other folders are symlinks. I can't find a file that matches the amount of bytes that is listed above.
So then I tried another test. I removed every single symlink related to the
v4l-cx2341x-enc.fw file and the v4l-cx2341x-dec.fw file and also renamed the
original files to something else. Then I rebooted and checked dmesg. If it was
reading it from that folder it should have failed to initialize the enc and dec
firmware. Here's the weird part, it still loaded the firmware successfully
according to dmesg! Now this proves it's not loading the firmware from those
files in the /lib/firmware folder. Of course i'm a beginner when it comes to
Linux so I might be missing something that is really obvious to you pros out
there. I'm hoping someone who knows more about Linux than me can shed some
light on this.
I figure the answer lies in finding out where it's actually loading the
firmware from, and then making sure all the necessary files are there with the
right versions.
If anyone has any suggestions on how I can find out where it's loading the
firmware from it would be greatly appreciated.
-Thanks, Raj
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
1st thing would be to find all instances of that file:
$ find / -name 'v4l-cx2341x-*.fw'
- or -
$ locate v4l-cx2341x
If it's only in 2 places, or one other place, you have your culprit.
If it's in several, then you can either rename and figure out via
process of elimination, or you can go look in your firmware helper file
and figure out which instance would have precedence.
--
Mark Paulus
2424 Garden of the Gods Rd | Phone: v622-5578 / 719-535-5578
0419/117 - LEC Access ; D5-1010 | FAX: 719-535-1665
Colo Springs, CO 80919 | 1800PageMCI / 1406052
AIM : mgpaulus1 / sametime : mark.paulus
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-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
