On 6/19/05, Ant Daniel <[EMAIL PROTECTED]> wrote: > I originally setup my FC3 system following Jarod's guide. My ivtv > driver came from ATRpms, (0.2.0 rc3j) I included the step of building > an initrd for boot time. > > I wanted to update my driver to the latest 0.3.6 so I could start > testing the new X driver. But the initrd continued to load the old > ivtv driver. (I had removed the old ATRpms modules). > > I had a go at editing the /sbin/mkinitrd-ivtv created from the guide > as some of the files names where different, but booting with that > results in a boot up process with the following information > (transcribed as I go, so somethings missed out). There are large > pauses at certain points of the process. > > insmod: error inserting '/lib/ivtv.ko': -1 Unknown symbol in module > ERROR: /bin/insmod exited abnormaly! > insmod: error inserting '/lib/ivtv-fb.ko': -1 Unknown symbol in module > ERROR: /bin/insmod exited abnormaly! > > Initializing hardware... storage network > Starting readahead_early: [FAILED] > /etc/rc.d/rc: line 67: 7423 Killed $i start > Applying iptables firewall rules: [OK] > touch: cannot touch '/var/lock/subsys/iptables': Read-only file system > Starting pcmcia: [OK] > Starting network parameters: [OK] > Bringing up loopback interface: [OK] > Bringing up interface eth0: [OK] > touch: cannot touch '/var/lock/subsys/network': Read-only file system > Starting system logger: [FAILED] > > Continues like this, eventually boots and I am able to get a a login > (even via ssh), however none of the log files are updated, mounts > loaded, X refuses to run and loads of other errors. > > I also built initrd with /sbin/mkinitrd-ivtv without the --ivtvdev > argument as well as using /sbin/mkinitrd but they result in similar > behaviour to the above (except without the ivtv.ko/ivtv-fb.ko errors). > > I don't have the original initrd file that was created before > following the instructions in Jarod's guide so I'm stuck with using > 0.2.0 rc3j. > > I suspect that the problem might have something to do with the fact > that ATRpms where installed in a different directory to my hand built > 0.3.6. Although I can't find anything in mkinitrd(-ivtv) that > hardcodes the path. The system had been depmod'd after installing. > > I had a go at moving the new .ko modules to the ATRpms location but > that eventually results in a kernal panic. > > I am at a loss, I don't know what to try next. > > Ant. >
No one got any suggestions? I'm thinking now of removing the kernel and then reinstalling it, hopefully this will get me back to the pre initrd issues, then I can wind the process forwards again (ignoring the initrd step). ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
