Tftp get of minimyth.conf not working anymore (0.20.2-38)

Help with booting MiniMyth

Moderator: Pablo

Post Reply
bcromwell
Contributor
Posts: 64
Joined: Thu Nov 22, 2007 5:08 am

Tftp get of minimyth.conf not working anymore (0.20.2-38)

Post by bcromwell » Tue Feb 12, 2008 11:53 pm

0.20.2-30 - 0.20.2-33 always worked great for tftp'ing the conf files but I appear that .2-38 doesn't even try to fetch the configs over tftp. Did something change or is it a bug? I also tried adding to my boot line: "MM_MINIMYTH_BOOT_URL=tftp://${MM_TFTP_SERVER}${MM_TFTP_ROOTDIR)/conf/mythLR/minimyth.conf"
But that didn't appear to help the problem either. Suggestions before I set up a web server just for serving conf files?

Feb 12 22:12:16 UDA in.tftpd[1761]: remap: done
Feb 12 22:12:16 UDA in.tftpd[1761]: RRQ from 10.201.30.125 filename pxelinux.cfg/01-00-09-6b-e9-54-07
Feb 12 22:12:16 UDA in.tftpd[1762]: remap: input: message.txt
Feb 12 22:12:16 UDA in.tftpd[1762]: remap: done
Feb 12 22:12:16 UDA in.tftpd[1762]: RRQ from 10.201.30.125 filename message.txt
Feb 12 22:12:16 UDA in.tftpd[1763]: remap: input: minimyth-0.20.2-38/kernel
Feb 12 22:12:16 UDA in.tftpd[1763]: remap: done
Feb 12 22:12:16 UDA in.tftpd[1763]: RRQ from 10.201.30.125 filename minimyth-0.20.2-38/kernel

Then Minimyth stops boot because it has no config file.

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

Post by Pablo » Wed Feb 13, 2008 12:16 am

Could you telnet into the frontend and provide the output of

Code: Select all

cat /etc/conf.d/dhcp
and

Code: Select all

cat /etc/conf.d/dhcp.override
Also, MM_MINIMYTH_BOOT_URL is the path to the boot directory (i.e., the directory containing your conf directory) not the path to minimyth.conf. In addition, it should not contain any variables (e.g. MM_TFTP_SERVER and MM_TFTP_ROOTDIR).
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

bcromwell
Contributor
Posts: 64
Joined: Thu Nov 22, 2007 5:08 am

Post by bcromwell » Wed Feb 13, 2008 12:49 am

root@mythLR:~ # cat /etc/conf.d/dhcp
MM_NETWORK_INTERFACE='eth0'
MM_TFTP_SERVER='10.201.30.3'
MM_TFTP_BOOT_URL=''
root@mythLR:~ #



Don't have a dhcp.overide file.

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

Post by Pablo » Wed Feb 13, 2008 12:50 am

bcromwell wrote:root@mythLR:~ # cat /etc/conf.d/dhcp
MM_NETWORK_INTERFACE='eth0'
MM_TFTP_SERVER='10.201.30.3'
MM_TFTP_BOOT_URL=''
root@mythLR:~ #



Don't have a dhcp.overide file.
dhcp.override
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

bcromwell
Contributor
Posts: 64
Joined: Thu Nov 22, 2007 5:08 am

Post by bcromwell » Wed Feb 13, 2008 12:52 am

Incase I have missed something Here is my Pxe conf and Dhcp conf.

LABEL minimyth-0.20.2-38
KERNEL minimyth-0.20.2-38/kernel
APPEND ro root=/dev/nfs nfsroot=10.201.30.194:/array/minimyth-0.20.2-38 ip=dhcp MM_BOOT_TYPE=network MM_DEBUG=yes




host mythLR
{
hardware ethernet 00:09:6b:e9:54:07;
fixed-address 10.201.30.125;
option host-name "mythLR";
option root-path "/var/public/tftproot/minimyth-0.20.2-38";
}


