It's working for now, still got to stress test it. It was missing the hwmakoa.bin firmware (however you spell it).
That doesn't fix my compile problem though. I manually copied over only the cx25840.o and wm8775.o files. Now I am running a patched together install of 3 different ivtv versions. 4.0, 4.1rc1(?) and 4.1 release. Here is the following md5sums of the files I got working. [EMAIL PROTECTED]:/lib/modules/2.4.27-2-386/kernel/ivtv# md5sum * d40aebe606895a394ca41e7ebab604c8 cs53l32a.o 4d8714475830c17868fa705f4cc246e3 cx25840.o 163e329c1d15fb5f909ce6aedfe1d3d6 ivtv-fb.o 44ac05e46f464a3d6562e3bf33cc7add ivtv.o 41aec7265b607990ddc55633a31d48f5 msp3400.o aae7cc7a364b51923157690faa4af5cf saa7115.o eed8df1bb5a5664c8f20192444b84d73 saa7127.o 6cbe115aa02778eb97320be8b1555d70 tda9887.o 60b17509e3ead63c7c8bc33846ce7329 tuner.o 4d774f1b49660b7e87d597992d370455 tveeprom.o 087ff9b8c1202980352282afa52435be wm8775.o And the 4.0 install (and other files) in the video directory: [EMAIL PROTECTED]:/lib/modules/2.4.27-2-386/kernel/drivers/media/video# md5sum * 91365948f14def5aaa27435a75c0f538 adv7175.o 87127e3b92e89fc062110eeb9a209c4a bt819.o ea245af7142674ff6ddb7e6a15fcda41 bt856.o 4688e6f942d5dc7f9ddfd241e51bd102 bttv.o 6cfdccfbae312551eb62317bbb5658ef bw-qcam.o 62555e18cbed51731d6d7df1b0e4c987 cpia.o f86867e4e6df659d854cb76ef299a8fd cpia_pp.o e4aaaf018f9751e23f9b8fb8e0ac2897 cpia_usb.o 99326fbdcccedf06cf3832c29869aa74 c-qcam.o 669d0379240fbae9cc1ceb1b03423e34 cs53l32a.o 49f87d7520faac692898c1661a93466d cx25840.o 820b6a4b2ca67be1849386d4cd64914f i2c-old.o 889fe665662215f648322a23a546b253 i2c-parport.o a7737b55abc8ef21e4ddce0627b9fe03 ivtv-fb.o 86c385498a2bee7de1f7697ee27db4d6 ivtv.o 91952bc0ac1719d1c82bfc2f2e1410e2 meye.o 7bbd3bdd36d5062751100af7de023b24 msp3400.o ac26b63ad382c8e95ed61d4e77ce5921 pms.o 3d5ee6172f422f80bfb0c3ce769ad3ea saa5249.o ca3422dfe9875bb5a384171dfb88107a saa7110.o 05b4767a0c88a2ff20fa08b24a1306da saa7111.o 6d7ae2d6ec7ccfcafb23cc2c91b6ac79 saa7115.o 16dd88138f838142b523083ea8b0d3d3 saa7127.o 46fc0281695f70eb603cd71c2265ab76 saa7185.o 7a6b784b461ba36b2b07a70e6024ce1a stradis.o fdfcb26930ba02c48138d850451b00dc tda7432.o 0a1853e258ebbe2751853b33bf589eb8 tda9875.o babf2ed964e607761e09c81bdfe4c26d tuner-3036.o f639de7b9099b91b1cedef7def772aac tvaudio.o a46856f7e374268fa4d8472e4fc0db75 tveeprom.o 2821e2c1f1aeaf3543a1fdee65c9abce tvmixer.o 162f827fb1a1a9a3004a52d1a1e419c3 videodev.o dca7d4fb134d3a768e55705f732a9309 w9966.o 104b7bad01ce8bee9a0462e8b78f3423 wm8775.o 0dc93bbdf3a6bfd0ebd534ae2da738ac zoran.o 1c3e17a258511c84ee62a390bad71b05 zr36067.o At least it works, I would like to have the ivtv makefile work for me though. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith C Sent: Thursday, December 22, 2005 11:17 AM To: User discussion about IVTV Subject: Re: [ivtv-users] 4.1 release compile problem On Dec 22, 2005, at 8:46 AM, Brent Kilgore wrote: > That's a bad idea btw. I copied and chmod-ed the files (same thing > install does, if im going to do it manually im doing it REALLY > manual). > > Box became a toaster. Wouldn't even boot in single mode. > > I had to physically remove cards and boot to restore my old drivers. > > Of course, this might just be an indicator that the new drivers > FUBAR my > box all by themselves. This seems to me to be even more evidence that something fundamental is wrong with the kernel. There's no reason why it would die that hard. Do you have the pvr-350 output module added to your boot disk image or something? Usually if I start having troubles this bad, I abandon my current kernel version and upgrade to something newer, just to clear out the old junk and start from scratch. Keith C > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Keith C > Sent: Wednesday, December 21, 2005 10:22 PM > To: User discussion about IVTV > Subject: Re: [ivtv-users] 4.1 release compile problem > > On Dec 21, 2005, at 8:48 PM, Brent Kilgore wrote: > >> I did do a make first. I assumed that was a given sorry. I meant >> I hadn't gotten around to flipping through the directories to make >> sure everything built (the old ones omitted several modules). I >> was just going to do a make install to apply over my current >> install and see if I could have "gotten away with it" >> >> > > Ok, I figured as much, but didn't want to assume anything. So we're > talking about a broken make/make install process. > > Looking at this section of your make install : > ld -m elf_i386 -e stext -r -o ivtv-fb.o ivtv-osd.o ivtv-queue.o > make[3]: Leaving directory `/root/ivtv41off/ivtv-0.4.1/driver' > make[2]: Leaving directory `/usr/src/kernel-headers-2.4.27-2-386' > install -d /lib/modules/2.4.27-2-386/kernel/ivtv > install -m 0644 /lib/modules/2.4.27-2-386/kernel/ivtv > install: too few arguments > > There's definitely something broken. Here's the install from > Makefile2.4 : > install: all > install -d $(DESTDIR)/$(MODDIR) > install -m 0644 $(OBJS) $(DESTDIR)/$(MODDIR) > install -m 0644 $(INSTALL_INIT_FILES) $(DESTDIR)/$ > (MODULESDIR) > > The $(OBJS) is not set, so the second install line fails. But > Makefile2.4 clearly declares : > OBJS = msp3400.o saa7115.o cx25840.o wm8775.o tveeprom.o ivtv.o > saa7127.o cs53l32a.o > > So.... Not sure what to tell you. You could do the install by hand, > moving modules and settings permissions for the modules manually, but > I'm sure something as strangely broken as this might have > repercussions in other places as well. > > Keith C > > >> >> >> >> >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:ivtv-users- >> [EMAIL PROTECTED] On Behalf Of Keith C >> Sent: Wednesday, December 21, 2005 9:37 PM >> To: User discussion about IVTV >> Subject: Re: [ivtv-users] 4.1 release compile problem >> >> >> >> On Dec 21, 2005, at 7:57 PM, Brent Kilgore wrote: >> >> >> >> >> Quick recap. I am the guy with the pvr-350 working with a 4.1 svn >> installed over top a 4.0 install because the make files would not >> build all the modules I needed, but the overlapping installs worked. >> >> >> >> I just got a pvr-150 mce model 1402. I, of course, have no sound. >> I tried installing the 4.1 release which is supposed to fix this >> and got the make install errors at the bottom of this email. I >> tried applying that mentioned before to the Makefile2.4 only to >> find that I cannot find any of the variables referenced in it. >> >> >> >> >> I'd say that it needs to make cleanly before it should be expected >> to work. >> >> >> >> >> >> >> I tried using the ivtvctl register hack but I was greeted with the >> following error. >> >> >> >> IVTV_IOC_G/S_DECODER_REG failed for saa7114 decoder >> >> >> >> I have not been able to get a make file to work "out of the box" >> since 3.7ish. I havn't even had a chance to see if it even >> compiling all the modules yet. >> >> >> >> Thanks for your help. >> >> >> >> --------------------------------------------------------------------- >> - > >> -- >> >> >> >> make -C driver install >> >> >> >> Why a make install statement, with no make and the unnecessary -C >> driver? I'm no expert, but I always just do : >> >> make >> >> sudo make install >> >> >> >> from the ivtv directory. Never had a problem. >> >> >> >> >> >> Keith C >> >> >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
