IPXE - Revision history

Leo: /* Example scripts */

2021-12-10T06:34:43Z

Example scripts

← Older revision		Revision as of 06:34, 10 December 2021
Line 161:		Line 161:
	This may be useful when your network has no DHCP server.		This may be useful when your network has no DHCP server.
	\|{{Highlight		\|{{Highlight
	\| code = set net0/ip 100.64.1.127		\| code = #!ipxe
			set net0/ip 100.64.1.127
	set net0/netmask 255.255.255.0		set net0/netmask 255.255.255.0
	set net0/gateway 100.64.1.1		set net0/gateway 100.64.1.1

Leo at 05:28, 8 December 2021

2021-12-08T05:28:36Z

← Older revision		Revision as of 05:28, 8 December 2021
Line 129:		Line 129:
	*http://ipxe.org/cfg		*http://ipxe.org/cfg

	===Example ~~Scripts~~===		===Example scripts===
	{{highlight\|lang=text\|code=		{\| class="wikitable"
			!Description
			!Script
			\|-
			\|Obtain an IP from DHCP and PXE boot.
			The file will be obtained via tftp from the next-server as configured by the DHCP server.
			\|{{highlight\|lang=text\|code=
	#!ipxe		#!ipxe

Line 141:		Line 147:

	}}		}}
			\|-
			\|Obtain an IP from DHCP and override the next-server.
			Download and run the main.ipxe script. If this fails, enter a shell.
			\|{{Highlight
			\| code = #!ipxe
			dhcp
			set next-server 100.64.1.119
			chain http://${next-server}/main.ipxe {{!}}{{!}} shell
			\| lang = text
			}}
			\|-
			\|Set a static IP address and boot netboot.xyz.
			This may be useful when your network has no DHCP server.
			\|{{Highlight
			\| code = set net0/ip 100.64.1.127
			set net0/netmask 255.255.255.0
			set net0/gateway 100.64.1.1
			set dns 8.8.8.8
			ifopen net0
			\| lang = text
			}}
			\|}


Line 281:		Line 309:

	===Initramfs unpacking failed: junk in compressed archive===		===Initramfs unpacking failed: junk in compressed archive===
	When attempting to boot Linux with iPXE using a custom netboot.xyz menu, I constantly ran into an issue where the kernel isn't able to extract the loaded initrd image. ~~As a result,~~ the kernel ~~would panic with an error <code>VFS: Unable to mount roott fs on unknown-block(0,0)</code>~~. ~~Inspecting the~~ kernel ~~logs, the~~ boot messages ~~will~~ show:{{Highlight		When attempting to boot Linux with iPXE using a custom netboot.xyz menu, I constantly ran into an issue where the kernel isn't able to extract the loaded initrd image. iPXE was able to boot the same kernel and initrd directly when I bypassed netboot.xyz. The kernel boot messages do show:{{Highlight
	\|code=Unpacking initramfs...		\|code=Unpacking initramfs...
	Initramfs unpacking failed: junk in compressed archive		Initramfs unpacking failed: junk in compressed archive
	Freeing initrd memory: 46288K\|lang=text}}If you~~'re certain that the initrd image is valid, your likely culprit is forgetting~~ to free the loaded images~~/iPXE scripts~~ before ~~starting~~ the kernel. ~~Every time you chain an~~ iPXE ~~script, it gets loaded in memory. You need to call <code>imgfree</code> to clear this before loading initrd. Otherwise, the kernel will not be able to recognize~~ the initrd ~~header and bail out~~.		Freeing initrd memory: 46288K\|lang=text}}It turns out that you need to free the loaded iPXE images before loading the kernel and initrd. The loaded iPXE scripts were interfering with the initrd payload. The fix here is to call <code>imgfree</code> before loading the kernel and initrd.
			==See Also==
	The fix here is to call <code>imgfree</code> before loading the kernel and initrd.
	===See Also===

	*http://ipxe.org/howto/sccm		*http://ipxe.org/howto/sccm

Leo: /* Initramfs unpacking failed: junk in compressed archive */

2021-12-08T00:43:14Z

Initramfs unpacking failed: junk in compressed archive

← Older revision		Revision as of 00:43, 8 December 2021
Line 250:		Line 250:
	===Troubleshooting===		===Troubleshooting===

	==== A winpeshl.ini file is present, but no commands were successfully launched ====		====A winpeshl.ini file is present, but no commands were successfully launched====
	Issue: The image doesn't run the vbscript on start up. Instead, a command prompt opens with the following message:		Issue: The image doesn't run the vbscript on start up. Instead, a command prompt opens with the following message:
	A winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name. Please consult the documentation for more information.		A winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name. Please consult the documentation for more information.
Line 256:		Line 256:
	Solution: I messed up the ini file. Copy it as it is shown above. I did not copy the interpreter which was the first argument.		Solution: I messed up the ini file. Copy it as it is shown above. I did not copy the interpreter which was the first argument.

	==== unrecognized block type 0. bad MZ magic d5e9 ====		====unrecognized block type 0. bad MZ magic d5e9====
	Issue: When using {{code\|imagex}}from {{code\|wimlib}}, I got weird boot errors including:		Issue: When using {{code\|imagex}}from {{code\|wimlib}}, I got weird boot errors including:
	unrecognized block type 0		unrecognized block type 0
Line 266:		Line 266:
	==Troubleshooting==		==Troubleshooting==

	=== Unsupported devices ===		===Unsupported devices===
	The following servers and workstations do not work with iPXE.		The following servers and workstations do not work with iPXE.

Line 281:		Line 281:

	===Initramfs unpacking failed: junk in compressed archive===		===Initramfs unpacking failed: junk in compressed archive===
	When attempting to boot Linux with iPXE using a custom netboot.xyz menu, I constantly ran into an issue where the kernel isn't able to extract the loaded initrd image. ~~iPXE was able to boot~~ the ~~same~~ kernel ~~and initrd directly when I bypassed netboot~~.~~xyz. The~~ kernel boot messages do show:{{Highlight		When attempting to boot Linux with iPXE using a custom netboot.xyz menu, I constantly ran into an issue where the kernel isn't able to extract the loaded initrd image. As a result, the kernel would panic with an error <code>VFS: Unable to mount roott fs on unknown-block(0,0)</code>. Inspecting the kernel logs, the boot messages will show:{{Highlight
	\|code=Unpacking initramfs...		\|code=Unpacking initramfs...
	Initramfs unpacking failed: junk in compressed archive		Initramfs unpacking failed: junk in compressed archive
	Freeing initrd memory: 46288K\|lang=text}}~~It turns out~~ that ~~you need~~ to free the loaded iPXE ~~images~~ before ~~loading~~ the kernel ~~and~~ initrd. ~~The loaded iPXE scripts were interfering with~~ the initrd ~~payload~~. The fix here is to call <code>imgfree</code> before loading the kernel and initrd.		Freeing initrd memory: 46288K\|lang=text}}If you're certain that the initrd image is valid, your likely culprit is forgetting to free the loaded images/iPXE scripts before starting the kernel. Every time you chain an iPXE script, it gets loaded in memory. You need to call <code>imgfree</code> to clear this before loading initrd. Otherwise, the kernel will not be able to recognize the initrd header and bail out.

			The fix here is to call <code>imgfree</code> before loading the kernel and initrd.
	===See Also===		===See Also===

Leo at 23:42, 7 December 2021

2021-12-07T23:42:03Z

@@ Line 4: / Line 4: @@
 You can build iPXE from source with a functional C compiler in a standard development environment. Alternatively, you can use an automated web application called ROM-o-matic to automatically generate the compiled iPXE files based on your desired build options.
-=== Using ROM-o-matic ===
+===Using ROM-o-matic===
 The easiest way to get ROM-o-matic working is to use the Docker image from this project: https://github.com/xbgmsharp/ipxe-buildweb/. Under the hood, the build environment is based on Ubuntu. I had some issues with the web interface throwing a 500 error but it seems to work after retrying when that happens.
 {{Highlight
@@ Line 248: / Line 248: @@
 }}
-===Unsupported Devices===
+===Troubleshooting===
 The following servers and workstations do not work with iPXE.
 {| class="wikitable"
@@ Line 262: / Line 280: @@
 |}
-===Troubleshooting===
+===Initramfs unpacking failed: junk in compressed archive===
-Issue: The image doesn't run the vbscript on start up. Instead, a command prompt opens with the following message:
+When attempting to boot Linux with iPXE using a custom netboot.xyz menu, I constantly ran into an issue where the kernel isn't able to extract the loaded initrd image. iPXE was able to boot the same kernel and initrd directly when I bypassed netboot.xyz. The kernel boot messages do show:{{Highlight
- A winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name. Please consult the documentation for more information.
+|code=Unpacking initramfs...
+Initramfs unpacking failed: junk in compressed archive
-Solution: I messed up the ini file. Copy it as it is shown above. I did not copy the interpreter which was the first argument.
+Freeing initrd memory: 46288K|lang=text}}It turns out that you need to free the loaded iPXE images before loading the kernel and initrd. The loaded iPXE scripts were interfering with the initrd payload. The fix here is to call <code>imgfree</code> before loading the kernel and initrd.
 ===See Also===
