| From: Chris Rouch <[EMAIL PROTECTED]>
| Try removing video4linux (and the part of rc.sysinit that modprobes it, if
| you've made the changes Jarod suggested way back when). I had the same
| problem, and removed ivtv and video4linux and the re-added ivtv and now
| everything is sweet. I think v4l is part of the kernel now.
Thanks for the suggestion.
The problem has been bypassed, but I don't quite know what it actually
was.
(A) What didn't work:
rpm -iv <the RPMs I listed in earlier messages>
modprobe ivtv
(B) What did work:
kind of following parts of Jarod's guide.
What made the difference? I don't know, but here are some differences
that might matter:
- in (A) I never ran depmod. This might mean that some
fedora-supplied modules were used rather than the replacement atrpms
modules.
- in (A) I never added lines to /etc/modules.conf
- in (B) I used yum to add perhaps a hundred rpms. In (A), I only
added half a dozen. Maybe one of the missing ones mattered.
I cannot easily rerun my experiment to find out which of these
mattered.
I find it odd that depmod needs to be run manually. I would have
expected a postinstall script of an rpm installing kernel modules to
run depmod. But Jarod's instructions do specify that one should
manually run the depmod command. Perhaps this is redundant;
otherwise, I think that the .spec file should be updated to run depmod
in postinstall.
I don't imagine that the modules.conf entries caused the problem.
After all, they only provide an alias. I didn't need one since I
explicity specified "ivtv".
I don't think that the other RPMs should matter. If they did, they
should have been flagged as missing dependencies.
So: my system works. I don't know what was wrong. All my hypotheses
have holes.
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
