Linux Boot Server - Revision history

Boiarino: /* Setting of the Linux server to be used for PXE and EFI boot of the VME controllers */

2026-03-15T16:59:13Z

Setting of the Linux server to be used for PXE and EFI boot of the VME controllers

← Older revision		Revision as of 12:59, 15 March 2026
Line 259:		Line 259:
	'''Configuring snapshot area'''		'''Configuring snapshot area'''

	The list of files and directories which suppose to be in snapshot area (which has RW permissions) should be set in config file ''/diskless/.../snapshot/files''. In particular, ''/et'' has to be added there, and also directory ''/diskless/.../root/et'' should be created.		The list of files and directories which suppose to be in snapshot area (which has RW permissions) should be set in config file ''/diskless/.../snapshot/files'' for CentOS5, or in config file ''/diskless/../root/etc/statetab'' for CentOS7. In particular, ''/et'' has to be added there, and also directory ''/diskless/.../root/et'' should be created.

	'''Reboot server, make sure everything is running as expected.'''		'''Reboot server, make sure everything is running as expected.'''

Boiarino: /* VTP CentOS boot */

2026-02-03T21:40:18Z

VTP CentOS boot

← Older revision		Revision as of 17:40, 3 February 2026
Line 8:		Line 8:
	== '''VTP CentOS boot''' ==		== '''VTP CentOS boot''' ==

	UBOOT (example for gem0vtp~~; '''NOTE: for copy-paste, lines with '$' and '{' and similar have to be in single quote brackets !'''~~):		UBOOT (example for gem0vtp):

	Zynq> printenv		Zynq> printenv

Boiarino: /* Configuring in chroot */

2026-02-03T21:39:04Z

Configuring in chroot

← Older revision		Revision as of 17:39, 3 February 2026
Line 265:		Line 265:
	== '''Configuring in chroot''' ==		== '''Configuring in chroot''' ==

	'''NOTE:~~'''~~ using ''chroot'' method will allow to run ''yum'', but ''systemctl'' commands will not work. Instead of using ''chroot'', you may boot coontroller with ''rw'' option instead of ''ro''. For VME boot, it can be done by changing ''grub.cnf'', while for VTP boot you have to stop boot proocess using serial connection, and then type ''run tftpboot_rw''.		'''NOTE: using ''chroot'' method will allow to run ''yum'', but ''systemctl'' commands will not work. Instead of using ''chroot'', you may boot coontroller with ''rw'' option instead of ''ro''. For VME boot, it can be done by changing ''grub.cnf'', while for VTP boot you have to stop boot proocess using serial connection, and then type ''run tftpboot_rw''.'''

	Since root area in VME controllers will be read-only, you cannot ssh to controllers as root and change anything there, only snapshot area can be modified. To make changes in root area, in particular to configure and run ''yum'', ''chroot' command should be used. Login to the boot server as root and do following:		Since root area in VME controllers will be read-only, you cannot ssh to controllers as root and change anything there, only snapshot area can be modified. To make changes in root area, in particular to configure and run ''yum'', ''chroot' command should be used. Login to the boot server as root and do following:

Boiarino: /* Configuring in chroot */

2026-02-03T21:37:51Z

Configuring in chroot

← Older revision		Revision as of 17:37, 3 February 2026
Line 265:		Line 265:
	== '''Configuring in chroot''' ==		== '''Configuring in chroot''' ==

	'''NOTE:''' using ''chroot'' method will allow to run ''yum'', but ''systemctl'' commands will not work. Instead of using ''chroot'', you may boot coontroller with ''rw'' option instead of ''ro''. For VME boot, it can be done by changing ''grub.cnf'', while for VTP boot you have to stop boot proocess using serial connection, and then type ''run ~~ftp...~~.		'''NOTE:''' using ''chroot'' method will allow to run ''yum'', but ''systemctl'' commands will not work. Instead of using ''chroot'', you may boot coontroller with ''rw'' option instead of ''ro''. For VME boot, it can be done by changing ''grub.cnf'', while for VTP boot you have to stop boot proocess using serial connection, and then type ''run tftpboot_rw''.

	Since root area in VME controllers will be read-only, you cannot ssh to controllers as root and change anything there, only snapshot area can be modified. To make changes in root area, in particular to configure and run ''yum'', ''chroot' command should be used. Login to the boot server as root and do following:		Since root area in VME controllers will be read-only, you cannot ssh to controllers as root and change anything there, only snapshot area can be modified. To make changes in root area, in particular to configure and run ''yum'', ''chroot' command should be used. Login to the boot server as root and do following:

Boiarino: /* Configuring in chroot */

2026-02-03T21:35:47Z

Configuring in chroot

