It is somewhat confusing that the firmware.agent is never actually used considering that is where the FIRMWARE_DIR is set. I copied the firmware.agent file to drivers.agent just to verify that would actually be called on a modprobe and it does.
I'm not sure what my next step could possibly be. Hotplug and udev are fairly new to me. I suppose I can play around with some more logging in hotplug.functions. Does anyone know what actually prints the IVTV log messages? I'm still at a loss as to why it doesn't list what firmware drivers it wants to load...
Scott
On 5/23/06, Mark Paulus <[EMAIL PROTECTED]> wrote:
On my system, my stuff is being handled/loaded by udev, which seems to
have its own set of helper files in /lib/udev/firmware.agent and
/lib/udev/hotplug.functions.
This whole hotplug/udev this kind of confusing to me as to who is
handling which piece. If you still can't get it to work, then my
suggestion is to start putting 'echo' statements into firmware.agent.
If you don't see any output, you know you aren't looking at the proper
instance. If you do start to see output (maybe 'echo in firmware.agent
>> /var/log/syslog' as a starter), then you can output what directory
you are looking in, and what's there/not there.....
scott miller wrote:
> Portage seemed to take care of most of those steps but I redid them
> manually, verifying that the FIRMWARE_DIR in hotplug's firmware.agent
> was pointing to the correct path, and that that path was on the root
> filesystem.
>
> I also verified the md5sums for the files.
>
> Thanks,
>
> Scott
>
> On 5/23/06, *Mark Paulus* <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>> wrote:
>
>
> scott miller wrote:
> > Hello,
> >
> > I'm having a problem getting my Hauppague PVR-250 card to work.
> > Admittedly I haven't used the card for a very long time, and it
> sat in a
> > box for about a year, but it still seems to be recognized fine by
> the
> > system.
> >
> > lspci -v output:
> >
> > 05:06.0 Multimedia video controller: Internext Compression Inc iTVC15
> > MPEG-2 Eoder (rev 01)
> > Subsystem: Hauppauge computer works Inc. WinTV PVR-250
> > Flags: bus master, medium devsel, latency 64, IRQ 58
> > Memory at d0000000 (32-bit, prefetchable) [size=64M]
> > Capabilities: [44] Power Management version 2
> >
> >
> > Anyway I am running Gentoo on an AMD64 processor with a 2.6.12
> kernel.
> >
> > Here is the dmesg output from a modprobe ivtv.
> >
> > ivtv: ==================== START INIT IVTV ====================
> > ivtv: version 0.4.2 (tagged release) loading
> > ivtv: Linux version: 2.6.12-gentoo-r6 SMP 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 (cx23415 based)
> > ACPI: PCI Interrupt 0000:05:06.0[A] -> Link [APC1] -> GSI 16 (level,
> > low) -> IRQ 58
> > tveeprom: ivtv version
> > tveeprom: Hauppauge: model = 48011, rev = G510, serial# = 2670671
> > tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2)
> > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> > tveeprom: audio processor = MSP3435 (type = a)
> > 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=MSP3435G-B6 +nicam +simple +simpler +radio
> mode=simpler
> > ivtv0: i2c attach to card #0 ok [client=MSP3435G-B6, addr=40]
> > msp3400 0-0040: msp34xxg daemon started
> > ivtv0: unable to open firmware
> > 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:05:06.0 failed with error -12
> > ivtv: ==================== END INIT IVTV ====================
> >
> > The confusing bit to me is the "unable to open firmware"
> bit. Doing a
> > search for similar problems most people seem to actually have the
> name
> > of the firmware file that ivtv is unable to load...
> >
> > Any help would be greatly appreciated!
> >
> > Scott
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected] <mailto:[email protected]>
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> <http://ivtvdriver.org/mailman/listinfo/ivtv-users>
>
> Please check out the firmware page here:
> http://www.ivtvdriver.org/index.php/Firmware, and try all the steps.
>
>
> --
> 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
>
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected] <mailto:[email protected]>
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
--
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
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
