Q: When I start "xawtv" I get error messages like

	VIDIOCSAUDIO: Invalid argument
	VIDIOCSFREQ: Invalid argument

   among other lines. What can be done?

A: Nothing to worry about. If you load the driver modules with suitable
   debug options you will see in your syslog file that xawtv calls
   these ioctl functions with arguments which are not allowed. The mfII
   module objects it and returns an error code to xawtv in those cases.
   It's a fault - or let's say, the conduct - of xawtv.

-------------------------------------------------------------------------------

Q: After loading the modules, when I start "xawtv" I get a warning that
   "v4l and dga disagree about the framebuffer base" and I should "insmod
   the bttv module with 'vidmem=0xyz'" and that overlay mode is disabled.
   But I have a running TV picture on the screen - somewhat slow. How's
   that?

A: You forgot to update the "vidmem" parameter of the mfII module. Read
   the INSTALL file, section PARAMETERS, again.
   The TV picture was displayed though by way of grabdisplay mode instead
   of overlay mode.

-------------------------------------------------------------------------------

Q: I turn sound off with "mfIIset|mfIIradio --volume=0". After that I
   want to turn sound on again by "--mute=off". But I get no sound. ??
   
A: It can not work that way. "--mute=off" actually means "return to
   previous volume level". If you set the volume level to zero, you can't
   unmute without specifying a new volume level different from zero. To
   achieve a temporary mute state execute either a "--volume=0" ->
   "--volume=nnnn" sequence or a "--mute=on" -> "--mute=off" sequence.

-------------------------------------------------------------------------------

Q: I think I have to setup colour depth and palette settings for an AVI
   recording. But there are no matching "mfIIset" commands.

A: Recording applications like xawtv's "streamer" prepare these settings
   themselves.
