Help! error: 'minimyth.conf' not found

Help with booting MiniMyth

Moderator: Pablo

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Help! error: 'minimyth.conf' not found

Post by mx-5 » Thu Mar 13, 2008 5:16 am

I have been trying to get my minimyth to boot up to no avail. I'm using 0.20.2-38, and I get as far as the blue MythTV screen with the scrolling bar at the bottom. It gets about 1/4 way through, and the machine stops booting and displays:

error: 'minimyth.conf' not found.

My files are located as follow:

pxelinux.0 is in /usr/tftpboot/PXEClient/pxelinux.0
minimyth.conf is in /usr/tftpboot/PXEClient/conf/default/minimyth.conf

I've tried this on my 3 frontends, and they all get the same error message. Please help! Thanks!

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Thu Mar 13, 2008 5:37 am

Could you telnet in and post the contents of the file /etc/conf.d/dhcp?

Also, could you post the contents of your /etc/dhcpd.conf from your DHCP server?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Thu Mar 13, 2008 7:36 am

Here's /etc/conf.d/dhcp from my frontend (A8N-VM CSM):

root@:/etc/conf.d # cat dhcp
MM_NETWORK_INTERFACE='eth0'
MM_TFTP_SERVER='192.168.188.130'
MM_TFTP_BOOT_URL='tftp://192.168.188.130/usr/tftpboot/PXEClient/'

192.168.188.130 is a VM Gutsy server where I have my tftp server running.

My DHCP is handled by my OpenWRT router using dnsmasq. Would that be the problem?

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Thu Mar 13, 2008 4:02 pm

Assuming that 192.168.188.130 is your TFTP server, then the only thing I can think of is that the permissions are wrong on conf/default/minimyth.conf
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Thu Mar 13, 2008 4:59 pm

And I had been down that path when I used the Search to see you suggesting that before, but I've verified the folders and the conf file to be 755.

I just recalled that I had tried using a dhcp from a server as well while disabling the one on my OpenWRT router, and that didn't work either.

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Thu Mar 13, 2008 5:13 pm

Could you try with the latest version rather than -38?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Thu Mar 13, 2008 6:15 pm

I'll try that when I get a chance. The other thought is to try dhcp and tftp on a physical box rather than in a virtual machine, although VMs have been great for these kinds of tests.

Is using a home router to handle DHCP pretty common? If dnsmasq on the OpenWRT isn't supported, I'll run dhpcp from a server.

Thanks.

MythLegend
Contributor
Posts: 56
Joined: Thu Jul 12, 2007 7:46 pm

Post by MythLegend » Thu Mar 13, 2008 7:44 pm

Odd, I have been trying to get nfs booting sorted (not managed so far), but I also get this minimyth.conf not found message on every first boot after I change the pxelinux.cfg/default {effectively, it is the mac nic card address that it is loading from rather than "default"} file back to boot from a ram-minimyth image, I end up just hitting the reset on the PC and the next time it is OK, hadn't given it too much thought - It is almost as though something is being served from a cache ? or an uninitialised variable somewhere ?

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Thu Mar 13, 2008 8:59 pm

MythLegend wrote:Odd, I have been trying to get nfs booting sorted (not managed so far), but I also get this minimyth.conf not found message on every first boot after I change the pxelinux.cfg/default {effectively, it is the mac nic card address that it is loading from rather than "default"} file back to boot from a ram-minimyth image, I end up just hitting the reset on the PC and the next time it is OK, hadn't given it too much thought - It is almost as though something is being served from a cache ? or an uninitialised variable somewhere ?
I haven't had this luck. Reset gives me the same result.
I thought I made some strides already with getting PXE to work properly to tftp the image. I wasn't even seeing the blue MythTV screen at first - just getting this "Init 5: no more processes left in this runlevel"

I've also tried this on a Compaq iPaq (toaster oven like pc) based on the i810 or i815 chipset. It doesn't quite reach the blue MythTV screen, but it stops with a video mode error (although aren't the i810 video drivers included?) But when I telnet in to check /var/log/messages, I see 'minimyth.conf' not found.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Sat Mar 15, 2008 1:23 am

Fixed! So it was dhcp. I disabled the dnsmasq and used dhcpd on my tftp server, and it went past not finding minimyth.conf. Does anyone have dnsmasq on OpenWRT working for their minimyth install?

Currently troubleshooting something else... The splash screen completes, see a quick X cursor in the middle of a black screen, then stuck at a blinking underline cursor at the top right... arg....

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Sat Mar 15, 2008 2:36 am

Currently troubleshooting something else... The splash screen completes, see a quick X cursor in the middle of a black screen, then stuck at a blinking underline cursor at the top right... arg....
Telnet in as user 'minimyth' and run 'xinit'. That way you will be able to see the output in the telnet window.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Sat Mar 15, 2008 4:23 am

Thank you Paul! Didn't know 0.21 frontend didn't work with my 0.20 backend. Went back to 0.20.2-38 and it's finally working!

Time to tweak minimyth.conf a bit further, but very nice out of the box!

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Sat Mar 15, 2008 5:08 am

mx-5 wrote:Thank you Paul! Didn't know 0.21 frontend didn't work with my 0.20 backend. Went back to 0.20.2-38 and it's finally working!

Time to tweak minimyth.conf a bit further, but very nice out of the box!
I am glad that you got it to work.

There are newer releases of MiniMyth build with MythTV 0.20.

Each release stable MythTV release has changes to the communication protocol. As a result, they are incompatible. In fact, the MythTV developers discourage using different versions of MythTV on the backend and frontend, even when they are the same stable release at a different patch level.

MiniMyth can be built with different versions of MythTV: 0.20, 0.21 and trunk. In addition to the download/stable/latest directory which contains a build with MythTV 0.21, there is the download/stable/lastest-0.20 directory contains which a build with MythTV 0.20.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Sat Mar 15, 2008 6:44 am

Yes, I'm definitely going to move to 0.20.2-42.
Thanks for all the help. Time to end this thread and start new ones for new questions... :)

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Sun Mar 16, 2008 11:32 pm

Ok, so I had to post back in this thread.
My original posting was for the message

error: 'minimyth.conf' not found.

I was able to resolve it by moving my DHCP from dnsmasq on my OpenWRT router to dhcpd on a virtual Ubuntu Gutsy server. But I hope to let my OpenWRT router continue to handle dhcp, so disabling dnsmasq wasn't what I was hoping for.

dnsmasq appears to work in giving the clients an ip address, the tftp instructions to tftp/pxe boot from another server (the virtual Ubuntu Gutsy server), etc. But the client wasn't able to get the conf file. So... I looked at my tftp server's /var/log/syslog and found this:

Mar 16 15:21:21 VMWGutsyS1 atftpd[3892]: Serving /usr/tftpboot/PXEClient/minimyth-0.20.2-42/kernel to 192.168.188.105:57099
Mar 16 15:21:21 VMWGutsyS1 atftpd[3892]: Serving /usr/tftpboot/PXEClient/minimyth-0.20.2-42/rootfs to 192.168.188.105:57100
Mar 16 15:21:56 VMWGutsyS1 atftpd[3892]: Serving usr/tftpboot/PXEClient/conf/default/minimyth.conf to 192.168.188.105:47858

kernel and rootfs work properly, but not minimyth.conf. Syslog showed atftpd on my virtual Gutsy server was passing the path with /usr/tftpboot/... for kernel and rootfs, while it was just usr/tftpboot/... without the slash at the front of the path. Could this be the issue? Any ideas how to resolve?

Thanks!!

Post Reply