@@ Line 281: / Line 290: @@
 *http://www.thesccm.com/ipxe-sccm/
-==Netboot.xyz==
+{{Navbox Linux}}
 [[Category:Linux]]
 [[Category:Networking]]

Leo at 23:37, 7 December 2021

2021-12-07T23:37:28Z

← Older revision		Revision as of 23:37, 7 December 2021
Line 1:		Line 1:
	iPXE is a PXE boot firmware which can be used to PXE boot systems that may not have support. iPXE supersedes the older and no longer actively maintained gPXE boot firmware.		iPXE is a PXE boot firmware which can be used to PXE boot systems that may not have support. iPXE supersedes the older and no longer actively maintained gPXE boot firmware.

	==~~Building~~==		==Compiling iPXE==
	You can build the iPXE image from source ~~pretty easily~~ with the ~~added benefit of being able~~ to ~~customize~~ the ~~image with custom embedded~~ iPXE ~~scripts (see scripting section below)~~.		You can build iPXE from source with a functional C compiler in a standard development environment. Alternatively, you can use an automated web application called ROM-o-matic to automatically generate the compiled iPXE files based on your desired build options.

			=== Using ROM-o-matic ===
			The easiest way to get ROM-o-matic working is to use the Docker image from this project: https://github.com/xbgmsharp/ipxe-buildweb/. Under the hood, the build environment is based on Ubuntu. I had some issues with the web interface throwing a 500 error but it seems to work after retrying when that happens.
			{{Highlight
			\| code = # docker pull xbgmsharp/ipxe-buildweb
			# docker run -d \
			--publish 8080:80 \
			--publish 22:22 \
			--name ipxe-buildweb \
			xbgmsharp/ipxe-buildweb

			# Navigate to docker-host:8080
			\| lang = terminal
			}}

			===Building from source===
			On a system with the C development packages installed, you can use the project's Make file to generate the desired iPXE file.

	~~===Example===~~
	The following script will build iPXE with an embedded script which automatically boots from a HTTP resource.		The following script will build iPXE with an embedded script which automatically boots from a HTTP resource.

