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
