Taking into account the number of reports on MythTV, I think something went wrong with it. I get the same thing here. But... I'm not a MythTV expert at all. If anyone has some extensive experience with MythTV and can take a look in it's settings, database, etc. (disregarding Pluto, since it's probably a MythTV config problem only), I'd appreciate if you could tell me "this setting is wrong. it looks like this, but it should actually look like this". Thanks.
I'm not sure if this will help to others as well, but here are the steps I had to do to get mythtv working under 0.32:
1. I had problem cause ivtv installation installs tveeprom.ko that collides with bttv's same kernel module. I just renamed that from ivtv and bttv loaded fine since then (I use bttv only for surveillance cams)
2. I had problems not spotting /dev/videoX registration when loading ivtv driver - but don't worry that's not an issue - it seems like ivtv in 4.0 version doesn't report device it registers on, but it's there ...
3. mythtv after steps 1. and 2. still didn't work (mythbackend was running, but it had no tuners available) and cause was quite trivial: I had to reenter card config in mythsetup. Now it's working again.... I'm not sure when this happened, but suspect after 0.32 upgrade... I also added slave backend on my Digimatrix, so maybe this caused my problems and erased config on main server ...