Thanks for the help Palbo.

bcromwell
Contributor
Posts: 64
Joined: Thu Nov 22, 2007 5:08 am

Post by bcromwell » Wed Feb 13, 2008 12:55 am

root@mythLR:~ # find / -name dhcp*
/etc/conf.d/dhcp
/etc/rc.d/init.d/conf.d/dhcp
/etc/rc.d/init.d/dhcp
/initrd/rw/rootfs/etc/conf.d/dhcp
/initrd/rootfs-ro/etc/rc.d/init.d/conf.d/dhcp
/initrd/rootfs-ro/etc/rc.d/init.d/dhcp
root@mythLR:~ #



Don't have that file either.

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

Post by Pablo » Wed Feb 13, 2008 1:00 am

I can see few things that are missing

next-server and filename are missing. without them, minimyth cannot determine the location of the boot directory.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

bcromwell
Contributor
Posts: 64
Joined: Thu Nov 22, 2007 5:08 am

Post by bcromwell » Wed Feb 13, 2008 1:03 am

That was just a snippet; The whole thing is:

#ddns-update-style ad-hoc;
ddns-update-style none;
next-server 10.201.30.3 ;
option tcode code 101 = text;
option tcode "America/New_York";
option ntp-servers 192.43.244.18;
if substring ( option vendor-class-identifier, 0, 9) = "PXEClient"
{
filename "pxelinux.0" ;
next-server 10.201.30.3 ;
}

subnet 10.201.30.0 netmask 255.255.255.0 {
option routers 10.201.30.1;
option domain-name-servers 10.201.30.10 ;
range 10.201.30.126 10.201.30.150 ;
max-lease-time 300;

}

host mythLR
{
hardware ethernet 00:09:6b:e9:54:07;
fixed-address 10.201.30.125;
option host-name "mythLR";
option root-path "/var/public/tftproot/minimyth-0.20.2-38";
}

host mythMR
{
hardware ethernet 00:0d:60:3d:fc:5b;
fixed-address 10.201.30.124;
option host-name "mythMR";
option root-path "/var/public/tftproot/minimyth-0.20.2-32b1.nvidia-96.43.01";
}

host mythTS

{
hardware ethernet 00:09:6b:e9:46:92;
fixed-address 10.201.30.122;
option host-name "mythTS";
option root-path "/var/public/tftproot/minimyth-0.20.2-32b1.nvidia-96.43.01";
}

host mythBR
{
hardware ethernet 00:06:5B:9E:28:45;
fixed-address 10.201.30.123;
option host-name "mythBR";
option root-path "/var/public/tftproot/minimyth-0.20.2-32b1.nvidia-96.43.01";
}



My other FE's work when running -33 and -30.

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

Post by Pablo » Wed Feb 13, 2008 1:21 am

DHCP needs to send filename and next-server to the frontend all the time, not just during the initial PXE boot.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

bcromwell
Contributor
Posts: 64
Joined: Thu Nov 22, 2007 5:08 am

Post by bcromwell » Wed Feb 13, 2008 1:31 am

Wow, Thanks that fixed it.. Wonder why it has always work the other way until now.

Thanks for your insanely quick responses!

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

Post by Pablo » Wed Feb 13, 2008 1:50 am

I believe that it was a combination of two things.

First, you boot line contains MM_BOOT_TYPE. In the past, this told minimyth to use network boot even though network boot was not detected. MiniMyth assumes local boot when it did not receive filename from DHCP.

Second, your filename shows that pxelinux.0 is in the root of your TFTP server. Therefore, the boot directory is in the root of your TFTP server. As a result, MiniMyth did not need to know filename in order to get the boot directory correct.

Now that MiniMyth does not use MM_BOOT_TYPE the lack of filename from DHCP causes MiniMyth to think that you are doing a local boot.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

Post Reply