The string "ivtv: requesting firmware" is only printed from the
function that uses hotplug to do the loading.  Try putting the
firmware into /lib/firmware and see what happens.

Hotplug is actually configurable about where it checks for firmware,
see '/etc/hotplug/firmware.agent'.


On 5/24/05, Chris Kennedy <[EMAIL PROTECTED]> wrote:
> Oh, it's not loading the firmware, that's the error it's giving.
> 
> Thanks,
> Chris
> On Tue, May 24, 2005 at 10:03:48AM -0400, Hilary L Hertzoff wrote:
> > On Tuesday 24 May 2005 09:20, Chris Kennedy wrote:
> > > I think the firmware isn't under /lib/modules/
> > >
> > > Thanks,
> > > Chris
> >
> > Where should it go then?  That is where the files are currently (and on the
> > old system).
> >
> > Hilary
> >
> > >
> > > On Tue, May 24, 2005 at 09:07:26AM -0400, Hilary L Hertzoff wrote:
> > > > I've been running IVTV on SuSE 9.2 for about 6-8 months.
> > > >
> > > > Now on a new install of 9.3 on a new harddrive, I'm running into
> > > > problems. None of the other hardware has changed.
> > > >
> > > > I've tried using the included IVTV package, reinstalling the package,
> > > > upgrading to the latest tarball, reinstalling the firmware, copying over
> > > > my modprobe files from the old installation, replacing the firmware 
> > > > files
> > > > with newly extracted ones and with the ones from the old installation.
> > > >
> > > > None of this has fixed the problem.  When I run modprobe IVTV I get the
> > > > following messages.  Everything seems to be fine, but it's not finding
> > > > the firmware (which is in the same place as it was in the old install).
> > > >
> > > > Any thoughts?
> > > >
> > > > Thanks
> > > > Hilary
> > > >
> > > > May 24 09:05:59 linux kernel: ivtv: ==================== START INIT IVTV
> > > > ====================
> > > > May 24 09:05:59 linux kernel: ivtv: version 0.3.2 (c) loading
> > > > May 24 09:05:59 linux kernel: ivtv: Linux version: 2.6.11.4-20a-default
> > > > gcc-3.3
> > > > May 24 09:05:59 linux kernel: ivtv: In case of problems please include
> > > > the debug info
> > > > May 24 09:05:59 linux kernel: ivtv: between the START INIT IVTV and END
> > > > INIT IVTV lines when
> > > > May 24 09:05:59 linux kernel: ivtv: mailing the ivtv-devel mailinglist.
> > > > May 24 09:05:59 linux kernel: ivtv: Autodetected WinTV PVR 250 card
> > > > May 24 09:05:59 linux kernel: ivtv: Found an iTVC16 based chip
> > > > May 24 09:05:59 linux kernel: ACPI: PCI interrupt 0000:00:08.0[A] -> GSI
> > > > 19 (level, low) -> IRQ 185
> > > > May 24 09:05:59 linux kernel: ivtv: VIA PCI device: 0x3188 vendor: 
> > > > 0x1106
> > > > May 24 09:05:59 linux kernel: i2c-algo-bit.o: (0) scl=1, sda=1
> > > > May 24 09:05:59 linux kernel: i2c-algo-bit.o: (1) scl=1, sda=0
> > > > May 24 09:05:59 linux kernel: i2c-algo-bit.o: (2) scl=1, sda=1
> > > > May 24 09:05:59 linux kernel: i2c-algo-bit.o: (3) scl=0, sda=1
> > > > May 24 09:05:59 linux kernel: i2c-algo-bit.o: (4) scl=1, sda=1
> > > > May 24 09:05:59 linux kernel: i2c-algo-bit.o: ivtv i2c driver #0 passed
> > > > test. May 24 09:05:59 linux kernel: ivtv: i2c attach 
> > > > [client=tveeprom,ok]
> > > > May 24 09:05:59 linux kernel: tuner: chip found at addr 0xc2 i2c-bus 
> > > > ivtv
> > > > i2c driver #0
> > > > May 24 09:05:59 linux kernel: ivtv: i2c attach [client=(tuner unset),ok]
> > > > May 24 09:05:59 linux kernel: saa7115: starting probe for adapter ivtv
> > > > i2c driver #0 (0x10005)
> > > > May 24 09:05:59 linux kernel: saa7115: detecting saa7115 client on
> > > > address 0x42
> > > > May 24 09:05:59 linux kernel: saa7115: writing init values
> > > > May 24 09:05:59 linux kernel: ivtv: i2c attach [client=saa7115[6],ok]
> > > > May 24 09:05:59 linux kernel: saa7115: status: (1E) 0x48, (1F) 0xc0
> > > > May 24 09:05:59 linux kernel: msp34xx: init: chip=MSP3445G-B8 +nicam
> > > > +simple +simpler +radio mode=simple
> > > > May 24 09:05:59 linux kernel: ivtv: i2c attach [client=MSP3445G-B8,ok]
> > > > May 24 09:05:59 linux kernel: msp3410: daemon started
> > > > May 24 09:05:59 linux kernel: tveeprom: Hauppauge: model = 32062, rev =
> > > > B185, serial# = 7363116
> > > > May 24 09:05:59 linux kernel: tveeprom: tuner = TCL 2002N 6A (idx = 85,
> > > > type = 50)
> > > > May 24 09:05:59 linux kernel: tveeprom: tuner fmt = NTSC(M) (eeprom =
> > > > 0x08, v4l2 = 0x00001000)
> > > > May 24 09:05:59 linux kernel: tveeprom: audio_processor = MSP3445 (type 
> > > > =
> > > > 12) May 24 09:05:59 linux kernel: ivtv: Tuner Type 50, Tuner formats
> > > > 0x00001000, Radio: yes, Model 0x00891615, Revision 0x80344736
> > > > May 24 09:05:59 linux kernel: ivtv: NTSC tuner detected
> > > > May 24 09:05:59 linux kernel: ivtv: Radio detected
> > > > May 24 09:05:59 linux udevd[2303]: move seq 1129 with timeout 10 to exec
> > > > queue May 24 09:05:59 linux kernel: ivtv: requesting firmware
> > > > May 24 09:06:00 linux udevd[2303]: move seq 1130 with timeout 10 to exec
> > > > queue May 24 09:06:00 linux kernel: ivtv: firmware load failed
> > > > May 24 09:06:00 linux kernel: ivtv: failed loading encoder firmware
> > > > May 24 09:06:00 linux kernel: ivtv: Error loading firmware -3!
> > > > May 24 09:06:00 linux kernel: ivtv: Error -3 initializing firmware.
> > > > May 24 09:06:00 linux kernel: ivtv: Error -12 on initialization
> > > > May 24 09:06:00 linux kernel: ivtv-iTVC15_16_mpg2_encoder_card: probe of
> > > > 0000:00:08.0 failed with error -12
> > > > May 24 09:06:00 linux kernel: ivtv: ====================  END INIT IVTV
> > > > ================
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.Net email is sponsored by Oracle Space Sweepstakes
> > > > Want to be the first software developer in space?
> > > > Enter now for the Oracle Space Sweepstakes!
> > > > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> > > > _______________________________________________
> > > > ivtv-devel mailing list
> > > > [email protected]
> > > > https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by Yahoo.
> > Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> > Search APIs Find out how you can build Yahoo! directly into your own
> > Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> > _______________________________________________
> > ivtv-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> 
> --
> ---
>  Chris Kennedy / [EMAIL PROTECTED]
>   Engineer KMOS-TV/KTBG-FM
>   Broadcasting Services Department
>   Central Missouri State University
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> 


-- 
Tyler Trafford


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to