Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
troubleshooting [2006/07/12 00:53] stockholm created |
troubleshooting [2008/08/08 05:11] (current) verkout |
||
---|---|---|---|
Line 7: | Line 7: | ||
<file>next-server 192.168.0.1;</file> | <file>next-server 192.168.0.1;</file> | ||
in your ''dhcpd.conf'', somewhere in the global section near the top, will do the trick. | in your ''dhcpd.conf'', somewhere in the global section near the top, will do the trick. | ||
+ | |||
+ | ==== "Error 0x..." ==== | ||
+ | **Problem:**\\ gPXE is failing with an error code that is not human-readable. | ||
+ | |||
+ | **Solution:**\\ Error codes are generally internal errors. Many user errors are displayed as human-readable messages. Error codes allow the developers to identify the location in gPXE where the error is coming from. You can use the web-based [[http://etherboot.org/share/stefanha/errcode.php|gPXE Error Code Lookup]] or ask ''gpxebot'' for help on the [[contact|IRC channel]]. Fully investigating an error code will require the gPXE source code. Start by looking at ''src/include/errno.h''. Developers are often available for help on the [[contact|IRC channel]]! | ||
+ | |||
+ | ==== "Etherboot with Linux 2.6 hangs/does not boot" ==== | ||
+ | |||
+ | **Problem:**\\ You have created a network-bootable-image (NBI) of a Linux 2.6 (or higher) kernel with mknbi-* and want to boot it using Etherboot but Etherboot stops after loading the image and either hangs or enters an infinite reboot-cycle. | ||
+ | |||
+ | **Solution:**\\ Use wraplinux to make the NBI in stead of mknbi-*. [[http://www.kernel.org/pub/linux/utils/boot/wraplinux|Wraplinux]] can be downloaded from here. Preferably, if you can, you might want to upgrade from using etherboot to using gPXE as netbootloader. |