- What is MiniMyth?
- Where can I download MiniMyth?
- How much memory does MiniMyth require?
- How can I see the console output of mythfrontend?
- Why do I get "Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(1,0)"?
- Why can I play some DVDs but not other DVDs?
- Why is my favorite Myth plugin missing from MiniMyth?
- Why are my temperature and fan sensors missing or wrong?
- Why doesn't MM_DEBUG work?
- How can I build MiniMyth from source?
- How do I report a bug or request a feature?
The answer to this question can be found on the MiniMyth home page.
The answer to this question can be found on the MiniMyth download page.
MiniMyth redirects mythfrontend's console output to syslog. It is logged with the facility 'local0', the level 'info' and the tag 'mythfrontend'. Therefore, you can find mythfrontend's console output in the file '/var/log/messages', assuming you have not configured a network log server.
There is at least one possible reason.
If the memory allocated by the kernel for the RAM root file system is less than the size of the RAM root file system, then the RAM root file system will be incomplete and fail to mount. The 'ramdisk_size' boot line parameter sets the memory allocated by the kernel for the RAM root file system. The value of the 'ramdisk_size' parameter must be at least the size of the RAM root file system. You can find more information here.
Earlier versions of MiniMyth used the 'ramdisk' boot line parameter rather than the 'ramdisk_size' boot line parameter. However, the kernel obsoleted 'ramdisk' in favor of 'ramdisk_size'. Therefore, MiniMyth had to switch from 'ramdisk' to 'ramdisk_size'. If you are using the 'ramdisk' parameter, then you need to switch to using the 'ramdisk_size' parameter or you will see the above error when trying boot.
Earlier versions of the MiniMyth root file system fit in 64000kB of memory. As a result, the earlier versions of MiniMyth documentation suggested that 'ramdisk_size' be set to 64000. However, with the addition of new functionality and the increase in the size of MythTV, the MiniMyth root file system no longer fits in 64000kB of memory. Therefore, users need to change 'ramdisk_size' from 64000 to something larger (e.g. 192000).
There are at least two possible reasons.
The first reason is that some DVDs are encrypted using CSS. In order to play these DVDs, you need libdvdcss.so.2. Because of legal issues surrounding other software that allows Linux users to play their legally purchased DVDs, libdvdcss.so.2 is not included in the binary MiniMyth distribution. Although libdvdcss.so.2 is very different from this other software, legal concerns still exist. Because libdvdcss.so.2 only depends on Linux and glibc, you should be able to use any libdvdcss.so.2 that has been compiled for i386, i486 or i586 (when using a 32-bit version of MiniMYh) or x86_64 (when using a 64-bit version of MiniMyth).
Once you have a copy of libdvdcss.so.2, you can add it to your MiniMyth system at boot by including it in the 'lib' directory of your extras file system (see the MM_EXTRAS_URL variable in the MiniMyth configuration file). If you compile MiniMyth yourself, then the extras file system image that the build system creates will contain libdvdcss.so.2.
The second reason is that some DVD drives require their region code to be set. You can set your DVD drive's region code using the 'regionset' utility that is included in MiniMyth. For information on how to use 'regionset', see the regionset readme.
There are two reasons that some Myth plugins are not included in MiniMyth: the plugin has not been requested, and the plugin depends on software that is not included.
The following plugins have not been included because they depend on software not included in MiniMyth:
You may notice that you get no output from your temperature and fan sensors.
The reason for this is that the sensor chip's kernel module is not loading. Unfortunately there is no simple detection method for sensor chips. In order to "auto-detect" the sensor chip, MiniMyth goes through a two step process. First, MiniMyth attempts to detect the motherboard vendor and product. Second, MiniMyth maps the motherboard vendor and product to sensor chip's kernel module. It is likely that this is not working for your motherboard, because MiniMyth does not have the necessary information. If you let us know the motherboard vendor and product, the output of the command 'cat /sys/class/dmi/id/modalias' and (if you know it) the sensor chip kernel module, then we can add the necessary information to MiniMyth.
You may notice that either a sensor reports a temperature that is very wrong or a label next to a temperature or fan sensor is wrong.
The reason for very wrong temperature readings on VIA EPIA motherboards is either the specific temperature sensors are not used by the motherboard or there is something wrong with the vt1211 sensors driver. I do not know which it is. However, it is safe to assume that the motherboard is not at a temperature that is below freezing.
The reason for the wrong labels is that the motherboard vendor did not wire the sensors as suggested by the sensor chip vendor. As a result, while the values are correct, they are attributed to the wrong temperature or fan sensors on the motherboard. At some point, we may add motherboard specific sensors configuration files to address this problem.
People tend to have one of two problems when trying to enable debugging.
First, they set MM_DEBUG in the wrong place. As mentioned in the configuration obtained from the boot line section, MM_DEBUG="yes" must be set on the boot line. If it is set in the MiniMyth configuration file, then it will be ignored.
Second, they quote the MM_DEBUG variable value incorrectly. As mentioned in the configuration obtained from the boot line section, unlike MiniMyth variable values in the MiniMyth configuration file which should be single quoted ('), MiniMyth variable values on the boot line must be either unquoted or double quoted ("). Single quoted variable values such as MM_DEBUG='yes' will not work correctly.
The answer to this question can be found on the MiniMyth build system instructions page.
The best way to report a bug or request a feature is to let us know about it.