← Older revision		Revision as of 17:35, 3 February 2026
Line 264:		Line 264:

	== '''Configuring in chroot''' ==		== '''Configuring in chroot''' ==

			'''NOTE:''' using ''chroot'' method will allow to run ''yum'', but ''systemctl'' commands will not work. Instead of using ''chroot'', you may boot coontroller with ''rw'' option instead of ''ro''. For VME boot, it can be done by changing ''grub.cnf'', while for VTP boot you have to stop boot proocess using serial connection, and then type ''run ftp....

	Since root area in VME controllers will be read-only, you cannot ssh to controllers as root and change anything there, only snapshot area can be modified. To make changes in root area, in particular to configure and run ''yum'', ''chroot' command should be used. Login to the boot server as root and do following:		Since root area in VME controllers will be read-only, you cannot ssh to controllers as root and change anything there, only snapshot area can be modified. To make changes in root area, in particular to configure and run ''yum'', ''chroot' command should be used. Login to the boot server as root and do following:

Boiarino: /* VTP CentOS boot */

2026-01-29T15:40:40Z

VTP CentOS boot

← Older revision		Revision as of 11:40, 29 January 2026
Line 20:		Line 20:
	devicetree_load_address=0x2000000		devicetree_load_address=0x2000000
	ethact=ethernet@e000b000		ethact=ethernet@e000b000
	ethaddr=ce:ba:f0:03:00:d1		ethaddr=ce:ba:f0:03:xx:xx
	extargs=setenv bootargs ${bootargs} console=ttyPS0,115200 ip=:::::eth0:dhcp uio_pdrv_genirq.of_id=my-uio rootwait cma=384MB		extargs=setenv bootargs ${bootargs} console=ttyPS0,115200 ip=:::::eth0:dhcp uio_pdrv_genirq.of_id=my-uio rootwait cma=384MB
	fdt_high=0x20000000		fdt_high=0x20000000

Boiarino: /* VTP CentOS boot */

2026-01-29T15:29:41Z

VTP CentOS boot

← Older revision		Revision as of 11:29, 29 January 2026
Line 55:		Line 55:
	setenv nfsip		setenv nfsip
	setenv nfsroot		setenv nfsroot
	~~ssetenv dboot~~		setenv sdboot
	setenv sdboot_no		setenv sdboot_no
	~~ssetenv etboot~~		setenv setboot
	setenv tftpboot_no		setenv tftpboot_no

Boiarino: /* VTP CentOS boot */

2026-01-29T15:29:08Z

VTP CentOS boot

← Older revision		Revision as of 11:29, 29 January 2026
Line 49:		Line 49:
	Copy-Paste following on uboot prompt to program above settings (do it by groups as shown, otherwise it may place some bull...):		Copy-Paste following on uboot prompt to program above settings (do it by groups as shown, otherwise it may place some bull...):

	~~setenv~~ setenv bootargs		setenv bootargs
	setenv gatewayip		setenv gatewayip
	setenv ipaddr		setenv ipaddr

Boiarino: /* VTP CentOS boot */

2026-01-29T15:28:19Z

VTP CentOS boot

← Older revision		Revision as of 11:28, 29 January 2026
Line 48:		Line 48:

	Copy-Paste following on uboot prompt to program above settings (do it by groups as shown, otherwise it may place some bull...):		Copy-Paste following on uboot prompt to program above settings (do it by groups as shown, otherwise it may place some bull...):

			setenv setenv bootargs
			setenv gatewayip
			setenv ipaddr
			setenv kernel_path
			setenv nfsip
			setenv nfsroot
			ssetenv dboot
			setenv sdboot_no
			ssetenv etboot
			setenv tftpboot_no

	setenv autoload 'no'		setenv autoload 'no'
Line 84:		Line 95:
	setenv tftppath 'linux-install/CentOS7-armv7-Diskless'		setenv tftppath 'linux-install/CentOS7-armv7-Diskless'

	~~setenv~~

	After that, customize following:		After that, customize following:

Boiarino: /* VTP CentOS boot */

2026-01-29T15:18:03Z

VTP CentOS boot

← Older revision		Revision as of 11:18, 29 January 2026
Line 47:		Line 47:
	Zynq>		Zynq>

	Copy-Paste following on uboot prompt to program above settings (do it ~~line-~~by~~-line~~, otherwise it may place some bull...):		Copy-Paste following on uboot prompt to program above settings (do it by groups as shown, otherwise it may place some bull...):

	setenv autoload 'no'		setenv autoload 'no'
Line 83:		Line 83:
	setenv tftpboot_rw 'dhcp && run tftp_boot_string nfsargs extargs bootrw load_kernel load_devicetree && bootm ${kernel_load_address} - ${devicetree_load_address}'		setenv tftpboot_rw 'dhcp && run tftp_boot_string nfsargs extargs bootrw load_kernel load_devicetree && bootm ${kernel_load_address} - ${devicetree_load_address}'
	setenv tftppath 'linux-install/CentOS7-armv7-Diskless'		setenv tftppath 'linux-install/CentOS7-armv7-Diskless'

			setenv

	After that, customize following:		After that, customize following: