Mailing List Archive: ivtv: devel

Why won't my firmware load?

Index | Next | Previous | View Threaded

misassistant at yahoo

Apr 7, 2008, 11:42 AM

Post #1 of 12 (2610 views)
Permalink

Why won't my firmware load?

I have recently decided to make the leap from my
rickety old 2.4.32 kernel over to a bright, shiny
2.6.24.4, and I immediately realized all kinds of
benefits, not the least of which was the ability to
use all my EIDE/SATA ports.
I also dutifully compiled in the new kernel support
for IVTV, all as modules, of course.
Having used my PVR-350 for the last few years on the
2.4 series of kernels, I was eagerly expecting to
finish the last component that would compell me to
make the switch over to 2.6 permanent.
Well, I have been frustrated to all ends of the earth
on this one, as I am unable to use my PVR-350 at all.
I first discovered that it would not load the modules,
but not load the firmware at all, so I poked around on
the web for a while until I saw that the 2.6.24
kernels require that the ivtvfb module be loaded to
enable firmware loading.
So, I went to "modprobe -r ivtv" to unload all the
modules first (yes, I checked to ensure that all the
modules unloaded with lsmod), then executed a
"modprobe -v ivtvfb."
Well, all the modules quickly load until the ivtvfb
module, then it sits for about two full minutes, then
exits with the error "FATAL: Error inserting ivtvfb
(/lib/modules/2.6.24.4/kernel/drivers/media/video/ivtv/ivtvfb.ko):
No such device"
Hmmm...
I did a "dmesg" and saw the following information:

ivtv0: Removed Hauppauge WinTV PVR-350, card #0
Linux video capture interface: v2.00
ivtv: Start initialization, version 1.1.0
ivtv0: Initializing card #0
ivtv0: Autodetected Hauppauge card (cx23415 based)
ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level,
low) -> IRQ 22
ivtv0: YUV filter table not found in firmware.
msp3400 4-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c
driver #0)
msp3400 4-0040: MSP4448G-A2 supports radio, mode is
autodetect and autoselect
saa7115 4-0021: saa7115 found (1f7115d0e100000) @ 0x42
(ivtv i2c driver #0)
tuner 4-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 4-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 4-0043: type set to tda9887
tuner 4-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tveeprom 4-0050: Hauppauge model 48132, rev K168,
serial# 2947630
tveeprom 4-0050: tuner model is LG TAPE H001F MK3 (idx
68, type 47)
tveeprom 4-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 4-0050: audio processor is MSP4448 (idx 27)
tveeprom 4-0050: decoder processor is SAA7115 (idx 19)
tveeprom 4-0050: has radio, has IR receiver, has no IR
transmitter
ivtv0: Autodetected Hauppauge WinTV PVR-350
saa7127 4-0044: saa7127 found @ 0x88 (ivtv i2c driver
#0)
tuner-simple 4-0061: type set to 47 (LG NTSC (TAPE
series))
tuner 4-0061: type set to LG NTSC (TAPE serie
ivtv0: Registered device video0 for encoder MPG (4096
kB)
ivtv0: Registered device video32 for encoder YUV (2048
kB)
ivtv0: Registered device vbi0 for encoder VBI (1024
kB)
ivtv0: Registered device video24 for encoder PCM (320
kB)
ivtv0: Registered device radio0 for encoder radio
ivtv0: Registered device video16 for decoder MPG (1024
kB)
ivtv0: Registered device vbi8 for decoder VBI (64 kB)
ivtv0: Registered device vbi16 for decoder VOUT
ivtv0: Registered device video48 for decoder YUV (1024
kB)
ivtv0: Initialized card #0: Hauppauge WinTV PVR-350
ivtv: End initialization
ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
(must be 376836 bytes)
ivtv0: Did you put the firmware in the hotplug
firmware directory?
ivtv0: Retry loading firmware
ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
(must be 376836 bytes)v4l-cx2341x-init-mpg.bin
ivtv0: Did you put the firmware in the hotplug
firmware directory?
ivtvfb0: Failed to initialize ivtv
ivtvfb: no cards found

Now, I put all of the required firmware files (named
properly, mind you) in /lib/modules, /lib/firmware
/usr/lib/hotplug/firmware.
And, yes, I also created symbolic links for
v4l-cx2341x-init.mpg over to v4l-cx2341x-init-mpg.bin
v4l-cx2341x-init-mpeg.bin (for good measure) in those
directories, all to no avail.
Is there some hidden kernel parameter that still needs
to be enabled?
Is there a new version of the hotplug package that
needs to be installed?
I also just now installed udev-1.20, and that didn't
work, either.
Is there something in my /etc directory that I should
be doing here?
Also, it seems to at least attempt to load those
firmware files, but it reports the size as incorrect.
WTF?
I have to brush the handsful of hair I have pulled out
off my keyboard to type this.
Anyone? Anyone? Bueller?

____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

sander.sweers at gmail

Apr 7, 2008, 12:22 PM

Post #2 of 12 (2518 views)
Permalink

Re: Why won't my firmware load? [In reply to]

On Mon, Apr 7, 2008 at 11:42 AM, Scott A. Conway <misassistant[at]yahoo.com> wrote:
> Having used my PVR-350 for the last few years on the
> 2.4 series of kernels, I was eagerly expecting to
> finish the last component that would compell me to
> make the switch over to 2.6 permanent.

[snip]

> So, I went to "modprobe -r ivtv" to unload all the
> modules first (yes, I checked to ensure that all the
> modules unloaded with lsmod), then executed a
> "modprobe -v ivtvfb."
> Well, all the modules quickly load until the ivtvfb
> module, then it sits for about two full minutes, then
> exits with the error "FATAL: Error inserting ivtvfb
> (/lib/modules/2.6.24.4/kernel/drivers/media/video/ivtv/ivtvfb.ko):
> No such device"

[snip]

> ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
> (must be 376836 bytes)

A lot has changed since then when it comes to the firmware versions,
and how they are loaded. I would recommend you get the latest
recommended firmware from [1]. I expect your problems will go away.

Greets
Sander

[1] http://dl.ivtvdriver.org/ivtv/firmware/firmware.tar.gz

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

misassistant at yahoo

Apr 7, 2008, 1:08 PM

Post #3 of 12 (2523 views)
Permalink

Re: Why won't my firmware load? [In reply to]

--- Sander Sweers <sander.sweers[at]gmail.com> wrote:

> On Mon, Apr 7, 2008 at 11:42 AM, Scott A. Conway
> <misassistant[at]yahoo.com> wrote:
> > Having used my PVR-350 for the last few years on
> the
> > 2.4 series of kernels, I was eagerly expecting to
> > finish the last component that would compell me
> to
> > make the switch over to 2.6 permanent.
>
> [snip]
>
> > So, I went to "modprobe -r ivtv" to unload all
> the
> > modules first (yes, I checked to ensure that all
> the
> > modules unloaded with lsmod), then executed a
> > "modprobe -v ivtvfb."
> > Well, all the modules quickly load until the
> ivtvfb
> > module, then it sits for about two full minutes,
> then
> > exits with the error "FATAL: Error inserting
> ivtvfb
> >
>
(/lib/modules/2.6.24.4/kernel/drivers/media/video/ivtv/ivtvfb.ko):
> > No such device"
>
> [snip]
>
> > ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
> > (must be 376836 bytes)
>
> A lot has changed since then when it comes to the
> firmware versions,
> and how they are loaded. I would recommend you get
> the latest
> recommended firmware from [1]. I expect your
> problems will go away.
>
> Greets
> Sander
>
> [1]
>
http://dl.ivtvdriver.org/ivtv/firmware/firmware.tar.gz

I hate to break it to you, but that is the firmware
that I am using in all three of the locations I
mentioned in my original query.
Also, that firmware exits with the same error about
incorrect size with both 2.6.22 and 2.6.23.
What now?

____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

sander.sweers at gmail

Apr 7, 2008, 1:29 PM

Post #4 of 12 (2519 views)
Permalink

Re: Why won't my firmware load? [In reply to]

On Mon, Apr 7, 2008 at 1:08 PM, Scott A. Conway <misassistant[at]yahoo.com> wrote:
> ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
> (must be 376836 bytes)
>
> http://dl.ivtvdriver.org/ivtv/firmware/firmware.tar.gz
>
> I hate to break it to you, but that is the firmware
> that I am using in all three of the locations I
> mentioned in my original query.
> Also, that firmware exits with the same error about
> incorrect size with both 2.6.22 and 2.6.23.
> What now?

Seeing the error I am pretty sure it is loading the wrong sized
firmware from somewhere. I do not know where "your distro" looks for
firmware but usually this is /lib/firmware.

Greets
Sander

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

ttrafford at gmail

Apr 7, 2008, 1:43 PM

Post #5 of 12 (2516 views)
Permalink

Re: Why won't my firmware load? [In reply to]

Scott A. Conway wrote:

> I first discovered that it would not load the modules, but not load
> the firmware at all, so I poked around on the web for a while until I
> saw that the 2.6.24 kernels require that the ivtvfb module be loaded
> to enable firmware loading.

I don't believe this is true.

> ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
> (must be 376836 bytes)
> ivtv0: Did you put the firmware in the hotplug
> firmware directory?

> Now, I put all of the required firmware files (named properly, mind
> you) in /lib/modules, /lib/firmware /usr/lib/hotplug/firmware.

Is udev installed from source then? If so, where is your firmware.sh
located?
--
Tyler Trafford

A sect or party is an elegant incognito devised to save a man from
the vexation of thinking.
-- Ralph Waldo Emerson, Journals, 1831

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

ttrafford at gmail

Apr 7, 2008, 2:20 PM

Post #6 of 12 (2508 views)
Permalink

Re: Why won't my firmware load? [In reply to]

Sander Sweers wrote:
> On Mon, Apr 7, 2008 at 1:08 PM, Scott A. Conway <misassistant[at]yahoo.com> wrote:
> > ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
> > (must be 376836 bytes)
> >
> > http://dl.ivtvdriver.org/ivtv/firmware/firmware.tar.gz
> >
> > I hate to break it to you, but that is the firmware
> > that I am using in all three of the locations I
> > mentioned in my original query.
> > Also, that firmware exits with the same error about
> > incorrect size with both 2.6.22 and 2.6.23.
> > What now?
>
> Seeing the error I am pretty sure it is loading the wrong sized
> firmware from somewhere. I do not know where "your distro" looks for
> firmware but usually this is /lib/firmware.

That message is a general failure. It doesn't mean it actually found a
file and it was the wrong size.
--
Tyler Trafford

A sect or party is an elegant incognito devised to save a man from
the vexation of thinking.
-- Ralph Waldo Emerson, Journals, 1831

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

misassistant at yahoo

Apr 7, 2008, 6:24 PM

Post #7 of 12 (2497 views)
Permalink

Re: Why won't my firmware load? [In reply to]

--- Tyler Trafford <ttrafford[at]gmail.com> wrote:

> Scott A. Conway wrote:
>
> > I first discovered that it would not load the
> modules, but not load
> > the firmware at all, so I poked around on the web
> for a while until I
> > saw that the 2.6.24 kernels require that the
> ivtvfb module be loaded
> > to enable firmware loading.
>
> I don't believe this is true.

I beg to differ.
2.6.22 and 2.6.23 both attempt to autoload the
firmware with or without the frame buffer module.
2.6.24.4, however, loads only the modules without
attempting firmware loading.
If I do a "modprobe ivtvfb," however, it DOES attempt,
ending of course, in failure, as I have indicated.
Keep in mind here that the IVTV Frame Buffer module
changed name from "ivtv-fb" to "ivtvfb" with the
2.6.24 kernel.

> > ivtv0: Unable to open firmware v4l-cx2341x-enc.fw
> > (must be 376836 bytes)
> > ivtv0: Did you put the firmware in the hotplug
> > firmware directory?
>
> > Now, I put all of the required firmware files
> (named properly, mind
> > you) in /lib/modules, /lib/firmware
> /usr/lib/hotplug/firmware.
>
> Is udev installed from source then? If so, where is

Affirmative.
I compiled, then installed ver 1.20 from source
myself.

> your firmware.sh
> located?

/usr/lib/udev

Frustating...isn't it?

____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

ttrafford at gmail

Apr 7, 2008, 7:43 PM

Post #8 of 12 (2503 views)
Permalink

Re: Why won't my firmware load? [In reply to]

Scott A. Conway wrote:
> --- Tyler Trafford <ttrafford[at]gmail.com> wrote:
>
>> Scott A. Conway wrote:
>>
>>> I first discovered that it would not load the
>> modules, but not load
>>> the firmware at all, so I poked around on the web
>> for a while until I
>>> saw that the 2.6.24 kernels require that the
>> ivtvfb module be loaded
>>> to enable firmware loading.
>> I don't believe this is true.
>
> I beg to differ.
> 2.6.22 and 2.6.23 both attempt to autoload the
> firmware with or without the frame buffer module.
> 2.6.24.4, however, loads only the modules without
> attempting firmware loading.

Oh right, that firmware load was moved. It now happens before the first
capture, not at module load time.

I didn't think that change was in the kernel yet.

>> your firmware.sh
>> located?
>
> /usr/lib/udev
>
> Frustating...isn't it?

There should be a /etc/udev/hotplug.rules. At the end of that file is a
commented line to enable some verbose debugging to /var/log/hotplug.log.

Try enabling that and then rebooting.
--
Tyler Trafford

A sect or party is an elegant incognito devised to save a man from
the vexation of thinking.
-- Ralph Waldo Emerson, Journals, 1831

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

ttrafford at gmail

Apr 7, 2008, 7:50 PM

Post #9 of 12 (2498 views)
Permalink

Re: Why won't my firmware load? [In reply to]

Tyler Trafford wrote:
> There should be a /etc/udev/hotplug.rules. At the end of that file is a
> commented line to enable some verbose debugging to /var/log/hotplug.log.
>
> Try enabling that and then rebooting.

Oh that may be distribution dependant... first check that one of the
rules files in /etc/udev has this:

SUBSYSTEM=="firmware", RUN+="firmware.sh"

--
Tyler Trafford

A sect or party is an elegant incognito devised to save a man from
the vexation of thinking.
-- Ralph Waldo Emerson, Journals, 1831

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

misassistant at yahoo

Apr 7, 2008, 9:07 PM

Post #10 of 12 (2488 views)
Permalink

Re: Why won't my firmware load? [In reply to]

--- Tyler Trafford <ttrafford[at]gmail.com> wrote:

> Scott A. Conway wrote:
> > --- Tyler Trafford <ttrafford[at]gmail.com> wrote:
> >
> >> Scott A. Conway wrote:
> >>
> >>> I first discovered that it would not load the
> >> modules, but not load
> >>> the firmware at all, so I poked around on the
> web
> >> for a while until I
> >>> saw that the 2.6.24 kernels require that the
> >> ivtvfb module be loaded
> >>> to enable firmware loading.
> >> I don't believe this is true.
> >
> > I beg to differ.
> > 2.6.22 and 2.6.23 both attempt to autoload the
> > firmware with or without the frame buffer module.
> > 2.6.24.4, however, loads only the modules without
> > attempting firmware loading.
>
> Oh right, that firmware load was moved. It now
> happens before the first
> capture, not at module load time.
>
> I didn't think that change was in the kernel yet.
>
> >> your firmware.sh
> >> located?
> >
> > /usr/lib/udev
> >
> > Frustating...isn't it?
>
> There should be a /etc/udev/hotplug.rules. At the

Interestingly enough, I have no such file, either in
the source packages for hotplug, the source for udev,
or even lurking somewhere on my system ANYWHERE.
Am I in some kind of parallel universe?

> end of that file is a
> commented line to enable some verbose debugging to
> /var/log/hotplug.log.
>
> Try enabling that and then rebooting.

Sadly, it appears that I have no such recourse.
Man, this is about as easy to figure out as Chinese
arithmetic.
:-(

____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

misassistant at yahoo

Apr 8, 2008, 1:25 AM

Post #11 of 12 (2485 views)
Permalink

Re: Why won't my firmware load? => It does NOW! [In reply to]

--- Tyler Trafford <ttrafford[at]gmail.com> wrote:

> Tyler Trafford wrote:
> > There should be a /etc/udev/hotplug.rules. At the
> end of that file is a
> > commented line to enable some verbose debugging to
> /var/log/hotplug.log.
> >
> > Try enabling that and then rebooting.
>
> Oh that may be distribution dependant... first check
> that one of the
> rules files in /etc/udev has this:
>
> SUBSYSTEM=="firmware", RUN+="firmware.sh"

Success!
I finally used the "--verbose" flag with udevd to find
the two problems that were, in fact, stopping it from
loading the firmware at all, error about file size
notwithstanding.
I quickly learned that it was looking for firmware.sh
in /lib/udev instead of in /usr/lib/udev.
It was trivial to create that directory, then copy the
firmware.sh file to it.
Next, I discovered an error about "...missing sysfs.."
(sorry, I didn't save the full text), so I poked
around until I realized that I needed to have a /sys
properly mounted via /etc/fstab.
Coming over from a 2.4 kernel, I was unaware that I
needed that.
Rebooted, did a simple "modprobe ivtvfb," and it
easily loads the firmware!
Yipee!
I can now change channels, then view the output from
/dev/video0.
The moral of this story is to start up udev in exactly
this way to force it to spit out all manner of useful
information:
udev --verbose --daemon

Okay, now I have a more minor problem that needs
addressing, which is the terribly sluggish playback
that makes the audio quickly outrun the video, looking
worse than the crappiest Kung-Fu movie I ever saw.
This occurs when I do a simple "mplayer /dev/video0"
Again, I am certain that my system has plenty of
horsepower to watch output directly from the video
capture device, as I am running a P4 3.0GHz with 2.5GB
RAM, and it easily played video directly that way
using my 2.4 kernel with not even a hint of
sluggishness.
I imagine that I either need to enable a flag when
loading the modules, or I need to use an option with
the userspace utilities that come with the IVTV
package, such as ivtvctl.
Anyone wanna take a crack at this one?

____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

misassistant at yahoo

Apr 8, 2008, 2:35 AM

Post #12 of 12 (2472 views)
Permalink

Re: Why won't my firmware load? => It does NOW! [In reply to]

--- "Scott A. Conway" <misassistant[at]yahoo.com> wrote:
[...]
> Okay, now I have a more minor problem that needs
> addressing, which is the terribly sluggish playback
> that makes the audio quickly outrun the video,
> looking
> worse than the crappiest Kung-Fu movie I ever saw.
> This occurs when I do a simple "mplayer /dev/video0"
> Again, I am certain that my system has plenty of
> horsepower to watch output directly from the video
> capture device, as I am running a P4 3.0GHz with
> 2.5GB
> RAM, and it easily played video directly that way
> using my 2.4 kernel with not even a hint of
> sluggishness.
> I imagine that I either need to enable a flag when
> loading the modules, or I need to use an option with
> the userspace utilities that come with the IVTV
> package, such as ivtvctl.
> Anyone wanna take a crack at this one?

Sorry, folks!
My bust here, but it turned out to be the simple lack
of my using the "-cache 8192" flag with mplayer to
make the audio/video burps stop completely.
With that flag, I now get perfectly smooth playback.
That little command line flag might come in handy for
the novices out there, much as I hate to admit that I
confounded myself with such a rookie mistake.
:-~

____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

_______________________________________________
ivtv-devel mailing list
ivtv-devel[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com