Line 270:		Line 286:
	This project makes it very easy to boot into a wide range of Linux or BSD based distributions either as a live image or as an installers. It also comes with a good selection of utilities like memtest.		This project makes it very easy to boot into a wide range of Linux or BSD based distributions either as a live image or as an installers. It also comes with a good selection of utilities like memtest.

	=== Customization ===		===Customization===
	You may also create a custom netboot.xyz repository with customization.		You may also create a custom netboot.xyz repository with customization.

Line 286:		Line 302:
	}}		}}

	== Troubleshooting ==		==Troubleshooting==

	=== Initramfs unpacking failed: junk in compressed archive ===		===Initramfs unpacking failed: junk in compressed archive===
	When attempting to boot Linux with iPXE using a custom netboot.xyz menu, I constantly ran into an issue where the kernel isn't able to extract the loaded initrd image. iPXE was able to boot the same kernel and initrd directly when I bypassed netboot.xyz. The kernel boot messages do show:		When attempting to boot Linux with iPXE using a custom netboot.xyz menu, I constantly ran into an issue where the kernel isn't able to extract the loaded initrd image. iPXE was able to boot the same kernel and initrd directly when I bypassed netboot.xyz. The kernel boot messages do show:
	{{Highlight		{{Highlight

Leo at 04:51, 9 November 2021

2021-11-09T04:51:58Z

Show changes

Leo at 22:22, 14 June 2020

2020-06-14T22:22:22Z

← Older revision		Revision as of 22:22, 14 June 2020
Line 266:		Line 266:
	* https://netboot.xyz/		* https://netboot.xyz/
	* https://github.com/antonym/netboot.xyz		* https://github.com/antonym/netboot.xyz


	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
			[[Category:Networking]]

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T06:20:41Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

← Older revision		Revision as of 06:20, 1 September 2019
Line 268:		Line 268:


	[[Category:Linux]]~~{{Navbox Linux}}~~		{{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

2019-09-01T05:11:10Z

Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

← Older revision		Revision as of 05:11, 1 September 2019
Line 268:		Line 268:


	[[Category:Linux]]~~{{Navbox Linux}}~~{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

2019-09-01T05:08:06Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:08, 1 September 2019
Line 268:		Line 268:


	[[Category:Linux]]{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}{{Navbox Linux}}