PXE boot stuck just prior to download kernel

Help with booting MiniMyth

Moderator: Pablo

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

PXE boot stuck just prior to download kernel

Post by mx-5 » Mon Oct 13, 2008 6:14 am

I just got my hands on an original Via EPIA 800 mobo.
http://www.via.com.tw/en/products/mainb ... oard_id=21

C3 800MHz, PLE133 chipset, VT8231 southbridge, VT6103 lan, etc.

I have 3 other minimyth frontends in my home setup. TFTP handled by the same Ubuntu server which is my mythbackend. All 3 other frontends boot up fine using either pxe-minimyth-0.21.0-58 and pxe-minimyth-0.21.0-57-nvidia.96.43.07. However, with this EPIA board, the bootup gets stuck during the PXE. It grabs addresses, etc., but gets stuck just before it grabs the kernel. Here are the last 3 lines:

TFTP prefix: /usr/tftpboot/PXEClient/
Trying to load: pxelinux.cfg/01-00-40-63-cb-xx-xx
boot: _

After I hit the Enter key, the kernel and rootfs will proceed to load. Not so convenient to need a keyboard with the frontend. Any reason why this happens and why this behavior is different from my other minimyth frontends?

Thanks.

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

Post by mx-5 » Sat Oct 18, 2008 4:59 am

So I tried a few things, including updating my pxelinux.0 file, booting without the PCI video card, resetting CMOS settings, etc.

Turns out, if I disconnect the network cable and force PXE to error out and give me the following:

PXE-E61: Media test failure, check cable

PXE-M0F: Exiting Intel PXE ROM.

Then when I reboot with the network cable plugged in, it doesn't get stuck at the "boot: _" anymore. Not sure what causes it to be stuck, because the problem has reoccurred, but sure enough disconnecting the network cable has worked thus far.

Not sure why, but that seems to be a fix. No newer mobo BIOS since this is an older board.

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

Post by Pablo » Sat Oct 18, 2008 5:51 am

If you add

Code: Select all

via-rhine.avoid_D3=1
to your boot line, then are you able to restart successfully after rebooting with this boot line option at least once?

If so, then could you post the output of

Code: Select all

cat /sys/class/dmi/id/board_name
cat /sys/class/dmi/id/bios_vendor
cat /sys/class/dmi/id/bios_version
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 » Sun Oct 19, 2008 10:44 am

Pablo wrote:If you add

Code: Select all

via-rhine.avoid_D3=1
to your boot line, then are you able to restart successfully after rebooting with this boot line option at least once?
Yes, it booted.
If so, then could you post the output of

Code: Select all

cat /sys/class/dmi/id/board_name
cat /sys/class/dmi/id/bios_vendor
cat /sys/class/dmi/id/bios_version
EPIA
Award Software International, Inc.
6.00 PG

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

Post by Pablo » Wed Oct 22, 2008 3:29 am

So, the boot parameter fixes the problem?

If so, this is odd. As far as I can tell, the via-rhine Ethernet driver already blacklists D3 for the device identified by this BIOS Vendor and BIOS version.
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 » Sun Nov 02, 2008 10:12 pm

In a handful of boots, it seems to start ok. I'll have to put it through more bootups though - not a frequently used machine.

Just tried build 59 though and I'm getting the following (which I saw in the beta builds):

error: 'minimyth.conf' not found.

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

Post by Pablo » Tue Nov 04, 2008 4:20 am

mx-5 wrote:Just tried build 59 though and I'm getting the following (which I saw in the beta builds):

error: 'minimyth.conf' not found.
If you add MM_INIT_TYPE=sh to your boot line, does this problem go away?
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 » Wed Nov 05, 2008 4:53 am

Nice! Working now on both the ram-minimyth-0.21.0-59 and the legacy ram-minimyth-0.21.0-59-nvidia-96.43.07 versions.

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

Post by Pablo » Wed Nov 05, 2008 5:07 am

mx-5 wrote:Nice! Working now on both the ram-minimyth-0.21.0-59 and the legacy ram-minimyth-0.21.0-59-nvidia-96.43.07 versions.
Are you saying that it works with MM_INIT_TYPE=sh but not with MM_INIT_TYPE=perl?
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 Nov 06, 2008 6:15 am

Pablo wrote:
mx-5 wrote:Nice! Working now on both the ram-minimyth-0.21.0-59 and the legacy ram-minimyth-0.21.0-59-nvidia-96.43.07 versions.
Are you saying that it works with MM_INIT_TYPE=sh but not with MM_INIT_TYPE=perl?
I didn't try MM_INIT_TYPE=perl.

MM_INIT_TYPE=sh is working for both of the 59 versions.

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

Post by Pablo » Thu Nov 06, 2008 6:22 am

As support for sh based init will be dropped at some point, it would be nice to track down any problems with the perl based init. Therefore, could you try it with MM_INIT_TYPE=perl?
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 Nov 08, 2008 9:17 pm

Just tried it on one of the frontends. Same "minimyth.conf not found" error with MM_INIT_TYPE=perl.

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

Post by Pablo » Sat Nov 08, 2008 9:34 pm

Can you telnet into the frontend after the error occurs?

If so, what are the contents of

Code: Select all

/etc/conf.d/dhcp
and what is the output of

Code: Select all

hostname
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 Dec 13, 2008 4:15 am

Sorry for the delay, Pablo.

I've given up on using the Via EPIA800 board - not enough time to troubleshoot what might be limited horsepower that's causing some other issues. However, I tried to look at this minimyth.conf not found error with my other frontends.

With another frontend, now running 0.21.0-61, I'm still getting the same error if I don't use MM_INIT_TYPE=sh.

When I get the error, I can telnet to the frontend, and here's the output you're looking for:

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

root@cfi:/etc/conf.d # hostname
cfi

The boot line and minimyth.conf have been carried over version to version. I believe things worked without MM_INIT_TYPE=sh before maybe 0.21.0-57?

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

Post by Pablo » Sat Dec 13, 2008 5:20 am

mx-5 wrote:Sorry for the delay, Pablo.

I've given up on using the Via EPIA800 board - not enough time to troubleshoot what might be limited horsepower that's causing some other issues. However, I tried to look at this minimyth.conf not found error with my other frontends.

With another frontend, now running 0.21.0-61, I'm still getting the same error if I don't use MM_INIT_TYPE=sh.

When I get the error, I can telnet to the frontend, and here's the output you're looking for:

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

root@cfi:/etc/conf.d # hostname
cfi

The boot line and minimyth.conf have been carried over version to version. I believe things worked without MM_INIT_TYPE=sh before maybe 0.21.0-57?
Until recently, MM_INIT_TYPE=sh was the default and before that MM_INIT_TYPE=sh was the only choice.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

Post Reply