I posted about this some time ago. I'm still trying to figure out the proper fix, but putting /sbin/udevsend in /proc/sys/kernel/hotplug has worked as a temporary workaround for me.
--Brian Jackson On Monday 13 March 2006 14:05, dill weed wrote: > Sorry if this is a question that has already been asked or if this is the > wrong list, howerver, I can't find a workable solution and am looking here > for help. Anyways, I'm trying to get the firmware loaded so that my capture > cards work. > > A little about my system. I have one PVR-250 and one PVR-500 in my system > I'm also running an up to date Gentoo system with a 2.6.15 kernel. I know > the cards work, because they worked with earlier versions of the ivtv > driver. But because of other issues with the computer I went back to a > Windows system until different drivers (ndiswrapper) became more refined > and didn't keep locking up my system. > > Anyways, I remember that ivtv drivers use to look for firmware in the > /lib/modules directory, but that has since moved to a hotplug system. Not > sure if that is good or bad, but it is causing me to pull my hair out, and > I don't have much left as it is. It seems that Gentoo uses udev as default > to load drivers upon booting. If udev doesn't have the proper rules its > suppose to "switch/call" hotplug to finish the process. However, this > doesn't seem to be working properly though. When ever I load ivtv into the > kernel I get this: > > (start > snip)---------------------------------------------------------------------- >----------------------------------------- > > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.4.3 (tagged release) loading > ivtv: Linux version: 2.6.15-gentoo-r1 preempt K7 gcc-3.4 > ivtv: In case of problems please include the debug info between > ivtv: the START INIT IVTV and END INIT IVTV lines, along with > ivtv: any module options, when mailing the ivtv-users mailinglist. > ivtv0: Autodetected WinTV PVR 250 card (cx23416 based) > ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> > IRQ 5 > tveeprom: ivtv version > tveeprom: Hauppauge: model = 32062, rev = C199, serial# = 8115600 > tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50) > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) > tveeprom: audio processor = MSP3445 (type = c) > tveeprom: decoder processor = SAA7115 (type = 13) > ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] > tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 > ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] > saa7115 0-0021: ivtv driver > saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) > ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] > msp3400 0-0040: ivtv driver > msp3400 0-0040: chip=MSP3445G-B8 +nicam +simple +simpler +radio > mode=simpler > > msp3400 0-0040: msp34xxg daemon started > ivtv0: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40] > ivtv0: unable to open firmware v4l-cx2341x-enc.fw > ivtv0: did you put the firmware in the hotplug firmware directory? > ivtv0 warning: failed loading encoder firmware > ivtv0 warning: Error loading firmware -3! > ivtv0: Error -3 initializing firmware. > ivtv0: Error -12 on initialization > ivtv: probe of 0000:00:0b.0 failed with error -12 > > (end snip, happens for both all > cards)-------------------------------------------------------------- > > Supposedly hotplug is looking for firmware in /lib/firmware according to > /etc/hotplug/firmware.agent, but for some reason it doesn't see it. If I do > this "cat "/sbin/hotplug" > /proc/sys/kernel/hotplug" then ivtv loads > perfectly. Upon rebooting /proc/sys/kernel/hotplug reverts back to > "/sbin/udevsend". I've tried the workaround in this post > http://www.pchdtv.com/forum/viewtopic.php?t=914, but it seems that udev-079 > (which I'm using) already has this fix incorporated into it. I'm at a loss > at what to do, and my wife is getting more anxious then ever to her PVR > back. Is there anyone out ther also running Gentoo or running into a > similar problem as this and has a fix for it? > > Another question, what caused the developers to switch to hotplug, rather > then keeping the firmware located in /lib/modules? Is there a make switch > that we can use to when compiling the ivtv driver so that it looks in > /lib/modules again rather then using hotplug? > > Thanks for the help, > Reid _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
