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
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
