Great suggestions. My /usr/lib was already a symlink to /usr/lib64. I also unloaded and reloaded the ivtv module, but unfortunately dmesg output was still the same, which suggests that it might not be a problem with visibility from the root partition during boot (although I'll fiddle with that just to make sure).
-dk Dustin Nicholas Jenkins <[EMAIL PROTECTED]> wrote: > I had a similar issue. First, I had to make sure that my /usr/lib was > a symbolic link to /usr/lib64, and that /usr was not on a separate > partition since it wasn't being mounted in time at boot, which meant I > had to put it in /lib/firmware (or somewhere on the root partition and > point the FIRMWARE_DIR to it). > > Is this happening during startup? If so and you unload the ivtv > module, then reload it, does dmesg still have the error? > > Hope that helps, > Dustin > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
