MythDora 12.23 Release Notes

Mythdora 12.23 has been released. There are a few changes from 10.21 but mostly on the cosmetic side of things. We're now using the stock mythtv theme out of the box, as well as stock paths. Please review the following release notes and use this link to retrieve the isos.

Thanks to all the beta testers for their support.
Pisani

System Requirements:

   * A minimum of 512MB of RAM is suggested to use the graphical installer
   * A hard disk of 15GB in size if you choose to use the default partitioning

General Features:

   * Fedora 12 + updates
   * mythtv-0.23-rc2+
   * kernel 2.6.32.11-99
   * lirc-0.8.6-6
   * imdb-bulk-update-1.16

DVD Features:

  * Gnome,KDE, LXDE, XFCE, and ratpoison desktops
  * nvidia driver packages, 195, 173xx and older 96xx
  * Handbrake-0.9.4

LiveCD Features:

  * XFCE desktop environment
  * nvidia-195 driver package
  * Ability to change timezone in firstboot's configuration

Changes in MythDora 12:

  * The auto-installation method has been removed
  * The frontend now heavily relies on the timezone of the system matching the backend
  * mythflix, mythphone and mythstreamtv have been dropped
  * Only themes based on the new API are included
  * atilibusb and other ir devices are now standardized under the devinput userspace. Note that lircd & lircrc files have changed
  * Forced execution of mythdora setup via firstboot so it cannot be missed
  * Stock rpmfusion based mythtv packages, settings and themes
  * Updated the included firmware for expanded model support

Changes in Fedora 12:

  * mdadm tool now seems to auto-schedule a weekly integrity check on all of your raid volumes. The output of the mdadm --detail command may lead users to believe that their device is rebuilding, when in fact it is being checked. Use /proc/mdstat to verify status of your md devices and note that you can disable the weekly check in /etc/sysconfig/raid-check.

Notes on Usage:

Installation:

  * Some users may experience issues with the standard & vesa install options on the dvd not initializing s-video outputs with nvidia driver cards. A possible work around is to edit the install line and set xdriver=nv.
  * Some users have reported issues with the MythDora configuration tool after they've deselected "System Clock uses UTC" in the anaconda installer. The cause is not yet known, but if you have an issue with MythDora Configuration locking up while processing selections this is most likely the cause. A re-install without this unchecked is the best cause of correction. Then make the change later.
  * Some users have had to specify ALSA:front manually in their sound setup for the frontend to deliver sound properly. This may not be necessary for all hardware.

LiveCD:

  * Default root password is 'mythtv'
  * By default the Live media will do it's best to determine video & audio drivers at boot time. This may cause issues for users of specific pieces of hardware. For example, nvidia users will likely want to specify the nvidia driver in the boot line by specifying xdriver=nvidia. The default action of the kernel will be to load the "nv" drivers for you device.
  * When installing from the desktop icon on the livecd you may get prompted to initialize more than one device. Anaconda is incorrectly trying to initialize /dev/sr0 (the optical drive) and this attempt will make the installer fail. YOU MUST CLICK IGNORE WHEN ASKED TO INITIALIZE /dev/sr0
  * A bug in the livecd installation causes a crash in the desktop installer when the user selects the current timezone of the live media (EASTERN); Which prevents the install from succeeding. A work around is to select another timezone other than EASTERN/New York and then change it after the installation has finished successfully.

Upgrading from 10.21:
Beta testing confirmed that upgrading via the DVD does work from 10.21 to 12.23.

  * If you use an nvidia card, you may need to append to your bootloader line (/etc/grub.conf) rdblacklist=nouveau so that your video will properly initialize video. If you choose to overwrite the bootloader this step may not be needed.
  * Upgrading will not overwrite your crontab. Depending on the configuration you chose, you may have mail spooling as a result of the stock cron entries for maintenance. You may want to redirect output from the minutely "becheck" to >/dev/null or at the top of your crontab set MAILTO=/dev/null if you wish to keep mail from spooling.
  * Upgrading may alter the lircd socket location and not be reflected in the database properly. One beta tester noted that the lircd socket option in the frontend needed to be changed from /dev/lircd to /var/run/lirc/lircd to make things work.