Hi,
   I have a Gentoo machine that used to run devfsd but was converted
to udev to run MythTV. The conversion seemed to have worked fine.
devfsd was disabled and a kernel built that used udev instead. The
machine is using a development version of the ivtv driver not
available yet from portage due to the PVR capture card choice. The
driver was built and installed as per the included instructions. The
machine was working fine. It continued to work after many reboots,
etc., so everything was fine as far as I could tell.

   Later, when doing a clean up on the world file, the command emerge
-pv --depclean told me that it wanted to remove devfsd. I didn't do it
at first but later decided to let it remove devfsd in favor of
depending on udev. At first it appeared that there were no problems
but recently it seems that the ivtv driver is not loading correctly at
boot time. The driver is loaded and I do not see any error messages
but when attempting to capture video I get bad audio and a blue
screen. After doing an rmmod ivtv && modprobe ivtv both the audio and
video are perfect.

   My question is whether the emerge -C devfsd has somehow caused this
misoperation or is it more likely that some other update has caused
this problem?

   I have tried re-emerging devfsd and also re-emerging udev but
nothing I do so far seems to get it back to where it was.

   I really do not understand how udev works other than there are some
rules that create devices. Is it possible that with udev the required
v4l devices are somehow not created and the driver install at boot
time doesn't find what it needs thus causing this problem?

   I hope someone can help shed some light on this. Let me know what
sort of info might help about the machine. It's a fully up to date
mostly non-~x86 box running 2.6.11-gentoo-r9 and is an Nforce-2 MB.
It's been up and running Gentoo since it's birth almost 2 years ago.

Thanks,
Mark

-- 
gentoo-user@gentoo.org mailing list

Reply via email to